I think we need some clarifications about the anti-brick procedure.
Now i'm on eu miui 11.0.2.0 android 9 with twrp and magisc. Let's say i flash preloader and ik.
Question 1- will i still have twrp or do i have to flash it again?
Q 2 - will i be able to enter miui or do i have to flash it again?
Q 3 - if i want to flash stock miui how can i do it without risking overwriting the preloader?
Q4 - i read that after flashing preloader i have to flash indian vendor,is that true? If yes,where can i find it,and will it work with my eu version?
Q5 - will i be able to flash the custom roms that are android 10 or will i have issues?
I think many users have these questions and would be very helpfull to have some answers.
Regards
Ok, until I understand you don't have flashed the preloader ? I am not a expert but in my case I have flashed the preloader, them lrtwrp ( root and close avb) and everything works fine.
Q1: flashing preloader and lk don't affect recovery but the way to enter recovery and fastboot change.
Q2: preloader don't affect current miui rom ( only Android 9)
Q3: good question? I want know too ?
Q4: it's not true, I flashed preloader using Indonesian rom without issues ( Indian vendor is for custom ROMs)
Q5: in every thread of custom rom developer recommend flashing preloader before of all.
I am not a developer but have some experience, if someone think I am wrong let me know, I talked with my only experience.
djzero86 said:
Ok, until I understand .......
with my only experience.
Click to expand...
Click to collapse
Thanks for thw answer.that was really helpful.
I have a backup tha i created months ago. after flashing preloader,will i be able to restore the backup without overwriting the the preloader? I mean is the stock preloader and ik stored inside the system and data backup?if it is stored somwhere else i guess,not in buckup,i should have no problem right?
ariber14 said:
Thanks for thw answer.that was really helpful.
I have a backup tha i created months ago. after flashing preloader,will i be able to restore the backup without overwriting the the preloader? I mean is the stock preloader and ik stored inside the system and data backup?if it is stored somwhere else i guess,not in buckup,i should have no problem right?
Click to expand...
Click to collapse
This depends if you backup contain those partitions, I think the most recommended is making a new backup :good:
ariber14 said:
Thanks for thw answer.that was really helpful.
I have a backup tha i created months ago. after flashing preloader,will i be able to restore the backup without overwriting the the preloader? I mean is the stock preloader and ik stored inside the system and data backup?if it is stored somwhere else i guess,not in buckup,i should have no problem right?
Click to expand...
Click to collapse
Assuming you are talking about a TWRP backup (I dont exactly see how it could be different but in case) to backup those partitions (they are their own partitions not part of system or data or boot or whatever), you actually need to manually select those partitions IF available for pickup (not always the case depending on devices and TWRP versions). If you only backed-up the usually recommended partitions being system, data and boot then no you do not risk to override anything from my understanding of things (please tell me wrong if I am).
About Q3 which was not previously answered:
If you manually flash that stock using fastboot method, you simply skip those 3 preloader partitions.
You can also remove those 3 partitions from the zip you previously downloaded if present. If not present you are safe.
About Q5 from my understanding the preloader fix thing is working for anything Android 9 based, stock or roms. Which means you are safe flashing Android 9 based roms. As for Android 10 based roms, well I guess you are back to normal bricking. This is only a safenet, you dont risk to brick anything if you follow the procedures properly as describe in first posts of all roms or things.
Hope this helps.
Excuse me but I need help is I will downstate to miui 11
I'm on miui 12.0 6.0 global my phone is global version
I will downgrade to miui 11.0.6.0 is it compatible
{
"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"
}
ariber14 said:
I think we need some clarifications about the anti-brick procedure.
Now i'm on eu miui 11.0.2.0 android 9 with twrp and magisc. Let's say i flash preloader and ik.
Question 1- will i still have twrp or do i have to flash it again?
Q 2 - will i be able to enter miui or do i have to flash it again?
Q 3 - if i want to flash stock miui how can i do it without risking overwriting the preloader?
Q4 - i read that after flashing preloader i have to flash indian vendor,is that true? If yes,where can i find it,and will it work with my eu version?
Q5 - will i be able to flash the custom roms that are android 10 or will i have issues?
I think many users have these questions and would be very helpfull to have some answers.
Regards
Click to expand...
Click to collapse
Bro help me look down
Related
TWRP 3.1.1 Moto G4/G4 Plus (athene)
{
"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"
}
TWRP changelog : Here
Working/Bugs : Lemme knoe if anything broken
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :twrp-3.1.1-0-O1-athene
Tree : Here
XDA:DevDB Information
twrp-athene, Tool/Utility for the Moto G4 Plus
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2017-10-07
Last Updated 2017-10-06
is this the recommended twrp for flashing O builds?
blowingoff said:
is this the recommended twrp for flashing O builds?
Click to expand...
Click to collapse
You can use it for N or O. No issues.
It says encryption is enabled!
Does that mean the problem where in the custom recovery couldn't mount anything when the device was encrypted, is solved with this??
Earlier I did need to do a factory reset from the stock recovery and then do anything on TWRP.
abhi212b said:
It says encryption is enabled!
Does that mean the problem where in the custom recovery couldn't mount anything when the device was encrypted, is solved with this??
Earlier I did need to do a factory reset from the stock recovery and then do anything on TWRP.
Click to expand...
Click to collapse
Oreo roms always says Encrypted but I've never noticed true encryption.
HueyT said:
Oreo roms always says Encrypted but I've never noticed true encryption.
Click to expand...
Click to collapse
No not this one! I am talking about the situation when i encrypt the phone! Once the phone is encrypted the custom recovery fails to read /data.. which leads to no flashing or anything else, until i factory reset the device via stock recovery!
I will try it out anyway!
Thanks brother! I can confirm it works perfectly on device protected with encryption !!
Sorry i couldn't understand the first important note. Will i lose data if i allow system modifications? As far as i remembered this option also shows on previous versions and ive always given permission to modify. Is this the same?
u_knw_who said:
Sorry i couldn't understand the first important note. Will i lose data if i allow system modifications? As far as i remembered this option also shows on previous versions and ive always given permission to modify. Is this the same?
Click to expand...
Click to collapse
Unless you do anything to system (for eg :wipe) allowing system modifications will not harm.
abhi212b said:
It says encryption is enabled!
Does that mean the problem where in the custom recovery couldn't mount anything when the device was encrypted, is solved with this??
Earlier I did need to do a factory reset from the stock recovery and then do anything on TWRP.
Click to expand...
Click to collapse
Yes.
rahulsnair said:
Yes.
Click to expand...
Click to collapse
Got it! Tried it yesterday! Thanks!
No offense, but there's already an official 3.1.1 version of TWRP out there... https://dl.twrp.me/athene
Shahbaz_23 said:
No offense, but there's already an official 3.1.1 version of TWRP out there... https://dl.twrp.me/athene
Click to expand...
Click to collapse
The official version can't use some Motorola configurations because their politics. TWRP unofficial can use that configurations, allowing to decrypt and encrypt /data. In summary, unofficial is better.
I think I can't format /data with F2FS. The option doesn't appear in TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TEAM WIN
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD
TWRP 3.2.1-0 v2
CHANGELOG
TWRP Changelog
INSTRUCTIONS
From fastboot:
Code:
fastboot flash recovery filename.img
From TWRP:
- Install>Flash Image>"Select the recovery to flash">Swipe To flash>Reboot Recovery
NOTE: If the recovery asks you for a password, you have to erase the /data partition. So press "Cancel" and then Wipe>Format Data>"yes" to fully decrypt your phone. Note that a decrypted phone will boot more faster and will improve the FS speed.
THIS WILL ERASE YOUR INTERNAL STORAGE
F.A.Q
Q: Can i flash MIUI ROMS with this recovery?
A: Yes, you can. If you flash an official MIUI ROM, you have to flash Magisk or Boot Image Patcher too, to disable the dm-verity and forced encryption.
Q: Can i flash custom ROMS with this recovery?
A: Yes, you can. This recovery is Oreo ready too.
Source Code: GitHub
Just thanks @Psy_Man, you are the best bringing news for MI Note 2.
And as always waiting for Oreo.
Works just fine on my Mi Note 2. Thank you!
Nice to see the new Twrp on our device. Thank you very much and keep up the good work !
Do i need to format it in order to decrypt?
Andrikkos said:
Do i need to format it in order to decrypt?
Click to expand...
Click to collapse
Yes! Backup your data first!
Nice ! The new version is already up ! Thank you for all the work you are doing , you are amazing !
You are the best @Psy_Man thank you very much.
3.2.1 cant load ..
Andrikkos said:
3.2.1 cant load ..
Click to expand...
Click to collapse
Broken download. Check the md5 before flashing somethimg.
Pixel Expiriance
When are you making that rom working ?
dont work for me ...
reboot on recovery ok , fastboot ok but no reboot on rom ???
dglingos said:
dont work for me ...
reboot on recovery ok , fastboot ok but no reboot on rom ???
Click to expand...
Click to collapse
What?
I'm having problems flashing official roms trought recovery, I don't know why. It seems to flashing ok but when the phone reboots it doesn't loads it got stucks at MI logo and nothing happens. Does anybody has this problem?
jorvacf said:
I'm having problems flashing official roms trought recovery, I don't know why. It seems to flashing ok but when the phone reboots it doesn't loads it got stucks at MI logo and nothing happens. Does anybody has this problem?
Click to expand...
Click to collapse
As i know , PsyMan said in the thread that when you install the official rom you need to flash either Magisk either Boot Image Patcher for it to boot.
Hi, this twrp version asks for a password (for decrypt purpose) ; why ? There was no password prompted in 3.1.0.0 .. My Mi Note 2 is not encrypted and obviously I don't want to format /data.
niczob said:
Hi, this twrp version asks for a password (for decrypt purpose) ; why ? There was no password prompted in 3.1.0.0 .. My Mi Note 2 is not encrypted and obviously I don't want to format /data.
Click to expand...
Click to collapse
Then flash 3.1.1 again and problem solved. Also , your data is password protected and everytime you start your rom it has to take some time to "unlock" your data partition. This way , if you format woth the new twrp, you will have a great increase in bootup speed.
alexmanu1 said:
As i know , PsyMan said in the thread that when you install the official rom you need to flash either Magisk either Boot Image Patcher for it to boot.
Click to expand...
Click to collapse
Let me see if I understand, I need to flash magisk and also boot imagen patcher? Where can I get this last one (boot imagen patcher) and it has to be done after flashing the ROM without restarting it?
jorvacf said:
Let me see if I understand, I need to flash magisk and also boot imagen patcher? Where can I get this last one (boot imagen patcher) and it has to be done after flashing the ROM without restarting it?
Click to expand...
Click to collapse
One of them . I recommend Magisk , don't really know which boot image patcher should we install.
jorvacf said:
I'm having problems flashing official roms trought recovery, I don't know why. It seems to flashing ok but when the phone reboots it doesn't loads it got stucks at MI logo and nothing happens. Does anybody has this problem?
Click to expand...
Click to collapse
I have the same problem
Hello Guys, I was trying to flash stokc firmware for 3 days and the device unable to flash
i'm on unlokced bootloader nad custom rom aosp 9.0 but when i try to back yo miui stock firmware i'm unable to
i've flashed the dummy img and twrp times and times it flash th recovery and the recovery stay but when i try to flash th stock rom using fastboot i can't it keeps closing automatically when run flash_all.bat
i tried mi flash tool but it shows what is in the picture
{
"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"
}
PLS HELP, i Want to revert to the pure stock rom with stock boot and stock recovery
anyhelp plz
NiceIceDice96 said:
Hello Guys, I was trying to flash stokc firmware for 3 days and the device unable to flash
i'm on unlokced bootloader nad custom rom aosp 9.0 but when i try to back yo miui stock firmware i'm unable to
i've flashed the dummy img and twrp times and times it flash th recovery and the recovery stay but when i try to flash th stock rom using fastboot i can't it keeps closing automatically when run flash_all.bat
i tried mi flash tool but it shows what is in the picture
PLS HELP, i Want to revert to the pure stock rom with stock boot and stock recovery
anyhelp plz
Click to expand...
Click to collapse
what version of miui did you had last time.? and wich version are you flashing.? seems ARB is kicking and not letting you flash rom
i had miui 10 and i've tried miui 9 and 10 and none able to flash....pls help
I did the exact same thing 2 days ago. Unlocked boot loader installed some custom roms for testing but i wanted to go back to official MIUI 9 so here is what i did. I have Redwolf TWRP recovery installed so all i did was put the full rom file of MIUI 9.6.4 in internal memory, did a format and wipe and installed it from there. It's working fine now and i am even getting a notification in updater that 10.0.2 is available (but i am not gonna install it because MIUI 10 sucks!)
Follow this tutorial starting from 8 minutes where you get the idea how to go back to MIUI from custom roms. Don't try the Mi Flash Tool method to go back!
https://www.youtube.com/watch?v=7cyzKebbah8
Thank You, I Will Try, Can You Give Me Stock ROM Global Links ?
NiceIceDice96 said:
Thank You, I Will Try, Can You Give Me Stock ROM Global Links ?
Click to expand...
Click to collapse
Here all the Roms links you need (use recovery not fastboot links for downloads) and make sure to read about ARB 3 and ARB 4 versions before messing up things http://en.miui.com/thread-2340434-1-1.html
Only go forward once you are sure about everything be it bypassing ARB, flashing TRWP recovery, using lazyflash file etc because one wrong step and you can endup with a bricked phone.
ALso check this link about bypassing http://en.miui.com/thread-3436592-1-1.html
i had miui 10 before can i flash miui 9...is it ok ?
WaseePK said:
Here all the Roms links you need (use recovery not fastboot links for downloads) and make sure to read about ARB 3 and ARB 4 versions before messing up things http://en.miui.com/thread-2340434-1-1.html
Only go forward once you are sure about everything be it bypassing ARB, flashing TRWP recovery, using lazyflash file etc because one wrong step and you can endup with a bricked phone.
ALso check this link about bypassing http://en.miui.com/thread-3436592-1-1.html
Click to expand...
Click to collapse
i had miui 10 before can i flash miui 9...is it ok ?
NiceIceDice96 said:
i had miui 10 before can i flash miui 9...is it ok ?
Click to expand...
Click to collapse
I also had MIUI 10 but now i am back to 9 so it's ok as long as you install ARB4 versions of MIUI 9 and they start from 9.5.19+ so never ever go for any version below that. I will recommend 9.6.4 (it is the final version of MIUI 9 Global) i am using it from 2 days it's stable and the only issue is battery isn't that good as it was in MIUI 10 but MIUI 10 had several issues so i will wait for a stable MIUI 10 instead of moving back just for battery.
ok, thank you bro much appreciate
NiceIceDice96 said:
ok, thank you bro much appreciate
Click to expand...
Click to collapse
No problem bro
NiceIceDice96 said:
Hello Guys, I was trying to flash stokc firmware for 3 days and the device unable to flash
i'm on unlokced bootloader nad custom rom aosp 9.0 but when i try to back yo miui stock firmware i'm unable to
i've flashed the dummy img and twrp times and times it flash th recovery and the recovery stay but when i try to flash th stock rom using fastboot i can't it keeps closing automatically when run flash_all.bat
i tried mi flash tool but it shows what is in the picture
PLS HELP, i Want to revert to the pure stock rom with stock boot and stock recovery
anyhelp plz
Click to expand...
Click to collapse
I have successfully recover the stock recovery but again not able to put the Customer recovery like TWRP. any help please......
V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.
Thank you for this!
amazing
let's hope something useful comes to the end user
Thanks so much for putting this together. Should I anticipate any issues doing TWRP ADB sideload coming from a Korean rom?
Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
{
"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"
}
smir_ant said:
Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
Click to expand...
Click to collapse
I can download it on windows, it's just extremely slow at 0.5 Mb/s
ghylander said:
I can download it on windows, it's just extremely slow at 0.5 Mb/s
Click to expand...
Click to collapse
yeap, from sative safari (without addblock and another addons) i download too, slow, but success,
thanks for reply
jacob019 said:
V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.
Click to expand...
Click to collapse
Could you reporst the download? I just installed windows 11, so maybe that's the issue, but I keep getting "v350awm30e.zip cannot be downloaded securely." and it refuses to even start the download. Any help would be appreciated.
Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip
jacob019 said:
Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip
Click to expand...
Click to collapse
Thanks for the fast reply here and in a DM. For anyone new to windows 11 like me, if you try to download from any website that doesn't have that S in it (http vs https), it will not let you download. After a quick google, you can still download from places like this by right-clicking on the download and selecting "keep this".
You can also click on the lock icon in the url bar and then going to permissions and selecting the option to download unsecure content from this website.
Cheers.
Hi everyone. Do you know where can I download a stock ATT firmware for lg v35? Mine is network locked and I have the code to unlock it but I have to be on original firmware. Please help me if you can. Thanks
Hello everyone. I currently have a A505W Canadian variant, bootloader unlocked and TWRP installed. I made the big mistake of updating to the last version of android 11 and, while I prefer android 10 for what I need the phone to do, I can't downgrade anymore. I'm trying to install, at that point, any custom rom there is. But I can't. I don't know if it's related, but every time I try to install a rom, with TWRP, I always get the error "Unable to mount '/vendor'" and the installation fail. Some rom get concidered successfully installed, by their custom installations process, but end in a boot loop. All I can do is install the stock firmware with odin. I've been on this for 3 days now, can anybody help me? That would be much appreciated. Have a nice day!
AliasGprime said:
Hello everyone. I currently have a A505W Canadian variant, bootloader unlocked and TWRP installed. I made the big mistake of updating to the last version of android 11 and, while I prefer android 10 for what I need the phone to do, I can't downgrade anymore. I'm trying to install, at that point, any custom rom there is. But I can't. I don't know if it's related, but every time I try to install a rom, with TWRP, I always get the error "Unable to mount '/vendor'" and the installation fail. Some rom get concidered successfully installed, by their custom installations process, but end in a boot loop. All I can do is install the stock firmware with odin. I've been on this for 3 days now, can anybody help me? That would be much appreciated. Have a nice day!
Click to expand...
Click to collapse
{
"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"
}
JuanTamqd21 said:
View attachment 5552791
Click to expand...
Click to collapse
Ok, so if I understand correctly I'll need to find custom roms specific to the A505W? which seem to be VERY rare.
AliasGprime said:
Ok, so if I understand correctly I'll need to find custom roms specific to the A505W? which seem to be VERY rare.
Click to expand...
Click to collapse
So far, only international variants(F and FN) are being built so we don't know if any rom will work on W variants. Maybe try GSI, they are almost the same but they mostly differ in vendor
JuanTamqd21 said:
So far, only international variants(F and FN) are being built so we don't know if any rom will work on W variants. Maybe try GSI, they are almost the same but they mostly differ in vendor
Click to expand...
Click to collapse
Alright, I don't exactly know what it is, but I'll check it out. Thanks for the help!
AliasGprime said:
Alright, I don't exactly know what it is, but I'll check it out. Thanks for the help!
Click to expand...
Click to collapse
yes, you should definitely check GSI and sGSI out. Some of the a50 users manage to boot android 13 dp1 on A50. for GSIs https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
JuanTamqd21 said:
yes, you should definitely check GSI and sGSI out. Some of the a50 users manage to boot android 13 dp1 on A50. for GSIs https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Click to expand...
Click to collapse
I'm on it. I think I found one GSI rom that is working pretty well for now. I need this phone to do a very specific job. I prefers magisk 23 for this since I need magisk hide. So I tend to go with older version of android (10 or 11). Also, the lastest stock firmware was not really up to the task either (got many bugs) and I made the mistake to update my android 10 stock, which was working perfectly, to the last official version of 11, so no downgrade possible for me. I just need to find the right rom for my needs now.
AliasGprime said:
I just need to find the right rom for my needs now.
Click to expand...
Click to collapse
Search XDA for the latest Frija Windows application version. Beyond that, sammobile.com is where I've pulled my provider's stock images for an upcoming downgrade attempt. You should be able find your provider's CSC easily enough elsewhere; you'll need it to pull the proper ROM.
@AliasGprime how did you unlock the bootloader on your A505W? I'm researching this and see only paid options to unlock BL and no one can reach the member who used to unlock.
EDIT: after several attempts, I did finally get the bootloader unlock menu.
Hi,
Just wanted to put this info out there for unlocking bootloader. ( This would wipe your data )
Model A505W
Steps:
Enable OEM Unlock
Power Off
Hold vol-up and vol-down and power button ( As per other tutorials and videos you have to attach charging cable but that did not work for me )
Follow instructions on screen
reboot ( It takes long to reboot as all data is going to be wiped )