Related
I received an update in Magisk just a while. Anx opening up i have found that my magisk is not not installed and so the root is gone.
I clicked on install button, it says Install with zip and another option is install with patched boot.
I clicked on install with zip, it downloaded a zip in download folder, but as we dont have recovery now i dont know what to do with that zip. or should i go for patched boot img. and if yes? then how? thanks!
I had it too and root was detected after I rebooted my phone.
did u update? and how?
+1
I lose my root, magisk don't update, and rebooting don't solved.
I'm getting tired of A2.
pack21 said:
+1
I lose my root, magisk don't update, and rebooting don't solved.
I'm getting tired of A2.
Click to expand...
Click to collapse
What are all of you doing? Just install the modified boot image and be done. Never had any issues here.
Benjamin_L said:
What are all of you doing? Just install the modified boot image and be done. Never had any issues here.
Click to expand...
Click to collapse
need a link of that modified boot image. !
Syed Shahriar said:
need a link of that modified boot image. !
Click to expand...
Click to collapse
It's in the dump thread of the August image
Benjamin_L said:
It's in the dump thread of the August image
Click to expand...
Click to collapse
i m a bit of noob here. i gathered that patched_boot.img from august dump. now what to do in order to get the latest magisk working?
Syed Shahriar said:
i m a bit of noob here. i gathered that patched_boot.img from august dump. now what to do in order to get the latest magisk working?
Click to expand...
Click to collapse
Just use as is, flash with fastboot, or patch the unpatched one with magisk manager and flash that. More wasn't needed on my side.
Benjamin_L said:
Just use as is, flash with fastboot, or patch the unpatched one with magisk manager and flash that. More wasn't needed on my side.
Click to expand...
Click to collapse
I flashed patched_boot.img, now it shows magisk installed . but root is not there still. i have one option INSTALL, clicking it says 1)via zip 2) patched boot
Syed Shahriar said:
my apology, here's what i should do:
1) fastboot flash patched_boot.img
2) reboot set and install latest magisk apk
3) hit install from that app
is it so?
Click to expand...
Click to collapse
No the patched boot image already is like installing magisk. Or to put it differently that's what happens when you install it the normal way so all you need is to flash the boot image and have magisk manager installed
Benjamin_L said:
No the patched boot image already is like installing magisk. Or to put it differently that's what happens when you install it the normal way so all you need is to flash the boot image and have magisk manager installed
Click to expand...
Click to collapse
ok now as its stands, just flash the boot image and then open up magisk. ( i have already magisk installed , but as unrooted, and it asks to update)
Can someone upload the stock boot img from the August security patch so I can patch it with the updated magisk v17 because I have the same problem?
I i already have the august patched boot image, can i just update magisk from the app?
conan_88 said:
Can someone upload the stock boot img from the August security patch so I can patch it with the updated magisk v17 because I have the same problem?
Click to expand...
Click to collapse
Find it in the dump thread
Benjamin_L said:
Find it in the dump thread
Click to expand...
Click to collapse
I couldn't find a boot.img in the dump files. only bootanimations.zip but I don't think that's it.
Can you please tell me the directory or the file name so I can search for it?
Thanks.
conan_88 said:
I couldn't find a boot.img in the dump files. only bootanimations.zip but I don't think that's it.
Can you please tell me the directory or the file name so I can search for it?
Thanks.
Click to expand...
Click to collapse
Dump thread I said: https://forum.xda-developers.com/showpost.php?p=77275242&postcount=25
Benjamin_L said:
Dump thread I said: https://forum.xda-developers.com/showpost.php?p=77275242&postcount=25
Click to expand...
Click to collapse
Found it. Thank you very much. It is working now.
I unlocked bootloader on Pie, .202 fw.
My camera preview is broken but I can take pictures.
Unable to find any fix for this. Isn't camera suposed to work when unlocking on pie?
Mustach said:
I unlocked bootloader on Pie, .202 fw.
My camera preview is broken but I can take pictures.
Unable to find any fix for this. Isn't camera suposed to work when unlocking on pie?
Click to expand...
Click to collapse
Are you sure you unlocked the bootloader on PIE .202?
BTW.
You could try the twrp camerafix together with the vbmeta parameters.
MartinX3 said:
Are you sure you unlocked the bootloader on PIE .202?
BTW.
You could try the twrp camerafix together with the vbmeta parameters.
Click to expand...
Click to collapse
100% I did. I tried camera fixes for twrp, also I tried magisk modules that are supposed to fix it. Nothing happened.
As it goes for the vbmeta parameters. I did change the parameters when flashing twrp. Maybe I did something wrong. I have no idea. 1st time rooting a Sony. Had one plus and huawei before.
Just to make sure. Can ypu point me to the right camera fix twrp zip and tell me wxactly what to do with vbmeta in case I did it wrong.
Thanks in advance man. Love your work.
Mustach said:
100% I did. I tried camera fixes for twrp, also I tried magisk modules that are supposed to fix it. Nothing happened.
As it goes for the vbmeta parameters. I did change the parameters when flashing twrp. Maybe I did something wrong. I have no idea. 1st time rooting a Sony. Had one plus and huawei before.
Just to make sure. Can ypu point me to the right camera fix twrp zip and tell me wxactly what to do with vbmeta in case I did it wrong.
Thanks in advance man. Love your work.
Click to expand...
Click to collapse
Thank you
Oh, just follow the TWRP instructions and everything is fine
And the camerafix is bundled in the twrp tar.gz file
Eerrm. Did you test the camera without the camerafix too?
Because since you unlocked it After .126 you should not need it and it should break your camera preview until you flash the vendor.sin via newflasher again.
MartinX3 said:
Thank you
Oh, just follow the TWRP instructions and everything is fine
And the camerafix is bundled in the twrp tar.gz file
Eerrm. Did you test the camera without the camerafix too?
Because since you unlocked it After .126 you should not need it and it should break your camera preview until you flash the vendor.sin via newflasher again.
Click to expand...
Click to collapse
Ok so now I flashed vendor with newflasher and rebooted, black camera preview. Then i went to change vbmeta parameters and flash camerafix, rebooted, Black preview. I don't even know what to do anymore.
Mustach said:
Ok so now I flashed vendor with newflasher and rebooted, black camera preview. Then i went to change vbmeta parameters and flash camerafix, rebooted, Black preview. I don't even know what to do anymore.
Click to expand...
Click to collapse
That's disgusting [emoji848]
Hmm, another approach would be to downgrade to Oreo and apply xperifix und a selinux permissive patch.
MartinX3 said:
That's disgusting [emoji848]
Hmm, another approach would be to downgrade to Oreo and apply xperifix und a selinux permissive patch.
Click to expand...
Click to collapse
Downgraded to oreo via flasher and I tried to install twrp. I install it. I flash magisk. and system won't boot. UGH.
Mustach said:
Downgraded to oreo via flasher and I tried to install twrp. I install it. I flash magisk. and system won't boot. UGH.
Click to expand...
Click to collapse
Did you wiped userdata?
(TWRP or userdata.sin)
MartinX3 said:
Did you wiped userdata?
(TWRP or userdata.sin)
Click to expand...
Click to collapse
yeah. keeps bootlooping on sony logo.
Mustach said:
yeah. keeps bootlooping on sony logo.
Click to expand...
Click to collapse
Did you use the OREO TWRP, the kernel installer.zip and the twrp installer.zip?
MartinX3 said:
Did you use the OREO TWRP, the kernel installer.zip and the twrp installer.zip?
Click to expand...
Click to collapse
yeah. forgot the kernel. Reinstalled the firmware, flashed twrp, kernel, and twrp.
Bootloops.
Turned it off. Tried to turn it on, now it says "Your device is corrupt. It can't be trusted and wont boot"
EDIT***
Cleared user data now that message is gone, but it still loops.
Mustach said:
yeah. forgot the kernel. Reinstalled the firmware, flashed twrp, kernel, and twrp.
Bootloops.
Turned it off. Tried to turn it on, now it says "Your device is corrupt. It can't be trusted and wont boot"
Click to expand...
Click to collapse
And did you flash magisk too?
MartinX3 said:
And did you flash magisk too?
Click to expand...
Click to collapse
Ofcourse
Mustach said:
Ofcourse
Click to expand...
Click to collapse
So you did exactly the steps in the instructions, full wiped your phone and used the kernel installer as first zip?
MartinX3 said:
So you did exactly the steps in the instructions, full wiped your phone and used the kernel installer as first zip?
Click to expand...
Click to collapse
hahah yes . stupid phone geez...
Mustach said:
hahah yes . stupid phone geez...
Click to expand...
Click to collapse
Hmmmm.
Does Oreo run without TWRP?
(And you didn't forget both vbmeta parameters?)
MartinX3 said:
Hmmmm.
Does Oreo run without TWRP?
(And you didn't forget both vbmeta parameters?)
Click to expand...
Click to collapse
it runs oreo without twrp. I didn't forget any parameters.
So I did th following:
Installed Oreo, booted it once to make sure it works.
flashed twrp.img
flashed vbmeta.img
rebooted to twrp.
flashed kernel, flashed twrp installer
rebooted to twrp.
flashed magisk.
reboot.
Bootloop.
Mustach said:
it runs oreo without twrp. I didn't forget any parameters.
So I did th following:
Installed Oreo, booted it once to make sure it works.
flashed twrp.img
flashed vbmeta.img
rebooted to twrp.
flashed kernel, flashed twrp installer
rebooted to twrp.
flashed magisk.
reboot.
Bootloop.
Click to expand...
Click to collapse
Hmmm, I am feeling lost.
Which device do you use?
MartinX3 said:
Hmmm, I am feeling lost.
Which device do you use?
Click to expand...
Click to collapse
XZ2 H8216
Mustach said:
XZ2 H8216
Click to expand...
Click to collapse
That's very weird, this device is confirmed to work. @Pandemic , do you have any clue?
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.
Hi all, I'd like to share my experiences here about trying to patch boot.img for the Blackview BV6300 Pro which is one of the countless MediaTek Helio P70 (aka MT6771) China phones that can be had for a bit of change at every corner nowadays. It features a fairly non-clutter generic Android 10 ROM.
I bought it because of good feature/price ratio. I also like the fairly idiot-proof MTK Preloader/SP Flash Tool combo and expected no big problems having the phone patched. Apparently that estimate was wrong.
I extracted the boot.img (at exactly 32768k) and started patching it with the latest Magisk Manager (8.0.4). When set to "Stable" the patched result came out less than 12Megs which struck me as very odd, so I did not bother trying to flash that and switched to "beta". Et voila, out came a patched image that appeared to have just the right size.
Unfortunately, after flashing the patched image, the device detected a modified boot signature and flagged "Red State, rebooting in 5s", effectively entering a boot loop. Going back to stock, then unlocking the bootloader with fastboot and reflashing patched boot changed the "Red State" to "Orange State" but the boot loop persisted.
The boot loop message also suggests to either reflash stock or "disable verified boot". Yeah, but... Magisk Manager 8.0.4 seems to have lost the "Advanced Options" menu that had been there in previous versions, allowing users to toggle dmverity while patching boot images... so I wonder how to get around this!? Any suggestions?
Any solution for this, or any suggestions to try??
Have you tried this?
https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Didgeridoohan said:
Have you tried this?
Click to expand...
Click to collapse
Thanks for your suggestion but it seems like this requires TWRP and, as far as I know, no TWRP recovery is available for the BV6300 Pro.
You have to unlock your bootloader FIRST and not after.Start from scratch and it will work,im sure.Cheers!!!
First make the new,i mean flash fresh firmware blablabla.Extract your firmware,copy boot img to phone,install magisk manager and patch the boot img(im sure you can do it without root(on my Redmi 9 it works),copy patched boot imhg to pc and use adb to flash,but be sure your bootloader is unlocked before.Good luck.
We must unlock the bootloader with fastboot mode or we can do it through developer options??
black_knight_ said:
We must unlock the bootloader with fastboot mode or we can do it through developer options??
Click to expand...
Click to collapse
Fastboot
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
Did you flashed vbmeta.img ,thats important.
-CALIBAN666- said:
Did you flashed vbmeta.img ,thats important.
Click to expand...
Click to collapse
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
black_knight_ said:
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
Click to expand...
Click to collapse
Ive flashed vbmeta with adb on my phones,like my Redmi 9,when you dont have vbmeta i think u cant do anything with flashing something,just google for it or look here for it,good luck!!!
hi there im looking for tester to make a full compatible twrp for samsung m10. then i made this Test 1 from scratch.
dont worry if its fail your phone wont be bricked just read carefully i case bootloop
in case bootloop:
first get logs recovery.log and dsmeg then reply i will fix it soon
if you see blue (cyan) screen just plug your phone with pc and flash via odin your stock recovery.
if your phone wont boot and see a msg in read like "could not boot blah blah.." press sound button up + down in same time and plug .. like above
if you see black screen and your phone loop turn on off ... click power + sound up.. for 5 s then your phone shut down and in same time press sound button up + down in same time and plug .. like above
i used twrp 9.0 branch
link:
Release Test 1 twrp · SA-15/android_device_samsung_m10lte
Contribute to SA-15/android_device_samsung_m10lte development by creating an account on GitHub.
github.com
if it works please say it and soon i will build ofox or shrp
not work m105G, succes flash but stay in stock recovery
Kakang_Ragil said:
not work m105G, succes flash but stay in stock recovery
Click to expand...
Click to collapse
it stays on stock hmm do you have magisk ?
SA-15 said:
it stays on stock hmm do you have magisk ?
Click to expand...
Click to collapse
when i pacthed rom with magisk. system not run normaly, (it's softbrick) screen say " only official software ....bla bla bla...",, even though i'm already open oem unlock via developer option.
Kakang_Ragil said:
when i pacthed rom with magisk. system not run normaly, (it's softbrick) screen say " only official software ....bla bla bla...",, even though i'm already open oem unlock via developer option.
Click to expand...
Click to collapse
ah yes i think its dm-verity then you should flash a disabler sorry about the twrp
SA-15 said:
ah yes i think its dm-verity then you should flash a disabler sorry about the twrp
Click to expand...
Click to collapse
how to disable dm-verity? how to do that?
Kakang_Ragil said:
how to disable dm-verity? how to do that?
Click to expand...
Click to collapse
flash this on twrp
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.1.zip
then also its recommended to flash magisk
Kakang_Ragil said:
when i pacthed rom with magisk. system not run normaly, (it's softbrick) screen say " only official software ....bla bla bla...",, even though i'm already open oem unlock via developer option.
Click to expand...
Click to collapse
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Kakang_Ragil said:
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Click to expand...
Click to collapse
no there is no devs for this phone
Kakang_Ragil said:
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Click to expand...
Click to collapse
if you can help me to revive this phone again. my telegram @rogerfortun
SA-15 said:
if you can help me to revive this phone again. my telegram @rogerfortun
Click to expand...
Click to collapse
how?? what can i help?
Kakang_Ragil said:
ok, i try,... btw any kernel for this devices? i need to control cpu for minig crypto.
Click to expand...
Click to collapse
no there is no kernel for this device
SA-15 said:
no there is no kernel for this device
Click to expand...
Click to collapse
Ok,,,, thanks info
Kakang_Ragil said:
Ok,,,, thanks info
Click to expand...
Click to collapse
can you try this twrp
https://github.com/n7105/Action-Recovery-Builder/releases/download/2974756341/recovery.img
dont forget to compress it into .tar