Related
Dear Xda,
Im An Oppo user my Device details As follows.
Device: Oppo F3 ( CPH1609)
MTK6750T
4Gb Ram, 64 GB ROM
Running on ColorOs 3.0.0i (Based on Android 6.0)
There are lot of problems / bugs in Os which Oppo Even failed to rectify.
When ever i Mailed them they simply quoting their common quotes
So i decided to Root my phone to develop ( no i cant do it lone )
During search of Root i found few obstacles
1) Oppo made decision to remove fastboot option fron their device
Ref: https://forum.xda-developers.com/r7-plus/help/decision-oppo-bootloader-fastboot-t3348114
2) MTK droid Tools not fully supporting the chipset
Ref:https://forum.xda-developers.com/attachment.php?attachmentid=4178413&thumb=1&d=1497202499
3) One click Root is not working ( king, farma etc)
4) cannot obtain boot & Recovery imgs to development
5) i thought stock firmware flash file may have useful but there are 2 types of probles
(A) flashablezip version : it has boot. Img but no recovery.img included. Also it is With. Ozip Not with. Zip extension
(B) PC version : it is like encrypted file. With. Ofp extension And With some other type file. And it is not flashing through SP-FLASH TOOLS. The flashing tool is different.
Ref https://m.youtube.com/watch?v=qw4HIQER0mg
Guys thease are my problems. Coz of those i failed to root my device.
My only Hope is Xda, you people know better than me ( probably Best) . Please analyze and and give suggestions.
Thanks In Advance
LEAGOO_T5_OS2.1_E_20180116 (Not THFC edition):
https://www.mediafire.com/#3c2rnntnz3kw0
LEAGOO_T5_OS2.1_E_20181025.zip -- Original Leagoo T5 ROM
LEAGOO_T5_OS2.1_C_20181025.zip -- Custom Leagoo T5 ROM
----
Package includes:
Firmware: Leagoo device files for SP Flash, full ROM pack with updated boot & recovery (2018).
MDROM Files: APDB, MDDB and MDROM files for SN Write Tool (IMEI, MAC's).
MTK USB Drivers: Drivers for Windows 10, follow the instructions.
Pack: Contains notes and changes for the current build.
----
Tools:
MTK Extractor: Extracts .img files for inspection or modification, be aware system.img cannot be modified.
Platform Tools: Android ADB and Fastboot executables and other related programs.
SN Write Tool: Writes IMEI and MAC address data incase of loss or format.
SP Flash Tool: Used to flash files and backup your phone.
----
Comments:
I have pre-setup the readback option in "SP Flash" to backup your current NVRAM and NVDATA partitions.
Simply set a save location to save the files and press readback, now you have a backup.
If you have formatted your phone, you can use this pack to restore it.
Write down your phones mac addresses.
----
How to restore:
Open two "SP Flash Tool" windows, load one with "Firmware" as "Format + download", load the other with the "MDROM files" as "Download".
Swap over the file locations so that the "Firmware" window downloads the "MD" files, and "MD" downloads the "Firmware" files.
Format + download with the "Firmware" window, once complete, do not power on the phone, simply unplug the USB cable.
Now load "SN Writer" and install your IMEI and MAC's. Unplug the power cable, again, not powering on.
Go back to the "MD" window, and download (update) the files, now restart the phone.
----
If you are updating your ROM from an older version, don't install "cache" and "userdata".
----
Tools and guides for debloating and customizing the ROM, without root, are included.
thfc version
Ferather said:
LEAGOO_T5_OS2.1_E_20180116 (Not THFC edition):
Sources: Needrom (still can't add links yet, sorry.)
----
Package includes:
Firmware: Leagoo device files for SP Flash, full ROM pack with updated boot & recovery (2018).
MDROM Files: APDB, MDDB and MDROM files for SN Write Tool (IMEI, MAC's).
MTK USB Drivers: Drivers for Windows 10, follow the instructions.
Pack: Contains notes and changes for the current build.
----
Tools:
MTK Extractor: Extracts .img files for inspection or modification, be aware system.img cannot be modified.
Platform Tools: Android ADB and Fastboot executables and other related programs.
SN Write Tool: Writes IMEI and MAC address data incase of loss or format.
SP Flash Tool: Used to flash files and backup your phone.
----
Comments:
I have pre-setup the readback option in "SP Flash" to backup your current NVRAM and NVDATA partitions.
Simply set a save location to save the files and press readback, now you have a backup.
If you have formatted your phone, you can use this pack to restore it.
Write down your phones mac addresses.
----
How to restore:
Open two "SP Flash Tool" windows, load one with "Firmware" as "Format + download", load the other with the "MDROM files" as "Download".
Swap over the file locations so that the "Firmware" window downloads the "MD" files, and "MD" downloads the "Firmware" files.
Format + download with the "Firmware" window, once complete, do not power on the phone, simply unplug the USB cable.
Now load "SN Writer" and install your IMEI and MAC's. Unplug the power cable, again, not powering on.
Go back to the "MD" window, and download (update) the files, now restart the phone.
----
If you are updating your ROM from an older version, don't install "cache" and "userdata".
----
Tools and guides for debloating and customizing the ROM, without root, are included.
Click to expand...
Click to collapse
Hey, i own a thfc version of this phone , and the software is total garbage , i want to flash the non thfc version to my phone , will that brick it? There is very little if any difference in the t5 and t5 thfc versions , besides the custom color outer cover and logo, also thfc version does not shiw the notification led , it might be bug? no updates awailable as usual, thanks if you answer.
B.
Leagoo T5 THFC: https://www.devicespecifications.com/en/model/6d9b43f7
Leagoo T5: https://www.devicespecifications.com/en/model/13b543f6
The difference is the camera's, although I did once flash my T5 with the THFC edition, it runs, but I did not test the camera.
No it will not brick your phone, but the cameras might not work, flash back to THFC if this is the case.
Edit: The LED is for charging on both models, no notification LED.
----
camera
Ferather said:
Leagoo T5 THFC: https://www.devicespecifications.com/en/model/6d9b43f7
Leagoo T5: https://www.devicespecifications.com/en/model/13b543f6
The difference is the camera's, although I did once flash my T5 with the THFC edition, it runs, but I did not test the camera.
No it will not brick your phone, but the cameras might not work, flash back to THFC if this is the case.
Edit: The LED is for charging on both models, no notification LED.
----
Click to expand...
Click to collapse
So in thory if i add the camera drivers from the thfc edition , it may function the same?
I really need something that improve its battery life because it barely can do 1 day.
Also audio is not very loud.
Any " god firmware " for it?
I might take it if it do not brick it... , because serously this is a joke that is installed on it.
Also if you happen to know the z5 lte im looking for a better rom for that too, i found a lot , but all crc problems or cant install, i already have twrp , and root on it.
You should only need to flash boot, recovery and system, however if I remember correctly when I flashed my T5 to THFC edition, I flashed the whole lot.
Download my custom version with root, if you need add or replace files or apk's, it's likely to work without further modifications.
MOD Edit Links Removed- T5: Latest official (ignore some of the older posts).
MOD Edit Links Removed -- T5: Custom based stock with root.
I cannot comment on the Leagoo Z5 LTE, because I don't own one, sorry.
You could try these "prop" (system.img or boot.img) tweaks:
# System properties
ro.media.enc.jpeg.quality=100
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
logcat.live=disable
ro.HOME_APP_ADJ=1
wifi.supplicant_scan_interval=120
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
ro.ril.power_collapse=1
pm.sleep_mode=1
ro.mot.eri.losalert.delay=1000
power_supply.wakeup=enable
ro.config.hw_fast_dormancy=1
ro.config.hw_power_saving=1
persist.adb.notify=0
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.scrollingcache=3
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
touch.pressure.scale=0.003
# End properties
Personally I am impressed with the overall quality of the newer Leagoo phones.
If you want more beef get a phone with a "Helio P60" SoC or better.
https://www.devicespecifications.com/en/model/728e4dfb -- Leagoo S10 (Example)
----
When buying a new phone, checkout your current phones specifications, and then the model you are currently looking at, here are some tips:
Compare CPU cores and speed. RAM size, speed, and channels (single, double, quad). GPU cores and speed.
Make sure the modem meets the standards used by your sim provider (technology and frequency).
The last step is to read reviews and watch videos, when happy make your purchase.
Useful sites:
https://benchmarks.ul.com/compare/best-smartphones
https://www.devicespecifications.com/
----
The z5 lte has mtk6737 its not a bad cpu in a budget phone , currently im waiting for the t8s to arrive, also i got a power 2 on the way.
The z5 lte runs well with manually updated firmware , but the t5 thfc edition is straight garbage.
I may try your suggestions , thanks.
---------- Post added at 10:49 PM ---------- Previous post was at 10:17 PM ----------
I found a phone with same capabilities as my leagoo z5 lte , its a 4.5" doopro p4 , same screen resolution same cpu , same ram same rom size , screen is 0.5" smaller but only stock rom available for , can you help me port this to my leagoo ?
I have looked into the T8s, It's an upscaled T5, so hardware modifications should be the same (same prop tweaks). It's Oreo based, and does have slightly different parts.
Since the SoC is the same as the T5, it's limits are the same (single channel RAM, 2 core GPU), however I doubt you will find better for the money.
I play games on my gaming PC, the T5 was an ideal phone (I got mine new for £68), quality parts, great camera, it's also quite loud.
I have looked at other brands for the same price, not much to say except I am happy I bought the Leagoo.
Reply to edit:
Leagoo Z5 LTE - MT6735M - https://www.devicespecifications.com/en/model/24663de4
Doopro P4 - MT6580 - https://www.devicespecifications.com/en/model/7adb48ba
Different SoC. Try this Google search for the MT6735M:
https://www.google.co.uk/search?q=MT6735M+firmware
Stock Leagoo Z5 LTE : https://firmwarefile.com/leagoo-z5-lte
https://www.google.co.uk/search?q=leagoo+z5+lte+firmware
----
I suggest the stock Leagoo firmware, install Magisk and modify boot, you will then have root, and can flash back to stock.
Also you can edit the ".img" files, by extracting or mounting them with Linux-Unix, or other utilities.
https://forum.xda-developers.com/general/general/commander-cygwin-cmder-t3910807
----
First modify the 'default.prop' with device tweaks, then delete any apps you do not want, if you break it, flash it back.
Write down the device's details: MAC addresses (bluetooth, wifi), IMEI's, and serial number (barcode).
Use 'SP flash tool' to upload firmware's, and also to backup your current one (use a guide).
And use 'SN write tool' to restore your devices details, as above.
----
But the leagoo , claims it has 6737m , not 35 , thats nearly the same , i done a search for mt6737 854x480 1gb 8gb , it gave me homtom ht26 , huawei y3 , vkworlf f1 , and doopro p4 . Which of these will be better to do ports from? Or do i need to go cm 14.1 or linage direction ?
I am not sure to be honest, I guess the one that has cameras and other parts that are the same or similar, with the least amount of apps installed.
You would probably be better of with CM or Lineage like you said, the other ROM's will have device branding and properties.
Dear all,
Here is a tutorial to unlock meizu E3 without any malicious software.
The idea is to edit frp partition and make the fastboot flashing unlock pass the security check.
Please note below might damage your phone so do it as your own risk, i do not responsible to any damage made.
Detail step:
(1)get root access
(2)install terminal emulater app
(3)dump frp partition
(4)modify frp by hex editor at offset 7fff8 and 7fff to 1 (not sure 7fff8 or 7ffff take the effect, so i edit both) as frp1
(5)write frp1 back to frp partition
(6)reboot boot loader
(7)fastboot flashing unlock
(8)press up-vol or down-vol (not sure, i stop here, feedback welcome)
(9)done
This is generic enough for MTK and Qcom soc, success story other than sdm636 and mt6755 are welcome.
Other phone unlock tutorial:
Meizu M3note bootloader unlock
Regards,
99degree
An unofficial twrp for MeizuE3 is available below for people unlocked bootloader and would like to play with custom rom.
twrp custome ver 3.3.1:
http://s000.tinyupload.com/?file_id=01088261345935635855
-ramdisk is from twrp.me model whyred
-kernel is self compile, based on LA.UM.8.2.r1-05700-sdm660.0
-with lcd and touchpad driver patched
BTW, this twrp support encrypted data partition, so it is working parallel with flyme8 well.
An official MeizuE3 recovery img is also provided here for people would like to boot and restore flyme back.
https://gofile.io/?c=pFRTJy
A vlog for booting MeizuE3 with LineageOS 17.1 up to splash screen is available at youtube:
It is based on below LOS custom system build from rcstar6696 and kvsjxd, credit him:
https://forum.xda-developers.com/mi-a2/development/10-x-lineage-17-0-jasminesprout-t3966643
and with his another wayne vendor:
https://forum.xda-developers.com/mi-a2/xiaomi-6x-wayne/rom-lineageos-17-0-t3989193
Found in other thread* that mentioned about persist partition might be wiped by LOS17 or other custom rom and cause Wlan mac missing etc. I suspect this is also true for unstable wifi too. So if there is anybody have an original persist partition dump please upload and share. [20200303]The issue is fixed by two thing. /persist/wlan_mac.bin modification. Recompile kernel to include 3 more modules (fw-api, qca-wifi-host-cmn, qcacld-3.0).
https://forum.xda-developers.com/showpost.php?p=80217431&postcount=2
Hi there,
MeizuE3 boots up LOS17.1 with WIFI, detail is at below youtube video. Check it out!
Custom ROM from rcstar6696 and ItsMeShouko, creadit them.
https://forum.xda-developers.com/mi-a2/development/10-x-lineage-17-0-jasminesprout-t3966643
Or my modified ROM based on above jasmine sprout ROM.
https://forum.xda-developers.com/android/development/meizu-e3-lineageos-17-1-rom-porting-t4055605
Thx,
99degree
I'm having trouble understanding the architecture of mobile (and Android) devices. I compare it a lot to the design of PCs, laptops, etc, which I know quite well.
Here's my understanding on how PCs work when booting:
The hardware has firmware stored in ROM (Read Only Memory). Actually, Flash memory is used nowadays, on which the stored content can of course be changed, unlike real ROM memories in the old days. Because the firmware is hardware-specific and its operation is very critical, its content is rarely updated or otherwise changed. Installing new firmware is called flashing. Firmware in a PC is most commonly BIOS or UEFI, the task of which is (briefly) to first run the POST tests, provide some interfaces and finally start the software in the mass storage. By mass storage, I mean memory separate from the firmware's Flash memory, which can also be Flash memory, such as an SSD disk, or a more traditional hard disk.The BIOS (i.e. firmware) in the specified order (which first is the internal NVMe SSD or the external USB hard disk?) tries to load the software into the RAM memory for execution from mass storage MBR (Master Boot Record) part . Master boot record is a physical defined area in mass storage. Bootloader software is stored on this MBR part.When the bootloader (located on the MBR part) is loaded into RAM and run, it knows the contents of the end of the disk and starts the kernel from there.The kernel starts (in Linux) the init process, nowadays often Systemd, which starts the rest of the software.--------------------
What kind of memories and storages are most commonly found in Android devices? One main memory (i.e. RAM)? One Flash memory for firmware (i.e ROM)? Another separate flash drive that acts as mass storage? Possibly SD card and USB stick as external mass storage?
What is firmware on Android devices?
What is the bootloader in (located in MBR part) on Android?
Linux is the kernel used by Android, which is started by the bootloader? After that, Android continues to boot, how?
A pile of terms, which I have ambiguities:
Bootloader; What's it like on Android? It is often characterized as hardware specific. So is it the case that the bootloader in Android is firmware? So in Android, the firmware runs the tasks of the PC world BIOS and bootloader (located in the MBR part), and then starts the Android located on the mass storage?
Recovery; What is this technically?
Android ROM; I can't understand this. As far as I know, Android is an operating system located mass storage, not Read-Only-Memory firmware.
Rooting; On a PC, we are used to the fact that the owner of the device has root rights. Is it just that the manufacturers have decided to set the default root password to some generated random string, and by default, the user only has access to the basic user account?
After the above has been answered, I would like someone to explain to me (separately) technically, starting from the hardware level (where and how), how do Android devices booting and work? Links to additional information are also welcome. hank you very much! If anyone can answer my questions, thank you very much!
Your questions should put you to shame.
Start reading yourself, building up your knowledge as you read.
Anyway, welcome to the forum. After a year of reading, you will laugh at your post.
ze7zez said:
Your questions should put you to shame.
Start reading yourself, building up your knowledge as you read.
Anyway, welcome to the forum. After a year of reading, you will laugh at your post.
Click to expand...
Click to collapse
I know my questions are stupid, but I'm impasse. It seems that there is much less information about designing for mobile devices than PCs. Could you link some articles on this? As the last article I read this, but it didn't help much, because I compare too much what I learned on PCs.
There are no stupid questions, there are only stupid answers.
Start with the basics based on information from google:
Architecture overview | Android Open Source Project
source.android.com
ze7zez said:
There are no stupid questions, there are only stupid answers.
Start with the basics based on information from google:
Architecture overview | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
That is useful, but there is a reason why I asked about mobile/Android device design/architecture. Android itself is as far as I know (if I'm not mistaken) just an operating system, like the desktop operating systems Windows and Ubuntu, but mobile/Android devices are very different from PCs in terms of hardware and firmware. For example: https://www.quora.com/Is-there-anything-like-BIOS-in-mobiles-How-do-they-boot
How long is a huge ball of string?
No simple answer...
This is for those who are new to Android development and basically have NO understanding about the partition structure. I will give a high-level introductory explanation. PC GNU/Linux users: please note this is completely different from x86 (PC Linux) partition table. You will not come across partitions denoted as sda1, sda2, sdb1, sdb2, and so on. Instead, it will be structured as follows:
/boot
This is the partition that has all the data that is necessary for the phone to boot. It includes the kernel and the RAMDISK (these are the only components of the operating system that are stored in this partition. The remaining are stored in /System). Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, except the kernel and the RAMDISK (as mentioned in /boot explanation). This includes the Android User Interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, but you will still be able to boot into the /recovery partition to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. Think of this like a proprietary recovery partition that PC companies put on prebuilt PCs. When you flash a custom recovery such as TWRP or CWM, you are overwriting this partition.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to store your media, documents, downloads, pictures, videos, ROMs etc. on it. It is like the equivalent of the ' Users/[Username] ' folder in Windows and ' /home/~ ' folder in x86 Linux. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
/Boot (Is NOT viewable in Android)
/Recovery (Is NOT viewable in Android)
/Data (Userdata) (Is viewable in Android)
/Cache (Is viewable in Android)
/System (Is viewable in Android)
/Misc (Is NOT viewable in Android)
Ram
https://developer.android.com/topic/performance/memory-management
Understanding Firmware naming:
N986USQU1ATGM
N=Note
986U or F etc, the model of device
SQ, FX etc = CPU and model specific
U,S,E = Update, Security, Engineering, respectively
1,2,3,4,5 etc = bootloader revision (This is important! You cannot go to a previous revision)
A,B,C,D = Android version
T, U = Year (T=2020, U=2021 etc)
A,B,C etc = month (January A - December L)
1 - 9 and then A - Z =build compilation. This basically means how many builds there are in a month. They start at 1 and go to Z
So N986USQU1ATGM would be
N968-U-SQ-U-1-A-T-G-M
N968U (Note 20 Ultra Carrier version), SQ (Snapdragon), U (Update), 1 (Bootloader version), A (Build 10), T (2020), G (July), M (22nd build)
How to enter Download Mode:
Turn off the device.
Connect USB cable to your PC (Leave it disconnected from the phone)
Press and hold down the Volume Up and Volume Down buttons. While they are still pressed, plug in the USB cable into your phone.
The phone will go into download mode press volume up. In Odin you will see that phone is added.
Dirty Flash:
I would only do this if you are having to manually update to the newer firmware and would not do it if you are coming/going to U/U1 or from beta firmware or if you are on an old firmware. I'd also highly recommend doing a back up prior to the doing this
Load these into Odin
BL
AP
CP
HOME_CSC
Do NOT flash CSC or USERDATA, either of these WILL wipe your device
This is a "dirty flash" and these can sometimes cause issues. Keep in mind if things start going sideways and stuff starts not working right, your first step to a solution will be to wipe the device.
Tips on flashing U1 Firmware:
You will have to wipe, can NOT dirty Flash going between U and U1 firmware
Use the patched ODIN linked in post #2 or #3, Odin3_v3.13.3b (They are exactly the same)
Have an active US Carrier SIM installed to get carrier features
If you get your CSC Stuck on XAA/XAA/(Insert your carrier here), and can not get Carrier options back.
PIT files
https://ihax.io/samsung-pit-files-explained
plus_rlus said:
I know my questions are stupid, but I'm impasse. It seems that there is much less information about designing for mobile devices than PCs. Could you link some articles on this? As the last article I read this, but it didn't help much, because I compare too much what I learned on PCs.
Click to expand...
Click to collapse
The are no stupid questions.
Questions are asked when we do not understand something and want to learn.
There is nothing wrong or negative about asking questions.
Questions are a part of how we learn.
Cheers.
plus_rlus said:
<SNIP>
What kind of memories and storages are most commonly found in Android devices? One main memory (i.e. RAM)? One Flash memory for firmware (i.e ROM)? Another separate flash drive that acts as mass storage? Possibly SD card and USB stick as external mass storage?
What is firmware on Android devices?
What is the bootloader in (located in MBR part) on Android?
Linux is the kernel used by Android, which is started by the bootloader? After that, Android continues to boot, how?
A pile of terms, which I have ambiguities:
Bootloader; What's it like on Android? It is often characterized as hardware specific. So is it the case that the bootloader in Android is firmware? So in Android, the firmware runs the tasks of the PC world BIOS and bootloader (located in the MBR part), and then starts the Android located on the mass storage?
Recovery; What is this technically?
Android ROM; I can't understand this. As far as I know, Android is an operating system located mass storage, not Read-Only-Memory firmware.
Rooting; On a PC, we are used to the fact that the owner of the device has root rights. Is it just that the manufacturers have decided to set the default root password to some generated random string, and by default, the user only has access to the basic user account?
After the above has been answered, I would like someone to explain to me (separately) technically, starting from the hardware level (where and how), how do Android devices booting and work? Links to additional information are also welcome. hank you very much! If anyone can answer my questions, thank you very much!
Click to expand...
Click to collapse
Firmware is the hardware specific drivers, library files and other resources that are supplied by the manufacture(s) and are chipset specific.
The firmware is proprietary and normally closed source. Basically the parts that make the hardware work.
The bootloader is what actually boots the device.
This is supplied by the device manufacture(s) and is device specific.
It is separate from the system.
Recovery is a mini Android environment.
- Factory (Stock) recoveries are restricted to the user but have unrestricted (root) access to the device.
- Custom recoveries (TWRP, OrangeFox, ..) allow the user unrestricted (root) access to the device.
Android ROM (rom) is the actual system (OS) and normally you would include the version that you are running.
Stock roms - Google 12L, AOSP xx, OOS 12, MIUI xx, ColorOS xx, ...
Custom roms - Lineage 19.1, crDroid 12.1, AospExtended 12.1, ...
In computer terms it would be..
Windows 7, Linux (Fedora 34), MacOS Monterey.I am not sure what the current versions of MIUI and ColorOS are, hence the xx.
Once the bootloader boots the device, a few things can happen.
- The system boot image (system kernel) takes over and boots the device into system (rom).
- The recovery boot image (recovery kernel) takes over and boots the device into recovery (mini Android environment).
- If system fails to boot, device reboots into recovery (Recovery Party) if recovery can boot.
- If no boot image takes over, you will stay in the bootloader, reboot into some special mode or just a good old fashion boot-loop.
There have been a lot of changes to Android though the years..
Each device, manufacture, Android version.. can be different from another.
The most common bootloader is (or supports) fastboot but, this is manufacture and device specific.
Not to be confused with fastboot_d (new story that started with Android 10/11?).This has also changed though the years, some manufacture use their own variation of bootloader.
HTC had H-BOOT, Samsung does their own thing along with some other manufactures.
Rooting....
By default the substitute (switch) user su command is removed from Android.
This is what most refer to as superuser since it defaults to root user if you do not specify a substitute user.
This has been a long and changing story in the Android world also.
Old but, well worth the read.
How-To SU - [chainfire.eu] - Link
The current most popular used root solution is Magisk.
It is a little more than just su. Magisk - [GitHub] - Link
---
It might be easier if you see an actual partition table.
Nexus 7 16 Gig WiFi - [PastBin] - Link
Might as well make it an ... interesting one.
In this example, userdata only has 1.2 Gigs since the rest is used by other partitions.
userdata is mounted as /sdcard.
Save for boot, cache, system, misc, recovery and userdata.
The other partitions would be considered firmware.
When the device boots, the partitions get mounted to /dev/block.
Hope it helps more than confuse.
Cheers.
Hi everyone, today I want to share my experience of rooting OPPO A15s (CPH2179)
(Specs: Mediatek Helio P35, 4GB RAM LPDDR4x, 64GB storage, 2 nano SIMs 4G, SD card supported)
It seems like fastboot doesn't really work on newer OPPO phones, as neither did my phone get that to work. Trying "adb reboot bootloader" (of course after unlocking OEM in dev options) will give the "fastboot_unlock_verify fail".
It was such a pain in the ass for me trying to find a way to flash my phone with Magisk (fastboot failed, TWRP needs fastboot to flash), until I found mtkclient.
The steps are simple through the command line; I've got some bootloops, red code, etc... But those problems can be easily avoided if you made them right.
In the end, I still managed to make my phone gets rooted.
A thing to notice is that don't try to use the GUI interface; otherwise, you will get stuck in "Waiting for connection" while your phone still stays in BROM mode.
CLI is recommended.
OPPO phones have the Secure Payment feature, which helps to check the integrity of the system in order to allow banking apps to execute. This feature checks if your phone is rooted (you can hide that easily using Zygisk); and if your phone has an unlocked bootloader.
If one of those conditions is met, then banking apps will be blocked by a system banner. The system will also issue a root detection to the app so in case you made it to turn off the system banner, you won't be able to get into the app.
Losing the ability to use banking apps brought me a lot of inconvenience at the end of the day, so while I still have yet to find out a Magisk module to bypass the system check, I decided to relock my bootloader - which in order to do must delete metadata and userdata, of what that also made my phone unrooted.
If you are planning to root the OPPO A15s, visit mtkclient's Github link for the tutorial. Keep in mind that you'll still need a copy of the stock ROM in case of something goes nuts, and an ozip to zip decryptor to decrypt the stock ROM ozip file (OPPO sucks)
Links:
mtkclient: https://github.com/bkerler/mtkclient
ozip to zip: https://github.com/bkerler/oppo_ozip_decrypt (bkerler massive tbh)
CPH2179 stock ROM: https://support.oppo.com/in/software-update/software-download/?m=A15s