Hi everyone,
I just got my bramble today. And yes, the first thing I did, was unlocking the bootloader and rooting it.
Here I tell you how I did it.
You need a ADB/Fastboot suite installed and this rooted kernel.
Section 1: Unlocking your Bootloader Unlocking your Bootloader will erase all your data - so best case is a brandnew and clean bramble...:
1. Go to settings - "About phone" and tip 6 times on "Build number" until you see "congratulations, you are a developer"
2. Go to settings - "System", tip on "Advanced" and then on "Developer options". Now you can see "OEM unlocking". Enable it (yes it warns you about security and stuff... It´s your choice - I did it ).
3. Install Adb and Fastboot suite and scroll to the adb-folder inside your windows explorer and when you are there, copy the rooted boot.img to your adb-folder (you need that for section 2).
4. Right click + shift on the white background of your adb-folder "open power shell window here"
5. Reboot your bramble holding vol- and you will enter the fastboot screen. Connect your bramble to your pc and type in your power shell window the following code:
Code:
./fastboot flashing unlock
and hit enter
6. Your bramble will warn you that unlocking your bootloader is insecure! And one really important thing again: This will format all your data
7. Use the vol-/vol+ keys to accept and violla, you unlocked your Bootloader!
Section 2: flashing the patched boot.img
1. Luckily you already copied the rooted boot.img to your adb folder and you are still in your power shell window. That gives you everything for 2.
2. type the following in your power shell window:
Code:
./fastboot flash boot boot.img
3. hit enter and
4. reboot to system (yes it has to be setup again since your data got wipede) and install Magisk manager after setting up your system
Congrats, your system is now rooted with Magisk!
@TNSMANI, sorry, unfortunately I put this into the wrong forum. It hast to be unter "Guides news and discussion". Would you be so kind to put it from here to there? Thx.
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay
{
"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"
}
bkdodger said:
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay View attachment 5138473
Click to expand...
Click to collapse
He's got a case of the "didn't enable show file extensions" in windows. I downloaded my own system image and then patched the boot.img with magisk manager. I hate for you to have to piece it together, but I got my phone yesterday and worked through these things. Check it out here:
https://forum.xda-developers.com/pixel-4a-5g/help/magisk-boot-img-patching-flashing-t4191955
bkdodger said:
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay View attachment 5138473
Click to expand...
Click to collapse
Funny, maybe Gdrive removes double endings... I'll edit my post, thx!
Hey there,
after following your instructions Magisk Manager does not seem to detect Magisk (see Attachment). Can anyone help me figure out what am i missing?
Here's my consoleoutput:
Code:
$fastboot flashing unlock
OKAY [ 0.290s]
Finished. Total time: 0.291s
-------------------------------
$fastboot flash boot ./boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.850s]
Writing 'boot_b' OKAY [ 0.310s]
Finished. Total time: 3.520s
-------------------------------
Also: will there be a way to hide the 'device-is-unlocked-warning' on boot?
Thank you!
[Jan] said:
Hey there,
after following your instructions Magisk Manager does not seem to detect Magisk (see Attachment). Can anyone help me figure out what am i missing?
Here's my consoleoutput:
Code:
$fastboot flashing unlock
OKAY [ 0.290s]
Finished. Total time: 0.291s
-------------------------------
$fastboot flash boot ./boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.850s]
Writing 'boot_b' OKAY [ 0.310s]
Finished. Total time: 3.520s
-------------------------------
Also: will there be a way to hide the 'device-is-unlocked-warning' on boot?
Thank you!
Click to expand...
Click to collapse
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
About BL-Warning. I have the same... And I dont´t know how to remove it. We would need to manipulate the bl, what I would not do...! Just ignore it!
Voodoojonny said:
;83961089']
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
Click to expand...
Click to collapse
For me, it also didn't work with your pre-patched boot.img (also on latest November update). Had to download the factory image and patch it myself to make it work.
Voodoojonny said:
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
About BL-Warning. I have the same... And I dont´t know how to remove it. We would need to manipulate the bl, what I would not do...! Just ignore it!
Click to expand...
Click to collapse
Hm.. actually been on the latest available build. Can you confirm this boot.img is working for build-id *.003.B1? (Also appended file-checksum, even though I doubt the file is damaged).
Code:
$shasum -a 256 ./boot.img
50fc81f5f59def3f366fcddd7976cbcbdc406172685c3e8a6cc24968d55c5964 ./boot.img
-------------------------------
$adb shell getprop | grep "ro.build.date\|ro.build.date\|ro.build.id\|ro.build.tags\|ro.build.product\|ro.build.version"
[ro.build.date]: [Tue Oct 6 11:12:31 UTC 2020]
[ro.build.date.utc]: [1601982751]
[ro.build.id]: [RD1A.201105.003.B1]
[ro.build.product]: [bramble]
[ro.build.tags]: [release-keys]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [6886588]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2020-11-05]
-------------------------------
Simma said:
For me, it also didn't work with your pre-patched boot.img (also on latest November update). Had to download the factory image and patch it myself to make it work.
Click to expand...
Click to collapse
Thanks, will try this as well!
UPDATE: Got it successfully rooted by patching the factory image.
[Jan] said:
Hm.. actually been on the latest available build. Can you confirm this boot.img is working for build-id *.003.B1? (Also appended file-checksum, even though I doubt the file is damaged).
Code:
$shasum -a 256 ./boot.img
50fc81f5f59def3f366fcddd7976cbcbdc406172685c3e8a6cc24968d55c5964 ./boot.img
-------------------------------
$adb shell getprop | grep "ro.build.date\|ro.build.date\|ro.build.id\|ro.build.tags\|ro.build.product\|ro.build.version"
[ro.build.date]: [Tue Oct 6 11:12:31 UTC 2020]
[ro.build.date.utc]: [1601982751]
[ro.build.id]: [RD1A.201105.003.B1]
[ro.build.product]: [bramble]
[ro.build.tags]: [release-keys]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [6886588]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2020-11-05]
-------------------------------
Thanks, will try this as well!
UPDATE: Got it successfully rooted by patching the factory image.
Click to expand...
Click to collapse
I don't know what I'm doing wrong I can't patch it .. unsuccessful..ughhh
bkdodger said:
I don't know what I'm doing wrong I can't patch it .. unsuccessful..ughhh
Click to expand...
Click to collapse
My advice would be:
- ensure you got the factory image from developer.google.com corresponding to your buildnumber
- ensure you are using canary magisk manager (which is the only version as of today supporting redfin and bramble)
[Jan] said:
My advice would be:
- ensure you got the factory image from developer.google.com corresponding to your buildnumber
- ensure you are using canary magisk manager (which is the only version as of today supporting redfin and bramble)
Click to expand...
Click to collapse
I check the build is latest ...my Magisk is below
bkdodger said:
I check the build is latest ...my Magisk is below View attachment 5138961
Click to expand...
Click to collapse
Magisk version fits.
What about the boot.img file? It should be originated from path '*/bramble-{buildnumber}-factory-{sha}.zip/bramble-{buildnumber}/image-bramble-{buildnumber}.zip/boot.img'.
[Jan] said:
Magisk version fits.
What about the boot.img file? It should be originated from path '*/bramble-{buildnumber}-factory-{sha}.zip/bramble-{buildnumber}/image-bramble-{buildnumber}.zip/boot.img'.
Click to expand...
Click to collapse
Oh maybe I'm doing this part wrong ? I moved over the top file
bkdodger said:
Oh maybe I'm doing this part wrong ? I moved over the top file
Click to expand...
Click to collapse
It's the boot.img inside the next zip (image-bramble...)
Simma said:
It's the boot.img inside the next zip (image-bramble...)
Click to expand...
Click to collapse
Thanks for reply ..it was in there and I finally got it rooted ...I really don't know why it was not working but the third time was the charm ...[emoji16]
I'm trying to install Magisk, but I need a custom recovery. I can't figure out how to install one. TWRP app keeps force-closing when I try to install it, and there's no Pixel 4a 5G listed in devices in the TWRP website. I also can't find anything from ClockworkMod.
Hey, there ist no custom recovery available yet, becouse this phone is brandnew! There will be TWRP and other recoveries in the future, until then, we need to be creative. One way is extracting and patching the boot.img and reflash it via fastboot. How to do that is described in OP!
I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.
WhiteAsIce said:
I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.
Click to expand...
Click to collapse
Have you tried hiding the apps in Magisk? Do you want safetynet for a specific app that won't launch/complains about being rooted? Try MagiskHide in Magisk Manager if you haven't. Exclude those apps to hide root from them.
Related
{
"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"
}
Team Win Recovery Project
for Lenovo Vibe Z2 Pro
The only true recovery built straight from 8.1 source code.
Key features:
Based on android-8.1 TWRP sources and LineageOS 15.1
"eng" build (no adb authorization required, ro.secure=0)
Full /data HW decryption support (PIN/password/pattern)
Full adb support - sideload, etc...
Full SELinux support
OTA updates support
MTP & USB-OTG support
F2FS support
List of partitions:
System - /system
Data - /data
Persist - /persist
Preload - /preload
Firmware - /modem
Bootloader - /aboot
Boot (kernel) - /boot
Recovery - /recovery
Splash - /splash
Misc - /misc
FS Golden - /fsg
ESF (NV Data) - /modemst1 & /modemst2
MRD Data - /mrd
How to enter recovery?
Hold the POWER button and BOTH VOLUME buttons simultaneously until you see the TWRP logo.
Downloads
TWRP_3.2.1-0_K920.img (2018/02/24) [15.5 MB] | Google Drive Mirror
TWRP_3.1.1-0_K920.img (2017/10/15) [12.7 MB]
TWRP_3.1.0-0_K920.img (2017/03/21) [12.7 MB]
TWRP_3.0.3-0_K920.img (2017/01/24) [14.7 MB]
TWRP_3.0.2-2_K920.img (2016/11/26) [13.3 MB]
TWRP_3.0.2-1_K920.img (2016/10/08) [10.7 MB]
TWRP_3.0.2-0_K920.img (2016/09/04) [10.7 MB]
I am not responsible for anything that happens to your phone or computer. You have to understand what you are doing.
Sources
Manifest: https://github.com/K920/android/tree/master/twrp
Device tree: https://github.com/K920/android_device_lenovo_kingdom/tree/twrp
Dev Info
To build with 15.1 sources requires:
export ALLOW_MISSING_DEPENDENCIES=true
repopick -t oreo-lineage-build (omnirom)
Manual removal of "vendor" under out/.../recovery/root/
Screenshots
FAQ:
How do I flash this TWRP .img? (with PC)
If you haven't already, install ADB+Fastboot with drivers (I recommend this installer)
Enable ADB debugging on your phone (in Settings->Developer Options)
After connecting the phone to the PC, pop up may appear, tick Always allow from this computer and click OK
Extract downloaded recovery zip and copy .img file to C:/adb
Now open cmd line (press Start+R, type "cmd", press OK) and go to C:/adb (type "cd C:/adb" and hit Enter)
Reboot into bootloader (fastboot mode) (type "adb reboot-bootloader")
Your phone should now reboot into the bootloader (Little green android logo in the middle of the screen)
Flash the recovery.img (type "fastboot flash recovery recovery.img")
Finally, reboot!
Done!
Do I have to have unlocked bootloader?
Yes!Whenever I try to flash something, I'm getting ERROR 7. Help!
Reboot->Recovery, also make sure that your flashable zip isn't corrupted.I have formatted encrypted /data partition, now I can't mount it.
Reboot->RecoveryWrong password?!?
Reboot->RecoveryDoes this work on CN variants?
Yes!I can't flash my favorite ROM/.zip/we, this is not a kingdom_row device! (3.0.3+)
Yes, that's right. For the sake of using the same device tree as official Lineage OS, we're using common 'kingdom' device name. Many flashable .zips include safety mechanism to prevent them being flashed on unsupported device. If this is the case, ask the creator of your .zip to assert also on 'kingdom' device name. (e.g. by using TARGET_OTA_ASSERT_DEVICE), or edit the updater-script by yourself.
Electry said:
reserved
Click to expand...
Click to collapse
Installation error - android\google\update-binary
CM13 (03092016)
Alexander_Gostev said:
Installation error - android\google\update-binary
CM13 (03092016)
Click to expand...
Click to collapse
It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).
Electry said:
It is not a flashable zip... If you want to install this TWRP, you'll have to extract the .zip and flash the .img through fastboot (fastboot flash recovery recovery.img).
Click to expand...
Click to collapse
Thanks, I understood and flashed through recoveri.
How do the two systems?
Updated to 3.0.2-1
/persist is now mounted RW
thx, good work
Hello
After last update of CM 14.1 via OTA (20161104) I cannot re-flash TWRP when I trying to do that via TWRP i see error http://i.imgur.com/tJ4IZXf.png. Is it a problem with permissions or with something else ? Thx
yes it's not working. you can use "fastboot flash recovery recovery.img"
Sent from my K920 using Tapatalk
Hello friends,
I try to flash it but got this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (17332 KB)...
OKAY [ 0.547s]
writing 'recovery'...
FAILED (remote: invalid data)
finished. total time: 0.758s
My phone is lenovo K920
Android version 5.0.2
Anyone can help me?
Thank you.
Do first unlock bootloader
Wysłane z mojego K920 przy użyciu Tapatalka
Electry said:
Updated to 3.0.2-1
/persist is now mounted RW
Click to expand...
Click to collapse
https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
не рабочая ссылка!
broken links!
Alexander_Gostev said:
https://mega.nz/#!YIRiFZra!a3fVWBylwMDRghq3Aa15Q3R4WrSIFFMZLvHQa_HMLn4
?? ??????? ??????!
broken links!
Click to expand...
Click to collapse
wtf? they're not broken
Electry said:
wtf? they're not broken
Click to expand...
Click to collapse
link does not boot at all, you can move?
ссылка не грузиться вобще, можете перезалить?
Hi all,
As I got instruction few posts before I tried to copy last version of twrp via ADB but it does not work. Installed TWRP 3.0.2-1 ,
When i try to push it via ADB I see an error -------------------------------------Ä»αÑñѽѡ¿Ñ ΓѽÑΣ«¡á
List of devices attached
89355fd4 recovery
-------------------------------------ÅÑαѺáúαπº¬á ó bootloader
-------------------------------------çá»π߬ root-shell
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.458s]
booting...
OKAY [ 0.019s]
finished. total time: 0.477s
-------------------------------------Åα«Φ¿ó¬á recovery
failed to copy 'fw\twrp.img' to '/sdcard/twrp.img': Read-only file system
CANNOT LINK EXECUTABLE "/system/bin/sh": library "libNimsWrap.so" not found
-------------------------------------ÅÑαѺáúαπº¬á ó recovery
-------------------------------------çáóÑαΦÑ¡«
-------------------------------------ì᪼¿ΓÑ ½εíπε ¬½áó¿Φπ.
internal mem is Read only mode ????
ROOT for ADB , USB enabled.
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx
seekator said:
Hi all,
...
As I mentioned before flashing via TWRP dow not work too.
Any suggestions?
Thx
Click to expand...
Click to collapse
no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.
ps: I'm uploading 3.0.3-0 with F2FS support.
Electry possible to make re-initialization of the system partition? To release the space not used by the system. She's stock was designed for Roma. A cm (lineage) is much easier.
And what topics can be done f2fs?
Отправлено с моего K920 (ROW) через Tapatalk
Sorry my google English)
Electry said:
no, I won't provide support for any 3rd party batch scripts (or w/e is that log from). If you can't figure out how to flash single .img, you shouldn't be messing with this stuff.
ps: I'm uploading 3.0.3-0 with F2FS support.
Click to expand...
Click to collapse
OK Thanks . When you mentioned about unsupported script I have taken a look on it and .... Yep I used wrong zip with adb . When I tried right one I had another output . Strange, I had TWRP, ROOT but locked bootloader.
Then QPST to version 143 ,update to lollipop, bootloader , root, yours TWRP and I have last recovery, LineageOS :good:
UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .
seekator said:
UPDATE
Something wrong is with last TWRP 3.0.3-0. Because I started fresh installation lastest TWRP and CM I had to install everything from the scratch and ..... I was not able to install GAPPS, error 64 and something about architecture, yep I was trying to install 32 bit gapps so it was ok, when I pressed reboot it came back to TWRP, reboot to system the same, Bootloader too. When I switched back to previous version TWRP_3.0.2-2_K920.img I was able to install gapps and reboot menu was operating as it should.
On TWRP_3.0.2-2_K920.img is ok .
Click to expand...
Click to collapse
That's an issue with gapps. TWRP 3.0.3-0 uses toybox instead of busybox and the 'unzip' executable/link is missing. Check my 2nd post (FAQ) there is a way around it, but you can just use 3.0.2-2 if that's easier.
EDIT: I've rebuild 3.0.3-0 with busybox included, so this shouldn't be an issue anymore.
whats new in TWRP 3.2.0-0? when the official release of twrp for our k920?
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed)
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
{
"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"
}
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Code:
fastboot flash splash splash.img
Chrono Leggionaire said:
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed)
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Code:
fastboot flash splash splash.img
Click to expand...
Click to collapse
WORKS !! THANKS search0123 :fingers-crossed: :good:
anyone have cool splash img? do share ty
Dark images included work well with paranoid boot animation, thanks! No more blinding mornings...
Good to know... Custom splash does not affect OTA to 10.0.7.0.
mi logo
I don't have a Windows but python should be cross-platform...
Because I have a Mac, I had to run xcode-select --install to get zlib in place for Pillow.
I had to pip2.7 install Pillow to get the PIL library that the script wanted.
Then I could run python2.7 splash_gen.py and it produced a splash.img for me.
no more full screen unlocked bootloader warning. thanks
I conpreased the image file as a zip when I go to twrp which should I select boot or something else
rob420p said:
I conpreased the image file as a zip when I go to twrp which should I select boot or something else
Click to expand...
Click to collapse
This is a bootloader splash. Flash from fastboot.
fastboot flash splash splash.img
a1291762 said:
This is a bootloader splash. Flash from fastboot.
fastboot flash splash splash.img
Click to expand...
Click to collapse
I understand that but I can't for the life of me get this to work on fastboot idk what I'm doing wrong I know how to use fast boot so I'm loat
rob420p said:
I understand that but I can't for the life of me get this to work on fastboot idk what I'm doing wrong I know how to use fast boot so I'm loat
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
What errors do you get from fastboot?
a1291762 said:
Do you have an unlocked bootloader?
What errors do you get from fastboot?
Click to expand...
Click to collapse
Unlocked custom rom when I type the commands its always saying no file
rob420p said:
Unlocked custom rom when I type the commands its always saying no file
Click to expand...
Click to collapse
So you don't have a splash.img then?
a1291762 said:
So you don't have a splash.img then?
Click to expand...
Click to collapse
I've downloaded them from this pafe
rob420p said:
I've downloaded them from this pafe
Click to expand...
Click to collapse
Is your phone in fastboot mode? Showing the rabbit with the blowtorch?
Do you have the fastboot program on your computer?
a1291762 said:
Is your phone in fastboot mode? Showing the rabbit with the blowtorch?
Do you have the fastboot program on your computer?
Click to expand...
Click to collapse
Yes I know all that.I got that
Ok, let's try something else. Here's what I see when I flash.
Code:
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ adb reboot bootloader
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot flash splash splash_stock_dark.img
Sending 'splash' (1460 KB) OKAY [ 0.080s]
Writing 'splash' OKAY [ 0.032s]
Finished. Total time: 0.159s
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
Can you please include what you see when you flash the splash image?
Chrono Leggionaire said:
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Click to expand...
Click to collapse
Hi great Dev can you explain me how to remove the " unlocked bootloader warn" whit your app? Sorry for my English thanks for your time and your work
rob420p said:
I've downloaded them from this pafe
Click to expand...
Click to collapse
taht is the correct comman as he said
fastboot flash splash splash.img
CLOSED PER OP REQUEST
{
"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"
}
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2020-01-08
first
Wahoo. Thanks for this.
Oooo nice ?
new build is up
fingerprint should be fine now
10.0x whatever is the latest release blobs.
other little stuff
and whats below:
darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-19
Click to expand...
Click to collapse
download error!
Thx. How to root??
Just_Pisces said:
Thx. How to root??
Click to expand...
Click to collapse
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.
p70shooter said:
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.
Click to expand...
Click to collapse
Thx. Just forgot to check“Preserve AVB 2.0/dm-verity”. Now Successfully
Hello to all ..... Unfortunately, the download link is not up to date or the destination host is not available ... could someone please upload the ZIP or create a new link to download? many thanks
its back online
darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-22
Click to expand...
Click to collapse
Hi for some reason it didn't work for me
Wipe successful could not partition
Error message Failed remote not discoverable when flashing images.
I'm paraphrasing I accidentally closed the command prompt after rebooting.
It clearly says its only for people that can read and follow instructions.
Hm, I can't write system neither to 'a' or 'b' slot ... boot image is looking ok.
What I am doing wrong?
I am on latest 10.0.4.
Code:
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.309s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.651s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.412s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.039s]
Finished. Total time: 0.047s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.317s]
Writing 'boot_b' OKAY [ 0.410s]
Finished. Total time: 2.753s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.450s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
EDIT:
Not sure if it helps but this is what I get from "fastboot getvar all"
Code:
(bootloader) has-slot:system:no
Also tried it from 10.0.3 base to check if it's bootloader issue with no change.
EDIT2:
Oh well, I am an idiot who can't read instructions properly and didn't realize there are two fastboots
You need to reboot to fastbootd from fastboot !!
I will leave this here for people like me.
@darkobas thanks for the amazing rom!!! it works flawlesly
guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks
darkoj2007 said:
guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks
Click to expand...
Click to collapse
Find the kernel patch then we can continue to talk
maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
Can we talk about Wireguard?
maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?
houmles said:
Can we talk about Wireguard?
Click to expand...
Click to collapse
No - somr things never change
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
darkoj2007 said:
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?
Click to expand...
Click to collapse
BORING!!!
{
"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"
}
Download :
GApps : https://dl.omnirom.org/tmp/def/
microG : https://dl.omnirom.org/def/
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
Get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
You should see a recovery like screen with a red "fastbood" message
Extract payload.bin using payload dumper (google it for tutorials)
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
UPDATE
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram group for One Hyper : https://t.me/MotoOneHyper
XDA:DevDB Information
OmniROM, ROM for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-02-02
Created 2020-02-02
Last Updated 2020-08-15
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
orimigato said:
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
Click to expand...
Click to collapse
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
vache said:
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
Click to expand...
Click to collapse
Yes I got an OTA when I got my phone today.
orimigato said:
Yes I got an OTA when I got my phone today.
Click to expand...
Click to collapse
Download stock ROM that match your current version from https://mirrors.lolinet.com/firmware/moto/def/official/
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
vache said:
Download stock ROM that match your current version from ...
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
Click to expand...
Click to collapse
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
orimigato said:
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
vache said:
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
orimigato said:
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
Click to expand...
Click to collapse
Wew cool it worked, i was running out of ideas xD
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
orimigato said:
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
Click to expand...
Click to collapse
Thanks for the detailed report.
1. About bluetooth, noticed that later while testing, already fixed.
2. You'd better install back Moto Camera 2 from Play Store if you want to get all stock features.
3. Never used that feature tbh, could you grab some logs ? (i'll make some tests on my side anyway)
I'll try to release the new build later today.
Edit : Created an account here : https://www.linphone.org/freesip/home
Then used https://freephonebox.net/ to call me, and it seems to work. (see attached screenshots)
SIP
Retried the SIP and now it is working. Possible was not working earlier since my old phone was still registered. Thanks for checking:good:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
orimigato said:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
Click to expand...
Click to collapse
Sorry, it was delayed cause i was working on dolby. Ill post it tomorrow.
Edit : New build ->https://www.androidfilehost.com/?fid=4349826312261718849 (check OP for update instruction)
Changelog :
- Fix bluetooth audio playback
- Added Dolby audio (Use QS Tile to open it for now)
- Added Google Feed to launcher
- February security patch
- Fixed tap to wake
- Synced kernel source with CAF
https://gerrit.omnirom.org/q/status:merged
https://github.com/boulzordev/device_motorola_def/commits/android-10
https://github.com/boulzordev/kernel_motorola_sm6150/commits/android-10
Bluetooth works perfectly now. Dolby is also very nice. Many thanks!
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
htcmusic said:
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
Click to expand...
Click to collapse
Yes what's the best root method you guys using?
young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
I will receive this phone next week (US version) and I will use patching boot.img method
mingkee said:
I will receive this phone next week (US version) and I will use patching boot.img method
Click to expand...
Click to collapse
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
young-ster said:
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
Click to expand...
Click to collapse
I see it
https://mirrors.lolinet.com/firmware/moto/def/official/RETUS/
Because really, a Realme GT ME is a killer with an AOSP ROM...
- - - - - - - - WARRANTY VOID IF YOU DO THAT - - - - - - - -
(Use original charger cable to connect phone to PC)
Download : ADB/fastboot, Deep Test apk, Magisk apk/zip 25.2, LOS (Lineage OS) recovery, custom ROM zip and GAPPS zip (if needed by your custom ROM)
Update phone by OTA for Android 12 RUI3 Export (french network for me)
Check options in developer menu (USB debugging/OEM unlock)
Install and launch the Deep Test apk
Restart phone into fastboot mode (power + volume down)
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot flashing unlock
Unlock bootloader on phone
Restart phone
Download firmware RMX3363export_11_C.08_2022062322020000.ofp
Extract boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img with ofp_qc_decrypt.py (Github Python3 script)
Install and launch Magisk apk
Copy extracted boot.img and vendor_boot.img on phone
Patch files with Magisk
Copy patched files on PC
Restart phone into fastboot mode
Choose "Recovery mode" and wipe data
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Type CMD : fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Type CMD : fastboot --set-slot=all flash boot patched-boot.img
Type CMD : fastboot --set-slot=all flash vendor_boot patched-vendor_boot.img
Restart phone (rooted)
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --set-slot=all flash boot LOS-recovery_boot.img
Type CMD : fastboot --set-slot=all flash vendor_boot LOS-recovery_vendor_boot.img
Type CMD : fastboot reboot recovery
Format DATA (factory reset) into LOS recovery
Launch ADB sideload into LOS recovery (and note active slot)
Type CMD on PC : adb devices (phone must be detected)
Type CMD : adb sideload <custom ROM>.zip
Relaunch ADB sideload into LOS recovery
Type CMD : adb sideload <GAPPS>.zip
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --set-active=<x> (a or b, depend of active slot at step 31)
Type CMD : fastboot reboot recovery
Launch ADB sideload into LOS recovery
Type CMD on PC : adb devices (phone must be detected)
Type CMD : adb sideload <custom ROM>.zip
Relaunch ADB sideload into LOS recovery
Type CMD : adb sideload <GAPPS>.zip
Restart phone
Welcome to your custom ROM !
(Perhaps you'll have, like me, to apply Magisk.zip in recovery mode to be definitively rooted)
After tested official ElixirOS and unofficial LineageOS, I prefer the second. So for me :
- lineageos-19.1-20220823-unofficial
- NikGapps-full-arm64-12-20220904-signed
- AGC8.4.300_V9.2_fix2
{
"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"
}
Animated notification's background (with LSPosed module) :
Where can I get a supported Depth Test app? Because I have tried all the depth test apps but they don't work..
Bungaza said:
Where can I get a supported Depth Test app? Because I have tried all the depth test apps but they don't work..
Click to expand...
Click to collapse
I'm sorry. This one works for mine :
https://androidfilehost.com/?fid=14655340768118457493
Hello,
Thanks for your simple guide, it worked for me!
enonaw said:
I'm sorry. This one works for mine :
https://androidfilehost.com/?fid=14655340768118457493
Click to expand...
Click to collapse
Not work
Bungaza said:
Not work
Click to expand...
Click to collapse
Do you have C08 export firmware ?
enonaw said:
Do you have C08 export firmware ?
Click to expand...
Click to collapse
I don't have
Amazing guide!
Bungaza said:
I don't have
Click to expand...
Click to collapse
Ok, so I'm sorry, I can't help you because this guide is for C08_Export...
enonaw said:
Ok, so I'm sorry, I can't help you because this guide is for C08_Export...
Click to expand...
Click to collapse
You're talking about C08 Export while my device doesn't support deep test apk. Unless you're talking about how to get into fastboot mode. I was able to get the export C08 firmware through a google search.
You should add in the guide the fact that if you are going to use Magisk on the custom rom you need to patch the boot.img and the vendor_boot.img of the specific rom extracted using payload-dumper-go tool
Bungaza said:
You're talking about C08 Export while my device doesn't support deep test apk. Unless you're talking about how to get into fastboot mode. I was able to get the export C08 firmware through a google search.
Click to expand...
Click to collapse
Hmmm... Ok. But this guide is for C08_export OTA updated smartphone (step 2). So, if you can't do step 2 before the step 4 (deep test), I can't help you.
leoufort said:
You should add in the guide the fact that if you are going to use Magisk on the custom rom you need to patch the boot.img and the vendor_boot.img of the specific rom extracted using payload-dumper-go tool
Click to expand...
Click to collapse
No. Look at "(Perhaps you'll have, like me, to apply Magisk.zip in recovery mode to be definitively rooted)" after the last step. I only did this to be able to use Magisk on custom ROM.
hi enonaw
i download RMX3363export_11_C.08_2022062322020000.ofp but unable to extract ofp file.
can u share here boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img from your pc.
Thnks in advance
ATuthura said:
hi enonaw
i download RMX3363export_11_C.08_2022062322020000.ofp but unable to extract ofp file.
can u share here boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img from your pc.
Thnks in advance
Click to expand...
Click to collapse
Hi, It's not a good idea to share stock img, because files can be altered when upload/download. Why are you unable to extract ofp file ? Did you use ofp_qc_decrypt.py (it works on both linux and windows) ?
ofp_qc_decrypt.py
enonaw said:
Hi, It's not a good idea to share stock img, because files can be altered when upload/download. Why are you unable to extract ofp file ? Did you use ofp_qc_decrypt.py (it works on both linux and windows) ?
ofp_qc_decrypt.py
Click to expand...
Click to collapse
i already tried, i cant. can u help me remotely via team viewer
ATuthura said:
i already tried, i cant. can u help me remotely via team viewer
Click to expand...
Click to collapse
See attached files, that's an archive of patched files by Magisk (password : rmx3363).
But verify the hash of your download before apply
And don't forget that I'm not responsible for what you do.
i am unbale toextract file
dear sir, just try
i face this issue
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
392a6bdd fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disa
ble-verification flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ 0.002s]
writing 'vbmeta'...
OKAY [ 0.009s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disa
ble-verification flash vbmeta_vendor vbmeta_vendor.img
target reported max download size of 805306368 bytes
sending 'vbmeta_vendor' (4 KB)...
OKAY [ 0.002s]
writing 'vbmeta_vendor'...
OKAY [ 0.009s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-slot=all flash bo
ot patched-boot.img
fastboot: unknown option -- set-slot=all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-slot=all flash ve
ndor_boot patched-vendor_boot.img
fastboot: unknown option -- set-slot=all
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse