Hi everyone!
How can I get the bootloader unlock code? I wrote to Huawei and they wrote: "..., Huawei has decided to terminate the unlock code application service, the unlock code application service was terminated. ..."
Is it possible to unlock the bootloader without a code or get it somehow (for free)?
I extracted the boot file and edited the fstab file, like this, but I don't know what it's good for: (
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09)
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09) On Huawei website: http://consumer.huawei.com/en/tablets/mediapad-t3-10/ ROM stock: AGS-W09: AGS-W09_AGSW09C233B215 AGS-L09: AGS-L09_AGSL09C233B216 Custom Recovery: In English: TWRP...
forum.xda-developers.com
)
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check, fileencryption
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check
(deleted the "fileencryption" part)
What happens if I flash the modified boot file?
NayemUM said:
Hi everyone!
How can I get the bootloader unlock code? I wrote to Huawei and they wrote: "..., Huawei has decided to terminate the unlock code application service, the unlock code application service was terminated. ..."
Is it possible to unlock the bootloader without a code or get it somehow (for free)?
I extracted the boot file and edited the fstab file, like this, but I don't know what it's good for: (
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09)
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09) On Huawei website: http://consumer.huawei.com/en/tablets/mediapad-t3-10/ ROM stock: AGS-W09: AGS-W09_AGSW09C233B215 AGS-L09: AGS-L09_AGSL09C233B216 Custom Recovery: In English: TWRP...
forum.xda-developers.com
)
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check, fileencryption
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check
(deleted the "fileencryption" part)
What happens if I flash the modified boot file?
Click to expand...
Click to collapse
Hello and good afternoon, @NayemUM Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Related
hi @ all
for my project i need to "simualte" a file in android / java and i don't know if this is possible?
what i want to do:
- create a file (eg /sdcard/test.txt)
- everytime when the system or another app wants to read form /sdcard/test.txt i should receivec an event / call and can send requestet bytes
is this even possible?
kind of the /dev/random file...
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Hey Peeps,
A Great XDA Dev @lebigmac has written a script that will allow us to have full Read/Write and Mount access while rooted on Android 10 devices. While it has had great succeess on Xiaomi devices, he's steadfastedly working hard on ensuring Motorola devices don't get left out.
So, I'm asking to the brave to come and test out his script and give feedback! It's really important so bugs and errors can be worked out.
I've been testing his script with my Moto One 5G Ace and we haven't been successful yet, but we need more Moto devices to compare where the problem may be at as to why the script isn't working for the Moto devices.
So please, come to his thread and try his script and report the findings. It would be a great help to make sure we finally get write access and mount access to our system files. TWRP and Non-TWRP users are both welcome.
Thanks.
The Script is here on XDA:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Thanks for sharing!
I have a moto g power 2021 bootloader unlocked and rooted. I have tried everything even the r/w files from all kinds of forums to get access on Android 10, 11, & 12. I can't figure out how to make the system read and write. I've tried the unofficial twrp and it doesn't have touch. I am on android 11 with the June security patch. I need r/w access to be able to edit the build prop and to edit my wifi and network properties. Any help would be appreciated.
Devices: Samsung A125F and Samsung A8 Star
Terminal commands that have been run: mount -o rw,remount / (but reports read only)
Why does Android 9+ default Android root system ro and that hard to be remounted rw?
And what patches will be helpful for doing so when terminal fails?
This also makes build.prop and fstab prevented to be written
Hi @hd_scania you can try my SystemRW / SuperRW featuring MakeRW script. Also keep in mind I am working on brand new version which will be released very soon!
To make it work in Android 12 you can simply open the file systemrw.sh with text editor and comment out line number 415 by adding comment symbol ( # ) in front. It should look like this #sdkCheck. Now save file and run script as usual. Please show me your log afterwards. Thanks. Good luck!
Wait a second you are running Android 9 ? Please keep in mind my script was designed for Android 10 and later!
In Android 9 and earlier by default you should be able to remount your partitions as rw without any problems as long as your device is rooted.
I instead flashed the VNDK edition of the Lineage 19.x GSI (i.e. I’m running Android 12, system rw/ro is ultimately GSI dependent), and now system becomes RW
hd_scania said:
Devices: Samsung A125F and Samsung A8 Star
Terminal commands that have been run: mount -o rw,remount / (but reports read only)
Why does Android 9+ default Android root system ro and that hard to be remounted rw?
And what patches will be helpful for doing so when terminal fails?
This also makes build.prop and fstab prevented to be written
Click to expand...
Click to collapse
@hd_scania
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A as it didn't qualify for development.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Does anyone have the lgv60ea version to decompress the modemst1, modemst2, ftm, fsc, fsg partitions in Qualcomm 9008 mode
@kaitian1978 Welcome to XDA! I hope you'll always find and get the support you require.
However, I've moved this thread to Q&A and closed it as duplicate of your hours earlier created one:
Ask to extract some partitions of lgv60EA
Does anyone have the lgv60ea version to decompress the modemst1, modemst2, ftm, fsc, fsg partitions in Qualcomm 9008 mode
forum.xda-developers.com
Please review the XDA Forum Rules, to which you agreed to adhere when you registered a few hours ago, with currently special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
I have installed Android x86 9.0_r2 in a virtual machine using the virt-manager application (QEMU/KVM connection) on Ubuntu 22.04, and I installed it using the ISO and manually selecting the OS as Android x86 9.0. Upon booting, I see a Trusted GRUB 1.1.5 menu and I am able to boot Android x86.
However, my resolution is stuck in 1024x768, and I have to manually edit the GRUB entry and add 'vga=914' after the kernel option to boot with a resolution of 1920x1080.
I read some forum posts stating that the GRUB boot options are located in either a 'menu.lst' file or an 'Android.cfg' file, so I opened the terminal emulator and ran the following commands to find these files in the root directory or sub directories. I also searched for the GRUB directory directly.
su
find / -iname menu.lst -type file -mindepth 100
find / -iname android.cfg -type file -mindepth 100
find / -iname grub -type directory -mindepth 100
However, these commands did not yield any results. So I decided to use grep to try and find the statements present in the boot commands in any of the files present in the system. I decided to search for the statement "root=/dev/ram0", so I ran the following commands to run grep recursively and print the filename where the given text occurs, ignoring errors and binary files:
su
grep --exclude-dir /proc -sIrl "root=/dev/ram0" /
This search took too long, so I narrowed my search to the term "ram0" and checked individual directories instead. However, there were no readable text files containing the boot menu configuration.
Am I making a mistake in any of these commands? Where is the GRUB configuration file located? Please feel free to ask for any additional information to troubleshoot this problem.
Thank you in advance for your help and have a nice day.
kb_android_x86 said:
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
Click to expand...
Click to collapse
Hello and good morning, @kb_android_x86
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
I have found the solution to this problem.
To access the GRUB configuration files, you must boot Android x86 in Debug mode, and then type the following commands into the terminal:
mount -o remount rw /mnt
cd /mnt/grub
vi menu.lst
Then you can edit the GRUB configuration permanently. I am unsure why these files are hidden when booting Android x86 normally, even when I browse the filesystem with root privileges enables.