Related
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Downloading, will post results!!! Thanks!
milankragujevic said:
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Click to expand...
Click to collapse
Not working twrp not working touch screen
I have twrp all work i Russia
milankragujevic said:
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Click to expand...
Click to collapse
Could it work with alacatel 1 (5033a)? It has the same chipset but differs in other characteristics.
Hey, are you still building a Lineage OS?
Los link estan caidos. Instale el twrp pero queda en bootloop twrp. Saque el boot.img con el twrp para parchearlo con magisk pero al flashearlo con cmd vuelve a quedarse en el twrp. Podrias pasar el boot.img stock? Gracias
Flash recovery
AUTH files doesn't work with A variant (5059A).
January 2020 and the link is gone. (I can host it if you like. Message me.)
The files are back up. Sorry about the inconvenience.
NP. Thanks.
Update links PLS
Hello? Does anyone have the DA and Auth files? The links are broken and I cant find online, help pls my phone is hard bricked. Thanks.
T3ll3S said:
Hello? Does anyone have the DA and Auth files? The links are broken and I cant find online, help pls my phone is hard bricked. Thanks.
Click to expand...
Click to collapse
Links are back, the server had failed and I moved the files to another datacenter which took 3 days.
Here's a MEGA link just in case, if this happens again: https://mega.nz/file/i3BhASJJ#pNzwAsflvcvdfr3pGzUfbNhe3fHUCnfyoAR_O4IsFAE
Hi again, does anyone of you know how to fix this error, im very scared that my phone wont show any screen again.
This is what happened: I tried to install Android 10 GSI and bootlooped so I went to TWRP and used my backup but from no reason the phone died during the backup and when I powered it on it vibrates but it doesnt show any image at all and takes a bit longer to vibrate.
The error on SP Flash Tool is STATUS_BROM_CMD_FAIL (0xC0060005). What do I do? When I try to flash it turns the LED on but then it turns off and turns on again but gives this error. If also there is a way to boot to bootloader directly tell me PLSS. Its Hard Bricked.
T3ll3S said:
Hi again, does anyone of you know how to fix this error, im very scared that my phone wont show any screen again.
This is what happened: I tried to install Android 10 GSI and bootlooped so I went to TWRP and used my backup but from no reason the phone died during the backup and when I powered it on it vibrates but it doesnt show any image at all and takes a bit longer to vibrate.
The error on SP Flash Tool is STATUS_BROM_CMD_FAIL (0xC0060005). What do I do? When I try to flash it turns the LED on but then it turns off and turns on again but gives this error. If also there is a way to boot to bootloader directly tell me PLSS. Its Hard Bricked.
Click to expand...
Click to collapse
You did not flash correctly. The device isn't hard bricked, you have to turn it off (take it apart and disconnect the battery then reconnect it but don't turn on, keep the back cover off because you will surely need to repeat this many times), go to Options, Download and enable "Storage checksum" and "USB checksum", and then start flashing and then plug in the phone while SPFT is trying to flash. When SPFT starts flashing do not touch it, when it flashes the phone will reboot. You also need a proper stock ROM.
You can also just literally use the Mobile Upgrade S Gotu2 tool from Alcatel: https://mega.nz/file/DjpzTRDB#vC3SrO5hQr1Nzn32lWxVGLhmclfSpPF6CsIWHRaTsP8 and restore the stock ROM that way.
I cant with SP Flash Tool It gives the same error and with the other softwate it tels that i am at the latest version
T3ll3S said:
I cant with SP Flash Tool It gives the same error and with the other softwate it tels that i am at the latest version
Click to expand...
Click to collapse
You can, you are just doing it wrong. Check the checksum options I mentioned and retry.
Do i need to touch in any button before i flash? The other software why it tells that im on the newest version? What is the error about? I cant boot onto nothing it doesnt even show a screen but i will try harder
T3ll3S said:
Do i need to touch in any button before i flash? The other software why it tells that im on the newest version? What is the error about? I cant boot onto nothing it doesnt even show a screen but i will try harder
Click to expand...
Click to collapse
Yes, I clearly told you:
In SP Flash Tool: Go to Options, Download and enable "Storage checksum" and "USB checksum".
THEN flash.
I enabled but still no results. The button i was talking about is on the phone do i need to touch the phone or just put the usb?
I open this thread because in my opinion the development situation of the various versions of the device is very confusing. I seem to have understood that as regards the unlocking of the bootloader with a working fingerprint, the situation is evolving well only on the China and India version while on the European version nothing moves ... In my modest opinion, Realme deciding to treat those who buy its phones in Europe as users of its lower series devices compared to other areas of the world are wrong because little development leads to a few posts in the various forums and few voices in google searches that each of us does when deciding what to buy ... What do you think you realme device owners in Europe?
I have the 1993ex version and the FP is working fine after a16
hammerheading said:
I have the 1993ex version and the FP is working fine after a16
Click to expand...
Click to collapse
Thanks for the information ... What procedure did you use to unlock the bootloader?
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Bolumstar said:
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Click to expand...
Click to collapse
So you too like me, although there is news of the working fingerprint on the EU, believe that it is still not worth unlocking.
I ask it because I repeat following the various treadhs on the forum it gets confused. It is sometimes indicated that the finger epint works and that for example magisk can work in normal mode and not core only ... This would already be a lot, to say yes it could use the viper4android.
surferbyter said:
Thanks for the information ... What procedure did you use to unlock the bootloader?
Click to expand...
Click to collapse
I used this guide, it works the same for X2.
hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
surferbyter said:
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
Click to expand...
Click to collapse
First time i flashed the twrp i folowed this but now i simply skip the vbmeta and flash twrp directly from bootloader and it works fine.
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
woocashewski said:
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
Click to expand...
Click to collapse
never installed a gsi, if I'm not mistaken it takes the image of the vendor ... if you can give me a link to a guide to get started? Thanks in advance...
Howto thread is on this forum...
woocashewski said:
Howto thread is on this forum...
Click to expand...
Click to collapse
I'm doing something wrong because i get bootloop everytime. i tryed to follow the guide with different gsi but no luck. Can you give a quick step how you did it ?
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
surferbyter said:
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
Click to expand...
Click to collapse
I've been there, i think the problem was the adb. I used the Minimal adb and it worked, give it a try
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
woocashewski said:
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
Click to expand...
Click to collapse
So gsi roms also have fingerprint problems ... However, more than a custom rom, I was interested in coloros with root ...
I can't give up the fingerprint though because some applications of the company I work for use it for authentication ...
I managed to root, magisk 20.3 zip flash on twrp, on the European version a17 with this guide:
https://forum.xda-developers.com/showpost.php?p=81579961&postcount=44
To make the vbmeta flash command work I used the minimal adb version 1.43, with previous versions it doesn't work.
The fingerprint works very well and energy consumption has not changed compared to use with locked boot.
After carrying out all the procedure, the magisk manager indicates the certified safety net unlike the play store which is instead not certified. To have it certified, you need to download the Device ID app, copy the GSF code that gives you the result by opening it and insert it on the page of this link:
https://www.google.com/android/uncertified/?pli=1
After having it delete the data of google service framework and google play store, force the arrest of the second and reopen it ...
hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Sandalwood83 said:
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Click to expand...
Click to collapse
Ok my bad then, i follow more than one guide so im not sure were i got the apk from. anyway good job finding it for future unlocks!
ROM Stock EU Version
Here the ROM Stock EU https:// drive.google.com/file/d/1-GpV3YBMCCCrQPvCKqqK3cYRXmBMzTCy/view?usp=drivesdk
Just copy the link
Since this device tends to bootloop easily and because I've seen lots of questions about it and information is spread across many threads and posts, I'm writing this guide to help you guys troubleshoot bootloops before asking generic "help me" questions.
I) Terminology
1) BROM - A readonly memory on the SoC that runs right when the device boots. Loads the preloader. SPFT talks to it after authentication.
2) Preloader - MTK firmware that resides on flash. It is loaded on the chip's SRAM. It is responsible for initializing DRAM, and is one way of authenticating SPFT (the other is authenticating directly with the BROM, but I believe the way thi is done is known only to MTK and OEM engineers, and not even to authorized service centers). It also loads LK. Its source is distributed to OEMs, but is otherwise unavailable. Plenty of leaks for other devices can be found on the internet (some from the OEMs themselves).
3) LK - Little Kernel. This seems to be the most common platform for Android bootloaders. Mediatek has its own proprietary branch. Same source status as preloader. As an android bootloader, it is responsible for loading recovery or usual kernel image, as well as fastboot flashing.
4) Kernel - If you're on these forums, you should know what it is. You can find it in boot.img
5) DTBO - The device tree for the linux kernel. It specifies which hardware is available on the device. On usual (x86) PC platforms, the BIOS and Option ROMs store device information and offer it to the kernel (through UEFI/ACPI). As arm boards do not have such those, the linux kernel uses dtbos which play the same role.
II) Boot process
1) The ARM cores on the SoC start and jump to the address of the BROM.
2) (I'm not very sure of this, there's too little information) BROM puts the cores into a known state, should listen on the in-build UART for some time (half a decade ago, some leaks said something about 150ms), and if it doesn't receive anything, it loads the preloader.
3) The preloader initializes basic stuff like DRAM (phone's ram), watchdog, USB, etc. If the phone is connected to SPFT, it talks to it and authenticates it (the (in)famous "Account not authorized for this operation" should come from a check in here). I believe it also turns on the charging light. On a normal boot, it further loads lk. I belive that it also shows the chinese menu on pressing the Vol- button on factory preloader, but I did not check this.
4) LK (the one that comes with factory preloader) checks if Vol+ is pressed, and displays the bootloader menu (the one with the 4 english entries). When selecting recovery, it loads recovery. If normal boot is selected, it loads boot.img and dtbo.img and I believe it makes some checks on them (possibly of signatures, see the kernel trees). It then loads the proper image from the logo.bin partition and displays it (note: I've checked Logo Builder; rebuilding the logo.bin partition with it makes LK reboot before showing any image - this is done after the boot menu); examples are the one where it shows "Unlocked" or the Fastboot background. It also checks vbmeta for verified boot. Then it boots the selected entry.
5) The linux kernel does some hardware init, mounts system and starts Android's init.
6) Android does its usual init, mounting vendor, loading modules and firmware, turning on stuff like wifi, bluetooth, gnss, etc.
III) Tips for diagnosing bootloops
1) When bootlooping, plug your phone in a computer and check for the following (this is from my experience):
a) Charging light turning on
b) Vol+ menu showing up
c) Redmi logo showing up
d) Charging light turning off
e) Boot animation showing up
2) Things to do based on where things didn't work as in (1):
If (a) doesn't turn on, you're most likely in deep ****, and I'm not sure who can help you. Edit: Try pressing Vol+ and see if a device with VIDID 0x0e8d:0x0003 shows up. That would be the BROM. If it shows up, try using SPFT (most likely won't work, but you have nothing to lose anyway).
If (b), try SPFT. If it shows "Account not authorized", you have the stock preloader. There's a couple threads here with some methods that may or may not work. Otherwise, ATM you'll quite literally have to pay for your mistake. Grab your wallet and your Windows VM. You'll need them. Be prepared to search for the least shady guy that can help you and have your usb passthrough (on the upstream hub) ready.
If (c) - i.e. you have the menu but no logo, this means you've got LK. Since the Redmi logo doesn't show up, it means something is not quite how lk likes it (and lk is very picky on this phone). If you can, you'll probably want to use fastboot and flash a known good image for whatever you changed. If not, use SPFT.
If (d) - i.e. you have the logo but the charging light doesn't turn off, this means LK didn't boot the linux kernel. Flash a different (working) kernel.
If (e) - the charging light turns off, but you have no boot animation, this means either the kernel panics before it can start Android or that Android failed to boot properly.
From here on, you can use /sys/fs/pstore/console-ramoops to diagnose the problem.
If you do get a boot animation or are close to it, you might also want to try using adb logcat (especially if you've turned on adb debugging, and your ROM can do it on boot).
3) /sys/fs/pstore/console-ramoops
You can access it on a normal boot on some roms (or mount it manually if you've got root), or it's usually mounted automatically on TWRP. This is the kernel log from the last boot and is theoretically stored in RAM (I have reasons to doubt that). Basically, it works like dmesg, but for the last boot.
While it is polluted by zealous MTK debugging info, scrolling through it can often show where the problem is. If you can figure it out yourself, great. If not, post it here, and I (or somebody else) might try to figure out what went wrong and put it on a list of known bootloop reasons and fixes below.
4) Recommendations on posting about bootloop problems:
I think it would help a lot specifying which step from above fails. Also, if the charging light turns off, please, please provide /sys/fs/pstore/console-ramoops. You can easily get it with adb pull from TWRP and it helps *a lot* in figuring out what went wrong.
Hope this info will help you guys getting your devices working again faster (and provide more accurate info when asking for help).
P.S.: Another reference on MTK boot, also around 5 years old.
Reserved for List of bootloop problems:
Reserved
i have:
dm-verity error
Android system on your device is corrupted.
Device will boot in 5s
Click to expand...
Click to collapse
can't boot to my mobile in past week
just i can see my device with "fastboot devices" but not found with adb devices
and in device manager "Android ADB Interface" it's not recognize ( yellow question marks).
also have "adb server version (41) doesn't match this client (39); killing"
hello..
So... /sys/fs/pstore/dmesg-ramoops .. is not there .... /pstore do not exist :-\
and /proc/last_kmsg.. neither :-(
i have.. lineage-14.1-20190213-nightly-asanti-signed install it....
He will be generating them elsewhere???
OP, please add the infamous soft brick symptoms in detail, this maybe help someone in the future.
It shows redmi logo, it can enter vol + menu with some messages (I forgot the message), and it can enter vol - (bootloader), and it will ask for authorization when hooked to SPFT. And also link to that telegram post for work around.
And also, this is crucial info I found. Anything prior global 12.0.7 can be dirty flashed to anything prior that (even A10 to A9). 12.0.7 onward, 12.0.7 is the lowest you can get for dirty flash. I don't know for clean flash. Maybe work, maybe not.
fla5 said:
i have:
can't boot to my mobile in past week
just i can see my device with "fastboot devices" but not found with adb devices
and in device manager "Android ADB Interface" it's not recognize ( yellow question marks).
also have "adb server version (41) doesn't match this client (39); killing"
Click to expand...
Click to collapse
What have you done prior brick? Do you do something like flashing global rom in a locked bootloader chinese flavor phone? If yes, do the unbrick with SPFT. If not, and you have unlocked your bootloader and access to fastboot, I think dirty flash will do the trick.
Sorry for being a lil' off-topic but I would love to ask how to prevent a bootloop after flashing back to stock recovery or/and boot. It happened twice - I used magisk+twrp, an update rolled out, I flashed the stock recovery for my official from (extracted from the official package) and ended up with a loop, did the mi authorized acc unbrick and it worked perfectly, now with the 12.5 rolling out I am preety sure i'll end with a loop again when I'll flash the stock boot or/and recovery.
luq90 said:
Sorry for being a lil' off-topic but I would love to ask how to prevent a bootloop after flashing back to stock recovery or/and boot. It happened twice - I used magisk+twrp, an update rolled out, I flashed the stock recovery for my official from (extracted from the official package) and ended up with a loop, did the mi authorized acc unbrick and it worked perfectly, now with the 12.5 rolling out I am preety sure i'll end with a loop again when I'll flash the stock boot or/and recovery.
Click to expand...
Click to collapse
you need to restore stock recovery and boot. and you can't install the update via updater nor twrp. install full rom via fastboot update or via mi flash (dirty flash is ok). but for 12.5 update, do it in twrp
from 12.0.7 onwards, downgrade without erasing data will lead to bootloop (just flash the correct build for remedy)
Thank you for your answer kekesed97.
Sorry, I made a small mistake. By saying that I used twrp means I had it installed not used for the flash. When the update came out, I thought that installing via ADB the stock recovery and boot will let me update the device like a completly unmodded model. Tried this Twice and always ended with a loop. Afterwards the only solution was updating via flashtools (it's bricked anyway so let's update manually hehe).
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Removing "Bloatware"
Probably one the main reasons for obtaining root privileges is to get rid of some default apps which come bundled with the official MIUI.
Given the current situation for this device, using classic methods (such as Titanium Backup / System App Remover / etc.) is not possible and - most probably - attempting in doing so will result in a soft-brick.
Instead, there is a particularly useful Magisk Module that can be used for this scope: Debloater.
You can read more about it here on XDA; the installation procedure will vary just a bit since there is currently no TWRP support for the Helio G85 Redmi Note 9.
Installing Debloater
Launch Magisk Manager and select "Download" from the menu
Use the search function to locate the package "Busybox for Android NDK"
Install the package, and chose to skip the reboot at the end of the procedure.
Use the search function to locate the package "Debloater Terminal Emulator"
Install the package and this time proceed with the reboot
When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
Open the terminal and issue:
Code:
su
(confirm the request for superuser access) and then
Code:
debloat
Now you can use Debloat to remove all the unwanted applications that come bundled with the ROM.
Please refer to the video included in the post mentioned above to learn more about Debloat and how to use it.
One Question
Can i know this work for Redmi Note 9 global non NFC?
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
dfahren said:
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
Click to expand...
Click to collapse
Sorry for the inconvenience, there is still the MEGA link from the first post up and working.
Here it is: https://mega.nz/file/ucFDXIaY#FrUllKuUASoStlSvrcMYABsbYv6ie-WHR4zOqJMdP4E
[email protected] said:
Can i know this work for Redmi Note 9 global non NFC?
Click to expand...
Click to collapse
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
N3OMOD said:
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
Click to expand...
Click to collapse
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
dfahren said:
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
Click to expand...
Click to collapse
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
dfahren said:
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
Click to expand...
Click to collapse
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
dfahren said:
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
Click to expand...
Click to collapse
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
dfahren said:
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
Click to expand...
Click to collapse
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Followed the steps, worked flawlessly on my Redmi Note 9 (Merlin) 3gb ram 64gb storage purchased in Europe, running Global 11.0.5.
Thank you so very much!
I had successfully done this in the past but messed something up with xposed later, I won't xposed it this time and just enjoy my root-ness.
N3OMOD said:
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
...
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
...
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
The original explanation from user "neko-kun" seemed to me an automatic translation hence the rather weird language.
I can testify to the statement that you can reflash the original boot.img file should you enter a bootloop (which I got).
AdAway is also working for me as does AFWall+ (I needed to leave logging of blocked packets as it is -> off)
N3OMOD said:
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
i'm having an infinite bootloop and keep pressing power + vol down didn't help , what should i do ?
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
dfahren said:
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
Click to expand...
Click to collapse
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
What about entering recovery?
noodlelicious said:
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
Click to expand...
Click to collapse
Try to enter stock recovery, if you can, select mi assitant. After that connect trough adb and run "adb reboot bootloader", that should do the trick.
If phone isnt booting none of main enviroments (system, recovery or fastboot/bootloader) battery drainage may restablish normal boot order. Just remember that if in any case it boots to recovery, use adb command to reboot to bootloader.
Tested on RN9 Global non-NFC (M2003J15SS) with MIUI 12 Global
Hi, just to inform. The following was tested in Redmi Note 9 Global non-NFC (M2003J15SS) with MIUI 12 Global.
- Patched boot image from MIUI12 Global (Android 10) works fine if dm-verity and forced encryption are disable at the time of making the boot image with magisk.
- vbmeta file provided by OP also works (I think any file would work if it's flashed with "--disable-verity --disable-verification" option. This option is essential to avoid bootloop after flashing any non-stock (or patched) image to any partition:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
The vbmeta file I used was extracted (and possibly) edited from a previous version of MIUI (MIUI11), and applied over MIUI12 ROM, that's why I think any file could be used.
Hi .. Is there a way to write to system / app. I need to be able to pass an application to system. Thank you.
Does netflix still work in HD after having the BL unlocked and further rooted?
How to patch vbmeta
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
N3OMOD said:
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Click to expand...
Click to collapse
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
can this be used to root the EU model: MZB9410EU ?
farvehar09 said:
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
Click to expand...
Click to collapse
Yes u can, i use the original vbmeta from miui_MERLINIDGlobal_V12.0.1.0.QJOIDXM_709d727d58_10.0.zip (ID variant)
Here's a quick guide for rooting your Fairphone 4.
DISCLAIMER
I'm not the author of this method, merely sharing the informations that can be found on fairphone community forums.
All credit goes to hirnsushi from fairphone community forum.
I will not be held responsible for any damage caused by this operation, flashing your device always implies a risk of manufacturing your very own plastic brick.
PREREQUISITES
- Unlocked bootloader
- Computer with adb & fastboot
- Magisk app installed on your device
- FP4's official stock boot.img
HOW TO ROOT
1. Copy the boot.img file on your device's internal memory
2. Patch the boot.img file using Magisk -> Installation -> Patch a file
3. Transfer the patched boot.img back to your computer
4. Reboot to fastboot: Power + vol up from off device OR adb reboot bootloader
5. Boot from the patched img by running: fastboot boot patched_boot.img where patched_boot.img is actually replaced with the path and name of your patched file
DO NOT FLASH THE PATCHED IMG. BOOT ONLY.
6. Your device will take much much more time to boot than usual, be patient.
7. Once booted, open Magisk, run a direct Install and reboot.
You are now rooted.
This will break your ability to use Google Pay. Though a workaround is described below.
[OPTIONAL]- PASS SAFETYNET AND GPAY CERTIFICATION
1. Download and enable the following Magisk mod:
- Riru module
- Riru’s universal SafetyNet’s fix 2.1.2
- SQLLite for ARM aarch64 devices
- GPay SQLLite Fix 2.5
2. Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
3. Now the part that is very important to follow otherwise it will not work :
- Put your phone in Airplane mode
- Clear all data from:
Google Play
Google Pay
Google Play Service: remember, clear ALL data, not just cache, even for this one
- Reboot
- Toggle Airplane mode off
You should now have a rooted device that can be used to pay for groceries. How cool is that.
If Pay app states device is not certified, there is high chances you did not follow exactly the described steps.
I really like a rooted phone as always. I will wait till there is a way to reinstall the standard ROM. Then it will be safe for me to try.
I'm on the latest update and not able to unlock the bootloader. I enabled OEM unlocking in developer options and rebooted to bootloader. On the first screen it says "Device status: Locked" and doesn't react on any fastboot command. When I enter recovery and start fastboot, each command will fail (command not present in this implementation). Any hints?
Finally managed to unlock the bootloader. The trick was to use an USB2.0 port on my PC.
I live in US so don't have one in my hands yet. Has anyone done a .QCN dump of the phone yet? Do you program the phone with Firehose EDL? Are there qualcomm drivers? I have so many questions.
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Generally speaking I can only but encourage you to register and browse the fairphone forum as there are much much more resources, guides and activity around the fairphone 4 than on xda.
I'm using latest magisk 24.1 and todays OTA fails. I tried with Zygisk on and off. In the magisk app under install there is a install to new slot thing but I feel like that's supposed to be used if it don't fail. will I brick my phone if i click it?
edit:
found this on fp forum
Fixing OTA after rooting
Because my FP is rooted, I couldn’t install the update right away. Message: Couldn't update, installation problem The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on Quora. This is how I was...
forum.fairphone.com
citroniais said:
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Click to expand...
Click to collapse
My Build-Number say I am on:
FP4.FP3R.A.099.20220112
So it seems my Bootloader version should be A.099 but there is no file like this:
https://storage.googleapis.com/fairphone-source/FP4/A.099-boot.img
Is it okay to take a older boot img or another?
Latest seems to be
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
and before that:
https://storage.googleapis.com/fairphone-source/FP4/A.091-boot.img
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
I'm using latest magisk and safetynet-fix-v2.2.1, GPay.SQLite.Fix.v2.5, SQLite for ARM aarch64 devices.
Thomas.swe said:
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
Click to expand...
Click to collapse
okay, so you are on a magisk-boot-v-A.094? I thought Magisk, run a direct Install then is only able to patch your current running patched-A.094 boot.
Am I wrong?
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Thomas.swe said:
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Click to expand...
Click to collapse
Yes that it true, you are have root now.
But I think you are on the bootloader version A.094.
the 099 came from OTA so why whould bootloader be 094?
Thomas.swe said:
the 099 came from OTA so why whould bootloader be 094?
Click to expand...
Click to collapse
I am just thinking that you are on 094. Perhaps I am wrong.
But in step 5 you boot the patched 094 img and with this 094 boot image you run the direct magisk install on step 7. If I a not wrong magisk used the current running boot-image. So magisk patched your 094.
Perhaps I am wrong, I am not sure.
EDIT:
You are right @Thomas.swe Sorry for confusing.
See here: https://forum.fairphone.com/t/fp4-root-access-is-possible-maybe-a-bit-risky/76839/144
EDIT2:
@Eznaa does "our device will take much much more time to boot than usual, be patient." mean more than 20 minutes?
EDIT3:
No I used the wrong bootloader. Iode OS has its own bootloader-image upsi
I had root working using this method on A.116-boot.img. I then uninstalled Magisk, did an OTA (to A.128), did "Install Magisk to inactive Slot" (as I successfully did in older OTA updates), but it bootloops. If I `fastboot flash boot A.128-boot.img` it boots normally, but as expected, without root.
I tried an `adb wait-for-device shell magisk --remove-modules` to make sure no Magisk modules are causing the bootloop. I am on Magisk 25.1, btw.
Do you have any idea what could cause the Magisk-patched image to bootloop?
Hi,
Did you try to patch A.128 and boot on it ?
fastboot boot [image]
Please note : the best way to find an answer about any issue related to Fairphone is in the "Fairphone Community Forum" : forum.fairphone.com - The Fairphone users are not using that much XDA
I am thinking of buying Fairphone 4 and need magisk. Can anyone answer a question about the installation instructions above? Magisk website says to flash the magisk patched boot image but here the instruction is to first boot from the magisk patched image, not flash it, and then once booted run a direct install from the magisk app. What is the reason for this extra step?
Just a heads up. Root/Unlock voids FairPhone warranty unfortunately. Only reason I haven't bought this phone.