The presented files for root in the official firmware f800 * Android 9. Based on the official sources PIE of the LG with minimal changes (fixed static boot ).
Only for F800 * phones with unlocked bootloader.
Small manual
LGup firmware in "partition dl" mode KDZ android 9, remove daws aboot, abootbak, laf ( laf must be left from android 7-8).
In Fastboot mode, run boot-twrp.bat (the kernel and TWRP will be flashed).
Go to TWRP: Cleaning - Selective cleaning - select the "ENCRYPTION" swipe ... be sure to before each DATA format .. (This is a feature of this TWRP only), data format, wipe cache and dalvik cache. Reboot TWRP.
Installing Magisk first, then Lg_rctd_disabler as desired. If you need to disable encryption, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020, otherwise you do not need to flash this file. TWRP supports encryption MTP+ADB+OTG .
For F800S only: Before the first system boot, System / Product / Priv-app remove "Findlostphone".
Next, reboot into the OS.
TWRP 3.4.0 : Enable MTP before connecting to PC! , Use the data backup with the previously disabled password lock, pin code, ....
Config TWRP android 9 (us996.zip)
MTP, second screen...OS no problem F800S version (as in android 7-8).
The "fixed static boot" and "us996.zip" files are the source for developers who wish to build their own kernel or TWRP.
Presented as is. any borrowing, modifications and changes are welcome
I need a more detailed explanation
With LGup what exactly to do
And I say exactly
And in the BAT file I get an answer "waiting for the device
I have drivers and it recognizes it
I'm talking about the device F800L
Awaiting quick reply Thanks in advance
LGup for KDZ firmware, for example (F800L30e_00_1022.kdz) for F800L.
BAT file for Fastboot mode of the phone.
Boot-twrp.bat + TWRP.img + boot1.img must be put in the Fastboot folder before starting.
It's very simple if you have experience unlocking the bootloader.
Den4ik111111 said:
LGup for KDZ firmware, for example (F800L30e_00_1022.kdz) for F800L.
BAT file for Fastboot mode of the phone.
Boot-twrp.bat + TWRP.img + boot1.img must be put in the Fastboot folder before starting.
It's very simple if you have experience unlocking the bootloader.
Click to expand...
Click to collapse
I already have the F800L30e installed
And I have the KDZ file
Where do I get the BAT file from?
And I get waiting for device
When I try to play the file
Yes i have drivers
yes i checked it works
This is just for short answers for you
You mean the BAT file that is in the first message Or another file
Because the same file in the first post I tried several times
And it does not work for me
In which folder to run the file In the fastboot folder
Or from the main folder
In the "download mode" you will not succeed. You need to put the phone in "fastboot mode" to write TWRP + boot.
If you do not have "fastboot mode" then the bootloader is blocked. If I understood you correctly, then this is exactly so.
^^^Only for F800 * phones with unlocked bootloader^^^
Den4ik111111 said:
In the "download mode" you will not succeed. You need to put the phone in "fastboot mode" to write TWRP + boot.
View attachment 5223339
If you do not have "fastboot mode" then the bootloader is blocked. If I understood you correctly, then this is exactly so.
^^^Only for F800 * phones with unlocked bootloader^^^
Click to expand...
Click to collapse
1 Yes I have F800L As you can see in the picture
2 This Write download mode That's what I put it on
3 How do I get to "fastboot mode "
Volume down + cable not working
Yes the cable is connected to the computer
Yes the device is turned off
AVIMPEG said:
3 How do I get to "fastboot mode "
Click to expand...
Click to collapse
You need to make DirtySanta Bootloader unlock!
Den4ik111111 said:
You need to make DirtySanta Bootloader unlock!
Click to expand...
Click to collapse
I left everything alone
hi thank you for your effort
Could you enlighten me about the f800l bootloader unlock
I have applied the dirtysanta method to unlock then I root with magisk now I am under pie and root with magisk but when I check the bootloder status it displays locked under nougat and under pie (when updating)
I wonder if the ditysanta method and to bypass restriction of the bootloader to root the mobile or it is a permanent unlock or imissed sme think?
jeddouu said:
hi thank you for your effort
Could you enlighten me about the f800l bootloader unlock
I have applied the dirtysanta method to unlock then I root with magisk now I am under pie and root with magisk but when I check the bootloder status it displays locked under nougat and under pie (when updating)
I wonder if the ditysanta method and to bypass restriction of the bootloader to root the mobile or it is a permanent unlock or imissed sme think?
Click to expand...
Click to collapse
You can ignore it!
The dirtysanta method does not bypass the bootloader.
The bootloader is overwritten by the engineering unlocked from us996 (aboot.img, abootbackup.img).
With the rule ((LGup firmware in "partition dl" mode KDZ, remove daws aboot, abootbak)), there will never be problems when downgrading or upgrading the android version (repeating the "dirtysanta method" will not be needed).
In short, "permanent unlock" with an unlocked bootloader from us996.
Den4ik111111 said:
You can ignore it!
The dirtysanta method does not bypass the bootloader.
The bootloader is overwritten by the engineering unlocked from us996 (aboot.img, abootbackup.img).
With the rule ((LGup firmware in "partition dl" mode KDZ, remove daws aboot, abootbak)), there will never be problems when downgrading or upgrading the android version (repeating the "dirtysanta method" will not be needed).
In short, "permanent unlock" with an unlocked bootloader from us996.
Click to expand...
Click to collapse
thank you very much... in your small manual you did not explain how to use the fixed static boot file because I have this problem thank you in advance for your patience
jeddouu said:
thank you very much... in your small manual you did not explain how to use the fixed static boot file because I have this problem thank you in advance for your patience
Click to expand...
Click to collapse
Added an explanation of the files.
one thing if you allow
it is about mic the caller does not hear me except in free hand I test the mic with app recording it works well I deactivate voice google I resolved by changing some value to mixer_paths. xml but the recording in somme apps like whatsup is very low and not clear in pie and nougat if you have an idea
jeddouu said:
one thing if you allow
it is about mic the caller does not hear me except in free hand I test the mic with app recording it works well I deactivate voice google I resolved by changing some value to mixer_paths. xml but the recording in somme apps like whatsup is very low and not clear in pie and nougat if you have an idea
Click to expand...
Click to collapse
The F800 dialer has a built-in call recording and records well. Google Voice is not needed for this. WhatsApp, like many other messengers, does not have a built-in recording, attempts to record by third-party applications often lead to poor quality (the compression quality plays a big role as the connection quality). Try every possible application, even outdated ones, and you might find the right one.
I can be wrong somewhere, I don’t use call recording.
Den4ik111111 said:
You need to make DirtySanta Bootloader unlock!
Click to expand...
Click to collapse
Does the DirtySanta Bootloader Unlock work for the F800K model? I should have gotten the F800L, but I ended up with the F800K which seems to have little mention anywhere.
.
DonChino said:
Does the DirtySanta Bootloader Unlock work for the F800K model? I should have gotten the F800L, but I ended up with the F800K which seems to have little mention anywhere.
Click to expand...
Click to collapse
Yes.
Hi im on f800l with pie have you a kernel for software Version 30h? Thanks
TarAntonio said:
Hi im on f800l with pie have you a kernel for software Version 30h? Thanks
Click to expand...
Click to collapse
The official kernel sources for Android 9 (LGF800L_LGF800K_LGF800S_Android_Pie_v20a) were released in a single version, without updates. PIE 30h, 30e must be compatible with the kernel. This kernel was posted by me on another resource more than a year ago, here recently. So far no one has spoken about the incompatibility of the kernel with the "30h" firmware. Otherwise it would have been indicated.
Den4ik111111 said:
The official kernel sources for Android 9 (LGF800L_LGF800K_LGF800S_Android_Pie_v20a) were released in a single version, without updates. PIE 30h, 30e must be compatible with the kernel. This kernel was posted by me on another resource more than a year ago, here recently. So far no one has spoken about the incompatibility of the kernel with the "30h" firmware. Otherwise it would have been indicated.
Click to expand...
Click to collapse
Have you a link for download only the pie kernel?
Related
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Msjoannalynn said:
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Click to expand...
Click to collapse
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Messi got you covered.
Personally I would recommend against rooting right now. There isn't much to be done with the Aristo at this point in time except to make backups of your system. Most you'll end up doing is learning a few things about why mixing system based and systemless mods can lead to pretty unpredictable results.
ninjasinabag said:
There isn't much to be done with the Aristo at this point in time except to make backups of your system.
Click to expand...
Click to collapse
This is exactly what I've wanted to do - preferably by having direct rw access to the flash, like I did on my old phone. Unfortunately the only viable custom recovery procedure right now (messi2050's) involves wiping the userdata partition (unless you somehow happen to have an unlocked bootloader). To make matters worse the userdata partition is encrypted AFAIK. Surely the keys are stored on the phone somewhere but there wouldn't be a way to get them without some exploit, and I don't know if this phone is popular enough for someone to bother researching and publishing an exploit.
There was some progress here (github.com/Lekensteyn/lglaf) on reversing and exploiting LG's LAF protocol in their recovery OS, but it hasn't been updated for more than a year now. If anyone wants to play around with that code, be sure to read this issue (github.com/Lekensteyn/lglaf/issues/7) which has ongoing attempts at reversing LAF's current auth methods. I don't have the time right now to dive into this unfortunately.
messi2050 said:
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Click to expand...
Click to collapse
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
1118niranjan said:
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
Click to expand...
Click to collapse
You need to do some search yourself
messi2050 said:
You need to do some search yourself
Click to expand...
Click to collapse
i saw your post in android form they've said u are the best guy to help any link if u can ?
1118niranjan said:
i saw your post in android form they've said u are the best guy to help any link if u can ?
Click to expand...
Click to collapse
Power your phone off.
Hold VOL DOWN WHILE PLUGGING DEVICE INTO COMPUTER WITH USB - this will bring it to the fastboot screen. If you have all drivers installed then you can simply open a cmd window and type "fastboot oem unlock" - which should unlock the bootloader - if all drivers are installed. Then continue with the tutorial as usual.
Is root worth it
So, I have an LG ms210 (Lg Aristo) that I've own for a little over 3 months now, but i have been experiencing this issue since about 1 week into ownership. The phone seams to have a RAM leak or something similar as about every hour it slows down substantially, usually to the point of freezing, or crashing all together and restarting on its own, even if not being touched since I power it on. Ive been thinking about rooting it to debloat, but im not sure if it will help, or if i should just invest in a new handset. I have since factory reset it, deleting more high-resource apps, and leaving it bare-bones system apps and nothing else, but the problem still persists. The carrier i MetroPCS if thats a factor, but i dont see why it would be. Any thoughts?
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!??
captnbluebeard said:
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!
Click to expand...
Click to collapse
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
ninjasinabag said:
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
Click to expand...
Click to collapse
I did that already, im trying to get xposed up and running but my model #lvl3 doesnt match what is in the terminal in twrp. I still get a weird error ph4u
Most likely shows as the lg stylo 2 plus as I guess your using the lineage backup. So just use the model of the lg stylo 2 in terminal? Guessing as I don't use xposed. What do you use xposed for?
To get it running on the aristo is to either edit build prop values to match the ms210 model, or remove the device requirements from xposed's update binary.
failed remote cannot flash this partition in unlocked state.
Anyone?
can some walk me thru this idk what im doing wrong but i go into adb i reboot bootloader and when i try to fastboot oem unlock it says device not found what am i doing wrong?
question
does this root works for lg ms210 security patch level jan 1 2018?
I believe the root is just twrp so it should work fine. Just update first then follow the steps for flashing twrp and the most recent magisk and probably dm verity thing. If something fails it can be eaily reflashed with the original firmware with correct software and the firmware image/kdz.
Edit: try to reinstall the lg drivers? Also a try a tool called minimal adb and fastboot here
Help. It just staus on "" waiting for device " with oem unlock step
Before rooting your phone , it is necessary to backup data for your phone .
pressing the vol - before plugging in, it would show "download mode" for a spit second and go straight to fastboot mode. i cant do anything in fastboot mode since i cant get it to show on "adb devices".
i was just starting to root this V300L30p and managed to flash the h930 to unlock the bootloader. after flashing the unlock bin i waited and held the vol - button as said in the guide but the phone never boot up. i waited 30 mins or so. i tried to get to download mode and reflashed the h930 rom using dual mode LGUP partition dl but it didnt work and i just got "cant open port" i tried refurbish and it also didnt work. i tried master reset and it didnt work in trying to reflash. after a while i just couldnt access the download mode and it just goes too fast to fastboot mode.
electrical potato said:
pressing the vol - before plugging in, it would show "download mode" for a spit second and go straight to fastboot mode. i cant do anything in fastboot mode since i cant get it to show on "adb devices".
i was just starting to root this V300L30p and managed to flash the h930 to unlock the bootloader. after flashing the unlock bin i waited and held the vol - button as said in the guide but the phone never boot up. i waited 30 mins or so. i tried to get to download mode and reflashed the h930 rom using dual mode LGUP partition dl but it didnt work and i just got "cant open port" i tried refurbish and it also didnt work. i tried master reset and it didnt work in trying to reflash. after a while i just couldnt access the download mode and it just goes too fast to fastboot mode.
Click to expand...
Click to collapse
In fastboot mode, is your Bootloader unlocked?
Can you run the getvar command?
What H930 KDZ did you flash? The right one?
ChazzMatt said:
In fastboot mode, is your Bootloader unlocked?
Can you run the getvar command?
What H930 KDZ did you flash? The right one?
Click to expand...
Click to collapse
just ran get var all command. it says "unlocked_count 1" and "unlocked: yes"
i used H93020d_00_OPEN_EU_OP_0326.kdz when it was available in the first post.
edit: also ran fastboot devices, it showed : ???????????? fastboot
edit 2: ran fastboot devices again and phone turned off. did it again and got : LGH930d794576b fastboot
electrical potato said:
just ran get var all command. it says "unlocked_count 1" and "unlocked: yes"
i used H93020d_00_OPEN_EU_OP_0326.kdz when it was available in the first post.
edit: also ran fastboot devices, it showed : ???????????? fastboot
Click to expand...
Click to collapse
OK if your Bootloader is unlocked and you have fastboot, then you don't need Download mode right now.
Install TWRP, root. Follow Section 6 of the WTF instructions.
Later after you restore modem you can worry about Download mode.
ChazzMatt said:
OK then you don't need Download mode right now.
Install TWRP, root. Follow Section 6 of the WTF instructions.
Click to expand...
Click to collapse
thanks man. really eased me up in there.
ChazzMatt said:
OK if your Bootloader is unlocked and you have fastboot, then you don't need Download mode right now.
Install TWRP, root. Follow Section 6 of the WTF instructions.
Later after you restore modem you can worry about Download mode.
Click to expand...
Click to collapse
it says that "Requested download size is more than max allowed"
electrical potato said:
it says that "Requested download size is more than max allowed"
Click to expand...
Click to collapse
See the Section 7 Trouble Shooting Tips.
You're using the TWRP listedto WTF post, right?
ChazzMatt said:
See the Section 7 Trouble Shooting Tips.
You're using the TWRP listedto WTF post, right?
Click to expand...
Click to collapse
tried it on my laptop and it works perfectly
electrical potato said:
tried it on my laptop and it works perfectly
Click to expand...
Click to collapse
That is one of the Trouble Shooting Tips... Try different computer.
Welcome to the Root Club!
ChazzMatt said:
That is one of the Trouble Shooting Tips... Try different computer.
Welcome to the Root Club!
Click to expand...
Click to collapse
another problem arose. now in TWRP. wipe to format data, typed yes, and it returns with red text "failed to mount /system (unknown error 150)". same happens when i try to do a backup.
should i go to advanced wipe and change the file system of /system to others and then back to ext4?
edit: fixed by selecting ext4 in change file system. /system was showing 0mb, after redoing the file system it is now 14mb and able to be backed up
I have problem with lg v30.
It is v30 VS996 (maybe). but it was flashed US998 Pie. And now it has an error on camera and fingerprint.
I can not enter download mode to flash stock rom and bootloader is locked.
Please, tell me what should i do.
Thank you.
CuDem said:
I have problem with lg v30.
It is v30 VS996 (maybe). but it was flashed US998 Pie. And now it has an error on camera and fingerprint.
I can not enter download mode to flash stock rom and bootloader is locked.
Please, tell me what should i do.
Click to expand...
Click to collapse
Try a regular Factory Data Reset from the Settings menu, if you haven't already. If the bootloader is locked and the phone never rooted (which it sounds like) it is unlikely that the actual ROM was corrupted - though or course not impossible.
What happens when you try to enter Download mode?
I tried to reset factory in setting and it had no effect. With reset data on recovery, it showed error message.
When i enter the download mode, it show 5 dots.
I have no idea to solve this issue
CuDem said:
I tried to reset factory in setting and it had no effect. With reset data on recovery, it showed error message.
When i enter the download mode, it show 5 dots.
I have no idea to solve this issue
Click to expand...
Click to collapse
Are you saying you have TWRP (custom recovery) on your phone? With BL locked?
Factory Reset from Settings menu only works with stock recovery, and goes deeper than TWRP wipe.
If you have TWRP, you can use that to re-flash your ROM (as ZIP) and/or to re-flash laf (Download Mode, either as ZIP or as image).
Otherwise it sounds like Download Mode is there, but LGUP isn't picking it up correctly. I suggest starting over with LGUP. People often have the wrong version, since so many are floating around: Uninstall it completely, delete its folders, possibly uninstall USB driver as well. Restart Windows. Now install drivers and LGUP from scratch using the exact versions and installation steps from ChazzMatt's Pie ROM thread linked below:
[US998][STOCK][PIE]LG V30 US998 US99830b_00_0902.KDZ
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
If that still doesn't do it, then try different USB port, different cable, even different computer. Some computers are not compatible with LGUP.
TheDannemand said:
Are you saying you have TWRP (custom recovery) on your phone? With BL locked?
Factory Reset from Settings menu only works with stock recovery, and goes deeper than TWRP wipe.
If you have TWRP, you can use that to re-flash your ROM (as ZIP) and/or to re-flash laf (Download Mode, either as ZIP or as image).
Otherwise it sounds like Download Mode is there, but LGUP isn't picking it up correctly. I suggest starting over with LGUP. People often have the wrong version, since so many are floating around: Uninstall it completely, delete its folders, possibly uninstall USB driver as well. Restart Windows. Now install drivers and LGUP from scratch using the exact versions and installation steps from ChazzMatt's Pie ROM thread linked below:
[US998][STOCK][PIE]LG V30 US998 US99830b_00_0902.KDZ
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
If that still doesn't do it, then try different USB port, different cable, even different computer. Some computers are not compatible with LGUP.
Click to expand...
Click to collapse
No, my phone bootloader is locked then i can not install TWRP. I tried with your LGuUP you mention above but not successfully.
May i try to flash by fastboot follow this link:
https://androidforums.com/threads/flash-using-fastboot-mode.970254/
thank you
CuDem said:
No, my phone bootloader is locked then i can not install TWRP. I tried with your LGuUP you mention above but not successfully.
May i try to flash by fastboot follow this link:
https://androidforums.com/threads/flash-using-fastboot-mode.970254/
Click to expand...
Click to collapse
Thank you for the update.
I wouldn't recommend that procedure you linked. That post is five years old, for a completely different phone (LG G2), using a KDZ extractor from 2014 which probably doesn't work with today's KDZ files.
I still don't see how your Download Mode could have been damaged on an unrooted phone. I think the problem is most likely your PC or your cable.
But that aside, I say it's time to rip off the bandaid: Unlock the bootloader and put TWRP onto the phone. It's easy on US998. Follow the guide linked below.
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
LG V30 is one of the most well documented, most rootable, and most supported phones on the planet -- largely thanks to the guy who wrote that guide. So don't look for any other solutions from anywhere else on the internet
TheDannemand said:
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
LG V30 is one of the most well documented, most rootable, and most supported phones on the planet -- largely thanks to the guy who wrote that guide. So don't look for any other solutions from anywhere else on the internet
Click to expand...
Click to collapse
Thanks for the very kind words. :good:
TheDannemand said:
I still don't see how your Download Mode could have been damaged on an unrooted phone. I think the problem is most likely your PC or your cable.
But that aside, I say it's time to rip off the bandaid: Unlock the bootloader and put TWRP onto the phone.
Click to expand...
Click to collapse
As we discussed elsewhere, however, he would need Download mode to go back to the early Oreo firmware is he wanted to bootloader unlock and root.
There have been reports of other people losing Download mode when updating to US998 Pie -- but those were people using the TWRP flashable zip. The fix was to flash US998 20e (Oreo) TWRP flashable zip and for some reason that restored Download mode. They could then try again to update to US998 Pie if they really wished. I haven't see that reported flashing with KDZ.
The fingerprint and camera issue is also reminiscent of a V30 that was on LOS-17 (which needs a permissive kernel). Even when going back to stock firmware, you still have to run permissive. The fix for THAT problem is to refurbish to Nougat stock firmware and then update back to newer stock firmware (last Oreo which is very stable or Pie which has some issues).
But he can't do that either until he gets Download mode back.
I really don't have any suggestions.
Thank you for pointing that out, @ChazzMatt!
@CuDem: ChazzMatt is completely right. I forgot you have to use Download Mode to roll back to 20b in order to use the WTF bootloader unlock trick. Duh... So that's not a path for you to fix this.
To me it sounds like this phone WAS previously BL unlocked and rooted, and that's where the problems with Download Mode began. Or LOS-17 was installed, causing the Camera and Fingerprint issues mentioned. Maybe the previous owner re-locked the bootloader and sold the phone, pretending it was in better shape than it was?
I can think of the following:
1) If you know the history of the phone and that it was never unlocked or rooted before, then I would still say it is unlikely that its laf partition (which contains Download Mode) was actually corrupted. The phone could still have been Frankensteined incorrectly or "abused" with LGUP, but because of very thorough integrity checking when flashing through Download mode, it would rarely cause you to lose Download mode. So if you KNOW it has never been BL unlocked, I would continue trying on a different computer, with different cables, different USB ports, drivers etc. If fastboot devices returns a serial number, that's a good test that USB drivers and ADB connection is working. But you could still have LGUP issues. Again, some computers (particularly some AMD processors) are simply not compatible with LGUP.
2) See if you can find the OTA update file for US99830b and force update it using LGUP FOTA mode. This works with the phone booted into the OS and MTP (file sharing) turned on. It may not complete the update since you are already on 30b, but it will rewrite laf (Download mode) as its first step. Several H932 owners have done that back in the Oreo days, and a few have done it on Pie. Study the thread linked below for the background and the procedure. But DO NOT use the files shared in that thread, NOR ANY OTHER H932 FILES. You will brick your phone if you flash anything H932 on any other model, or vice versa.
[H932][T-MOBILE] URL for the H932 Pie OTA file
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417
3) Use Qualcomm 9008 mode and the leaked firehose to rewrite the laf partition (or the entire firmware). This is a more complex procedure, which I cannot help you with, but it allows writing almost anything to the phone, and should be compatible with all V30 models EXCEPT H932. See the thread linked below, and be ready for some hard work:
LG V30 Unbrick guide (Qualcomm EDL 9008 Mode, Hardbirck, with no download mode)
https://forum.xda-developers.com/lg-v30/how-to/lg-v30-unbrick-guide-qualcomm-edl-9008-t4048661
4) Contact the XDA member from Moldova who can repair your V30 remotely for a fee. His name always escapes me, but maybe Chazz or others remember. He is also on eBay:
Remote Service Repair Unbrick LG G7 G6 V30 V35 V40 in Qualcomm Mode 9008
https://www.ebay.com/itm/Remote-Ser...794311?hash=item46994ee187:g:gd0AAOSw0qFdJi7a
And that's all I can think of. Once again, please report the outcome back here, as it may help others. Good luck to you
Edit: Oh, and then there is Update Error Recovery on the Update tab in LG Bridge, which has worked for some to fix Download mode. It also runs from inside the OS (at least initially). But I am not sure LG Bridge works with US998, let alone on Frankenstein'ed phones. Still, it's easy, so worth a try.
TheDannemand said:
To me it sounds like this phone WAS previously BL unlocked and rooted, and that's where the problems with Download Mode began. Or LOS-17 was installed, causing the Camera and Fingerprint issues mentioned. Maybe the previous owner re-locked the bootloader and sold the phone, pretending it was in better shape than it was?
Click to expand...
Click to collapse
Running this fastboot command and looking at unlock_count and lock_count can be used to determine if the phone was bootloader unlocked before...
Code:
fastboot getvar all
jptV30 said:
Running this fastboot command and looking at unlock_count and lock_count can be used to determine if the phone was bootloader unlocked before...
Click to expand...
Click to collapse
Oh yeah, right. That's a good idea if you don't know whether the phone has been rooted.
So to use this, you will need to be bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled this is a must!!(its always good to make a nandroid before making any changes on your phone). What this will do is more or less provision your Lg G8x to your Desired Carrier, it will also let you change your apns, so you have volte working and also the data indicator will change to match the carrier. WIfi calling is working on tmobile, will need someone to test other carriers.
There seems to be confusion , this is only for the Stock rom. this will do nothing for GSI roms.
Instructions:
1.Extract to Content of zip to Sdcard
2.Make a copy/backup of your own files: Go to twrp and backup your product partition and your op configs in case you need to restore them
3.Copy and paste the files from my zip to:
/product/op/config
and this single file cust.prop to /product/op
make sure permissions are 644.
4.Reboot your device it should now be provisioned to your Desired Carrier.
Click to expand...
Click to collapse
Download
Sprint Untested
SPR-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
T-Mobile
Tmo-VOLTE-VOWIFI-FIx-G8x
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
VZW Untested
VZW-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Credits:
vl48 this guy is awesome, and also very patient an expert in lg devices.
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
e20140 said:
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
Click to expand...
Click to collapse
There is one already made, you just need the correct twrp from telegram
siulmagic said:
There is one already made, you just need the correct twrp from telegram
Click to expand...
Click to collapse
Why not post on xda? Is everyone switching to telegram? I've read everything on xda and don't see a specific method to unlock bootloader+twrp+DM but a few failed attempts on ATT version of the G8X. I only see working solution for India, Europe, and Sprint Models. You are the only one that has successfully unlock it. I am sure more people will need help as 3G is going away and we need Volte working on this phone.
well the basic gist of it is:
This will WIpe Your Phone, make sure to backup first.
Cant post the recovery zip, but pm il send it to you. i will move this to a proper thread later today. and better formatted
1.install qpst/qualcom driver or use windows update ones
2. download firehose uncompress it somewere on your pc
3.download g8x twrp and magisk 20.4 zip also the dm verity zip
also make sure to grab the eng abl for the g8x(eng bootloader that will allow us to unlock).
4. enable oem unlock in developer settings
5. boot phone into edl mode
6.start qpst set storage type to ufs, slect built type, make sure it is flat build
7.Look for select programer then click browse, here you will chose the firehose file
8. click select port on qfil then double click 9008 com port were the phone is detected in edl mode
9.now in qfil select tools then partition manager
10. when the list of partitions show up look for abl_a,abl_b,modem a/b, and modemst1 and 2, you will right click each of them and click manage partition data then read data, this will back them up to your computer(be very careful you can wipe your whole phone if you click in the wrong place)
11.after you back up everything select load img and flash abl_a to Abl_a and abl_b. after this unplug phone and boot into bootloader mode.
To boot into bootloader mode turn off your phone and hold volm down and plug in your usb cable, this should boot it into bootloader mode .
12. if you see text that says you active boot slot, you now have successfully flashed the eng bootloader witch will allow you to unlock the bootloader.
13. now while the phone is pluged into your computer you will open a adb window and type fastboot oem unlock , the phone will ask you to agree to unlock the bootloader, select yes.
14.after this reboot your phone into edl mode, reflash your backup abl_a to abl_a and abl_b, this will restore stock bootloader you wont have fastboot anymore but no worries, also you can flash your stock rooted boot.img to boot_a and boot_b.
15. After you reboot into android, install magisk manager, flash the g8x twrp zip and without reboot, also flash magisk 20.04 zip, if you do not do it this way you will break your boot.img and have issues, like freezing system.
16 now reboot to recovery wipe data then reboot and flash the dm verity disabler to disable encryption. after this create a nandroid backup, then just reboot back to system and enjoy.
17. profit
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
e20140 said:
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
Click to expand...
Click to collapse
why 0o with gpst and firehose you can root bl unlock any att g8x, unless there something im not aware of?
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
e20140 said:
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
Click to expand...
Click to collapse
thats a driver error, you need to let windows install the driver from windows update or like i did use qpst on windows 7. i never got that erro fixed, so i just used windows 7 on a old laptop i have, and it works mint.
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
e20140 said:
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
Click to expand...
Click to collapse
well thats the error i got, with my g8 and g8x on windows 10.
wangsu10 suggested the error could be installation selection option for the QCOMM driver. Need to be install as 2nd option " ETHERNET-DHCP". I already returned mine
Maybe you can try it on your Win10 and report back. If it works, we need to have it added to the OP for all others to see.
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
nate0 said:
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
Click to expand...
Click to collapse
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
siulmagic said:
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
Click to expand...
Click to collapse
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
@siulmagic where is the twrp image for the g8x? Did they pull it down?
nate0 said:
@siulmagic where is the twrp image for the g8x? Did they pull it down?
Click to expand...
Click to collapse
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
nate0 said:
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
Click to expand...
Click to collapse
there is another app that needs updated i forgot witch one it was.
siulmagic said:
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
Click to expand...
Click to collapse
Newbie to Telegram, how does one find the group please?
mangojain said:
Newbie to Telegram, how does one find the group please?
Click to expand...
Click to collapse
LG Mobiles India 🇮🇳
Political Discussion, Obscene material/words, Selling, Fraudulent link posting will lead to Ban SHARING COPYRIGHT CONTENT & PIRACY NOT ALLOWED, it leads to REPORT & BLOCK Photography Group: @lgg8xphotography OT Group: @LG_G8X_OffTopic
t.me
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol