Related
A french WM6 rom for Trinity
Version 3.3
Thanks to bepe, Jasjamming, Tadzio for all.
Thanks to LVSW and mUn for their always great work.
Thanks to Ausdim for his help and fix.
Thanks to Olipro and Des for HardSPL
!!!!!!!!!!!!!OS + HardSPL!!!!!!!!!!!!!!!
VERSIONS:
DOWNLOAD v3.3
DOWNLOAD v3.3(Colrou's Mirror)
+ Old Versions, Radios, Fix, and more...
DOWNLOAD v3.3(Ilos's Mirror)
+ Old Versions, Radios, Fix, and more..
FIXES:
See F.A.Q: 2d post
BT Headset VOICE DIAL FIX for all versions (Rebuild)
!!!!!BEFORE UPGRADE, PLEASE REMOVE SD CARD!!!!!
v3.3:
New OS 5.2.1620 Build 18125.0.4.2(Thanks to bepe)
Added: setup operator, sap, gpsinfo, fieldtest, ...
Removed: PocketCM, CP, ...
Updated: new phonepad skin, pim backup 2.5, Duronmarcel Dialer v2.01, remote desktop by VNC viewer, task manager 1.51 (now exclusions work)
Fixed: mp3 trimmer in AM.
IF YOU APPRECIATE MY WORK YOU CAN MAKE A DONATION...
F.A.Q:
When you flash a new ROM, you will loose all your data!!! take this in consideration. So, you will make a full reisntallation of all your personals applications
1: To Enable The 6 Tab: (but the vibrate bug will be back too)
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\HTCHome]
"Tabsetting"="1,2,3,4,5,6"
2: ROM update Error:
-Use XP not Vista
-If you're stuck on bootloader (three colors screen showing IPL: SPL: ), start again update app without removing USB or restart the Phone
3: Startup animation:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\StartupAnimation]
-pour la désactiver totalement, mettre "Enabled"=0
-pour désactiver le volume mettre "Volumn"=127
4: Backup (SPB, ...):
Never restore a FULL backup from another rom version.
5: How to avoid the automatic connexion to the 3G network with the weather plugin?
in HTC home, click on "choisir votre ville ici", "menu", "options météo", and uncheck "téléchargement auto des infos météo", then reset.
6: Can't stop WLM with the X-button?
delete key "WLMMessenger.exe" in HKEY_CURRENT_USER\Software\HTC\TaskManager\APPS
then power off
AT ALL,
WE ARE ON AN ENGLISH FORUM
PLEASE SPEAK ENGLISH...
OR DOUBLE POST.
BIG THANKS.
Can't wait !!!!!! You're the best !
Good idea to create a new forum, the old one was becoming to be unreadable !
can't wait anymore...
can't wait !!!!
We're impatient...how can we waiting now...
Could explain us the difference between the new OS 5.2.1620 Build 18125.0.4.2 on Faman 3.3 and the OS Based on latest official dopod .18 dated 24/07/2007 on Faman 3.2 ?
----------------------------------------------------------------------
Peux tu nous donner les différences entre les OS sur les ROM Faman 3.2 et 3.3 ?
I'm using BEPE's 0.73BETA release since friday and I was waiting for a french release.
I suppose FAMAN 3.3 will be very close to it.
I can say the best improvement for me is that I have no more bug with HTC HOME profile, the phone doesn't go on vibrate on an appointment.
Hope this will be the case in this ROM.
Thaks a lot, FAMAN.
Jimbo78fr said:
Could explain us the difference between the new OS 5.2.1620 Build 18125.0.4.2 on Faman 3.3 and the OS Based on latest official dopod .18 dated 24/07/2007 on Faman 3.2 ?
----------------------------------------------------------------------
Peux tu nous donner les différences entre les OS sur les ROM Faman 3.2 et 3.3 ?
Click to expand...
Click to collapse
Hi, OS build differences concern improvments of Global system and core, in fact a higher version seems a more stable OS but if you really want details you should ask M......T
I test your rom immediately !!
Great job faman you're the best congratulations !!
Congratulation FAMAN !!
It's a nice present !
Thank's a lot great Job
Thank's for the opérator configurator
just some informations :
- what is VNC configuration used for ?
- is it possible to plug a stun SIP in this rom.
- where can we find the Core application (it was very nice in the 3.x)
I'm not shure but i think my problem of charge is fixed
Anyway a big thank's to all the guy's duron marcel , FAman and the other !!!
Thanks a lot, great job, I download and install it right now !!
Let's test it !!!
Peace and keep it up !!
Great, i test !
Installed since 3H now, and everythink seems to work fine...
I'll test it in deep, and write a feedback probably tomorrow...
hi everybody
i install and i tested the last rom 3.3 from 2hours ago !!
Everything is ok Tomtom works, wap sfr is ok !!
the dialer is very nice i don't have any problem for install all my applications
i need to try 2 or 3 days but the rom is a great job
Congratulations faman
En français
Bonjour je viens d 'installer la rom faman 3.3 et je la teste depuis 2 ou 3 heures et tout a l air de marcher nickel
Toutes mes applications marchent tomtom, le wap sfr marche, la rom est assez rapide , on dirait un peu moins que la 3.2 mais a vérifier
Le dialer de Duronmarcel est tres bien fait
pour l instant aucun bug particulier, a tester la perte de clé wep et la perte de compte mail que je vérifierai demain
Tres beau travail Faman comme d'habitude
N'hesitez pas c 'est du beau boulot
Thanks a lot, I just can't wait to test it.
Merci beaucoup, je suis impatient de la tester.
TT6 codes
Before installing this new ROM, I just wanted to know if the 3.3 ROM does initialize the TT6 settings like a previous version I had to give up because of that (I lost the different activation codes and TT does not want to give me another activation & product code).
Thks a lot to FAMAN & XDA forum and its people.
The Extrom
hi Faman,
thnks for the new rom and the fix for audio manager.
do you know which cab i can use in order to see the ext rom, i've tried axl3L cab but it orverwrote your rom!!!
and now i went back to the sfr official rom , i need to unlock the extrom to make some some change... and go back to ur rom.
i need help here,
thanks in advance
Hi,
My problem is simple, when I try to download anything on the play store, there is a very long loading (see attached screenshot) before the download start (some hours), the problem is not coming from my connection, I already contacted Google Play support and tried everything (data/cache deleting for Play store, Play Services and even the device, Google account suppression, dirty flash my firmware, root/unroot etc...) and nothing is working, I already had this problem before and after a full wipe it was gone but I don't really want to wipe everything again... Before to apply this radical method I ask the help of anyone who have maybe another solution.
Infos : - Device : OnePlus 3 A3003
- Firmware : Last Open BETA 28 (Oreo 8.0)
- Root : Yes with Magisk 14.5
- Kernel : Derp Kernel (but problem still here with stock kernel)
Thanks !
I finally wiped everything but the problem came back...
Have you cleared cache for the Google Play store, Services framework and Google Play services? You must do all 3 of them to ensure any change is effective.
Does it only have issues on a certain network/wifi ? Is this the only device that you have, if you have another device is that affected too on the same networks. Most issues on this front could be ISP/DNS related.
cbarai said:
Have you cleared cache for the Google Play store, Services framework and Google Play services? You must do all 3 of them to ensure any change is effective.
Does it only have issues on a certain network/wifi ? Is this the only device that you have, if you have another device is that affected too on the same networks. Most issues on this front could be ISP/DNS related.
Click to expand...
Click to collapse
Of course I already did it several times, it's not Network related I already tried with another WIFI and mobile data and other phones are working great.
cbarai said:
Have you cleared cache for the Google Play store, Services framework and Google Play services? You must do all 3 of them to ensure any change is effective.
Does it only have issues on a certain network/wifi ? Is this the only device that you have, if you have another device is that affected too on the same networks. Most issues on this front could be ISP/DNS related.
Click to expand...
Click to collapse
Oh It worked by wiping Google services Framework too ! Even Google customer service didn't said me to try this
Thanks !
I spoken too early... The delay problem came back few minutes after wiped everything
Same problem on huawei p10+. Anyone been able to resolve this? Hard reset not worked.
Bryandu13 said:
Hi,
My problem is simple, when I try to download anything on the play store, there is a very long loading (see attached screenshot) before the download start (some hours), the problem is not coming from my connection, I already contacted Google Play support and tried everything (data/cache deleting for Play store, Play Services and even the device, Google account suppression, dirty flash my firmware, root/unroot etc...) and nothing is working, I already had this problem before and after a full wipe it was gone but I don't really want to wipe everything again... Before to apply this radical method I ask the help of anyone who have maybe another solution.
Infos : - Device : OnePlus 3 A3003
- Firmware : Last Open BETA 28 (Oreo 8.0)
- Root : Yes with Magisk 14.5
- Kernel : Derp Kernel (but problem still here with stock kernel)
Thanks !
Click to expand...
Click to collapse
Je suis français et j'ai le même soucis
J'ai beau chercher tant que je veux, aucune solution....
I have the impression that it is a problem just French.... I look everywhere I find no solution
lexa06600 said:
Je suis français et j'ai le même soucis
J'ai beau chercher tant que je veux, aucune solution....
I have the impression that it is a problem just French.... I look everywhere I find no solution
Click to expand...
Click to collapse
Ouais c'est très étrange. La seule solution que j'ai trouvé c'était de partir sur une ROM Custom et pendant 2-3 mois aucun problème, ensuite je suis revenu sur OxygenOS dernière beta pour tester le Kernel EAS et le problème est revenu en 2 jours.
Heureusement maintenant ces problèmes sont derrière moi vu que j'ai acheté un Mi Mix 2S.
Bonne chance à toi^^ (seule solution --> ROM Custom).
Et bien justement non, moi mon problème se fait même avec les roms custom, et comme tu dis il faut attendre quelques mois avant que ça se remette
---------- Post added at 04:45 PM ---------- Previous post was at 04:38 PM ----------
English please
@lexa06600 and @Bryandu13
Please use English so that others too understand (XDA Policy).
tnsmani said:
@lexa06600 and @Bryandu13
Please use English so that others too understand (XDA Policy).
Click to expand...
Click to collapse
Nobody answered for 5 months, and the only guy who answer speak French, I think I can answer to him in French
Bryandu13 said:
Nobody answered for 5 months, and the only guy who answer speak French, I think I can answer to him in French
Click to expand...
Click to collapse
Forum Rules
"4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature)."
My post was not to find fault with you but to point out that others also should benefit. When the other member chose to atleast give a translation as per Forum Rules, you did not and continue to justify your action.
Leaked TCL Android TV 8.0 before it is updated on TCL's own website, so if you have a TCL Android TV of model types Percee TV you can injoy Android 8.
Please Note that you have to use USB Port 3 and Not USB Port 2 or you will Problem.
(.........1drv.ms/u/s!AnbGbXJxdf9Bg4Uwth3AFXu8xksloA.......)
Download the file and copy to a blank formatted USB Plug in the format USB drum 32
1. Turn off the TV (power supply - unplug the power cord)
2. Insert the USB stick in USB Port 3
3. Press and hold the power button on the TV: n (not the remote control)
4. Turn on the power to the TV (while pressing the power button)
5. After approximately ten seconds, you see the upgrade message on the TV as soon as you see this, release the power switch.
The TV will now be updated. Do not disconnect or press any buttons until you see the google welcome page. The update is now complete.
I have a USB 3 port and a USB2 port that says service on my TCL 55C2US anyone tried this one yet?
I would love to see if i can give it a bit of an update
How to remove automatic updates?
My tv are TCL U49C7006, and I want android 7 because works with NTFS system, but the Tv always update to android 8....
I dont find in the menu how to disable the updates...
Hi,
I would like to go back to android 7 because after update my TV has bad video quality. it's possible? please help me
The file is not available out there.. can you repost the link plase
wankhade said:
The file is not available out there.. can you repost the link plase
Click to expand...
Click to collapse
Here is the link shared by the developer. It has some versions, including nougat versions (not sure if you can downgrade). Haven't tried any of them yet.
Download Link
You should add to the first message that you have to use an USB 3.0 pendrive to make it work, i've tried many times with an USB 2.0 pendrive and it didn't work.
Is this version compatible with Tcl L55C1CUS Android 5
Firmware
Tcl 49s6800 usb software
I have a TCL 50p1US Smart TV that I know has Android 5.1.1, with this update unlock all the features of a true Android TV?
hi Guys i would need your help. because i realy don't want to brick my tv. i have tcl 55dc760 on android 6.0 i would like to update it to 8.0. can you explane me more detail what should i do?
thank you
the title is misleading, this is obviously not for all tcl (android) tv's.
i found the solution. thank you
Bonjour est ce compatible avec une Tv 55EP640 svp ?
merci par avance.
Mamut321 Comment as tu fait?
lemmej said:
Bonjour est ce compatible avec une Tv 55EP640 svp ?
merci par avance.
Mamut321 Comment as tu fait?
Click to expand...
Click to collapse
No it is not. but i could help you find the way for your TV. which version of android are you running and what software version do you have?
mamut321 said:
No it is not. but i could help you find the way for your TV. which version of android are you running and what software version do you have?
Click to expand...
Click to collapse
Merci beaucoup pour ton aide ma version tv est:
V8-R851T02-LF1V252.011680.
Comment je peut connaître ma version android? comment faire pour vous envoyé la photo?
lemmej said:
Merci beaucoup pour ton aide ma version tv est:
V8-R851T02-LF1V252.011680.
Comment je peut connaître ma version android? comment faire pour vous envoyé la photo?
Click to expand...
Click to collapse
that is enough info. As i see this is curently the newest version from official TCL website. And it is Android 9.0. you can check it here under download and click on software. https://www.tcl.com/eu/en/new-product-list/ep64-series/65--4k-hdr-tv-powered-by-android-tv.html
but as i said curently this is the newest version
merci pour votre retour,
on peut root cette tv? des applications ne sont pas présente sur google play et quand j installe des APK elle ne s installe pas sur la tv.
lemmej said:
merci pour votre retour,
on peut root cette tv? des applications ne sont pas présente sur google play et quand j installe des APK elle ne s installe pas sur la tv.
Click to expand...
Click to collapse
Hi, if you install (to install APK use file explorer. i use FX file explorer) application with APK you should install Sideload Launcher - Android TV and then open launcher and find app and open it. you don't need to root for this
mamut321 said:
Hi, if you install application with APK you should install Sideload Launcher - Android TV and then open launcher and find app and open it. you don't need to root for this
Click to expand...
Click to collapse
Merci Merci je vais essayer et je reviens vers vous encore une fois merci de votre réactivité.
Hi All,
I locked the bootloader of my MI 9SE and after the lock device doesn't start and shows "the system has been destroyed".
I can only enter in fastboot. Is there a possibility to fix it?
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Ok, solved
I relocked the bootloader with Mi Flash by flashing latest global firmware and selecting the option "clean all and lock". It worked.
Just an hint: when a I locked the bootloader I didn't have the MI account associated to the phone, for this reason I thinked that I couldn't unlock again the phone.
This is not true, if you log in in Mi Unlock with the same Mi account you used to unlock the first time it works even if it is not currently associated to the phone
MI9 se - MAJ OTA - le système a été détruit
Bonjour,
le bug s'est produit il y a 1 mois lors d'une maj demandé par XIAOMI, l'écran après le redémarrage a indiqué " the system has been destroyed ", il y avait d'ailleurs dans le répertoire download le fichier : miui-blockota-grus-eea-global-v10.2.9.0.PFBEUXM-v10.3.9.0PFBEUXM-13f0db, c'est donc la maj de MIUI v10.2.9.0 à 10.3.9
Sur xiaomi.eu/community, il est clairement indiqué que c'est un pb provenant du fichier ota, qui date du mois juin, et que xiaomi travaille pour le résoudre. Très bizarrement, sur les discussions, des coches vertes indiquent que le pb est résolu, alors qu'aucune solution n'est proposée !
Il est aussi écrit qu'il faut contacter le SAV XIAOMI, ce que j'ai fais, il m'a demandé de réinitialiser aux paramètres d'usine, mais après le redémarrage, on retrouve " the system has been destroyed " ! Maintenant, il vont vérifier la garantie, a suivre, je vous tiendrai informé.
En attendant, avec miniADB+ fastboot, on arrive a redémarrer, mais en MIUI v10.2.9.0, mais plus de MAJ, et en cas de batterie déchargée, impossible de redémarrer sauf a avoir un ordi avec miniADB+ fastboot.
Je constate :
- MIUI est une surcouche pour ANDROID faite par XIAOMI
- c'est la MAJ de MIUI V10.3.9 qui cause ce problème
- sur MIUI, suite au post indiquant que XIAOMI travaille pour résoudre le pb, aucune solution n'est donné, les discussions sont indiquées comme étant résolus, et puis plus rien
Je pense que la MAJ MIUI a créé un bug dans ANDROID, et qu'il faut réinstaller dans la ROM du téléphone l' opérating systéme complet ANDROID avec MIUI en version 10.3.9 ou supérieure, d'ou des solutions avec MIFLASH, bootlader débloqué, mais toujours su MIUI, des posts indiquent qu'un particulier ne peut plus le faire car XIAOMI veut nous obliger à recourir à son SAV en FRANCE, si ils veulent bien, généralement le téléphone renvoyé n'est pas le votre, et probablement avec des tarifs exorbitants,
A se demander si XIAOMI est toujours fidèle à lui même !
Tous vos avis, réactions et commentaires seront les bienvenus,
Cordialement
ErriK89 said:
Ok, solved
I relocked the bootloader with Mi Flash by flashing latest global firmware and selecting the option "clean all and lock". It worked.
Just an hint: when a I locked the bootloader I didn't have the MI account associated to the phone, for this reason I thinked that I couldn't unlock again the phone.
This is not true, if you log in in Mi Unlock with the same Mi account you used to unlock the first time it works even if it is not currently associated to the phone
Click to expand...
Click to collapse
hi,
it's a long time but after you relocked the bootlooader with mi flash, can you use netflix and google pay?
thanks
Errik 89 can u help me to unlock k20 pro
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
Errik 89 can u help me to unlock k20 pro
ErriK89 said:
Ok, solved
I relocked the bootloader with Mi Flash by flashing latest global firmware and selecting the option "clean all and lock". It worked.
Just an hint: when a I locked the bootloader I didn't have the MI account associated to the phone, for this reason I thinked that I couldn't unlock again the phone.
This is not true, if you log in in Mi Unlock with the same Mi account you used to unlock the first time it works even if it is not currently associated to the phone
Click to expand...
Click to collapse
Hey, @ErriK89 how could you unlock the bootloader on a device showing "the system has been destroyed"?
I am facing the same issue, access possible only with "fastboot" but I am unable to flash anything.
MasterLog80 said:
Hey, @ErriK89 how could you unlock the bootloader on a device showing "the system has been destroyed"?
I am facing the same issue, access possible only with "fastboot" but I am unable to flash anything.
Click to expand...
Click to collapse
Hi, sry for late answer. It's easy: use the same procedure you use as you are unlocking the bootloader with the phone normally working.
Open Mi flash unlock and follow the procedure, enter the MI account you used to unlock the phone for the first time.
ErriK89 said:
Hi, sry for late answer. It's easy: use the same procedure you use as you are unlocking the bootloader with the phone normally working.
Open Mi flash unlock and follow the procedure, enter the MI account you used to unlock the phone for the first time.
Click to expand...
Click to collapse
Thanks @ErriK89,
I have tried to unlock by using "Mi Unlock" but per attached screenshot and I can't proceed.
I used the same account on the phone before the issue occurred, but I have never any related settings: I think you may have done something before (probably you have requested to unlock the bootloader per 3 and 4 on https://c.mi.com/thread-1857937-1-1.html ????).... Did you?
Regards,
Hello guys,
I am still unable to unlock the device or reinstall a new OS.
Most likely if the bootloader wasn't unlocked (before) by the phone, it will stay lock and it's not possible to restore the OS.
Any suggestions welcome.
Regards,
Hello guys,
After a lot of investigation I come to the conclusion that to fix the issue "the system has been destroyed" in a device unable to start on recovery and with bootloader locked, it's required a Xiaomi authorized account, which is NOT provided to normal users.
Then, it's possible to proceed with "Mi Unlock" or "SP Flash tool" to reinstall the firmware.
I have seen that some guys connect by remote with their account for money, it may worth a try.
Regards,
MasterLog80 said:
Hello guys,
After a lot of investigation I come to the conclusion that to fix the issue "the system has been destroyed" in a device unable to start on recovery and with bootloader locked, it's required a Xiaomi authorized account, which is NOT provided to normal users.
Then, it's possible to proceed with "Mi Unlock" or "SP Flash tool" to reinstall the firmware.
I have seen that some guys connect by remote with their account for money, it may worth a try.
Regards,
Click to expand...
Click to collapse
Hello,
I have same error, I tray many ways, but bootloader is locked.
How are you doing? unlock your bootloader?
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
Hey bro i brick my 9 se, please help me add me on Facebook:
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
Hey bro help me i brick my 9 se
Contact me please:
Gian Quispe Mendoza
Gian Quispe Mendoza is on Facebook. Join Facebook to connect with Gian Quispe Mendoza and others you may know. Facebook gives people the power to share and makes the world more open and connected.
www.facebook.com
Guys, if in your phone the bootloader was already unlocked before to re-lock it or to obtain the error "system has been destroyed" it can be easily fixed by unlocking it again. It's just sufficient to use Mi Unlock tool, log-in with the account with which the bootloader was unlocked and unlock it. Once unlocked you can use MiFlash to flash the latest rom and if you neet to safely re-lock the bootloader.
If you never un-locked the boot loader there is no way, you need to send the phone to assistance through an authorized xiaomi center, because only with an autorhized account the bootloader can be unlocked if it's never unlocked with standard procedure before
Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
Hello, thanks for your explanation
I have a question :
If I remove my mi account from the settings and my mobile brick after relocking....
Can I unlock it again?
ErriK89 said:
Guys, if in your phone the bootloader was already unlocked before to re-lock it or to obtain the error "system has been destroyed" it can be easily fixed by unlocking it again. It's just sufficient to use Mi Unlock tool, log-in with the account with which the bootloader was unlocked and unlock it. Once unlocked you can use MiFlash to flash the latest rom and if you neet to safely re-lock the bootloader.
If you never un-locked the boot loader there is no way, you need to send the phone to assistance through an authorized xiaomi center, because only with an autorhized account the bootloader can be unlocked if it's never unlocked with standard procedure before
Click to expand...
Click to collapse
im sure that i have unlocked my bootloader before but i turned it off....thats why i have a mi account but, i get an error and telling me this, what should i do?
im facing the the system has been destroyed.
i got this when i was downgrading my miui from 12.0.3 to 12.0.2
there was a feature that got removed so i did downgraded, but i made a mistake... i didnt select the reset or format or erase data before installing the older version of rom 12.0.2.... i have downgraded before and it was succesful....
and now, i cant unlock my device, its asking me to do this,
please reply i really need help..
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
how i unlock my bootload ....my bootloader was unlocked before the command......but i have not login my xioami account
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
reserved
Arobase40 said:
Ok, I feel happy for you you succeeded to root your phone with your camera working and you pass the SafetyNet test by activating Zygist with safetynet-fix v2.2.1, but what have you done differently from my guide as you as you just got updated information from my thread ?
You passed SafetyNet test and so what next ???
Have you got Samsung Secure Folder, Samsung Health or Samsung Pay working or such other protected Samsung apps ???
Are you getting Xprivacylua or AfWall+ (may be this one but not sure) working ???
Firefds kit [R] is not yet update to be compatible with Android 12, so it only partially works...
On my Galaxy Note 9, I didn't pass SafetyNet test, but Samsung Secure Folder, Google pay, Samsung Health are fully working... ^^
Samsung Pay is working but only with a Samsung Watch...
With another configuration I passed SafetyNet test but all above apps aren't working at all !!! ^^
I don't mind you created another thread and another guide on how to root the A528B but what is the interest if you don't explain how you improved mine and what new features you got ???
Click to expand...
Click to collapse
A. I didn't read your guide since your guide openly says it doesn't work with camera
B. I needed camera so I created my own guide where the camera works and it is here for everyone to read
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
Ok, I confirm this works!! Way to go sir. Thanks so much and I encourage everyone to do this method. WooHoo
Arobase40 said:
Ok but does it changes anything since my post #218 of my own guide ?
Click to expand...
Click to collapse
not that i can tell
Arobase40 said:
UPDATED : How to root Galaxy A52S 5G (SM-A528B)
This is a highly updated tutorial on how to root the Galaxy A52S 5G (SM-A528B) phone based on new version of Magisk and from feedbacks I received from users after the release of the first guide version ! ;) This guide should work with other...
forum.xda-developers.com
As I was myself trying to use Zygist with SafetyNet 2.2.1 version even though I didn't mention it explicitely as Safetynet 2.2.1 is only working with Zygist ?
"Ok, nice try mate but Zygisk-LSPosed is even worse !!!
It broke FoxMagiskModuleManager when Zygisk-LSPosed has very poor modules list. It broke AfWall+ and it partially broke Firefds kit and no progress at all with Samsung apps !!!"
Does this still apply ?
Click to expand...
Click to collapse
yes as far as lsposed goes, never used the fox app or afwall so can't say. no gravity box for android 12 yet
Arobase40 said:
So that means that since my post #218 no one with failed camera has installed SafetyNet Fix 2.2.1 with Zygist and no one has checked if that has an impact on the camera, and thus no report to me ??? lol
I just remind you that my camera has always been working so I couldn't expected any changes on this aspect... ^^
Finally, if my guide offered "limited root", this one offers even more limited one as with the exception of AdAway what this root stands for if you can't at least protect your privacy ???
Click to expand...
Click to collapse
you are lucky enough to be in a region that allows the camera to function while boot loader is unlocked
One thing I've noticed, after a restart the camera fails until closing it and killing the app in recent apps, then it works.
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
thank you very much )))) I will try this weekend!
Guys, can anybody explain to me , why Samsung is apparently making it so hard for the customers to root their devices? Is it a problem with Samsung or with Magisk, or both?
Not being able to root via Magisk is a real dealbreaker to this otherwise well-specced phone (at least it is to me!).
Going to try this method with Android 11 using Magisk 24.3 and safety net 2.2.1 which I hope will allow the camera to work also.
Edit: It works with android 11.
Arobase40 said:
Why wouldn't it work with Android 11 as it is not related ???
You mean you downgraded to Android 11 and got stuck with a very old security patch just to get GravityBox and probably with Firefds Kit [R] working ??? lol
Click to expand...
Click to collapse
Yes, yes and yes. LOL and better battery life too
I've had no bootloops when changing things FireFDS and I'm glad to have a working gravity box... I'll report battery after a few days.
testestestest said:
Guys, I DID IT !!!!
Click to expand...
Click to collapse
Hi, I'm new here and I bought the A528B, I don't speak English and I use google translate... maybe this is asking too much but a step by step video would be too much to ask? having to translate it costs me a lot trying to follow the guide...
I don't understand how I have to do to be able to root it and have the camera working
bobfrantic said:
Ok, confirmo que esto funciona!! Bien hecho señor. Muchas gracias y animo a todos a hacer Desbloquee el gestor de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
Click to expand...
Click to collapse
testestestest said:
Chicos, LO HICE!!!!
Samsung A52s (SM-A528B/DS) en funcionamiento con cargador de arranque desbloqueado, rooteado (Magisk), pasando SafetyNet y CÁMARA DE TRABAJO (yaaay).
El problema es que no tengo idea de cómo lo hice, porque fueron 3 días de flashear, parchear, reinstalar y bloquear el teléfono también (desafortunadamente).
Adjunto una captura de pantalla que hice con el teléfono mientras escribía esta publicación en Word. Alguien quería capturas de pantalla en pantalla dividida como prueba, así que... boom, aquí tienes.
Tengo muchas fotos que hice en los últimos 3 días, así que intentaré escribir algunas instrucciones más detalladas pronto. Pero ahora al menos prueba esto:
Esto debería funcionar para cualquier persona, incluso para las personas que no tendrán una cámara en funcionamiento después de desbloquear el gestor de arranque.
1. Descargue el último firmware y Odin de samfw.com (no sé por qué, pero estos fueron solo uno que se cubrieron para mí, bloquearon mi teléfono antes con un firmware diferente)
2. Descomprima el firmware descargado y copie AP a un teléfono con Magisk 24.1
3. Use la aplicación Magisk para parchear el archivo AP y descárguelo nuevamente a la PC
4. Desbloquee el cargador de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
5. Reiniciar
6. Vaya al modo de descarga (debería ver OEM: APAGADO (U))
7. Flashee con Odin todos los archivos de Firmware que descargó, pero a AP puso el archivo parcheado
8. Reiniciar
9. Vaya a magisk, haga lo que quiera, reinicie, en la configuración active el host integrado, active Zygisk, reinicie, descargue e instale el módulo kdrag0n's safetynet-fix v2.2.1 ( https://github.com/kdrag0n/safetynet -fix/ lanzamientos )
10. reiniciar
11. siiii
ACTUALIZACIÓN: Ok, parece que el software de la cámara fallará después de reiniciar una vez. Cuando lo cierras y lo abres de nuevo, funciona.
CONFIRMADO: Tuve que volver a flashear después de probar TWRP y ahora puedo confirmar que parchear "safetynet-fix v2.2.1" te permitirá usar la cámara después de una ejecución. La aplicación Samsung Cam fallará en la primera ejecución, por lo que cuando la elimine en el conmutador de aplicaciones y vuelva a ejecutarla, funcionará de manera normal (cambiando de cámara, frontal/trasera y todo).
Click to expand...
Click to collapse
EL DESBLOQUEO DE ARRANQUE ES ANTES O DESPUES DE PARCHEAR EL AP
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
ch3mn3y said:
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
Click to expand...
Click to collapse
Well then, there you go. You got bootloop for not following the instructions
Did i understand right?
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
Click to expand...
Click to collapse
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
luffy786 said:
Did i understand right?
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
Click to expand...
Click to collapse
You can install the Magisk app without being rooted. It's an app like any other app, you simply won't have root access. So install it on your A52s 5G and patch your files with it.
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
BlueChris said:
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
Click to expand...
Click to collapse
Well, I added these 2 lines:
wlan.wfd.hdcp=disable
wifi.interface=wlan0
On the following files:
product/etc/build.prop
system/build.prop
system/system_ext/etc/build.prop
vendor/build.prop
vendor/default.prop
I'm pretty sure not all of them are needed but I'm too lazy to figure out which prop file really needs it lmao if I had to take a guess I'd say either vendor build.prop or default.prop, who knows.