Related
Hi, everybody.
Sorry if I post this thread in wrong section.
Howewer I hope that this thread would be an aid for thus want to try the different beta builds of our phone.
Ok. So.
1. Dual SIM B170 --- B188 --- (possible 190 or 194) --- B524 --- B550.
- all is fluent.
2. Single SIM B171 --- B525
- all is fluent
- howewer this build cannot upgrade to B550
- seems that developpement freeze at beta build stage (waiting for final build)
- oh, and surprise: You CAN use dual SIM. Yes its true, i flashed over dual sim model (so i guess that this works only on Dual Sim models)
3. Chinese firmware B535 (--- exist the beta build 551, but that doesnt leaked)
- all is fluent
BUT. The BIG difference between these builds is that the Chinese firmware come with MANY more functions, than the others: SmartCare, Camera modes, Barcodes in Messaging, Yellow Pages in Dialer, and so Many others (maybe I would collect them for the whole list)
So I use the Chinese build. With little tweak is wery well usable. You have little areas with chinese options (for example you must change the keyboard from chinese to huawei swype), but it isnt annoying.
Oh, and if you register an huawei account on chinese site, well, you have many other possibilities from this build.
I recommend this build over the others.
P.S. I would make a voting for those builds too but i dont know how (maybe the moderators...)
i have got b150... can i go for b170?
tamaskurti said:
BUT. The BIG difference between these builds is that the Chinese firmware come with MANY more functions, than the others: SmartCare, Camera modes, Barcodes in Messaging, Yellow Pages in Dialer, and so Many others (maybe I would collect them for the whole list)
So I use the Chinese build. With little tweak is wery well usable. You have little areas with chinese options (for example you must change the keyboard from chinese to huawei swype), but it isnt annoying.
Oh, and if you register an huawei account on chinese site, well, you have many other possibilities from this build.
I recommend this build over the others.
P.S. I would make a voting for those builds too but i dont know how (maybe the moderators...)
Click to expand...
Click to collapse
I've read that some are using the chinese version, but i couldn't found info how to get it.
All HowTos und firmware links lead to C432B550 or C432B524 in the end.
Could you post details how to get the chines beta on an european phone?
Norikio said:
I've read that some are using the chinese version, but i couldn't found info how to get it.
All HowTos und firmware links lead to C432B550 or C432B524 in the end.
Could you post details how to get the chines beta on an european phone?
Click to expand...
Click to collapse
Hm. I was sure that was here on xda, but anyway. I would quote.
Hello,
Finally we get EMUI 4.0 on P8 Lite. Few days ago I decided to change the location of my phone ALE-L21 because China goes beta test of 6.0 but with Chinese firmware installed on the B230 on ALE-UL00. And today the new Android 6.0 was successfully installed on my phone!
Cheers
FIRST and foremost you need change the location!!! to
unicomelectric/cn
To install OTA(EMUI 4.0) update is necessary to change your location and the Chinese version of the software B230
So here the OTA B535
Just put update.zip(1.1GB) into dload folder on your SDCard or internal memory!!! Then install as local update!
Guide how to install EMUI 4.0 Android 6.0 ALE-UL00C00B535 on device ALE-L21(P8 Lite)
Requirements
1.Unlocked bootloader
2. Rooted device
How to Change Region of Your Huawei Honor 4C [Root]
You can change the region of your Huawei Honor 4C and gain the ability to flash firmware from other countries by a few tweaks to the files that hold country settings. This step-by-step tutorial will guide you through the entire process and provide you with the files required.
Huawei Honor 4C
1. Requirements
Full root access
ES File Explorer (Root Explorer is not recommended at all!)
Backup of your current stock recovery and custom recovery
Full Nandroid backup of all partitions
OEM Info File (download here)
Warning: Although you might find this tempting, there’s a high chance that you’ll brick your phone in the process. That’s why you’re strongly advised to keep a handy nandroid backup. We hold no responsibility for any kind of damage caused during or after this procedure. You proceed entirely at your own risk!
2. Procedure
Step 1: First of all, find out your current vendor/country info. One way to do this is by dialing *#*#2846579#*#* – from the menu that pops up go to Network Information > Vendor/Country Info. Some of the vendors/countries are:
hw/spcseas – Malaysia
unicomelectric/cn – China
hw/meafnaf – Pakistan
mts/by – Belarus
Step 2: Now that you know your region information, open ES File Explorer and turn “Root Explorer” on from the menu in the sidebar. Select “/” (device) from the bar above and go to “Data”. Open custom.bin using the ES Note Editor. You’ll see the same vendor and country information in this file as you previously saw in engineering mode. Clear the text and insert the text corresponding to the region you wanna shift to. For example, if I were moving from Pakistan to Malaysia, I’d clear “hw/meafnaf” from custom.bin and insert “hw/spcseas” instead.
When you’re done, save the file and make sure its permissions are set to rw-rw-rw in its properties.
Step 3: Now download the OEM Info package from above and extract it. Inside the oeminfo folder, take the oeminfo file of the country you’re shifting to and copy it to [/device]/dev/block/hi_mci.0/by-name/. Replace the file that’s already present in by-name folder. I repeat – replace the file – don’t delete it! Make sure you’re doing this only through ES File Explorer. Make sure this file has rwx rwx rwx permissions.
Step 4: Finally, if you’ve done everything right, reboot your phone and check your vendor and country info again by dialing *#*#2846579#*#* in the dialer.
Step 5: Now you should be able to flash any firmware from the region you now have. In case you’re seeing “balong” in Settings > Update as your version number it means that you now won’t be able to receive any online updates. You don’t really need to worry about it. Simply download the firmware and flash it through the forced SD upgrade method (you know the one – Vol up + Vol down + Power).
______________________________________________________________________
Change location on your device to unicomelectric/cn
a) Copy file oeminfo to internal memory or SD Card
b) Replace oeminfo on path /dev/block/platform/hi_mci.0/by-name with downloaded one. Reboot
Instalation procedure
a) Downgrade to B052(fastboot) make wipe!
b) Install B230(fastboot) Make two wipe!!!
c) Install B535 as local update(put the update.zip on dload folder in internal memory) make wipe!
DONE!
PS: sokkoban was the autor (look at his label):
h t t p : / / huaweip8lite.blogspot . ro
I managed to find the thread, it's a bit messy because the Opening Post is deleted and i had to find all the filse cluttered over the thread.
Installation went quite smooth, but i'm a little bit worried because Model Number says hi6210sft, but that's something i can probably fix inside the build.prop.
so thanks tamaskurti for the info.
You guys think the best firmware is the chineese one ? I have all the files downloaded on my laptop but I doubt in installing it
look at:
h t t p : / / forum.xda-developers.com / p8lite / general / ale-ul00-t3339897
Honestly, i am disappointed with b550 official europe build.
I was on chinese b535 build, witch its beta, howewer, it has lot more functions than the europe builds. I wait for the final marshmallow build from chinese market, because, their rom is more ellaborated than the others. Sorry, huawei europe, but in comparison with chinese market, the final build seems for me that an early beta or alpha build.
Is there a way to get the Chinese version camera app to our phones (meaning official MM update)?
Hey guys, I bought RM3 few days ago.
I want to root it.
It's the global version. Can anyone please make a video on how to root global version of RM3? PLEASE
Thread is here - https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148
Texan1 said:
Thread is here - https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148
Click to expand...
Click to collapse
Can you please make a video?
I'm on global version. Why do I have to install Chinese version?
Saurabh Kash said:
Can you please make a video?
I'm on global version. Why do I have to install Chinese version?
Click to expand...
Click to collapse
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
I'm new to this kinda stuff and don't wanna mess things up. Can you please make a video?
em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
Please make a video for international Asia version. And I couldn't find link to global rom
em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
And will I still get ota update after root?
Saurabh Kash said:
And will I still get ota update after root?
Click to expand...
Click to collapse
No.
A suggestion: don't. You obviously don't know a lot about rooting and stuff and RM3 is a bit atypical amongst android phones, so it's more risky.
Why do you need root anyway?
Nightpwish said:
No.
A suggestion: don't. You obviously don't know a lot about rooting and stuff and RM3 is a bit atypical amongst android phones, so it's more risky.
Why do you need root anyway?
Click to expand...
Click to collapse
To restore my important backup that I made with titanium and to use theme engines because dark in built theme isn't working on my phone
Saurabh Kash said:
To restore my important backup that I made with titanium and to use theme engines because dark in built theme isn't working on my phone
Click to expand...
Click to collapse
I will say this the above posted is the only way to root global. If an OTA comes out you better not try to update. What you will have to do is BACKUP anything important to you, complete uninstall Magisk and modules, go into fastboot relock the bootloader which will factory reset the phone then update via OTA, re-unlock the bootloader and re-root with the updated boot.img which you will have to download.... Especially important if OTA updates security patch. You have to understand custom ROMs are developed for rooting, stock ROMs are not.... Hence all the trouble.
Hi,
Two things worth mentioning :
- it seems the procedure indicated to rrot does not work with EU v. 1.15 ; I just tried and phone reboots, but with no root
- rooting the phone will not allow OTA. You will get notified of an update, but the update will not apply to the end.
Regards.
First, here is the link to the TWRP zip I made to crossflash the sprint g8 to Open US 20c: https://forum.xda-developers.com/showthread.php?t=4181557
Second, crossflashing is really only useful for two cases: you have an at&t or sprint g8 that you bootloader unlocked for other reasons and want to get updates, or you absolutely need volte and/or vowifi to work. Bootloader unlocking just to crossflash in the way explained below without further reasons is practically pointless.
I'll just repeat some things I said in that post to clarify why the following steps need to be done: on the g8 and v50, LG implemented a hardware lock, where you have an OPID (operator ID, such as sprint), and a value of either 1 or 0 for IMPL. I'm not entirely certain about this, but I think the IMPL value being true or false determines whether the OPID will be checked or not, and IMPL can only be made 0 with some hardware mods. The OPID exists somewhere in the hardware and is then crosschecked with an OPID in the software, and if they don't match, you're greeted with the words "OPID mismatch" on boot (unless IMPL = 0). However, I discovered that the OPID checked during boot is just /OP/totc.cfg, which is a just a one line .cfg file containing something like "SPR_US." So, we can just flash most of the relevant partitions that get updated in OTAs from a different kdz, including system, vendor, boot (although using dragonfly or metaphysics kernel is better), and product. There are a bunch of other partitions like the abls and xbls that will stay the same during a major android update release, are probably the same across variants, and are generally just safer to leave be. For the OP partition, we can flash it, and since TWRP still works even when you face OPID mismatch when trying to boot into system, we can just replace the totc.cfg in the new /OP with one we saved from the original one. All that said, here are the steps to do all that after you choose a variant to crossflash to. Beware that on the korean v50, after crossflashing, changing NT code appears to be necessary for networks to work, which can only be done when IMPL = 0. This might apply to the Korean g8 as well or other models, but I think all US models should be fine (just don't crossflash to the korean variant). A prerequisite of the guide is also to have backups of your partitions, so you can just flash them back if you run into any unfixable issues.
Prerequisites:
- Have a backup of all the partitions that will be altered / flashed in this guide (system, product, vendor, boot, and most importantly, OP)
- Have a working TWRP where you can mount OP configs and successfully see /OP/totc.cfg
- This will wipe your data along with your internal storage, so make sure to backup what you need
- Have the disable dm verity force encrypt twrp zip, which is included in either of the bl unlock guides
- Half optional: have metaphysics or dragonfly kernel as your boot img so that you don't end up using an old stock boot img on a newer software version and potentially not boot
- At least half a brain
1. Go to /OP/totc.cfg either in a root file manager or in TWRP and copy it to your computer, sdcard, or wherever will survive an internal storage wipe
2. Go on lg-firmwares and download your desired kdz. I would use either the latest Open Canada or Open US one. Just because canada might be on 20h and OPEN US is on 20c, that doesn't mean OPEN US is really that far behind in updates, it just received less in total, so it could have arrived at the same security patch as Open Canada while having a much lower version number. If you live in the US, just go with OPEN US (same goes for Canada), and if you live elsewhere maybe go with the Canadian kdz
3. https://github.com/steadfasterX/kdztools READ the documentation
4. Use the documentation to figure out how to extract the system, vendor, and product partitions from your downloaded kdz and do so!
5. https://bbs.lge.fun/thread-75.htm Use this guide to extract the OP partition from your kdz. This is by far the hardest part because kdztools can't do it correctly on its own.
6. Transfer all the partitions to your phone: system, vendor, product, OP
7. Flash all those partitions in TWRP
8. Hold down vol- + power until you reboot from within TWRP, and keep holding that key combination until you get back into TWRP again
9. Format data in TWRP
10. Mount OP configs, go to /OP in TWRP's file manager, and delete totc.cfg
11. Transfer your saved totc.cfg (from your original OP partition), to your internal storage, and then copy that to /OP again using TWRP's file manager
12. Flash the disable dm verity force encrypt zip
13. Done
Hello, I have a question, does this procedure unlock the carrier? Or, is it still locked for sprint SIM cards?, Thanks.
Nice guide. Thank you so much! Now I can use Open firmware without unused operation apps.
Since we have the programmer file for EDL I would like to do this for my g8x sprint variant. However I still need to sim unlock it first before I attempt to boot loader unlock it. The OPID is in the first 2 offsets of hex code in the OP_a.bin image.
For example my partition dump for my G8x g850um reads the below
Code:
TMO_US
MSVN 0
So I extracted the tot file from the phone image dump and verified this for myself and am confused as to why it says TMO_US if I have a sprint splash screen. Was my phone cross flashed before I got it? How to I verify what the IMPL value is? Where is that stored?
antintin said:
First, here is the link to the TWRP zip I made to crossflash the sprint g8 to Open US 20c: https://forum.xda-developers.com/showthread.php?t=4181557
Second, crossflashing is really only useful for two cases: you have an at&t or sprint g8 that you bootloader unlocked for other reasons and want to get updates, or you absolutely need volte and/or vowifi to work. Bootloader unlocking just to crossflash in the way explained below without further reasons is practically pointless.
I'll just repeat some things I said in that post to clarify why the following steps need to be done: on the g8 and v50, LG implemented a hardware lock, where you have an OPID (operator ID, such as sprint), and a value of either 1 or 0 for IMPL. I'm not entirely certain about this, but I think the IMPL value being true or false determines whether the OPID will be checked or not, and IMPL can only be made 0 with some hardware mods. The OPID exists somewhere in the hardware and is then crosschecked with an OPID in the software, and if they don't match, you're greeted with the words "OPID mismatch" on boot (unless IMPL = 0). However, I discovered that the OPID checked during boot is just /OP/totc.cfg, which is a just a one line .cfg file containing something like "SPR_US." So, we can just flash most of the relevant partitions that get updated in OTAs from a different kdz, including system, vendor, boot (although using dragonfly or metaphysics kernel is better), and product. There are a bunch of other partitions like the abls and xbls that will stay the same during a major android update release, are probably the same across variants, and are generally just safer to leave be. For the OP partition, we can flash it, and since TWRP still works even when you face OPID mismatch when trying to boot into system, we can just replace the totc.cfg in the new /OP with one we saved from the original one. All that said, here are the steps to do all that after you choose a variant to crossflash to. Beware that on the korean v50, after crossflashing, changing NT code appears to be necessary for networks to work, which can only be done when IMPL = 0. This might apply to the Korean g8 as well or other models, but I think all US models should be fine (just don't crossflash to the korean variant). A prerequisite of the guide is also to have backups of your partitions, so you can just flash them back if you run into any unfixable issues.
Prerequisites:
- Have a backup of all the partitions that will be altered / flashed in this guide (system, product, vendor, boot, and most importantly, OP)
- Have a working TWRP where you can mount OP configs and successfully see /OP/totc.cfg
- This will wipe your data along with your internal storage, so make sure to backup what you need
- Have the disable dm verity force encrypt twrp zip, which is included in either of the bl unlock guides
- Half optional: have metaphysics or dragonfly kernel as your boot img so that you don't end up using an old stock boot img on a newer software version and potentially not boot
- At least half a brain
1. Go to /OP/totc.cfg either in a root file manager or in TWRP and copy it to your computer, sdcard, or wherever will survive an internal storage wipe
2. Go on lg-firmwares and download your desired kdz. I would use either the latest Open Canada or Open US one. Just because canada might be on 20h and OPEN US is on 20c, that doesn't mean OPEN US is really that far behind in updates, it just received less in total, so it could have arrived at the same security patch as Open Canada while having a much lower version number. If you live in the US, just go with OPEN US (same goes for Canada), and if you live elsewhere maybe go with the Canadian kdz
3. https://github.com/steadfasterX/kdztools READ the documentation
4. Use the documentation to figure out how to extract the system, vendor, and product partitions from your downloaded kdz and do so!
5. https://bbs.lge.fun/thread-75.htm Use this guide to extract the OP partition from your kdz. This is by far the hardest part because kdztools can't do it correctly on its own.
6. Transfer all the partitions to your phone: system, vendor, product, OP
7. Flash all those partitions in TWRP
8. Hold down vol- + power until you reboot from within TWRP, and keep holding that key combination until you get back into TWRP again
9. Format data in TWRP
10. Mount OP configs, go to /OP in TWRP's file manager, and delete totc.cfg
11. Transfer your saved totc.cfg (from your original OP partition), to your internal storage, and then copy that to /OP again using TWRP's file manager
12. Flash the disable dm verity force encrypt zip
13. Done
Click to expand...
Click to collapse
Do you think this method can be tried for flashing G8S partitions on a T-mobile G8 ? I really need VoLTE and my G8S has it.
antintin said:
LG implemented a hardware lock, where you have an OPID (operator ID, such as sprint), and a value of either 1 or 0 for IMPL.
Click to expand...
Click to collapse
as far as I discovered, there is no HW lock but it seems it is about sth like a serial number (maybe device id) which is later checked by software and determines the original opid of the device. you can check device id by the query "at%deviceid" in modem while port check is enabled.
however, erasing some partitions will hinder sw to check and inspect opid. In Open_ca 20 you can erase modem (not modemst) and it fails to check and determine the original opid so it lets device to get flashed by any kdz, although later it is needed to modify opid in op partition.
hello i'm new to the forum and i have a doubt, my lg g8 is blocked to use only at&t chip, if i do the bootloader deblocking and change the rom i can use another operator's chip ?, i'm in brazil and i can't use an operator local
At the moment no custom Rom for lg g8
I followed every step exactly as described for extracting OP partition but the resulting file size is around 16 MBs larger than my device's OP partition (LG V50 V450) , and TWRP cannot flash it (throws file size larger than device error), so I flashed in EDL mode by QFIL but it has a warning (file overflow) and it flashed without issue but the device gets stuck at boot and off course I copied over my original totc.cfg to the OP partition but still stuck on the boot screen, I also flashed boot image from the KDZ to the boot partition still the same , BTW my active slot is A , and it doesn't matter which kdz I use I always end up with same file size of 716 MBs , but my device's OP partition is 700 MBs, I backed everything up and I have no issue going back to stock sprint.
On many occasions I didn't copy the totc.cfg back to the device on purpose and I did not get OPID mismatch error which concludes that OP Decryption method from KDZ is buggy (at least for V450)
So is there something that I missed here ? or is this only working for G8 ?
Same size mismatch error with trying to crossflash OP partition on my LG G8. So not working either.
armodons said:
Same size mismatch error with trying to crossflash OP partition on my LG G8. So not working either.
Click to expand...
Click to collapse
So I was not the only one, there has to be a better way to extract the OP partition , deleting the first 512 bytes of code may not be enough , maybe in the middle or at the there are other things that need to be deleted using Ultra edit.
Bronnel said:
So I was not the only one, there has to be a better way to extract the OP partition , deleting the first 512 bytes of code may not be enough , maybe in the middle or at the there are other things that need to be deleted using Ultra edit.
Click to expand...
Click to collapse
I think the extracted OP partition after eliminating the 512 bytes of data is probably the correct version because it can be extracted and the contents viewed--different phone variants may just have differently sized partitions. No idea how to get around this issue though...
armodons said:
I think the extracted OP partition after eliminating the 512 bytes of data is probably the correct version because it can be extracted and the contents viewed--different phone variants may just have differently sized partitions. No idea how to get around this issue though...
Click to expand...
Click to collapse
you are correct but I tried many KDZs including pie and all of them end up the same file size (roughly 716 MBs), I mean shouldn't there be at least a minor difference ?
I can't help those with issues creating the OP partition, although one would have to think others have tried to do that / had probs / posted results. There must be help for that in some threads somewhere...
I used the OP partition (from us 20c) in this thread, and was able to accomplish what I needed with a lot less effort then doing this 'crossflashing' (thnx Cloud Man).
So, what I needed? Really only wanted volte and vowifi to work with my mint mobile sim. My sprint phone with a10 20f continuously tried to connect to 'carrier services' (it couldn't, I'm not on sprint), and vowifi or volte didn't work with other carrier even though it was sim unlocked.
A simple fix was to use twrp and flash only the OP partition (as described in this thread), then also restore the original totc.cfg (also as described in this thread).
Edit 11/8/21: Note: You don't need to flash the totc.cfg if you have a sprint device and flashing the us Open OP provide here, it already has the totc changed to sprint.
That's it, didn't flash any of the other partitions (did try that way initially but got boot loop). So now my sprint device is basically indistinguishable from a US Open device. No sprint bloat, no more constantly trying to 'configure carrier services', and vowifi and volte work.
cheers
Not sure if this is terribly different than the one in the OirgPost (20c), but this is the OP from latest US OP kdz (20f).
Also, as in op notes, have to put your original totc file in place of the one that this comes with.
cheers
antintin said:
First, here is the link to the TWRP zip I made to crossflash the sprint g8 to Open US 20c: https://forum.xda-developers.com/showthread.php?t=4181557
Second, crossflashing is really only useful for two cases: you have an at&t or sprint g8 that you bootloader unlocked for other reasons and want to get updates, or you absolutely need volte and/or vowifi to work. Bootloader unlocking just to crossflash in the way explained below without further reasons is practically pointless.
I'll just repeat some things I said in that post to clarify why the following steps need to be done: on the g8 and v50, LG implemented a hardware lock, where you have an OPID (operator ID, such as sprint), and a value of either 1 or 0 for IMPL. I'm not entirely certain about this, but I think the IMPL value being true or false determines whether the OPID will be checked or not, and IMPL can only be made 0 with some hardware mods. The OPID exists somewhere in the hardware and is then crosschecked with an OPID in the software, and if they don't match, you're greeted with the words "OPID mismatch" on boot (unless IMPL = 0). However, I discovered that the OPID checked during boot is just /OP/totc.cfg, which is a just a one line .cfg file containing something like "SPR_US." So, we can just flash most of the relevant partitions that get updated in OTAs from a different kdz, including system, vendor, boot (although using dragonfly or metaphysics kernel is better), and product. There are a bunch of other partitions like the abls and xbls that will stay the same during a major android update release, are probably the same across variants, and are generally just safer to leave be. For the OP partition, we can flash it, and since TWRP still works even when you face OPID mismatch when trying to boot into system, we can just replace the totc.cfg in the new /OP with one we saved from the original one. All that said, here are the steps to do all that after you choose a variant to crossflash to. Beware that on the korean v50, after crossflashing, changing NT code appears to be necessary for networks to work, which can only be done when IMPL = 0. This might apply to the Korean g8 as well or other models, but I think all US models should be fine (just don't crossflash to the korean variant). A prerequisite of the guide is also to have backups of your partitions, so you can just flash them back if you run into any unfixable issues.
Prerequisites:
- Have a backup of all the partitions that will be altered / flashed in this guide (system, product, vendor, boot, and most importantly, OP)
- Have a working TWRP where you can mount OP configs and successfully see /OP/totc.cfg
- This will wipe your data along with your internal storage, so make sure to backup what you need
- Have the disable dm verity force encrypt twrp zip, which is included in either of the bl unlock guides
- Half optional: have metaphysics or dragonfly kernel as your boot img so that you don't end up using an old stock boot img on a newer software version and potentially not boot
- At least half a brain
1. Go to /OP/totc.cfg either in a root file manager or in TWRP and copy it to your computer, sdcard, or wherever will survive an internal storage wipe
2. Go on lg-firmwares and download your desired kdz. I would use either the latest Open Canada or Open US one. Just because canada might be on 20h and OPEN US is on 20c, that doesn't mean OPEN US is really that far behind in updates, it just received less in total, so it could have arrived at the same security patch as Open Canada while having a much lower version number. If you live in the US, just go with OPEN US (same goes for Canada), and if you live elsewhere maybe go with the Canadian kdz
3. https://github.com/steadfasterX/kdztools READ the documentation
4. Use the documentation to figure out how to extract the system, vendor, and product partitions from your downloaded kdz and do so!
5. https://bbs.lge.fun/thread-75.htm Use this guide to extract the OP partition from your kdz. This is by far the hardest part because kdztools can't do it correctly on its own.
6. Transfer all the partitions to your phone: system, vendor, product, OP
7. Flash all those partitions in TWRP
8. Hold down vol- + power until you reboot from within TWRP, and keep holding that key combination until you get back into TWRP again
9. Format data in TWRP
10. Mount OP configs, go to /OP in TWRP's file manager, and delete totc.cfg
11. Transfer your saved totc.cfg (from your original OP partition), to your internal storage, and then copy that to /OP again using TWRP's file manager
12. Flash the disable dm verity force encrypt zip
13. Done
Click to expand...
Click to collapse
Hello, I don't want to bother you but by any chance do you have any idea in which file or partition the "sim" network lock is, I want to test if I can unlock the network of an LG G8 ThinQ Xfinity mobile
AsItLies said:
Not sure if this is terribly different than the one in the OirgPost (20c), but this is the OP from latest US OP kdz (20f).
Also, as in op notes, have to put your original totc file in place of the one that this comes with.
cheers
Click to expand...
Click to collapse
Would I be able to do a simple update to A11 US OPEN using LGUP when /if the kdz comes?
mangojain said:
Would I be able to do a simple update to A11 US OPEN using LGUP when /if the kdz comes?
Click to expand...
Click to collapse
No, I don't think so. You could try it, might work, don't know that anyone has tried that as we don't have updates coming.
But worse case scenario is you follow the OP and re crossflash and go through setup again. Not that big of a deal.
cheers
AsItLies said:
No, I don't think so. You could try it, might work, don't know that anyone has tried that as we don't have updates coming.
But worse case scenario is you follow the OP and re crossflash and go through setup again. Not that big of a deal.
cheers
Click to expand...
Click to collapse
You see, extracting the OP partition is beyond me, so i would have to wait for an expert like you to do it, IF the update comes. Actually I'm fairly hopeful that it will, considering that the CA OPEN has come.
mangojain said:
You see, extracting the OP partition is beyond me, so i would have to wait for an expert like you to do it, IF the update comes. Actually I'm fairly hopeful that it will, considering that the CA OPEN has come.
Click to expand...
Click to collapse
well thanks, but as far as the US version becoming available, keep in mind that LG has a long history here. It seems that their contracts with other US carriers stipulate the US op version can't be released until the carriers release their version. So if one of the carriers doesn't do the update, the US will never be available.
I may try the ca open soon and will modify the latest US open OP to work with it, that may well be the best (latest) update ever available?
cheers
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed for the Tab 10.1 (2019)).
It's been quite some time since I published a tutorial on XDA. So, I decided to put up this comprehensive tutorial, hope it helps everyone who's looking for it. We will take the direct approach of rooting the tab by patching the AP firmware and flashing the patched AP through Odin.
/* I will be using the same images I prepared for the tutorial to be posted on my blog. Sorry that they have been watermarked, that is to prevent scrapers from stealing. It took me enough time to capture them and do some post-processing. */
Before we start, here's the obligatory disclaimer and warning:
Unlocking the bootloader will erase all the data on your tab, including all the data that's on the internal storage. So, make sure that you have taken a complete backup of all your important data.
Flashing a custom binary (such as Magisk patched TAR in this guide) will trip the KNOX counter. Your device's official warranty will be void once KNOX is tripped.
You will not be able to use apps and services like Secure Folder, Samsung Pass, and anything that relies on KNOX.
Although I have tried this on my Galaxy Tab A7 (SM-500) and can confirm that this works, I will not take any responsibility of any bricked/toasted devices. Make sure that you fully understand what you're doing and accept the consequences if anything goes wrong.
If you do land your tablet in trouble, feel free to ask, I shall try my best to help.
Click to expand...
Click to collapse
Update log
Updated on March 2, 2021
Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".
Click to expand...
Click to collapse
Requirements
Your Galaxy Tab A7 with SM-T500 or SM-T505 model number
A compatible USB-C cable
A Windows computer. (Odin only works on Windows. If you're using Linux or Mac, you could try Heimdall)
Instructions
Step 1: Enable OEM Unlocking
In order to unlock the bootloader, you must first enable the 'OEM Unlocking' toggle. This toggle resides inside the 'Developer options' screen, which is hidden by default on most Android devices.
First, enable 'Developer options' by going to 'Settings' > 'About tablet' > 'Software Information' and repeatedly tap on the 'Build number' section five times. If you have a lock screen security set, you will need to input your PIN/Password/Pattern when prompted.
{
"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"
}
Once you do this, you should see a toast notification on the bottom of the screen saying that "Developer mode has been enabled".
Once that is out of the way, go to 'Settings' > 'Developer options' and turn ON the toggle next to "OEM unlocking". You will instantly be prompted to enter your PIN/Password/Pattern, so do it. Then select "Enable" to allow OEM unlocking.
Note: If the OEM unlocking toggle is grayed out, make sure that you have connected the tablet to the internet first (via WiFi or mobile network, your choice).
Step 2: Unlock the Bootloader
Start by powering off your tablet completely. Then while holding the Volume Up and Volume Down keys together, connect it to your computer using the USB cable. This should take you to the bootloader screen (I call it that because logically that's what directs you to either Download Mode or Device Unlock Mode). Long-press the Volume Up key to enter the 'Device unlock mode'.
Your tab should now prompt you with a confirmation screen, so press the Volume Up key to confirm and unlock the bootloader.
Your Tab A7's bootloader is now unlocked and it should reboot automatically. You should also see a warning message right before the Samsung splash screen, just as shown in the picture below. Don't worry, it's completely normal. And no, there's no way to get rid of it (unless of course, you relock the bootloader).
The first boot after unlocking the bootloader could take some time (took around 3-4 minutes for me). So be patient.
Now that the bootloader is unlocked, let's verify it. Samsung introduced a new feature known as "VaultKeeper", which will automatically relock the bootloader if you do not perform this step.
After your tab boots, connect it to the internet. Then enable the Developer options as shown in step #1 and go to 'Settings' > 'Developer options'. The OEM unlocking toggle should be greyed out and say that the bootloader is already unlocked. Again, refer to the picture below.
Step 3: Download the firmware package
With the bootloader properly unlocked, you can begin with the rooting part. As I mentioned, we will be patching the AP firmware file via Magisk App, as instructed by John Wu in his installation guide on Github.
So, you will need to download the firmware package for the software version that's currently installed on your tab. This is very important, do not use an older firmware, as it will result in issues. You could of course use a newer firmware, which will update your tab at the same time as rooting it.
To verify your software version, you can go to 'Settings' > 'About tablet' > 'Software information' and check the "Build number". The latter half of the mentioned build number is your tab's software version, which in my case as shown in the picture below is: T500XXU1ATJ2. So, I will need to download the firmware package for "T500XXU1ATJ2" and in your case you should download the one corresponding to the info you see under 'Build number'.
Where to download? You could use online FW databases like SamMobile, Samfrew, etc. However, I would recommend using Frija or Samloader as they allow you to download the firmware directly from Samsung's Firmware Update Servers and without any speed caps. If you're operating on Windows, use Frija. On macOS/Linux, use Samloader.
Step 4: Extract the AP firmware and transfer it to your Tab A7
Once you have the ZIP package downloaded, you will need to extract it to get The extracted folder should contain the individual firmware files like BL, AP, CP (only for SM-T505 LTE variant), and CSC/HOME_CSC (in .tar.md5 file format).
The file you'll require is the AP firmware, which in my case is "AP_T500XXU1ATJ2_CL19362637_QB34980135_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS10.tar.md5". Again, in your case, the filename would be a bit different, but it should follow the same structure.
After extracting the AP firmware, connect your tab to the computer, enable File Transfer (MTP) mode on it, and copy over the AP firmware to your tab's internal storage. Copy it to the root directory, that is, outside all the folders as shown below. The location of the file doesn't matter, you can copy it anywhere, but I prefer this for easier access.
Step 5: Patch the AP firmware using Magisk App
Now's the time to patch the AP firmware. To do this, download the latest version of the Magisk app from the official Github releases page to your Tab A7. This will be an APK file. Once downloaded, install the APK file using your choice of file manager.
Warning about unofficial sources of Magisk: Magisk does not have any officially registered domain. If you Google for it, you will probably come across multiple websites that have the word "Magisk" in their domain URL. They are there to deceive the users, and often misinform users, especially those who are new to the scene.
John Wu, as well as XDA have previously warned the users from falling into these deceptive websites. The only official place to get Magisk is from Github.
Click to expand...
Click to collapse
You do not need to change Magisk's update channel to Beta anymore. Starting January 12, Magisk v21.x was pushed to the stable channel (default).
After installing, go to the app drawer and launch the Magisk Manager app. Before you start patching, you would want to change Magisk Manager's update channel to Public Beta. This is because Magisk's latest version (i.e. v21.0) is only available on the beta channel and hasn't been pushed to the stable channel yet (at least at the time of publishing this tutorial).
To do this, press the settings icon on the top-right, tap on "Update channel" and select "Beta". Then go back to the app's main screen. It should refresh and show you the latest version as v21.0.
Press the "Install" button and then "Select and Patch a File" from the list of available methods. This should open the file selector, so navigate to the internal storage and select the AP firmware you transferred during the previous step.
Once the file is selected, hit "LET'S GO" to start the patching process. This should take a minute or so because the AP firmware is quite a heavy file. Once it is done, the patched AP firmware with the filename "magisk_patched_xxxxx.tar" (where "xxxxx" is an arbitrary code) should be stored inside the "Download" folder of your tab's internal storage.
Step 6: Flash the Patched AP Firmware using Odin
The last step is to flash the patched AP firmware to your Galaxy Tab A7 and root it. For this, connect your tab to the computer over USB and copy the "magisk_patched.tar" file from the Download folder. Paste this patched AP firmware inside the firmware folder that was extracted during step #5, along with the rest of the firmware files (BL, CSC, etc). Disconnect it from the PC after transferring the file.
Now, boot your Tab A7 into Download Mode. Power it off, and connect it to the computer over USB while holding the Volume Up and Volume Down keys together. This should bring up the bootloader screen. Simply tap the Volume Up key once to enter Download Mode. Here's what the Download Mode on the Tab A7 looks like.
Next, download Odin v3.14.1 from this XDA thread (NOT the patched version, but the regular one) and extract the contents of the downloaded ZIP package. Then launch Odin on your computer by double-clicking the "Odin3 v3.14.1.exe" executable and click "Ok" when prompted. You should see the Odin interface on your computer screen now.
Odin should automatically recognize your tab in Download Mode and display the COM ID on the top-left.
Click the 'Options' tab and uncheck the 'Auto Reboot' option. This will prevent the tablet from being automatically restarted after the flash is complete.
Now, load the firmware files in the respective slots of Odin.
The BL firmware file (BL_T500/5XXXXXXX_xxxxxxxxxxx.tar.md5) goes to the "BL" slot
The CP firmware file (CP_T505XXXXXX_xxxxxxxxxxx.tar.md5) goes to the "CP" slot. Note that the CP firmware only applies to the Tab A7 LTE variant with the SM-T505 model number.
The HOME_CSC firmware file (HOME_CSC_OMC_ODM_T500/5XXXXXXX_xxxxxxxxx.tar.md5) goes to the "CSC" slot. We will not be using the regular CSC, as it will erase all the data. If you want to do that, feel free to use it.
And finally, the patched AP firmware file (magisk_patched.tar) goes to the "AP" slot.
Once the files are loaded in their respective slots, hit the "Start" button to flash them to your tab.
Note: While you could get away with just flashing the patched AP firmware alone, John recommends NOT doing it. Always flash the patched AP along with the rest of the firmware files like BL, CSC, etc.
Wait for the flash to finish. Once it is, you should see the 'PASS!' message in Odin. Like so:
You can now close the Odin window and disconnect your tab from the computer.
Step 7: Perform a Factory Reset
Once the flash is complete, you will need to manually boot your tablet into the stock recovery mode and do a factory reset. This is only mandatory during the initial rooting process, which is exactly what we are doing here.
To do this, hold the Volume Down and Power keys together for about 7 seconds. As soon as the screen turns off, release the Volume Down key and quickly hold the Volume Up key, while still holding the Power key. Keep holding the keys until you see the stock recovery screen.
You should now see the stock recovery screen with some device information in yellow color at the top. Like so:
Use the Volume keys to move the selector to 'Wipe data/factory reset' and hit the Power key to confirm the selection.
You will now see a confirmation prompt on the screen. Select 'Factory Data Reset' to confirm and finally perform a factory reset.
Once done, select the 'Reboot system now' option from the recovery's main menu. Your Tab A7 should now reboot may be more than once, so be patient.
We're not done yet. After booting, you will need to open the Magisk app from the app drawer and follow the on-screen instructions to replace the Magisk stub with the actual full application, and further complete the required setup when prompted by Magisk app.
Once this is done, your Tab A7 should reboot one last time and should be rooted thereafter.
Your Tab is Rooted!
You may now go ahead and start using root applications, install some modules, etc. Since v20.4, Magisk Hide has been disabled by default on new installations in light of the new hardware-backed SafetyNet attestation. So, to use banking/security, or any other sort of apps that may detect root, you will need to turn ON Magisk Hide from within the Magisk App settings.
Before you leave, there are a few key things you should note:
Unlike some other Samsung phones, you will not need to follow any complex button combinations to boot into the stock recovery. A normal reboot will always boot your Tab A7 into the rooted Magisk system. On the other hand, the regular Volume Up + Power key combo will get your tab into the stock recovery mode.
Second, if a new software update is rolled out, you will need to repeat the same process from step #4 all the way to step #7. When updating the FW, you can simply use the HOME_CSC instead of the regular CSC to prevent your data from being wiped. A backup should still be taken.
Click to expand...
Click to collapse
That's all from my side. If you run into any issues, feel free to post. Don't forget to share details like the software version your tab is on, the firmware package you downloaded and used, and of course your tab's complete model number.
Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?
jserio said:
Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?
Click to expand...
Click to collapse
I was really inclined to the Tab S6 Lite. But being honest, I wouldn't have used the SPen that much. So, I dropped it.
I saw Tab A 10.1 (2019), the one you're referring to, and it was a steal for the specs. The reviews were good too. But then the A7 was released, an upgraded model along the same lines. I like it very much. For a budget tab, it really delivers decent performance and a premium-ish design. And, great speakers I must say.
Unlocking and rooting were really fun and easy as well. Overally, it's a pretty darn good tab for the price.
Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.
Gitah. said:
Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.
Click to expand...
Click to collapse
You're welcome!
For me, 3GB of RAM is enough, of course given my usage. I usually use it for browsing and streaming only. Not much of a mobile gamer, use real consoles and PC for that, lol.
I like Samsung's One UI experience, compared to any other OEM skin (apart from OxygenOS). It's quite smooth IMO. Already removed the bloatware via ADB, might as well come with a guide for that.
It could however be different under heavy multi-tasking usage, like playing mobile FPS titles, etc. Couldn't tell on that.
storage problem
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system
You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.
Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I cant seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?
Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse
Cloudxddd said:
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system
Click to expand...
Click to collapse
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.
Dj89 said:
You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.
Click to expand...
Click to collapse
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).
paziusss said:
Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse
Click to expand...
Click to collapse
It's more likely to be unit-based. For example, my OnePlus 8 still hasn't been forced to hardware-backed attestation for SN. But my friend's unit (same model and region) has been.
Have you tried enabling Magisk Hide? It is disabled by default. Another thing to try is the Magisk Props module.
jserio said:
Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I can't seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?
Click to expand...
Click to collapse
Could you share a picture of the screen you're referring to?
DJBhardwaj said:
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).
Click to expand...
Click to collapse
Thanks for the info! I'll post an update later this week once I get it going! Take care and thanks again for posting this guide!
DJBhardwaj said:
Could you share a picture of the screen you're referring to?
Click to expand...
Click to collapse
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.
jserio said:
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.
Click to expand...
Click to collapse
That's great!
As for updates, I think there was a way by blocking the update services using Titanium. Might have to look it up again. I did that years ago. Yes, TWRP would be great for flashing ROMs and NANDroid backups.
I was going for the 10.1 earlier, didn't knew it had one-sided speakers.
I have a question... Unlocking the bootloader and rooting a device are mostly the first steps to a custom rom like lineageos . I find tons of threads for the SM-T510, but not the SM-T505.
Will there ever be a custom rom for the T505?
DJBhardwaj said:
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.
Click to expand...
Click to collapse
So it's impossible to move apps to sd even with root?
Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?
Allow apps to be moved/installed on SD card
ormefocus said:
Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?
Click to expand...
Click to collapse
Same here i tried on 2 different sd cards(SD- HD) format them from the tablet and no one app won't move to the sd card.
I turn on the develpoers options and i fount this option: Force allow apps on external(Makes any app eligible to be written to external storage regardless of manifest values) and i tried to donwload Asphal 9 and Gangster Vegas and 2 apps downloaded to the internal storage...
I chekt if the options to move apps is visable on this apps and its not.
If any one fine how to transfer apps to the sd card i will very thankful
Pre requisites
• Unlocked Bootloader (probably only Indian variant?)
• ADB and Fastboot drivers (I'm assuming you've set that up since you unlocked bootloader)
• Python (used to extract boot image)
• Your stock rom (I found it here: https://realmefirmware.com/)
• time (need some time to download your stock rom and get a hold of your boot image)
Steps:
1) Download Oppo_Decrypt tool from here:
https://github.com/bkerler/oppo_decrypt
2) Extract the contents and place in a folder
3) go to that folder and open a command prompt/power shell in the folder
4) Use commands accordingly
If you've added pip to path:
pip install -r requirements.txt
If you've not added pip to path:
Python -m pip install -r requirements.txt
done? Everything installed?
now get your rom zip file, inside it you'll find a big .ofp file, extract that ofp file and place in the folder where you've extracted your tools
now inside this very folder where ur tools are, create another folder and name it "extract" (tbh u can name the folder anything you want but for the sake of explanation I named it that)
now open a command prompt in the folder where the tools are kept
type: Python
Press space
drag and drop the "ofp_qc_decrypt.py" file in the command prompt
Press space
Drag and drop the large .ofp file you extracted
Press space
Drag and drop the extract folder
Press enter
Wait for a while till there's a message saying
"Extracting super.img" or something along the lines
Exit out of command prompt
Go to the extract folder you'll see a file called "boot.img"
Send this boot.img file to your phone
(Also recommend keeping a copy of the boot.img on your PC for safety)
Install Magisk Manager Apk from the official website on your phone
Open Magisk manager
Click on Install
Click on select and patch a file
Choose the boot.img file you just sent from your PC
after done send the magisk_patched.img to your PC
Now boot your phone into Fastboot mode
(I'll assume you know how to since you've unlocked bootloader)
Connect your phone to your PC using USB cable
open a command prompt and check if your device is connected by typing:
fastboot devices
if it shows up then proceed
type:
fastboot flash boot magisk_patched.img
(Your file name can be different you can just drag and drop the file)
after it says success, type:
fastboot reboot
after reboot open Magisk manager app (might ask u to download?)
and reboot if it asks you to
Congratulations you now have root access!
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
//seems to work for others, i thought it's only for indian roms, because of other posts and EU was locked out for so long, seems to work for EU, too.
IMEI and Baseband only get lost if you unlock the bootloader with the wrong version or boot.img.
smashda said:
BEWARE:Only Indian variant, you lose your IMEI and Baseband!
Click to expand...
Click to collapse
I test it on RMX3311 EU and work fine.
Deleted
Can we make a boot.IMG for the RMX3311 so we can flash in Magisk ?
Hello,
Is there a easy way to hide banking apps some function don't work because my device is unlocked.
karayemis said:
Can we make a boot.IMG for the RMX3311 so we can flash in Magisk ?
Click to expand...
Click to collapse
It is the same method to extract boot image just get your corresponding rom and either use oppo decrypt tool if on version the phone ships with otherwise use payload dumper with correct ota
karayemis said:
Hello,
Is there a easy way to hide banking apps some function don't work because my device is unlocked.
Click to expand...
Click to collapse
Safetynet fix may help but you need root
BR4UTAL said:
It is the same method to extract boot image just get your corresponding rom and either use oppo decrypt tool if on version the phone ships with otherwise use payload dumper with correct ota
Click to expand...
Click to collapse
Hi,
Thanks, worked for me my device it is rooted now and banking apps are working now.
Device: RMX3311 EU
2 more questions:
1. is there a module i can use to activate call recorder on google dialer ?
2. When there is a new OTA can I just install and repeat all above ?
karayemis said:
2 more questions:
1. is there a module i can use to activate call recorder on google dialer ?
2. When there is a new OTA can I just install and repeat all above ?
Click to expand...
Click to collapse
When there is an ota update download it from software update and wait for it to finish extracting
DO NOT CLICK ON INSTALL
Go into Magisk
Do Uninstall Magisk > Restore System Images
Now Click on Install Magisk > Click Install to Inactive slot (after ota)
click ok and let's go
DO NOT CLICK ON THE REBOOT BUTTON
Now go to software update and click Install, your phone will reboot with root available still and ota update applied
For the model 3311 (EU) is there a step by step guide for root? Please, if exists, drop it here. Thank you
geovision said:
For the model 3311 (EU) is there a step by step guide for root? Please, if exists, drop it here. Thank you
Click to expand...
Click to collapse
The process is the same but instead of IN rom you need to get boot image from EU rom
karayemis said:
Hi,
Thanks, worked for me my device it is rooted now and banking apps are working now.
Device: RMX3311 EU
Click to expand...
Click to collapse
Banking app stops working after a while, this is the second time it stopped working.
karayemis said:
Banking app stops working after a while, this is the second time it stopped working.
Click to expand...
Click to collapse
Here's the Thread for it, you can just use the search on top of the page for things you want to fix, the banking issues come with root and you can find the appropriate Threads when searching for Magisk.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Currently iam on this version rmx3312_11_A.20 of realme ui so how can i get the boot image of this version
_PsyDuck_ said:
Currently iam on this version rmx3312_11_A.20 of realme ui so how can i get the boot image of this version
Click to expand...
Click to collapse
The Ota server only offers the latest version of Android 12 with the A.22 software