Basically, you can use mtkclient to unlock your bootloader, instead of going through all of the hassle involved with the mi_unlock tool! I have tested this on my global redmi 9c, running the latest MIUI. I tested this on Linux, but the same should apply running it from Windows.
You can follow the directions here:
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
www.droidwin.com
Also you can make it even easier on yourself and use the current git version of mtkclient, (mtkclient current git clone) which includes mtk_gui. Download the git repo, make sure you have python installed, from inside the directory of the git repo you downloaded run:
Linux
$ pip install -r requirements.txt
or something like this in windows:
C:\gtkclient> python -m pip install -r requirements.txt
That will install all needed requirements to run the app, then you can run mtk_gui by running:
Linux:
$ ./mtk_gui
Windows:
C:\mtkclient> python mtk_gui
From there you will need to WITH PHONE OFF, hold down volume up, then plug in your phone. If all goes well, your phone should be detected and you can click the "Flash Tools" tab, and click "Unlock Bootloader"
PS: I have tested this on linux with a patched kernel, you can do this easily by downloading fireiso, a bootable linux environment with the kernel already patched. Download fireiso, make a bootable USB from it, then boot it up, download mtkclient really quickly, extract it, open a terminal and cd into the directory you extracted it to, run pip install -r requirements.txt, then run ./mtk_gui
PSS: Apparently there is a LiveDVD linked to on mtkclient's github page as well, but its 3.9 GB as opposed to fireiso's <1GB
mtkclient: https://github.com/bkerler/mtkclient
fireiso: https://github.com/amonet-kamakiri/fireiso
I'll be happy to help anyone who has questions, and I would like to hear back from anyone who successfully tests this using Windows, just for posterity.
Thanks folks, and I hope this helps some of you avoid that nasty unlook tool like I did! LOL
Or we can unlock it easier using MTKClient GUI 2.0
That's exactly what I mentioned in the thread if you read the whole thing
hello can i use mtkclient even if im blocked for 7 days in mi flash
aye69 said:
hello can i use mtkclient even if im blocked for 7 days in mi flash
Click to expand...
Click to collapse
no i tried with a mtk device, you will just get dm-verity corruption error but your device still locked
karl615 said:
Basically, you can use mtkclient to unlock your bootloader, instead of going through all of the hassle involved with the mi_unlock tool! I have tested this on my global redmi 9c, running the latest MIUI. I tested this on Linux, but the same should apply running it from Windows.
You can follow the directions here:
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
www.droidwin.com
Also you can make it even easier on yourself and use the current git version of mtkclient, (mtkclient current git clone) which includes mtk_gui. Download the git repo, make sure you have python installed, from inside the directory of the git repo you downloaded run:
Linux
$ pip install -r requirements.txt
or something like this in windows:
C:\gtkclient> python -m pip install -r requirements.txt
That will install all needed requirements to run the app, then you can run mtk_gui by running:
Linux:
$ ./mtk_gui
Windows:
C:\mtkclient> python mtk_gui
From there you will need to WITH PHONE OFF, hold down volume up, then plug in your phone. If all goes well, your phone should be detected and you can click the "Flash Tools" tab, and click "Unlock Bootloader"
PS: I have tested this on linux with a patched kernel, you can do this easily by downloading fireiso, a bootable linux environment with the kernel already patched. Download fireiso, make a bootable USB from it, then boot it up, download mtkclient really quickly, extract it, open a terminal and cd into the directory you extracted it to, run pip install -r requirements.txt, then run ./mtk_gui
PSS: Apparently there is a LiveDVD linked to on mtkclient's github page as well, but its 3.9 GB as opposed to fireiso's <1GB
mtkclient: https://github.com/bkerler/mtkclient
fireiso: https://github.com/amonet-kamakiri/fireiso
Click to expand...
Click to collapse
it doesn't work for xiaomi devices
Yes, actually it does, I've unlocked the bootloader on every single MTK device I've owned, including my Xaiomi Redmi 9c
karl615 said:
Basically, you can use mtkclient to unlock your bootloader, instead of going through all of the hassle involved with the mi_unlock tool! I have tested this on my global redmi 9c, running the latest MIUI. I tested this on Linux, but the same should apply running it from Windows.
You can follow the directions here:
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
www.droidwin.com
Also you can make it even easier on yourself and use the current git version of mtkclient, (mtkclient current git clone) which includes mtk_gui. Download the git repo, make sure you have python installed, from inside the directory of the git repo you downloaded run:
Linux
$ pip install -r requirements.txt
or something like this in windows:
C:\gtkclient> python -m pip install -r requirements.txt
That will install all needed requirements to run the app, then you can run mtk_gui by running:
Linux:
$ ./mtk_gui
Windows:
C:\mtkclient> python mtk_gui
From there you will need to WITH PHONE OFF, hold down volume up, then plug in your phone. If all goes well, your phone should be detected and you can click the "Flash Tools" tab, and click "Unlock Bootloader"
PS: I have tested this on linux with a patched kernel, you can do this easily by downloading fireiso, a bootable linux environment with the kernel already patched. Download fireiso, make a bootable USB from it, then boot it up, download mtkclient really quickly, extract it, open a terminal and cd into the directory you extracted it to, run pip install -r requirements.txt, then run ./mtk_gui
PSS: Apparently there is a LiveDVD linked to on mtkclient's github page as well, but its 3.9 GB as opposed to fireiso's <1GB
mtkclient: https://github.com/bkerler/mtkclient
fireiso: https://github.com/amonet-kamakiri/fireiso
Click to expand...
Click to collapse
How do I find out the proper usage for mtkclient? mtk script....does this allow me to use a .sh script with this parameter?
mdwooten212 said:
How do I find out the proper usage for mtkclient? mtk script....does this allow me to use a .sh script with this parameter?
Click to expand...
Click to collapse
So I have a Xiaomi 11T MTK Dimmensity 1200 and tried this method, all I get now is "dm-verity corruption error" the device is still locked. Can someone help me please?
danieleal said:
So I have a Xiaomi 11T MTK Dimmensity 1200 and tried this method, all I get now is "dm-verity corruption error" the device is still locked. Can someone help me please?
Click to expand...
Click to collapse
Try:
python3 mtk e userdata
mdwooten212 said:
Try:
python3 mtk e userdata
Click to expand...
Click to collapse
It doesn't work in newer firmware, only on 13.0.2 or earlier
danieleal said:
It doesn't work in newer firmware, only on 13.0.2 or earlier
Click to expand...
Click to collapse
There is a dm-verity corruption error. How do I solve it on my 11t device or will unlock tools work?
danieleal said:
So I have a Xiaomi 11T MTK Dimmensity 1200 and tried this method, all I get now is "dm-verity corruption error" the device is still locked. Can someone help me please?
Click to expand...
Click to collapse
did you solve the problem
safaonal said:
did you solve the problem
Click to expand...
Click to collapse
what's ur MIUI version?
safaonal said:
did you solve the problem
Click to expand...
Click to collapse
I think Xiaomi patched the bootloader (but not the brom) in some devices
Related
This is a touch recovery, recovery source is from carliv. This is his recovery I compiled it for intel x86, more specifically for Dell Venue 8 (3830), This is a cwm 6.0.5.1 recovery.
Below link is to carliv's thread, this link explains about the recovery, so rather than just copy and paste I linked to his thread. [emoji14][emoji14]
http://forum.xda-developers.com/android/development/port-carliv-touch-recovery-v3-0-porting-t2970150
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is flashable via fastboot,
Download recovery
http://www.mediafire.com/download/o928o4l92f45wh2/carliv_touch_recovery.img
to install
boot into fastboot
fastboot flash recovery carliv_touch_recovery.img
Credits
carliv
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
moonbutt74
does adb work?
i get DellVenue8. . . unauthorized
joanthanmajh said:
does adb work?
i get DellVenue8. . . unauthorized
Click to expand...
Click to collapse
Yes, adb works, adb works in all my recoveries.
Code:
[email protected]:~/Desktop$ adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~/Desktop$ adb shell
# exit
[email protected]:~/Desktop$ adb devices
List of devices attached
DellVenue8000242287 recovery
[email protected]:~/Desktop$
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
Yes, adb works, adb works in all my recoveries.
Code:
[email protected]:~/Desktop$ adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~/Desktop$ adb shell
# exit
[email protected]:~/Desktop$ adb devices
List of devices attached
DellVenue8000242287 recovery
[email protected]:~/Desktop$
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
adb works just fine for me also, adb has worked on all your recoveries including the tethered version.
I think @joanthanmajh uses windows and doesn't have his drivers installed for recovery. When I used windows I had to install drivers while in recovery mode to get adb to work in recovery.
vampirefo said:
This is a touch recovery, recovery source is from carliv. This is his recovery I compiled it for intel x86, more specifically for Dell Venue 8 (3830), This is a cwm 6.0.5.1 recovery.
Below link is to carliv's thread, this link explains about the recovery, so rather than just copy and paste I linked to his thread. [emoji14][emoji14]
http://forum.xda-developers.com/android/development/port-carliv-touch-recovery-v3-0-porting-t2970150
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is flashable via fastboot,
Download recovery
http://www.mediafire.com/download/o928o4l92f45wh2/carliv_touch_recovery.img
to install
boot into fastboot
fastboot flash recovery carliv_touch_recovery.img
Credits
carliv
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
moonbutt74
Click to expand...
Click to collapse
Hey Vamp, thanks for this recovery, I just pulled this from your github to compare with mine, compiles and works correctly.
What font do you use? Mine seems too big. Also do you know of any other unlocked Intel tablets?
Dell V8 3830
tomtom1265 said:
Hey Vamp, thanks for this recovery, I just pulled this from your github to compare with mine, compiles and works correctly.
What font do you use? Mine seems too big. Also do you know of any other unlocked Intel tablets?
Dell V8 3830
Click to expand...
Click to collapse
I will have to look when I get home, next one above default, I can't remember what default is, I want to say I used 10 x 30, see if default is 10 x 24, if it is then I used 10 x 30.
I only have two Intel tablets, dell version same as your, unlocked, other is iview and it is locked, I don't know of any other device first hand that is unlocked.
sent from my kingSing T1 via taptalk
@vampirefo
Have you considered compiling a ROM?
tomtom1265 said:
@vampirefo
Have you considered compiling a ROM?
Click to expand...
Click to collapse
I think @social-design-concepts posted he was working on one, as for me a week ago, I would have said no, complete waste of my time. But if Alexander Weggerle (Intel) keeps his word, then yes I will do what I can to build, compile, port a rom.
vampirefo said:
I think @social-design-concepts posted he was working on one, as for me a week ago, I would have said no, complete waste of my time. But if Alexander Weggerle (Intel) keeps his word, then yes I will do what I can to build, compile, port a rom.
Click to expand...
Click to collapse
found it : well we find out over the weekend just finished putting my build box back together .
tomtom1265 said:
@vampirefo
Have you considered compiling a ROM?
Click to expand...
Click to collapse
Well still no word from Alex, I did go ahead and download aosp. It's way behind cm, wouldn't compile on my crunch machine, so I booted into old mint, it's a year since I used it, downgraded java on it now all ok as far as compiling, I am compiling now, on this old os will take a while.
I still wait for Alex to post his info, I can then add his changes to my build.
Sent from my Venue 8 3830 using Tapatalk
Well it appears to have completed. I got things to do now, but will test later, I guess many things wont work, might not even boot, lol.
It's a start and with Alex's info if he does follow through, the rom should work correctly.
I have
boot.img
recovery.img
system.img
aosp_yellowtail-ota-eng.vampirefo.zip
Code:
building image from target_files RECOVERY...
running: mkbootfs -f /tmp/targetfiles-5v9f0y/META/recovery_filesystem_config.txt /tmp/targetfiles-5v9f0y/RECOVERY/RAMDISK
running: minigzip
running: mkbootimg --kernel /tmp/targetfiles-5v9f0y/RECOVERY/kernel --ramdisk /tmp/tmpmeS15E --output /tmp/tmpNDbXm_
building image from target_files BOOT...
running: mkbootfs -f /tmp/targetfiles-5v9f0y/META/boot_filesystem_config.txt /tmp/targetfiles-5v9f0y/BOOT/RAMDISK
running: minigzip
running: mkbootimg --kernel /tmp/targetfiles-5v9f0y/BOOT/kernel --ramdisk /tmp/tmp6mknmP --output /tmp/tmppIGHf7
running: imgdiff -b /tmp/targetfiles-5v9f0y/SYSTEM/etc/recovery-resource.dat /tmp/tmp0Peb9v /tmp/tmp7V6HcO /tmp/tmpHmBpBw
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpGjf1v8 out/target/product/yellowtail/aosp_yellowtail-ota-eng.vampirefo.zip
done.
Just doing some quick research, if the Dell venue 8 3830 is intel atom z2580 and the 3730 is z2560, it looks as though that is the only difference (exempt obvious screen size difference).
That being said, shouldn't the same method be used to unlock Dell venue 7 as well ?
yohan4ws said:
Just doing some quick research, if the Dell venue 8 3830 is intel atom z2580 and the 3730 is z2560, it looks as though that is the only difference (exempt obvious screen size difference).
That being said, shouldn't the same method be used to unlock Dell venue 7 as well ?
Click to expand...
Click to collapse
I don't have a Dell venue 7, if I did I would have already tried it, you may try if you like, of course if it fails you are on your own.
I'm very tempted, what should I investigate prior to doing this ? ... I don't expect a step by step tutorial but if you can give me the jist I'll do some research.
If I can always get back into the bootlauncher I can recover stock roms again using the toolkit, if there's a chance it'll brick I want to do some serious digging and cross referencing. Am I on the right track in thinking I need to extract some things and compare how the partitions are mapped between the 2 devices?
Appreciate your guidance!
yohan4ws said:
I'm very tempted, what should I investigate prior to doing this ? ... I don't expect a step by step tutorial but if you can give me the jist I'll do some research.
If I can always get back into the bootlauncher I can recover stock roms again using the toolkit, if there's a chance it'll brick I want to do some serious digging and cross referencing. Am I on the right track in thinking I need to extract some things and compare how the partitions are mapped between the 2 devices?
Appreciate your guidance!
Click to expand...
Click to collapse
It works but you'll have no display until the device goes to sleep and you wake it up they're are a number of other stability issues as well. Over mounting mmc emmc sleep of death.
The chips being different is a big deal in and of its self now through in gpio and touch controllers screen controllers.
Then through in the fact that there are different versions of the 2560 and 2580 chips depending on features of the soc and pin out.
Way more diff under the hood than just the screen and chip.
But yes the basic process for unlocking is the same if we only had the needed ifwi file.
If you didn't know I have the 3730 so I've already explored this over and over again.
If you use this option be sure your familiar with the xfstk downloader and the unbricking process I have the files in the myKIT_BATCH thread
@vampirefo sorry my post was non related to the touch recovery care if I test it in the tethered environment
vampirefo said:
You need to already be rooted and have flashed unlocked_firmware provided by SDC
Click to expand...
Click to collapse
I cannot find the unlocked_firmware anywhere? Could you please explain what this means? Also, I couldn't get to it with the link that was provided. XDA 404'd me
ElmoRapz said:
I cannot find the unlocked_firmware anywhere? Could you please explain what this means? Also, I couldn't get to it with the link that was provided. XDA 404'd me
Click to expand...
Click to collapse
It's in the very first post.
Sent from my Venue 8 3830 using Tapatalk
I looked at it and I think the link was down. And I'm not finding it anywhere else
Sent from my A0001 using XDA Free mobile app
ElmoRapz said:
I looked at it and I think the link was down. And I'm not finding it anywhere else
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
vampirefo said:
This is a touch recovery, recovery source is from carliv. This is his recovery I compiled it for intel x86, more specifically for Dell Venue 8 (3830), This is a cwm 6.0.5.1 recovery.
Below link is to carliv's thread, this link explains about the recovery, so rather than just copy and paste I linked to his thread. [emoji14][emoji14]
http://forum.xda-developers.com/android/development/port-carliv-touch-recovery-v3-0-porting-t2970150
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is flashable via fastboot,
Download recovery
http://www.mediafire.com/download/o928o4l92f45wh2/carliv_touch_recovery.img
to install
boot into fastboot
fastboot flash recovery carliv_touch_recovery.img
Credits
carliv
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
moonbutt74
Click to expand...
Click to collapse
recovery is off
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent ?
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Rooted using same method but SP Flash Tools worked in my tablet.
Waiting for a TWRP ....
Yes, can confirm that method works for root.
Also tried the T10 TWRP and it's not working on the T8, just a black screen.
Don't need TWRP yet, some bugs in the ROM are more annoying than that
hi all
somebody tried the new rom v1.10 on needrom ??
marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
HI quick question what rom have u installed in ur T8, mine came with 1.01, i see in needrom have 3 versions: 1.06. 1.08, 1.10, have u updated to any of these?
Thanks
Polo19 said:
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Click to expand...
Click to collapse
Flashing ROM with SP flashtool - Teclast Master T8 (E8C1)
Fossxp13 said:
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
Click to expand...
Click to collapse
Hi! I haven't used in built update app so I'll try to explain how to update using flashtool. Follow the steps with your device disconnected from the pc and take into account your files will be erased.
First of all, I recommend you to install ADB and fastboot drivers: 15 seconds ADB Installer
As OP said download the rom from NeedRom and unzip it: You will have three folders:
升级工具, which contains flashtool
固件程序, with the rom
驱动程序, with the drivers
Rename all of them as flashtool, rom and drivers, for example. If you don't, you may have troubles launching flashtool or loading the scatter file.
Launch flashtool as administrator (升级程序, you could rename it too), if you get the message "The scatter file cannot found, please make sure the file exist before download" ignore it. In flashtool make sure MTK_AllInOne_DA.bin is selected as Download-Agent and select the scatter file inside rom folder as Scatter-loading file. Choose firmware upgrade from the list and click the Download button (the one with the green arrow).
Finally, switch off your device and connect it to your pc. Flashtool should do the rest, wait untill "Download Ok" message is displayed. Close flashtool, disconnect your device and switch it on.
IF your computer doesn't load needed drivers automatically, flashtool won't start the process as expected. You will need to open device manager on windows, right click on your device - update driver - choose manually - browse "inf" folder inside drivers folder (choose x86 or x64 according to your OS).
Hope it works! Good luck.
Prevent Brick and Xposed for Teclast Master T8 (E8C1)
Polo19 said:
OP
Click to expand...
Click to collapse
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Just need TWRP and I'm happy.
There's a chinese TWRP but it's not working decently.
Rotiaiso said:
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Click to expand...
Click to collapse
Yes, i also install Xposed using MagiskManager and it works. Now i am able to use all fonctions of Greenify, Amplify, Powernap and get a pretty decent standby batterylife.
marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi, I tried to follow the procedure but in ROM 1.10 doesn't work
---------- Post added at 01:37 PM ---------- Previous post was at 12:44 PM ----------
With the news roms doesn't work...
What is the rom that was working this WA??
Thanks!
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install MagiskManager-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting MagiskManager update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Kerrnel said:
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install *************-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting ************* update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Click to expand...
Click to collapse
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
i have the ota 1.10 update and the rooting was successful. magisk and xposed working flawlessly.
another point:
i have closed the bootloader after flashing the patched boot.img with "fastboot oem lock".
the device boot up is faster and the warning "...5 seconds" is gone.
now, i wait for twrp.
You dont need to unlock bootloader.
Just flash patched_boot with flash tool.
Zaphodb69 said:
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
Click to expand...
Click to collapse
I had multiple devices attached to the PC.
No -s ABC... needed if you only have the one.
Sent from my T8(E8C1) using Tapatalk
The suggested worked for me. I will also mention that you must be connected to the internet to patch the boot.img file with magisk manager (otherwise, the option will not be presented in the magisk manager GUI).
Were there made any changes for the fingerprint? Soimebody mentioned, it isn´t that good. Maybe the last updates change something...
WARNING:
You should only proceed if you are familiar with unlocking and rooting android cellphones in general or... if you dare. Instructions assume you have a working computer with adb installed.
1. Getting the cellphone ready
Enable Developer mode
Enable USB Debugging
Enable OEM Unlock
2. Download magisk apk
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
3 Install the apk using adb
adb install MagiskManager-v8.0.5.apk
4. Download original firmware (check precise version at About phone > Compilation number)
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
.... YOU MUST BE ABSOLUTELY SURE THIS IS THE SAME VERSION !!!!!
5. Unzip and copy boot.img to /sdcard/Download
adb push boot.img /sdcard/Download
6. Patch the boot.img
Open magisk on the cellphone and click Install (upper right corner)
"Select and patch file"
7. Copy the patched file to your computer
adb pull /sdcard/Download/magisk_patched_XXXXX.img
(replace XXXXX with appropriate characters)
8. Unlock the bootloader
Standard process for all motorola phones. Go to the bootloader:
adb reboot bootloader
Get the unlock data
fastboot oem get_unlock_data
With this information complete the process at:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
When you have the KEY, unlock with:
fastboot oem unlock <KEY>
9. Flash the unlocked boot.img
fastboot flash boot magisk_patched_XXXXX.img
10. Reboot and you're done
fastboot reboot
Don't forget to disable and uninstall lots of the built-in rubbish
Happy hacking!
Does it work with Moto One fusion + ?
I know i'm a little bit late, but... Is there a way to disable the bootloader unlocked screen?
Skycr0nos said:
I know i'm a little bit late, but... Is there a way to disable the bootloader unlocked screen?
Click to expand...
Click to collapse
You mean disable the message saying "your bootloader is unlocked, don't store data on the phone" ?
I'm not sure, but i don't think it's easy...
Can I root my device motorola one power fusions plus.?
Root work on this device .?
If root is work why YouTube not making videos about this device.?
I want to root my device. Than I need custom recovery.IMG file and magisk stable version.
Can you help me guys
Thanks, it worked for me, XT2073-2 128GB
BruceWawe said:
Does it work with Moto One fusion + ?
Click to expand...
Click to collapse
It does but make sure to download different stock firmware (its called liber go back a few folders in the link OP gave)
This guide will show you how to root your Nokia 4.2. This has been tested on TA-1157 and is working fine.
**Important** - If fastboot does not recognise your device In step 5, You need to download a driver. Here is the link: Download Driver (by Beebom)
Search up how to install custom driver and install it to the “Android” device.
Requirements:
Nokia 4.2 with unlocked bootloader
USB Cable
ADB/Fastboot.
Python
Your current ROM file
Internet.
Downloads:
ADB Installer (by Snoop05 on xda) : Download
Python : Download
Payload Dumper (vm03 on github): Download ( Click on code and select "download ZIP")
Magisk APK (on your phone) : Download APK ( Scroll down and you will find the APK file)
Code:
** I have only tested this on TA-1157. Other models may not work, but technically they should work.**
** Your warranty is now Void**
Step 1
Enable USB debugging on your phone. If you do not know how to do this, Search it up. It is easy.
Once that's enabled, Connect your phone to your PC/Laptop and open the command prompt (cmd) and type adb devices. It should show your device in the list.
Step 2
Locate the Python folder. To do this, simply type "python" in the start menu and click open file location. Then, Right click on "python.exe" and open properties. Then click open file location.
Once the folder opens, make sure to not close it.
Download the payload dumper.py which I have linked in the downloads section. Extract it and place the contents of the file in the Python folder.
Step 3
Download the ROM file. If you are using lineage OS on your Nokia 4.2, Download that file. If you are using the Stock rom, Download that. It should be a .zip file.
Extract the stuff from that file and take payload.bin and move it to the python folder.
Now, Open cmd in that directory by right clicking and opening cmd. Then, Type the following commands,
Code:
python -m pip install -r requirements.txt
then type,
Code:
python payload_dumper.py payload.bin
Once it is done extracting, Open the "output" folder. There you will find the "boot.img" file
Step 4
Use your USB cable or Google drive to transfer the "boot.img" to your phone. Once you have done that, Download the Magisk APK on your phone and install the app. (APK link in downloads section)
Once you have installed Magisk, open it and click "Install". Select the file from your phone and wait a few minutes for magisk to patch the "boot.img" file.
Once Magisk is finished patching, there will be a new file which magisk has created. Transfer the patched file to your computer via the USB cable or Google drive and make sure to rename it as "magisk_patched.img"
Step 5
You are almost done! Open CMD in the folder where you saved the "magisk_patched.img" and type
Code:
adb reboot bootloader
then type
Code:
fastboot flash boot magisk_patched.img
Once done, Reboot your phone and Voila! Your phone is now rooted. Make sure to open the magisk app and check it.
If you need any help or you get any errors, post it down here below.
Also, If this helped you, consider liking the post!
I will try this in my Nokia 4.2 (TA-1149) I have unlocked bootloader and I have LineageOS 20
RZavala_2003 said:
I will try this in my Nokia 4.2 (TA-1149) I have unlocked bootloader and I have LineageOS 20
Click to expand...
Click to collapse
Cool!
If you have any problems, let me know.
Geoperson8 said:
Cool!
If you have any problems, let me know.
Click to expand...
Click to collapse
I'm typing this reply, in my 4.2 with LOS 20 and root with Magisk 25, this guide was too easy to understand, thanks a lot!
RZavala_2003 said:
I will try this in my Nokia 4.2 (TA-1149) I have unlocked bootloader and I have LineageOS 20
Click to expand...
Click to collapse
Bro i would be very thankful if you told me how you installed lineage os 20 i have the stock ROM rooted
Love from India
thecubernoober said:
Bro i would be very thankful if you told me how you installed lineage os 20 i have the stock ROM rooted
Love from India
Click to expand...
Click to collapse
I could help you with that
Geoperson8 said:
I could help you with that
Click to expand...
Click to collapse
Yes please i would be very thankful
Geoperson8 said:
I could help you with that
Click to expand...
Click to collapse
Please tell me how to install lineage os 20 in Nokia 4.2
King root not work connection problem
___za_x4_pan___ said:
King root not work connection problem
Click to expand...
Click to collapse
Personally, I do not recommend Kingroot as it is not very reliable and safe. Instead, you can follow this guide or follow other guides on youtube.
hello @Geoperson8 I have currently installed lineage os 20 on my nokia 4.2
But i am facing an issue with rooting my phone when I flash the patched boot.img it asks me for factory reset after factory reset one important part of flashing lineage os is flashing the vendor image but when I flash teh vendor image after flashing magisk my wifi does not work and that's what happens when you don't flash the vendor image but my wifi does not work even after flashing teh vendor image so please help me with rooting my nokia 4.2
RZavala_2003 said:
I'm typing this reply, in my 4.2 with LOS 20 and root with Magisk 25, this guide was too easy to understand, thanks a lot!
Click to expand...
Click to collapse
did you have to format you os
thecubernoober said:
did you have to format you os
Click to expand...
Click to collapse
No bro, i only read this guide and i rooted successfully!
thecubernoober said:
hello @Geoperson8 I have currently installed lineage os 20 on my nokia 4.2
But i am facing an issue with rooting my phone when I flash the patched boot.img it asks me for factory reset after factory reset one important part of flashing lineage os is flashing the vendor image but when I flash teh vendor image after flashing magisk my wifi does not work and that's what happens when you don't flash the vendor image but my wifi does not work even after flashing teh vendor image so please help me with rooting my nokia 4.2
Click to expand...
Click to collapse
I would recommed to flash the vendor image before doing any modifications on your phone. Hope this helps.
RZavala_2003 said:
I will try this in my Nokia 4.2 (TA-1149) I have unlocked bootloader and I have LineageOS 20
Click to expand...
Click to collapse
Can you tell me where did you find the vendor for that model? I have the same
imthetoadXD said:
Can you tell me where did you find the vendor for that model? I have the same
Click to expand...
Click to collapse
I can reply to that
So I found the firmware from the lineage os page section where it says switch back to stock and there is the firmware given for Android 11
Nokia 4.2 ROMs, Kernels, Recoveries, & Other Devel
Improve your Nokia 4.2's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
Refer this page for the link of stock firmware
Just so you guys know, If you need any help. Feel free to ask me.
thecubernoober said:
I can reply to that
So I found the firmware from the lineage os page section where it says switch back to stock and there is the firmware given for Android 11
Nokia 4.2 ROMs, Kernels, Recoveries, & Other Devel
Improve your Nokia 4.2's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
Refer this page for the link of stock firmware
Click to expand...
Click to collapse
Is your lineage OS and root working fine?