This thread is a discussion request a new boot.img
A problem after update August, 2018. Any boot image patched not work. I'm extract OTA update and get a boot.img
I use Magisk Manager patched it (use Path Boot Image File)
This is my patched
Change log
- 28 September 2018
Update new boot image (boot_ 00WW_3_22C_September - Android 9 - Stable - with secrutiry patch September 1, 2018)
- 10 September 2018
Update new boot image (boot_ 00WW_3_190_September - Android 9 - beta 4.1)
- 07 September 2018:
Update new boot image (boot_00WW_2_22M_September - Android 8.1)
Download
http://mega.nz/#F!zypBQb6I!RG6T9A1h93PpE5HAJp6Ahg
Special thank
@narender singh confirm it work
----------------
Sorry, My english is bad
Hi, how did you extract the August OTA zip file? Did you download it from Nokia developers website or from where?
Rowdyy Ronnie said:
Hi, how did you extract the August OTA zip file? Did you download it from Nokia developers website or from where?
Click to expand...
Click to collapse
I'm use a payload_dumper script for extract Ota update
und3fined said:
I'm use a payload_dumper script for extract Ota update
Click to expand...
Click to collapse
I'm trying to extract payload.bin from OTA update with payload_dumper with no success. In fact payload_dumper cannot extract incremental build?
Folktroll said:
I try it with no success. payload_dumper cannot extract incremental build.
Click to expand...
Click to collapse
Please try it: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
Does anyone have the August stock boot image for TA-1046? The one given here is showing 00WW_2_22I whereas by device build number is 00WW_2_22A. So, I guess thus one belongs to TA-1062
Rowdyy Ronnie said:
Does anyone have the August stock boot image for TA-1046? The one given here is showing 00WW_2_22I whereas by device build number is 00WW_2_22A. So, I guess thus one belongs to TA-1062
Click to expand...
Click to collapse
Hi there,
In my mega.nz is boot image work for TA-1046 (extract from OTA - WW 2.22A SP02>WW 2.22A SP03 August 2018)
I can help me extract OTA update, u can share your url download OTA update?
Note: WW 2.22A SP03 is build number, 00WW_2_22I is build incremental (this code use for upgrade/downgrade android)
{
"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"
}
Update new boot.img for September update (07 September)
I'm extract stock boot.img from OTA link (https://android.googleapis.com/pack.../e8e501e4c4b78a42d433311bfdb2657948e45390.zip)
und3fined said:
Update new boot.img for September update (07 September)
I'm extract stock boot.img from OTA link (https://android.googleapis.com/pack.../e8e501e4c4b78a42d433311bfdb2657948e45390.zip)
Click to expand...
Click to collapse
What do you mean by September update? There is no September update available as of now. The latest update is for August 2018 (Second update for August).
Rowdyy Ronnie said:
What do you mean by September update? There is no September update available as of now. The latest update is for August 2018 (Second update for August).
Click to expand...
Click to collapse
It's a new patch for 8.1 (with August 2018 security patch)
und3fined said:
This thread is a discussion request a new boot.img
A problem after update August, 2018. Any boot image patched not work. I'm extract OTA update and get a boot.img
I use Magisk Manager patched it (use Path Boot Image File)
This is my patched
Change log
- 10 September 2018
Update new boot image (boot_ 00WW_3_190_September - Android 9 - beta 4.1)
- 07 September 2018:
Update new boot image (boot_00WW_2_22M_September - Android 8.1)
Download
http://mega.nz/#F!zypBQb6I!RG6T9A1h93PpE5HAJp6Ahg
Special thank
@narender singh confirm it work
----------------
Sorry, My english is bad
Click to expand...
Click to collapse
Lol. How Narendra confirmed it's working without Nokia7+ in his hand
isn't V2.22M AUG security patch?
Cathair2906 said:
isn't V2.22M AUG security patch?
Click to expand...
Click to collapse
It's a new AUG patch (ship in September 2018)
Just a tiny bug noticed after flashing, the "swipe to home" gesture option disappeared from the gestures menu and I can't use the feature anymore (along with the OEM unlock option greyed reading the same text as when the bootloader hasn't been unlocked yet)
These bugs are already present as I first boot up the patched .img to install magisk with the app. Any ideas for a fix? Thanks.
I'm on latest P beta 4.1
JBSroid said:
Just a tiny bug noticed after flashing, the "swipe to home" gesture option disappeared from the gestures menu and I can't use the feature anymore (along with the OEM unlock option greyed reading the same text as when the bootloader hasn't been unlocked yet)
These bugs are already present as I first boot up the patched .img to install magisk with the app. Any ideas for a fix? Thanks.
I'm on latest P beta 4.1
Click to expand...
Click to collapse
Turn off developer option,then turn on,it should now let you activate/deactivate oem option
cristi.blidariu said:
Turn off developer option,then turn on,it should now let you activate/deactivate oem option
Click to expand...
Click to collapse
Tried with no luck
Swipe up to home gestures not appearing either
JBSroid said:
Tried with no luck
Swipe up to home gestures not appearing either
Click to expand...
Click to collapse
Well I should tell you that I am using stock rom without any modifications, sorry I now see that you patch boot, probably that's the problem
Update new boot image (boot_ 00WW_3_22C_September - Android 9 - Stable - with secrutiry patch September 1, 2018)
Related
Hi There,
Wanna bored finding custom roms for your slim sexy marino device ?
Wanna want to go back home ?
Here is stock firmware (includes septmber 2017 security patch) for Lenovo k8 plus,XT-19202-2.
Disclaimer
Your warranty is not coming back.:laugh:
Flashing These images will not Re-Lock your Bootloader.
I am not responsible for bricked devices, dead SD cards,thermonuclear war.
Please do some research before flashing it!
YOU are choosing to make these modifications.
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Available Firmware Versions
Blur_Version.27.14.83 (January update) (OTA)
{
"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"
}
OMC27.70-52 (november security update)
OMC27.70-39 (july security update)
OMC27.70-37 (july security update)
Blur_Version.26.34.56 (Oreo OTA)
NMC26.74-31 (september security patch)
NMC 26.74-45_49 (january security update)
Both for 3GB & 4GB variants.
UP COMING
Next Security Update/OTA
What's Inside Fastboot Flash Scripts ?
Some Useful Batch Files For Windows Users
flashall.bat
hwflash.bat
programutags_XT1902-2_AP_Dual_SIM_3GRAM.bat
programutags_XT1902-2_AP_Dual_SIM_4GRAM.bat
Some Useful Shell Scripts For Linux Users
flashall.sh
hwflash.sh
programutags_XT1902-2_AP_Dual_SIM_3GRAM.sh
programutags_XT1902-2_AP_Dual_SIM_4GRAM.sh
DOWNLOAD
Note : It is recommended to join the telegram channel to get the links for next ROMs,patches,test-builds,other resources quicker than the thread . Our telegram group and channel is more active.
Blur_Version.27.14.83 (January security update)
Download
OMC27.70-52 (november security update)
Download
OMC27.70-39 (july security update)
Download
OMC27.70-35 (july security update)
Download
Oreo OTA Firmware(Blur_Version.26.34.56)
Download
NMC 26.74-31_31 (september security update)
Download
NMC 26.74-45_49 (january security update)
Download
------ Other Useful Files -------
FRP Removal Zip
Download
Fastboot Flash Scripts
Download
OTA Patch For Boot.img
Download
REPO
Note : It is recommended to join the telegram channel to get the links for next ROMs,patches,test-builds,other resources quicker than the thread . Our telegram group and channel is more active.
click on below image to go to Android File Host repository.
CREDITS
deadman96385 for november security update which was a paid download.:good:
Dhruv Agrawal,GEEKOFIA for files
Rupesh Tanwar for gdrive storage
Maanush for mega storage
And rest other people
SCREENSHOTS
In attachments.
OFFICIAL COMMUNITY
Official Telegram Group
Official Telegram Channel
======== GEEKOFIA ========
blog.geekofia.in
Ore
Can you upload the Oreo firmware also...
osmosi said:
Can you upload the Oreo firmware also...
Click to expand...
Click to collapse
O.P. is updated with oreo OTA firmware link.
One more thing , i need some one to create a mirror for PLAIN-ROM-GEEKOFIA-NIGHTLY-24012018_32bit.tar
Cause my drive storage is full and now-a-days i don't have a very stable and good internet connection as i had before.
GEEKOFIA said:
O.P. is updated with oreo OTA firmware link.
One more thing , i need some one to create a mirror for PLAIN-ROM-GEEKOFIA-NIGHTLY-24012018_32bit.tar
Cause my drive storage is full and now-a-days i don't have a very stable and good internet connection as i had before.
Click to expand...
Click to collapse
Thanks... What are the fastboot flash tools?
also Plain Rom??
---------- Post added at 07:20 PM ---------- Previous post was at 07:13 PM ----------
GEEKOFIA said:
O.P. is updated with oreo OTA firmware link.
One more thing , i need some one to create a mirror for PLAIN-ROM-GEEKOFIA-NIGHTLY-24012018_32bit.tar
Cause my drive storage is full and now-a-days i don't have a very stable and good internet connection as i had before.
Click to expand...
Click to collapse
Oreo Ota link is wrong i think...
Its seems incorrect oreo link
GEEKOFIA said:
O.P. is updated with oreo OTA firmware link.
One more thing , i need some one to create a mirror for PLAIN-ROM-GEEKOFIA-NIGHTLY-24012018_32bit.tar
Cause my drive storage is full and now-a-days i don't have a very stable and good internet connection as i had before.
Click to expand...
Click to collapse
Hi thank u for updating link but an oreo link that u updated showing nougat version as marino_oem_user_7.1.1_NMC26.74-45_49_release-keys_oem_SVCbyGaurav&Dhruv.rar.
Please check it and confirm the same.
Thank u.
saikarthik007 said:
Hi thank u for updating link but an oreo link that u updated showing nougat version as marino_oem_user_7.1.1_NMC26.74-45_49_release-keys_oem_SVCbyGaurav&Dhruv.rar.
Please check it and confirm the same.
Thank u.
Click to expand...
Click to collapse
Hmm , i was in a hurry and i copy paste the previous () and forget to replace the link. now it is updated. If it is still wrong there you can directly access it HERE
How to Sideload this oreo firmware
GEEKOFIA said:
Hmm , i was in a hurry and i copy paste the previous () and forget to replace the link. now it is updated. If it is still wrong there you can directly access it HERE
Click to expand...
Click to collapse
Hi thanks for providing update but can u help me how to sideload this oreo firmware i tried with adb sideload its showing error.
saikarthik007 said:
Hi thanks for providing update but can u help me how to sideload this oreo firmware i tried with adb sideload its showing error.
Click to expand...
Click to collapse
Upgrading to OREO steps for Marino (K8+) for superusers
1. download both 7.1.1 and 8.0 stock firmwares(stock nougat is required for unrooting the device, if you have stock recovery you can use it )
2. Extract nougat firmware archive.
3. Flash nougat first with the sp flash tool ( in nougat zip ) or the batch scripts ( also included in nougat zip or can be downloaded from O.P.)
4. Now copy oreo ota zip to internal storage and boot to recovery ... then select update from sdcard or whatever it is..and choose the ota zip.
Note : In sp flash tool don't choose "format all + download " it will brick your imei & baseband.
Updated to Oreo Successfully
GEEKOFIA said:
Upgrading to OREO steps for Marino (K8+) for superusers
1. download both 7.1.1 and 8.0 stock firmwares(stock nougat is required for unrooting the device, if you have stock recovery you can use it )
2. Extract nougat firmware archive.
3. Flash nougat first with the sp flash tool ( in nougat zip ) or the batch scripts ( also included in nougat zip or can be downloaded from O.P.)
4. Now copy oreo ota zip to internal storage and boot to recovery ... then select update from sdcard or whatever it is..and choose the ota zip.
Note : In sp flash tool don't choose "format all + download " it will brick your imei & baseband.
Click to expand...
Click to collapse
Hi thanks its worked.
saikarthik007 said:
Hi thanks its worked.
Click to expand...
Click to collapse
Press that thanks button instead of quoting to support me
Via ADB & Sideload ..
Please make a video guys and also how can i update with ADB & Sideload ?
jisanroyal said:
Please make a video guys and also how can i update with ADB & Sideload ?
Click to expand...
Click to collapse
Steps to sideload.
1. Turn off ur phone and enter into recovery mode by pressing vol down and power.
2. There Scroll down to select recovery option.
3. U will get no command display.
4. Then press vol up and power for few seconds then take ur finger from volup key but keep pressing power key.
5. Then u will enter into recovery mode.
6. There u can select install update from sdcard browse and select file.
7. Thats all.
can somebody pls give me instructions on how to flash the stock ROM?i need to downgrade from oreo to nougat firmware since the oreo build is too buggy
jisanroyal said:
Please make a video guys and also how can i update with ADB & Sideload ?
Click to expand...
Click to collapse
Updating Blog is here.
Join our telegram group to get help for these installation stuffs.
vishalaestro said:
can somebody pls give me instructions on how to flash the stock ROM?i need to downgrade from oreo to nougat firmware since the oreo build is too buggy
Click to expand...
Click to collapse
Just Flash the nougat firmware via fastboot.
Join our telegram group to get help for these installation stuffs.
downgrading procedure please
need stock recovery image
i want to lock my bootloader and install stock recovery on my k8 plus...can somebody explain the procedure plzz?
i am using twrp recovery now.but i want my stock recovery back cz i cant flash my official ota update(i.e-OMC27.70-47) with twrp recovery.
*otherwise if someone know the process how to flash official ota update with twrp then tell me
---------- Post added at 09:09 PM ---------- Previous post was at 09:04 PM ----------
santybraves said:
downgrading procedure please
Click to expand...
Click to collapse
just flash this firmware from spflashtool and u r done.:good:
~~Can someone share a flashable stock ROM that I may install using twrp? I don't have a PC right now~~
Edit : got it done now
Hi guys, this rom has Portuguese-Brazilian language? I've bought a lenovo k8 plus but only has Portuguese-Portugal.
So how should i flash this
---------- Post added at 07:50 AM ---------- Previous post was at 07:43 AM ----------
as i am new to this flashing i just wanna know how should I flash nougat rom as oreo rom is having so many bugs and the performance has gone down too.
I have not done anything in this phn before this
Here is the November security update
https://www.androidfilehost.com/?fid=11410963190603912196
as well as an FRP removal image
https://www.androidfilehost.com/?fid=11410963190603912197
Maybe you can get these added to the OP @GEEKOFIA
Reason for edit: Change title so more users can find this method since for now TWRP is working but not to root
Click to expand...
Click to collapse
Hello fellow XDA users,
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
I've been following all threads here on XDA and for the last few days its like a boom of new information, yesterday a Senior Member provided me with the Unlock Key generated with my IMEI1 and the phone's bootloader is now unlocked:
{
"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"
}
Now the next logical part I would be installing TWRP to flash the magisk flashable zip to the phone, but there is no TWRP built to our phones (old information, there is now an official TWRP build)..
To my surprise there is this thread that offers boot images already patched with root ( @nummerok are they patched under magisk?), I tried flashing first with:
Code:
fastboot boot NB1-0-484A-00WW-boot.img
But it did not worked, no matter what the installed Magisk Manager would not find the Magisk Module on the system.
Then I found out that some users were getting root but with the problem of losing wifi connectivity, that was found to be the fault of the phone having the March Security Patch (00WW_4_84A_SP01) while flashing the boot image of the phone with the February Security Patch (00WW_4_84A).
As of this new A-B partition scheme on Android, when your boot image does not pass dm-verity it restores the older version automatically (Am I right on this point?? can please someone confirm?!)
Since my phone WAS on the march patch I saw no other option but to wait someone to grab the march boot image to patch it Magisk Manager and get root.
Buut since my generation doesn't like to sit and wait I found that there was a way to roll back to the previous firmware!
What I did was, run this code below on adb to know which slot my phone was:
Code:
adb shell getprop ro.boot.slot_suffix
Then take note of the slot and run:
Code:
adb reboot bootloader
After the device starts up in Download Mode you need to switch to the other boot slot. Just run:
Code:
If you are currently on slot A, type this: [B][I]fastboot --set-active=_b[/I][/B]
Or on slot B type this: [B][I]fastboot --set-active=_a[/I][/B]
You should see something like this:
Code:
Setting current slot to 'a'... OKAY [ 0.046s] finished. total time: 0.046s
Now run the code below and cross your fingers!
Code:
fastboot reboot
Once the phone has booted, check in Settings/System/About Phone if your Android security patch level has downgraded to the February one and proceed to the next step.
I've downloaded the full NB1-484A-0-00WW-B03.nb0 firmware from @blackpanther0582 thread under the google drive link and extracted the boot image using the tool made by @heineken78 available over here (be sure to have lots of ram available for the unpack process :fingers-crossed.
With the file NB1-0-484A-00WW-boot.img at hand I've copied it to the Nokia 8 internal storage and ran Magisk Manager to patch it, follow instructions here under Via Magisk Manager (Only support v14.0+) part.
Now grab the patched_boot.img file provided by Magisk from the phone and save it (adb pull or whatever) to your pc and run these commands:
Code:
adb reboot bootloader
After the phone boots up in Download Mode run:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
With that done, after the boot you can open Magisk Manager to see it fully installed and later on install some root checker app just to be sure of the sucess of your rooting:
Split-screen to the rescue lol
This Nokia 8 is officially rooted but with the previous February patch and I'm itching to install the March OTA provided by @2WildFirE here, any thoughts on that? What about the official system update that still lists the 2018-03 security patch? Would any of which work?
And that is all for now folks!
I would like to thank @the_laser @heineken78 @topjohnwu @blackpanther0582 @nummerok and many others in this invaluable path to learning more about this phone and the Android system in general!
Good Luck!!
Reserved
Nice, this will help some people to understand.
Powered by Nokia 8 with open bootloader
2WildFirE said:
Nice, this will help some people to understand.
Click to expand...
Click to collapse
That's the idea @2WildFirE !
btw just to make things clear, the official system update is running for like 10 hours and it seems it's not going anywhere.. would I get success by doing the march update thru the zip you've found?
Yep was working fine here, to bring my wifi back, but lost root [emoji6] what we Really need is twrp and or a method to extract the boot.img from the *. Bin file included in the update zip.
Powered by Nokia 8 with open bootloader
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
contrahelix said:
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
Click to expand...
Click to collapse
It should work only if you have your bootloader unlocked @contrahelix
You might get it unlocked officially by Nokia or wait for an alternative method.
Also you should update your adb/fastboot tools, then you would get the right error message telling you about the still locked bootloader!
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
Click to expand...
Click to collapse
I have a TA-1012 i assume it won't work for me?
For everyone with unlocked bootloader, this is the method to root without TWRP !
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Raithlin said:
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Click to expand...
Click to collapse
Still have to rollback to official image.. you cannot upgrade with patched img unfortunately
As u have unlocked bootloader and installed magisk i have a question .
Is it worth to unlock bootloader and install magisk.......?
And one more any custom rom available for nokia8 ta1004.......?
شرا
{
"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"
}
#Pixel Experience 12.1#
Patch : April 2022
Device: odessa
Maintainer: Karoline Moraes
Build Status: UNOFFICIAL
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation). Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device. We are a community-driven open source project, so we have no affiliation with Google LLC company.
Based on Android 12.1
⚒ Changes:
• April Security Patch
• Fixed loading animation not appearing
• Fixed unlock sound playing repeatedly
• Updated translations
• CTS passing by default
• Selinux Enforcing
• Actions for assistant button in motorcycle actions.
• Added Zram
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, ALREADY INCLUDED
DOWNLOAD
Extract File | Boot Patched FOR ANYONE WANTING TO ROOT
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
Telegram Group
Telegram Group for Odessa
PixelExperienceOS
Android OS version: 12.1
Security patch level: April 2022
Contributors: Big Thanks to @erfanoabdi for their amazing working on trees.
Source code
PixelExperience
Kernel Source code
Kernel Source
Device Specific Code
Motorola_Odessa
Version InformationStatus: STABLE
Stable Release Date: 12-04-2022
It's a rom that needs no praise!
Very optimized in terms of battery and performance, as it is a PE, it is behaving better than other custons.
I used some modules to double the performance and stability.
The modules that were used: GPU Turbo Boost, ZRAMxSwap (RAM Expansion), Zeus Performance.
Check out the prints:
better ROM, and how bluetooth working is even better, thanks for making the rom available to us
To get root in this room, we need to patch with magisk the boot.img that is in the download section? Or should be flashed as is at once ??
Rom top de +
j3cnfa said:
To get root in this room, we need to patch with magisk the boot.img that is in the download section? Or should be flashed as is at once ??
Click to expand...
Click to collapse
we need to patch with magisk the boot.img and then by fastboot with patched file
j3cnfa said:
Para fazer root nesta sala, precisamos corrigir com magisk o boot.img que está na seção de downloads? Ou deve ser exibido como está de uma só vez ??
Click to expand...
Click to collapse
download the boot in the download section as it is already rooted
Wifi is still disconnecting randomly. No solution?
GabiAle97 said:
Wifi is still disconnecting randomly. No solution?
Click to expand...
Click to collapse
.
GabiAle97 said:
Wifi is still disconnecting randomly. No solution?
Click to expand...
Click to collapse
I uploaded the new test version and see the fix
CustomRom's said:
I uploaded the new test version and see the fix
Click to expand...
Click to collapse
The issue still persist, but it took a lot of time to appear...
GabiAle97 said:
Wifi is still disconnecting randomly. No solution?
Click to expand...
Click to collapse
upgrading to new version, see if it was fixed
Hello! Great rom, thanks for sharing! Forgive my ignorance, but how do i update to the latest version? Is there any way to update without flashing recovery and make a clean installation? Ty in advance!
chiconanni said:
Hello! Great rom, thanks for sharing! Forgive my ignorance, but how do i update to the latest version? Is there any way to update without flashing recovery and make a clean installation? Ty in advance!
Click to expand...
Click to collapse
Boot to recovery, apply update, from adb, adb sideload <filename>
Ty very much!
chiconanni said:
Hello! Great rom, thanks for sharing! Forgive my ignorance, but how do i update to the latest version? Is there any way to update without flashing recovery and make a clean installation? Ty in advance!
Click to expand...
Click to collapse
yes , download a custom one and extract it using payload_dumper , take the extracted files and go through FASTBOOTD mode using these commands :
fastboot.exe flash boot boot.img
fastboot.exe flash dtbo dtbo.img
fastboot.exe flash system system.img
fastboot.exe flash product product.img
fastboot.exe flash vendor vendor.img
fastboot.exe flash vbmeta vbmeta.img
fastboot.exe reboot
CustomRom's said:
yes , download a custom one and extract it using payload_dumper , take the extracted files and go through FASTBOOTD mode using these commands :
fastboot.exe flash boot boot.img
fastboot.exe flash dtbo dtbo.img
fastboot.exe flash system system.img
fastboot.exe flash product product.img
fastboot.exe flash vendor vendor.img
fastboot.exe flash vbmeta vbmeta.img
fastboot.exe reboot
Click to expand...
Click to collapse
Cuando puse fastboot flash system system.img me sale command failed
I just installed the ROM and I noticed that Google Pay isn't working (SafetyNet fails so that's probably the cause), could this be fixed in a future update?
Screenshots from Google Pay and SafetyNet Test are attached.
Phone arrived today, got on the website, downloaded the latest August build. I did not notice it was 13. Unlocked the bootloader, flashed the image and the phone booted right up. I was about to root when I realized I was on 13 and then came here and saw the PSA about the phone can't be downgraded from 13 to a previous build.
My question (I've searched and found nothing), can I root the Pixel 6a on the official August 13 build with Magisc? Will I need to do anything differently like disable verifications and stuff? Usually I install the latest Magisk (v25.2), patch the boot.img, flash the patchedboot.img and profit.
Thanks in advance.
Bad Bimr said:
My question (I've searched and found nothing) can I root the Pixel 6a on the official August 13 build with Magisc?
Click to expand...
Click to collapse
Yes
Bad Bimr said:
Will I need to do anything differently like disable verifications and stuff?
Click to expand...
Click to collapse
No. Disabling verity and verification is optional.
Bad Bimr said:
Usually I install the latest Magisk (v25.2), patch the boot.img, flash the patchedboot.img and profit.
Thanks in advance.
Click to expand...
Click to collapse
Yep
Rooting Android 13 works exactly the same way as Android 12. The only thing that would prevent rooting is a locked bootloader. Google hasn't done anything to prevent root (yet).
Lughnasadh said:
Yes
Click to expand...
Click to collapse
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
V0latyle said:
Google hasn't done anything to prevent root (yet).
Click to expand...
Click to collapse
I wish that, in addition to the "allow bootloader unlock" switch, there was a "don't be a nanny" switch.
Bad Bimr said:
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
Click to expand...
Click to collapse
Glad it all worked out! Yeah, the version of YouTube that comes with A13 is higher than the Vanced YouTube version.
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
i wish i could unlock my bootloader, mine is still greyed out
beanaman said:
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
Click to expand...
Click to collapse
Are there any rooted versions that work with A13? Is building it simple? I didnt see anything there just doing a quick search.
Yes very simple to build. Just use the builder and follow instructions to patch current YouTube APK.
Here is link to GitHub w instructions.
How to use revanced builder on Android
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com
beanaman said:
Yes very simple to build. Just use the builder and follow instructions to patch current YouTube APK.
Here is link to GitHub w instructions.
How to use revanced builder on Android
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Ok, that was stupid simple. Thanks
"Disabling verity and verification is optional"
What are the advantages or disadvantages of doing that?
beanaman said:
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
Click to expand...
Click to collapse
Thank you for this!
Bad Bimr said:
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
Click to expand...
Click to collapse
Just got a pixel 6a, updated to 13, pulled Vanced Manager off my old phone, and installed it. It's working fine for me
¯\_(ツ)_/¯
Hi, how to fix this issue?
{
"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"
}
7kAi said:
Hi, how to fix this issue?
View attachment 5804131
Click to expand...
Click to collapse
Try using the latest Platform Tools and also try using command prompt instead of PowerShell. Put the patched image in the Platform Tools folder, open up command prompt from that folder and flash.
fastboot flash boot <nameofpatchedimage>
Lughnasadh said:
Try using the latest Platform Tools and also try using command prompt instead of PowerShell. Put the patched image in the Platform Tools folder, open up command prompt from that folder and flash.
fastboot flash boot <nameofpatchedimage>
Click to expand...
Click to collapse
worked using
fastboot.exe flash boot <nameofpatchedimage>
Thanks!
people were reporting that the OTA Beta QPR2 (it was qp something) was having issues with root, but as far as I can tell, its cleared up.
Or just use AICP for the 6a. no issues. Had issues with crdroid
TechX1991 said:
people were reporting that the OTA Beta QPR2 (it was qp something) was having issues with root, but as far as I can tell, its cleared up.
Click to expand...
Click to collapse
It was QPR2 Beta 1 where root could not be obtained by flashing a patched Pixel 6 boot image, so people had to patch a Pixel 7 boot image to obtain root.
We don't know if this is "cleared up" since QPR2 Beta 2 has not been released yet.
Lughnasadh said:
It was QPR2 Beta 1 where root could not be obtained by flashing a patched Pixel 6 boot image, so people had to patch a Pixel 7 boot image to obtain root.
We don't know if this is "cleared up" since QPR2 Beta 2 has not been released yet.
Click to expand...
Click to collapse
Got it, thanks for clearing it up. I wonder if that's similar to the issues with crdroid rom. Root can't be done via recovery at all, it just errors out. When you patch the boot.img from crdroid's rom, at least for me, I had random crashes and bluetooth flat out didn't work. It would say the app for controlling bluetooth was crashing.
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
OOS 13.1 - 13.1.0.500(EX01) firmware is required (can update via firmware update tool found on download page, firmware button)
Download KIT files (download - this includes dtbo.img and vendor_boot.img)
Download recovery (from download page, recovery button)
Optional NikGapps core (download - note that you may also need setup wizard addon if you rely on Google restore)
Optional Magisk (boot.img used to patch with Magisk in order to get root, can be found in recovery folder from download page)
First time installation (clean flash):
Backup your data to PC, OTG flash drive
Make sure you have OOS 13.1 firmware installed (if used firmware flash tool from download page, proceed straight to install crDroid.zip)
Enter fastboot
Flash dtbo.img
Code:
fastboot flash dtbo dtbo.img
Flash vendor_boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Flash boot.img
Code:
fastboot flash boot boot.img
Boot to recovery (can do from bootloader or with buttons from power off state)
Now in recovery go to factory reset and confirm the reset
Reboot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload
Code:
adb sideload crDroid.zip
Go back to main menu and reboot to recovery to install gapps (if you don't want gapps, reboot to system)
To install gapps, simply sideload gapps.zip the same way you installed crDroid.zip then reboot to system
Update installation:
Via recovery (recommended way):
Boot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload and reboot
Code:
adb sideload crDroid.zip
If you had gapps, reboot to recovery and sideload gapps.zip and reboot
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
If you have Magisk installed, don't click reboot when prompted and go to Magisk and choose install to inactive slot
Reboot
Note: In some cases where incompatible gapps used, may result in boot issues that should get fixed by flashing gapps again in recovery.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM: https://crdroid.net/lemonade/9
Visit official website @ crDroid.net
crDroid OnePlus 9 Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Phoenix47 said:
@gwolfu you accidentally added QUESTION tag instead of DEVELOPMENT tag.
Click to expand...
Click to collapse
yeah I've seen in my other threads also )
should be fixed now
I tried to sideload GoogleSearch to get hey google but now I'm getting "Check your internet connection and try again" when I press unlock more assistant features.
Edit: GoogleSearch worked fine in android 12.
Forget about it I found the problem. Don't know why google setting were disable but after enabling, everything works.
Does this oos cam support slowmotion and h265 video rec ?
"Long press on fingerprint sensor to unlock phone" seems to be broken. It's turning off automatically when I try to turn it on.
Navigation with hand gestures disappears after 1 day!
Thank you for this amazing rom! I recommend using Msm tool (https://forum.xda-developers.com/t/...-for-indian-variant-flashing-as-well.4454357/ and see this video for further help
) if you are coming from Derp android 12 rom like I was. Everything works great, even the oos camera. Unlimited google photos upload works perfectly. I am also passing safetynet and play store settings check after following the youtube video titled SafetyNet ByPass & CTS Profile False Fix, and this is with Magisk 25.2 zip installed after first boot. I think the creator posts a lot on xda if I remember correctly.
Build 20221106 is ready
Changelog: https://crdroid.net/lemonade/9#changelog
Download: https://crdroid.net/lemonade/9
Build 20221111 is ready
Changelog: https://crdroid.net/lemonade/9#changelog
Download: https://crdroid.net/lemonade/9
The ROM is really smooth and stable. Big thumb up.
The only problem I ran into is that the kernel doesn't seem to support Network Signal Guru. Any idea? crDroid 8 worked fine with NSG.
lovebeta said:
The ROM is really smooth and stable. Big thumb up.
The only problem I ran into is that the kernel doesn't seem to support Network Signal Guru. Any idea? crDroid 8 worked fine with NSG.
Click to expand...
Click to collapse
It's not entirely rom based, if you're talking about an app they probably haven't Updated there app yet to 13. Lots of errors still occur on 13 based ROMs .
Vmo x said:
It's not entirely rom based, if you're talking about an app they probably haven't Updated there app yet to 13. Lots of errors still occur on 13 based ROMs .
Click to expand...
Click to collapse
That could be, had similar issue with Nameless A13 as well. However Network Signal Guru works with Evolution X A13...
Build 20221118 is ready
Changelog: https://crdroid.net/lemonade/9#changelog
Download: https://crdroid.net/lemonade/9
gwolfu said:
Build 20221118 is ready
Changelog: https://crdroid.net/lemonade/9#changelog
Download: https://crdroid.net/lemonade/9
Click to expand...
Click to collapse
Thanks for the Nov 18, 2022 Build. It works fine. However, I did have a problem with the boot-20221118.img file.
It just hangs & do not boot to recovery on my LE2115. I had to go back to the Nov 11, 2022 boot-20221111.img file to boot to recovery & install the new 11/18 ROM.
fastboot flash boot_a boot-20221118.img
fastboot flash boot_b boot-20221118.img
ygb7 said:
Thanks for the Nov 18, 2022 Build. It works fine. However, I did have a problem with the boot-20221118.img file.
It just hangs & do not boot to recovery om my LE2115. I had to go back to the Nov 11, 2022 boot-20221118.img file to boot to recovery & install the new 11/18 ROM.
fastboot flash boot_a boot-20221118.img
fastboot flash boot_b boot-20221118.img
Click to expand...
Click to collapse
Weird enough since same boot img is present in rom.zip
Also no need to update boot every update
ygb7 said:
Thanks for the Nov 18, 2022 Build. It works fine. However, I did have a problem with the boot-20221111.img file.
It just hangs & do not boot to recovery on my LE2115. I had to go back to the Nov 11, 2022 boot-20221118.img file to boot to recovery & install the new 11/18 ROM.
fastboot flash boot_a boot-20221118.img
fastboot flash boot_b boot-20221118.img
Click to expand...
Click to collapse
Same
for anyone using the latest update... DO NOT USE SMART LOCK! when you try to unlock using the normal pattern the system crashes and resets and you are stuck in an infinite loop. if you do manage to unlock it by some miracle and you try to go to settings and undo that smart lock huge mistake or change/disable the screen lock completely settings will crash so you ll still be stuck. do not use google remote lock as i did as that locks it forever, the brain dead people working for google removed the feature of remote unlock
gwolfu
Is it by desgin that the cdDroid ROM defaults to Sound in Do Not Disturb mode?
It not a problem to simply toggle the sound on. I was just wondering since on all of the upgrades the sound has been set back to Do Not Disturb mode.
ygb7 said:
Thanks for the Nov 18, 2022 Build. It works fine. However, I did have a problem with the boot-20221118.img file.
It just hangs & do not boot to recovery on my LE2115. I had to go back to the Nov 11, 2022 boot-20221111.img file to boot to recovery & install the new 11/18 ROM.
fastboot flash boot_a boot-20221118.img
fastboot flash boot_b boot-20221118.img
Click to expand...
Click to collapse
I have the same pronlem the phone always comes back to the bootloader mode
Build 20221126 is ready
Changelog: https://crdroid.net/lemonade/9#changelog
Download: https://crdroid.net/lemonade/9