DOWNGRADE STEPS for ALL Stock/Custom ROMS
!!!
DOWNSIDE = WIDEVINE L1 => L3
!!!
Prerequisite
. Downgrade = install the lower version of android [11] => [10]
. Upgrade = install the higher version of android [10] => [11]
- ADB & Fastboot required / Phone always connected !!!
- Download both : the full fastboot firmware (.tar) (12.0.8.0 i.e) and its recovery firmware (.zip)
- Extract super.img & stock recovery.img
- on normal fastboot, type :
fastboot flash recovery <stock-extracted-recovery>.img
fastboot reboot fastboot [mandatory+++]
- You are now in "fastbootd" (yellow), type :
fastboot erase super
fastboot flash super <extracted-super>.img
[this is mandatory because the "SUPER" structure from 10 is different to the one in 11]
fastboot flash recovery <twrp-recovery>.img
fastboot reboot [keep volume DOWN pressed until you see the normal fastboot splash (blue), then type again] :
fastboot reboot recovery
- in TWRP menu : if you can see the internal storage content, put the recovery firmware (.zip) and flash it.
- if you have corrupted internal storage, make a data format... reboot from TWRP to the normal bootloader and type again :
fastboot boot <twrp-recovery>.img
- in TWRP menu again : Put now the recovery firmware (.zip) to flash it.
- Without rebooting anything : put your android 10 ROM (LOS 17.1 i.e) +/- Magisk & gapps
- Flash 'em All in that order
- format data again
- reboot
These downgrade steps are "tested"
and
work 100% with no issue !!!
Reserved
PART II : UPGRADE
=
RESTORING DRM Keys
L3 => L1
Important !!!
As you you can see, downgrading your android version to [Q] [10] will automatically drop your Widevine to L3 level ... Because once you upgrade the firmware, the TrustedZone (if you downgraded before) will not accept rewriting your old DRM Keys even if you restore them from the "persist" partition. These DRM keys are crypted and stored, in reality, in the TrustedZone; the persist partition only write the decrypted keys to make them readable by your OS.
RESTORE Widevine L1 - STEPS
!!!
Upgrading = flashing SUPER.img and its recovery.img is mandatory
!!!
- The upgrade steps are the same as described in the downgrade process (first post)
- The only way to recover Widevine L1 again after downgrading is to flash the latest xiaomi.eu rom ... because it integers a tool to redownload a new certificate for DRM.
Stock-Original MIUI ROMs don't have this tool yet !!!
{
"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"
}
Select in "MIUI Settings" :
Here, you must set a lockscreen fingerprint to enable the next feature :[mandatory]
Select "Fingerprint payments" :
Then "Widevine (L1)" :
Click on "Download certificate" :
Check now your DRM status !
I rebooted to my TWRP, and installed Pixel Experience [11]. As you can see, the DRM Keys are still in L1 !!!
Netflix Settings :
Reserved
You can install any custom rom you want [Q] or [R] ... but keep in mind :
Downgrading to [10] = Loosing DRM L1 Keys
Upgrading to [11] = The only way to restore them !!!
To keep your DRM Keys in L1, you must stay in the latest [11] firmware (not necessarily a MIUI ROM) or the newer when it comes !
Cheers
gringo80 said:
Check now your DRM status !
Click to expand...
Click to collapse
Please convert your screenshots to thumbnails (use "Attach files" button at bottom left corner) to facilitate topic readability.
pnin said:
Please convert your screenshots to thumbnails (use "Attach files" button at bottom left corner) to facilitate topic readability.
Click to expand...
Click to collapse
It will scatter the steps !!! (Thanks to the XDA bad arrangement)
Use your smartphone ... as i'm doing right now. It's easy to read !
gringo80 said:
Use your smartphone ... as i'm doing right now. It's easy to read !
Click to expand...
Click to collapse
Thanks, but that's a total nightmare, even with the XDA app. My eyesight is not that good, so I have to use the PC.
pnin said:
Thanks, but that's a total nightmare, even with the XDA app. My eyesight is not that good, so I have to use the PC.
Click to expand...
Click to collapse
Use any smartphone browser. I never use XDA app !
Is there a way to restore the widevine to L1 after downgrading from global A11 to global A10?
kopaks said:
Is there a way to restore the widevine to L1 after downgrading from global A11 to global A10?
Click to expand...
Click to collapse
Hoping someone comes up with a solution, too -- won't risk upgrading until then.
gringo80 said:
Reserved
You can install any custom rom you want [Q] or [R] ... but keep in mind :
Downgrading to [10] = Loosing DRM L1 Keys
Upgrading to [11] = The only way to restore them !!!
To keep your DRM Keys in L1, you must stay in the latest [11] firmware (not necessarily a MIUI ROM) or the newer when it comes !
Cheers
Click to expand...
Click to collapse
Im not sure if this applies to all because in my case ive been flashing A11 miui stock or even custom A11 rom then come back to A10 many times and I didnt have any issue with widevine, its always L1
pnin said:
Hoping someone comes up with a solution, too -- won't risk upgrading until then.
Click to expand...
Click to collapse
flash A11 then download the certificate then go back to A10
amnher said:
flash A11 then download the certificate then go back to A10
Click to expand...
Click to collapse
If I only knew how...
amnher said:
Im not sure if this applies to all because in my case ive been flashing A11 miui stock or even custom A11 rom then come back to A10 many times and I didnt have any issue with widevine, its always L1
Click to expand...
Click to collapse
Do you have any proof ??? you are misleading people for things you have never done ... only in your mind !
Show us the proof here !
downgrade to any custom rom A10 with L1... 1 million dollars baby waiting for you !
Lol i myself did it back and forth flashing custom rom and stock a10 12.0.9.0 even a11 12.5.1.0 without loosing L1. no need to be rude. Im not saying this applies to everyone. What imsaying is a user like me. Did not have problems in widevine. I dont have the obligation to lie to you or whatsoever. I am here to share my experience just for your clarification. So stop the hate and sarcasm and be open minded kid
gringo80 said:
Do you have any proof ??? you are misleading people for things you have never done ... only in your mind !
Show us the proof here !
downgrade to any custom rom A10 with L1... 1 million dollars baby waiting for you !
Click to expand...
Click to collapse
same here. i didnt experience any widevine problems. i keep coming back and forth from a11 fw/miui to a10 fw/miui. the reason that it didnt lost it is because i use recovery upgrade from twrp recovery instead of using stock in OTA. and even with anti count of 2 due to fails of downgrading, it stays at L1. probably what you did is you let the system updates its widevine before trying to downgrade. probably it varies from everyone who got updated from a10 to a11 by using OTA.
Thread closed at op's request.
strongst
XDA Staff
Related
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
{
"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"
}
Here is complete guide to install android p dp5 on redmi 3s..
do every step carefully as messing up could brick your device
quick note ANDROID P WORTH READING THIS LONG ENGNEERING PAPER LIKE ARTICLE SO BE PATIENT
use trebal twrp link-https://forum.xda-developers.com/xiaomi-redmi-3s/development/recovery-unofficial-twrp-xiaomi-redmi-t3701841
step 1 ) choosing a base rom.
as project trebal can install android p on vender of oreo roms we need a campatable oreo rom (trebal supported)
i will suggest to go with lineage os
step 2) clean flash lineage os without gapps
step 3) without rebooting into system wipe all partitions except vender and internal storage
step 4) Download and extract the dp5.zip https://androidfilehost.com/?fid=5862345805528058112
copy img file in internal storage
step 5) install the gsi image as system image
[click on install image , select .img file, flash as system image]
check if vender and system partition is mounted properly
if error code 7 is shown unmount and mount vender
step 6) install postgsi 1 2 3 resspectively
pgsi 1-https://androidfilehost.com/?fid=5862345805528063582
pgsi 2-https://androidfilehost.com/?fid=5862345805528063581
pgsi 3-https://androidfilehost.com/?fid=5862345805528058103
step 7) install lag ,gcam fix
lag fix-https://drive.google.com/file/d/1r2oxwvaCCWEUw_iYIH_g25cescD-h0U4/view
gcam fix-https://drive.google.com/file/d/1YNxEuldCgIQzxOqp8_4Mwd--rf2uSy_1/view
volte fix and fingerprint fix not tested
volte fix-https://drive.google.com/file/d/1NFBU1KErlZgz-rg9NZdIHkWwalsW3phh/view
fp fix-https://drive.google.com/file/d/1nyO8c0Jpk445pbsGtYUN7Yaj8mCoUc08/view
before booting system format data to remove the encryption otherwise it will ask for password
step 8) boot into system
step 9) enabling MTP
after booting into android p
go to build no tap 5 times and enable dev options
in dev option select [default usb configration] to file transfer
step 10) fixig lag
go to dev options and decrease [window animation scale] to 0.5 for all 3
step 11) copy play services apk into the internal storage
play-https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-8-74-release/google-play-services-12-8-74-100400-204998136-android-apk-download/
install using file maneger...
step 12) logging in
open play store and log in to google account
step 13) setting up assistant
you have to initealise the assistant right now otherwise it wont work in future
open [google app] and set up assistant
step 14) rooting the device for cam2api
reboot to twrp and flash the magiks 16.7 only
link- https://www.mobileheadlines.net/download-magisk-16-7-beta/
reboot into system
install migiks maneger.apk link-https://******************/
install cam2api ebalbler in magics maneger
link-https://drive.google.com/open?id=1Xn9hSKGBAzgOA4wAYIo73iRykj5TUQb5
step 15) install gcam by urikil
link -https://drive.google.com/file/d/1VVrO0Lf3TN1te2fIaAA10OpBsfssMJV6/view?usp=sharing
open camera under [settings] [advance settings] [model] select [pixel 2]
if you are reading till this then you are a nerd and you definitely need something to control your addiction
luckyly google has you covered by digital wellbeing program
step 16) enroll for digital wellbeing
link-https://www.android.com/versions/pie-9-0/digital-wellbeing-beta/
sign up and you will get conformation mail in 7-8 hrs
finally you are in fully stable android p dev preview 5
CREDITS:
1)Lineage os team
2) erfanoabdi for huge contribution in this progect
Nice guide but
Post in general section pls
[email protected]$ said:
Nice guide but
Post in general section pls
Click to expand...
Click to collapse
Agree it's helpful. And I already report it. cc @engloa
Actually u can flash vendor.img directly then sGSI or sGSI first doesn't matter, for vendor.img just extract it from treble rom that u choose, after that u will need to decompress it from brotli ".br" extension..., Here's the link for brotli official software https://github.com/google/brotli/releases
Type from cmd "brotli -d vendor.new.dat.br" then you will get ".dat" extension, to convert it to ".img" use this script https://github.com/xpirt/sdat2img just run "./sdat2img.py vendor.transfer.list vendor.new.dat vendor.img" or from windows "python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img"
If after u reboot then stuck at "asking password for decrypt or whatever i forgot it exactly" just go to fastboot then type "fastboot -w" this will wipe your data and cache off course internal too ? ... But this will let u to boot to home screen, FBE_Disabler.zip from erfan will not work for us because our device using fde not fbe
And about fingerprint there's no need to flash any patch because fingerprint already work for goodix or fpc, the problem is your saved fingerprint will disappeare if u reboot your phone ... Only goodix has this problem not fpc... At least on mine goodix ?
Lagfix.zip i guess it's optional, because from my experience it's already smooth even without lagfix patch
For camera actually it already work even u just flash vendor.img sGSI and post 123, but the cam will take a minute to open... The bug just like our dev bringup custom rom nougat before, if u see the log u can see mm-qcamera-daemon crashes..., That's all from my experience on my country volte is not available so i don't have experience to explain ?
ndzaky said:
Agree it's helpful. And I already report it. cc @engloa
Click to expand...
Click to collapse
Moved :good:
Sorry guys for this I wasn't aware of that
I truely apologize for posting at wrong place
actully my main moto was to make this guide as simple as possible so i dont added extraction of vender image,
and added those steps which are more familier to end user so users wont freak out...
actully i installed gsi images before thats why it wasnt nessesary at this time so i forget to add that
thanks for reporting i will note that
actully i added lagfix so that if anyone use future images like pr1 they dont face any issue it is not nessesary for dp5 but listed to be future proff
actully i own 2gb+16gb version so couldn't verify that but listed for prime users just in case.......
and talking about volte i accidentaly damaged my bands while thermal repesting opration
so can't confirm that to lol....
at last thanks for taking interest and giving time for this post .....................have a great day
zainifame said:
Actually u can flash vendor.img directly then sGSI or sGSI first doesn't matter, for vendor.img just extract it from treble rom that u choose, after that u will need to decompress it from brotli ".br" extension..., Here's the link for brotli official software https://github.com/google/brotli/releases
Type from cmd "brotli -d vendor.new.dat.br" then you will get ".dat" extension, to convert it to ".img" use this script https://github.com/xpirt/sdat2img just run "./sdat2img.py vendor.transfer.list vendor.new.dat vendor.img" or from windows "python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img"
If after u reboot then stuck at "asking password for decrypt or whatever i forgot it exactly" just go to fastboot then type "fastboot -w" this will wipe your data and cache off course internal too ... But this will let u to boot to home screen, FBE_Disabler.zip from erfan will not work for us because our device using fde not fbe
And about fingerprint there's no need to flash any patch because fingerprint already work for goodix or fpc, the problem is your saved fingerprint will disappeare if u reboot your phone ... Only goodix has this problem not fpc... At least on mine goodix
Lagfix.zip i guess it's optional, because from my experience it's already smooth even without lagfix patch
For camera actually it already work even u just flash vendor.img sGSI and post 123, but the cam will take a minute to open... The bug just like our dev bringup custom rom nougat before, if u see the log u can see mm-qcamera-daemon crashes..., That's all from my experience on my country volte is not available so i don't have experience to explain
Click to expand...
Click to collapse
GUYS as i am on strictly bed rest now i have lot of time to test new mods on android p
if you have any ideas let me know
i will definately try those..........
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Kuchayhilal said:
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Click to expand...
Click to collapse
Strange ......try enabling gesture key
Kuchayhilal said:
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Click to expand...
Click to collapse
Strange ......try enabling gesture key
Kuchayhilal said:
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Click to expand...
Click to collapse
Is VoLTE working for you?
paarkhi said:
Is VoLTE working for you?
Click to expand...
Click to collapse
Yes, i flashed that VoLTE fix.
Kuchayhilal said:
Yes, i flashed that VoLTE fix.
Click to expand...
Click to collapse
Any major bugs? it's for a friend....
paarkhi said:
Any major bugs? it's for a friend....
Click to expand...
Click to collapse
I just used it for few hours, everything was working after flashing all the bug fixes.
Only problem was with on screen navigation keys, they aren't their.
Is this and the final Android Pie stable release the same?
Nevermind, I see it's not.
Kuchayhilal said:
I just used it for few hours, everything was working after flashing all the bug fixes.
Only problem was with on screen navigation keys, they aren't their.
Click to expand...
Click to collapse
Flash without volte fix,navi bar working for me..just try
I have tried the guide step by step carefully but with the final Android P image instead of DP5 and it's not booting.
Has someone been able to boot it? I'm stuck at the MI logo.
epraes said:
I have tried the guide step by step carefully but with the final Android P image instead of DP5 and it's not booting.
Has someone been able to boot it? I'm stuck at the MI logo.
Click to expand...
Click to collapse
I was able to boot final Android P Image but volte was not working so i revert back to MIUI.
Did all exactly as mentioned. Stuck at boot logo.
Root as well as Recovery galaxy a6plus (android pie).
REQ.
1-patched boot image.- https://drive.google.com/uc?id=1-d8HhTMc60cA3DExKe4xyUo2falMxeKf&export=download
2-Moded Recovery.- https://drive.google.com/file/d/10-3tGazfnt2RHZNkyx_RjmOn5YhChmkD/view?usp=drivesdk
3-Force Encryption Disabler.- https://drive.google.com/uc?id=1R7QyqUE4kadiCNciEDtcvJIoUSfFD7Ng&export=download
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
PLESAE BACUP ALL YOUR DATA BEFORE ROOTING AS AFTER ROOTING YOU WOULD HAVE TO RESTORE YOUR DEVICE ONCE.
AND make sure repartition is turned of in odin all the time.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1===ROOT
>turn oem unlocking on
>enter download mode and flash AP_a6plte_pie_root.img in AP SECTION.
>factory reset required at first boot do it.
>download and install latest magisk manager enjoy.
[WARNING =dont set any password,pin OR pattern on your device because it will give error of wrong pattern even if you try to unlock with the correct patern AND you cant login to your samsung account. {trying to solve these problems in next update}
2==RECOVERY
{
"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"
}
>enter download mode and flash a6plte_ONE_UI_TWRP.tar
>dont let system boot at first boot instead directly boot into TWRP
>change file system of data partition to fat and then back to exfat4
>again go to reboot and reboot to recovery and flash a6plte_PIE_Force_encryption_Disabler.zip
>wipe data reboot enjoy.
NOTE====PLEASE ROOT BEFORE FLASHING TWRP.
DM ME TO JOIN.
Parthkarmur said:
trying to solve these problems in next update
Click to expand...
Click to collapse
So your whole thing is useless? Rooting and installing TWRP was already possible, the problem was the lockscreen thing. Pretty pointless post if its not fixed.
pandavova said:
So your whole thing is useless? Rooting and installing TWRP was already possible, the problem was the lockscreen thing. Pretty pointless post if its not fixed.
Click to expand...
Click to collapse
Just try the recovery i uploaded once.(I recompiled IT)
And did we have force encryption disabler before for android pie?
====
one more thing i am working on knox right now if anybody intrested can help me link
https://forum.xda-developers.com/ga...inally-samsung-cheks-knox-bootloader-t3937529
My question is: Did you fix the thing that broke the lockscreen and the Samsung Account?
If not: Why did you rebrand TWRP when we already have a TWRP for the A6+ and why did you pretty much copy ashyx's Oreo Forced encryption disabler? You changed something in the fstab file and you removed ashyx's name in the updater-script.
Is there a problem with rooting a6+? That lockscreen etc?
joker.lg said:
Is there a problem with rooting a6+? That lockscreen etc?
Click to expand...
Click to collapse
Yes that problem does exists but if you have mistakenly set a password or pattern you can do this
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find) in TWRP RECOVERY:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Is it possible to get the device tree used to build this TWRP ?
Thank you in advance !
Parthkarmur said:
Yes that problem does exists but if you have mistakenly set a password or pattern you can do this
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find) in TWRP RECOVERY:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
I just want to know how to root a6+ without facing any problems? Or if i root with magisk which problems i will face ?
(I am not newbie for rooting but when i read comments i want to do it properly )
joker.lg said:
I just want to know how to root a6+ without facing any problems? Or if i root with magisk which problems i will face ?
(I am not newbie for rooting but when i read comments i want to do it properly )
Click to expand...
Click to collapse
In pie update samsung has used some new security method even if you flash custom kernal or you have
Set warrenty bit kernal . Elwarning you will not be able to login to samsung account even if you are not rooted.
And if you restore a data bacup of oreo using twrp
All the data would get restored except the samsung account.
Even when modifying a single file in sytem partition and then restoring stock bootimage(i.e. unrooting) would land you in boot loop
Parthkarmur said:
In pie update samsung has used some new security method even if you flash custom kernal or you have
Set warrenty bit kernal . Elwarning you will not be able to login to samsung account even if you are not rooted.
And if you restore a data bacup of oreo using twrp
All the data would get restored except the samsung account.
Even when modifying a single file in sytem partition and then restoring stock bootimage(i.e. unrooting) would land you in boot loop
Click to expand...
Click to collapse
Thank you for information. This is horrible samsung account not usable so we cannot use any rom except original ??
Parthkarmur said:
In pie update samsung has used some new security method even if you flash custom kernal or you have
Set warrenty bit kernal . Elwarning you will not be able to login to samsung account even if you are not rooted.
And if you restore a data bacup of oreo using twrp
All the data would get restored except the samsung account.
Even when modifying a single file in sytem partition and then restoring stock bootimage(i.e. unrooting) would land you in boot loop
Click to expand...
Click to collapse
I have 2 question ;
1)if i flash oreo official software than root my phone and use tnt rom will i lose Samsung account?
2) lets say i did #1 and i wanted to use official pie will i face any problem bcz of old root ?
joker.lg said:
I have 2 question ;
1)if i flash oreo official software than root my phone and use tnt rom will i lose Samsung account?
2) lets say i did #1 and i wanted to use official pie will i face any problem bcz of old root ?
Click to expand...
Click to collapse
1. No you can log in to your samsung account in oreo even if you are rooted
2.You will not face any problem unless your pie is rooted.
3. Be carefull you can trip knox(if its still not triped).
Parthkarmur said:
1. No you can log in to your samsung account in oreo even if you are rooted
2.You will not face any problem unless your pie is rooted.
3. Be carefull you can trip knox(if its still not triped).
Click to expand...
Click to collapse
your fstab still can trigger dm-verity...
/dev/block/bootdevice/by-name/system / ext4 ro,errors=panic wait,verify
should only "wait" without coma and verify
Im just sharing, im currently testing Plus version.
Pixel Experience 12 Renoir | OFFICIAL | Android 12 | Updated: 20220715
Instructions here and summary:
Unlock bootloader
Stock MIUI MANDATORY:
Included 13.0.4.0 firmware, so you don't need to flash it manually
(According to Xiaomi, all the fastboot roms are safe to upgrade and downgrade with xiaomi flash or console flash, also, if the rom dont have de fastboot file [e.g. fastboot.exe], you must to get it, maybe with sdk platform tools)
Into Fastboot (adb reboot fastboot or power off / reboot and press power + vol -)
fastboot flash vendor_boot this.img
fastboot flash boot recovery_file_from_rom_url.img
fastboot reboot recovery
Factory Reset, then Format data / factory reset
Return to Main and Apply update > ADB sideload
from pc terminal: adb sideload rom.zip
Back arrow in the top left of the screen, then “Reboot system now”
Enjoy
Latest buildJuly 15, 2022 19:44
MaintainersPatryk Zimnicki
{
"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"
}
Any idea why do we need to use the provided vendor_boot image? Since i have used the rom just flashing the system partition.
razor_1911 said:
Any idea why do we need to use the provided vendor_boot image? Since i have used the rom just flashing the system partition.
Click to expand...
Click to collapse
From the wiki
Warning: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Click to expand...
Click to collapse
Installed flawlessly in a jp versión, even the original base firmware was the jp not te eu provided and the ROM works fine, I notice some upgrade on bass from the speakers, It sounds awesome, I've nevea used Pixel roms so I dunno if Is normal to miss the autobrightness icon on settings panel, battery works pretty nice, alarms, sounds, vibrations, all works fine. Thanks to the dev.
Installed flawlessly also. But unfortunately, Wi-Fi did not work. After booting up, it hangs for quite long time searching for wi-fi networks until it quits and the wi-fi slider moves to the left. I chose to use carrier data to finish setting up my renoir phone, and then tried every trick possible to get wi-fi working, to no avail.
Then flashed DotOS... same story.
Had to go back to Xiaomi.EU rom.
maralvar71 said:
Installed flawlessly also. But unfortunately, Wi-Fi did not work. After booting up, it hangs for quite long time searching for wi-fi networks until it quits and the wi-fi slider moves to the left. I chose to use carrier data to finish setting up my renoir phone, and then tried every trick possible to get wi-fi working, to no avail.
Then flashed DotOS... same story.
Had to go back to Xiaomi.EU rom.
Click to expand...
Click to collapse
You need to flash V12.5.7.0.RKIEUXM Stable firmware before installing PE.
DanielTheHam said:
You need to flash V12.5.7.0.RKIEUXM Stable firmware before installing PE.
Click to expand...
Click to collapse
Can't do. I'm on stock renoir_global_images_V13.0.4.0.SKIMIXM_20220412, Miui13. I might brick the phone because of ARB.
What is ARB?
And i have question also about Magisk is it possible to be rooted?
maralvar71 said:
Can't do. I'm on stock renoir_global_images_V13.0.4.0.SKIMIXM_20220412, Miui13. I might brick the phone because of ARB.
Click to expand...
Click to collapse
If you're worried just flash stock V12.5.7.0 and start the installation process from there.
razor_1911 said:
And i have question also about Magisk is it possible to be rooted?
Click to expand...
Click to collapse
Maybe, just install TWRP and flash magisk
Steps and Link
I am on xiaomi.eu miui 13 version right now and I can't downgrade because my ARB is 1. Stock 12.5.7.0 EEA is ARB 0. Is there any fix to change that and downgrade without bricking my phone?
------------------
Nevermind. I just edit install script file.
I was on 13.0.4 global
Unlocked bootloader
Installed 12.5.7 full stock
After that all by instructions
All went smoothly no problems
So far works fine, thanks allot
Found a bug, after a while maybe like a 5-6 days, the phones does not ring or vibrate when ringing. After a restart is the same again, probably that vendor image is broken.
How is the SoT / battery? Better than miui or similar?
Personally, I installed it 1 week ago, and at first glance, everything worked flawlessly.
I was actually amazed of how good it worked! Until..
I realised the battery was.. TERRIBLE.
The battery don't lasts a lot, and for some reason, when i don't use my phone (sleep mode + airplane mode), It uses 20-30% for.. nothing.
I'm probably going to switch to LineageOS.
razor_1911 said:
And i have question also about Magisk is it possible to be rooted?
Click to expand...
Click to collapse
It indeed can be rooted, personally to root it i used a tool to get all the .imgs of the ROM, and patch it, then reflash.
If you are scared about that, TWRP should work just fine too.
Lolo280374 said:
It indeed can be rooted, personally to root it i used a tool to get all the .imgs of the ROM, and patch it, then reflash.
If you are scared about that, TWRP should work just fine too.
Click to expand...
Click to collapse
yeah i rooted it by the provided boot image in magisk, thanks.
Lolo280374 said:
Personally, I installed it 1 week ago, and at first glance, everything worked flawlessly.
I was actually amazed of how good it worked! Until..
I realised the battery was.. TERRIBLE.
The battery don't lasts a lot, and for some reason, when i don't use my phone (sleep mode + airplane mode), It uses 20-30% for.. nothing.
I'm probably going to switch to LineageOS.
Click to expand...
Click to collapse
Same here, but I do this after flash a new rom and battery drain ok
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I used to 13.0.4 global rom
Installation complete according to the guide
but recieved phone number is two number overlap
Had to go back to global rom
Performance test software:
- Install and Use DSU Sideloader with double speed of Stock A11. (may be the next thread separately) --> Howto install DSU Sideloader with CustomROM or A13 GSIs. very happy to test new A13 GSIs.
{
"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: https://sourceforge.net/projects/thegsis/files/PixelExtended/
**Use this variant> PixelExtended-13-arm64_bgN-UNOFFICIAL.img.xz Only
Why?
supported - R/W system , exFAT , Auto Screen Brightness, Offline-charging and much more features than Pixel Experience
Howto install this GSI.
1. Use TWRP's Fastboot
2. Use CustomAP md5.tar with Odin.
Howto TWRP's Fastboot.
2. Use CustomAP md5.tar with Odin.
**Test with A11 SM-T225
** Now i used only CustomAP Making for flashing with Odin , No TWRP ' s Fastboot flashing any more. (Except: want to dirty flash update GSI)
using Magisk v24.3 patch (boot + vbmeta) flash at USER DATA Slot.
First boot must connects internet and update magisk.
When opening the Magisk App, does a popup with "Additional Setup needed" confirm that, it'll reboot and it should be fully installed.
Live Wallpaper Home Screen
Fix the wrong Taskbar height.
https://github.com/Coxxs/hide-tablet-taskbar/releases/tag/1.0
download and install this module >magisk-pe-taskbar-fix-hide.zip
hide: Long press taskbar to completely hide it (for Android 12.1+)
Long press bottom of the screen (when not in desktop) to show taskbar again
In PixelExperience ROMs, hiding the taskbar pill also fixes the problem of not being able to add icons to the desktop
Custom Extension Features from PE
Coinfigured with Treble Phh setting for GSI bug fix.
Such as > set double tap to wake
Install Google Search and update software after disable some apps.
Install Root File Manager App. For edit R/W System.
Face unlock works
offline-charging
It's help for breaking Samsung " Warrant bit " Stop state , which you can use power-off button to restart device normally.
( This feature did not have generally in all GSIs)
its work properly on samsung tab a7 lite?
please reply.
nitin_42 said:
its work properly on samsung tab a7 lite?
please reply.
Click to expand...
Click to collapse
pictures from my DSU Sideloader On Tab 7 Lite SM-T225
hi, my model is the t225 T225OWO1BVGC_ZTO has Android 12, can I still downgrade? analyzing this information here below, is it possible? can you tell?
tuelho_post said:
hi, my model is the t225 T225OWO1BVGC_ZTO has Android 12, can I still downgrade? analyzing this information here below, is it possible? can you tell?
Click to expand...
Click to collapse
Didn't unlocked bootloader? if so can't downgrade.
tom.android said:
Didn't unlocked bootloader? if so can't downgrade.
Click to expand...
Click to collapse
now it is unlocked, but I have the rom T225XXU1BVGB_T225OWO1BVGC_ZTO
can i downgrade
tuelho_post said:
now it is unlocked, but I have the rom T225XXU1BVGB_T225OWO1BVGC_ZTO
can i downgrade
Click to expand...
Click to collapse
yes but your download mode show bootloader locked? please recheck.
tom.android said:
yes but your download mode show bootloader locked? please recheck.
Click to expand...
Click to collapse
no, now it is unlocked. see below
tuelho_post said:
no, now it is unlocked. see below
Click to expand...
Click to collapse
ok
tom.android said:
ok
Click to expand...
Click to collapse
Could you point me to the twrp that works on this model t225 (with LTE) and android 11? (I downgraded and I'm on android 11)
So much better than any stock currently available for this device better than a11 and a12 ... OneUi is just a pile of junk please make bunch of CustomAP''s for all variants this gsi is highly recommended I'm running it and feels so snappy and nice to use installed via DSU-Sideloader with a11 as base I hope someone makes customAP for both a11 and a12 XAR wifi only variant thanks to Tom for pointing out this new godie and all his testings
tom.android said:
ok
Click to expand...
Click to collapse
Hello Sr. One question using a11 or a12 as base for the customAP?
here my 2 cents disabling all animations and blurs in developers options and setting skiavl as default hi render using vulkan all works and very smooth and fast and less CPU usage and heating
ozmage said:
Hello Sr. One question using a11 or a12 as base for the customAP?
Click to expand...
Click to collapse
A11 Based can install much more GSIs and used storage less than A12.
for me storage is critical problem for SM-T22x
tom.android said:
A11 Based can install much more GSIs and used storage less than A12.
for me storage is critical problem for SM-T22x
Click to expand...
Click to collapse
Mtp works ?
ozmage said:
Mtp works ?
Click to expand...
Click to collapse
No
Aye , offline charging works but don't wake up on power button to see the % don't know if is because not flashed in the real partition or not , anyone has tried flashing the system.img of a gsi directly from the side loaded dsu I'm thinking on doing that on termux with dd if= of= maybe it does work maybe not and I end with soft brick tab XD
ozmage said:
Aye , offline charging works but don't wake up on power button to see the % don't know if is because not flashed in the real partition or not , anyone has tried flashing the system.img of a gsi directly from the side loaded dsu I'm thinking on doing that on termux with dd if= of= maybe it does work maybe not and I end with soft brick tab XD
Click to expand...
Click to collapse
work well when normal installation , all features came (derived) from PE+ except read/write system .
can you test derpfest 13
Difficul said:
can you test derpfest 13
Click to expand...
Click to collapse
not booted but ForkLos-13 works well but not supported exFat