Related
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
in cmd window :fastboot flash boot new_kernel.img
IMP:steps 1 & 2 are can also be used when u have met with an unexpected bootloop/restart problem at any time( if u don't want to flash the complete stock ftf,this boot image will help u in letting ur device come out of bootloop.
3.proceeding to our main thread....now boot into recovery & flash "magisk.zip"
4.wipe cache & dalvik.and reboot.
PROPERTIES OF THE KERNEL (new_kernel.img:---
Build 32.4.A.1.54
1. Sony RIC- disabled.
2. DM-Verity- disabled.
3. TWRP- disabled.
4. DRM Fix- enabled.
5. Superuser / root- Not present. ( flash magisk its better)
6. Busybox- Not present
7.many more tweaks to reduce heat & increase battery backup
LINK TO THE CONTENT
https://drive.google.com/drive/folders/1ic9zsMi576s1P9H6s1z4_g0ofSJJktIs?usp=sharing
I just want stock rooted rom with magiks
doctorsworld99 said:
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
Click to expand...
Click to collapse
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Sumantomar1709 said:
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Click to expand...
Click to collapse
u can try flashing magisk over stock.but whenever i did that my device used to go into bootloop.thats why i've to experiment with different twrps,kernels to detect the culprit.
finally i got this awesome kernel which helped me to come out of bootloops everytime.so i will suggest to use this [near to stock ] kernel .
but u can try flashing magisk over stock.....if anything goes wrong ,,,just flash the new_kernel,,and ua fine to go with magisk.
Thnx. I will try & let u know.
thank u sirThis kernel help me from bootloop .how did u make this kernel
Champsingh909 said:
thank u sirThis kernel help me from bootloop .how did u make this kernel
Click to expand...
Click to collapse
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
This kernel really working in bootloop.thnx
doctorsworld99 said:
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
Click to expand...
Click to collapse
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Champsingh909 said:
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Click to expand...
Click to collapse
creating a separate thread isn't a good idea ,i'll update the details of the kernel in this thread itself,plz give me some time.
Kernel properties added.
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
LoaderFabi said:
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
Click to expand...
Click to collapse
i got frequent bootloops on installing it over stock kernel and also over m-rom .i think the kernel was the culprit.
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
chrnodroid said:
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
Click to expand...
Click to collapse
Hopefully yes,flash it as instructed.best of luck:good:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
MrHands0m3 said:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
Click to expand...
Click to collapse
confirmed!! this kernel is the ****!.. try it... (don't blame me if you brick your device)
The link to download the kernel won't work anymore, is there a mirror?
Any oreo custom rom is fingerprint unlock is slow,any one is solution for this problem
twrp or file manager
Mr.mask said:
Any oreo custom rom is fingerprint unlock is slow,any one is solution for this problem
Click to expand...
Click to collapse
boot twrp , then go in /data/system/user/0
and delete theses files /fpdata/user.db, settings_fingerprint.xml
reboot the system and setup new fingerprints it should work better now.
BK said:
boot twrp , then go in /data/system/user/0
and delete theses files /fpdata/user.db, settings_fingerprint.xml
reboot the system and setup new fingerprints it should work better now.
Click to expand...
Click to collapse
But it only delete fingerprint lock data is reset ,I again add fingerprint lock in setting
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Worked !!!
Thank you dear. Its worked for mine in p585 oreo android....
Anyone can search mcmilk 7zip in google and download program to extract boot.img.lz4 and get boot.img :good:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Latest twrp dose not worked on my device but this solution work fine
I can confirm that this method does work. I used it on my SM-P580 yesterday. I would suggest that you first backup your all of your apps, contacts, photos, etc using SmartSwitch. You will need to restore everything after the tablet tells you that it needs to be reset because it wipes everything. After the restore, you will need to enter all of your accounts and passwords again but at least all of the data will be back.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
Im not sure if this post belongs here, you link to the T580 TWRP, not the P580.
Is that one compatible with P580?
nill3bor said:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Click to expand...
Click to collapse
If I do this, will I be able to mount my SD Card as internal storage? 16gb just isnt enough on this tablet.
Do you have to be on oreo already for this to work I'm still on 7.0 and with my system modified I can't upgrade normally
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
This one worked for me on a P585Y. You just have to skip the steps below.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
Click to expand...
Click to collapse
It will also show on the Device Maintenance, just ignore the warning.
You can freeze some of the system apps to prevent it from showing on the notification again.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Hello Gyus,
I managed to root the device with the method posted by @amosdinh (Thank you so much). Now I'm trying to configure adoptable storage. So far I didn't achieve this goal. ADB commands doesn't work and I can't install the ASPlugin.zip needed by Root Essentials to set adoptable storage by the app.
TWRP for P585 is corrupted, gives blue/red lines screen. The dev that maintains the code is absent since march. I'm out of luck on this. If anyone have a idea to get adoptable storage on this device while using Oreo, please comment.
Thanks!
---------- Post added at 11:17 AM ---------- Previous post was at 11:11 AM ----------
artaeun said:
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Click to expand...
Click to collapse
Just renaming magisk_patched.img to boot.img and adding to .tar file by 7zip worked for me.
We should ask a dev to update twrp for android 8.1
khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
Same freeze for me with the Omni - can't do anything outside of access download mode
Same Problem
cmzizi said:
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
Click to expand...
Click to collapse
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
Really wish this wasn't the case. I'd actually keep this thing if it had a working TWRP.
On my SM-P580 I used Odin and TWRP I don't get the black screen but when I reboot to get into TWRP recovery mode it shows the padlock and says swipe to unlock. Tried many times bit cannot swipe and cannot get past this. All I want is to be able to use the SD card as internal storage. HELP???? Thanks!!
luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
thanks in advanced
where can i find stock firmware?
I've just installed magisk using TWRP via command line. P580
I've just installed magisk using TWRP via command line.
Read the entire post before trying this yourself.
I installed the latest TWRP, the one that bugs and doesn't display anything, this allows to root without wiping data. I'm running the latest korean firmware for P580.
Just do this:
1. Launch TWRP and INMEDIATELY LOCK YOUR SCREEN. (I got ghost stripes that disappeared after 2 days when testing this, work with low light so you can notice your screen whenever it tuens on) Please don't forget this point, don't [temporarily] damage your screen as I did.
2. adb push Magisk-v[Current version].zip external_sd
3. adb shell
4. twrp install external_sd/Magisk-v[Current version].zip
After this you just need to install MagiskManager-v[Current version].apk and you will be all done.
But there is one thing...
If you ever get into recovery mode, there is no way out without using adb as far as I know. You can launch download mode and cancel it but you'll boot back to TWRP.
When in twrp touching your screen or any button will wake the device up and will start burning the ghost image to your screen.
So if you know of a method for rebooting to system without using adb, please let me know.
Also a solution for this would be to flash back the stock recovery, wich may or may not force to wipe system, that something that needs to be tested tho.
Update: Ok so, you can use a handy tool called MTKroot on recovery.img.lz4 to get recovery.img, then use 7z to pack it into a tar file and flash that tar file with odin (AP, same as TWRP)
This way you will not have a 0.001% chance of random boot into recovery mode and damage your screen
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Tsun_Pooka said:
So my question is, can you lock the bootloader with TWRP installed and still access the system?
Click to expand...
Click to collapse
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Tsun_Pooka said:
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Click to expand...
Click to collapse
How you unlock the bootloader?
bozka1 said:
Unfortunately, it's impossible... If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
Thanks for the tips! By the way, what is dload? If it's a website, I cant find it (the fact that dload is short of "download" doesn't really help). I am now in need of that full-stock ROM.
Tsun_Pooka said:
By the way, what is dload?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/help/formatting-dload-method-t3815949/page2
Whew. I got the bootloader AND FRP locked on me, and now I don't have a usable system. So now, I have to rely on eRecovery to download a 3GBs package and hope all things go well...the problem is, I'd need to find a place that offers fast WiFi...my internet is terrible.
EDIT: Got the system back up thanks to eRecovery. I'm not sure if I want to root or install a custom recovery on the Lite. I've realized even more that I should cherish my older phone, my Samsung Galaxy Win. At least this one isn't complicated or protected by Fort KNOX.
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
usman400 said:
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
Click to expand...
Click to collapse
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Tsun_Pooka said:
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Click to expand...
Click to collapse
I am certainly not up to what u r indicating so cant suggest a solution, earlier in my reply, I was only
indicating my experience with custom ROMs. I havent yet come across a single custom ROM for mate 10
lite that has no problems. Earlier Galaxy S4 Mini, there was custom ROM which was awsome, not a single issue
But for mate 10 lite camera problem is most common. Stock camera app often doesnt work or partially
works, restart of the app etc. You can install open camera, but it does not give u best shots, and filters.
Other issues are already discussed in every custom ROM thread, so I had to come back to Stock ROM
with magisk to remove any system apps that I dont need plus other goodies that magisk offers u (modules)
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Tsun_Pooka said:
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Click to expand...
Click to collapse
Flash the stock erecovery whenever i root my phone i always stick with stock recovery not custom recovery(TWRP)
Theres another method to flash the stock recovery but... This is my method on how to flash stock recovery(erecovery)
PC ONLY!!! and MAKE SURE TO HAVE UNLOCKED BOOTLOADER AND FRP!!!
1.Download MultiTool from https://pro-teammt.ru/en/multi-tool-huawei-honor/
2.Make sure to install Huawei driver from the MultiTool
3.Download This File i provided Here https://mega.nz/#!nZxl2AwZ!6qRIIRbLK4Ub80dPMae4HQQ7e-O49_f2BZ8PhbuZTYM
4.Go to MultiTool and go to recovey Section an select file that you download earlier
5.Make sure to CONNECT USB CABLE TO YOR PC now Reboot your device into Bootloader mode by PRESSING VOLUME DOWN BUTTON and CONNECT THE CABLE TO YOUR PHONE
6.Now on the MultiTool click on Flash Recovery_Ramdisk andlet it flash...,
7.Now You Have The Stock Recovery Installed Now You Can Install Offical Firmware Update On Your Phone
8.All Done
I Hope I Help You
I will follow your guide later today or tomorrow! Thank you for the help!
Tsun_Pooka said:
I will follow your guide later today or tomorrow! Thank you for the help!
Click to expand...
Click to collapse
Np
LoneWolfz said:
Np
Click to expand...
Click to collapse
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
Code:
Software install failed!
Failed to check the update files
Please download the package again
> Reboot system now
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Tsun_Pooka said:
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Click to expand...
Click to collapse
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
bozka1 said:
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Deathecho said:
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Click to expand...
Click to collapse
Yes you can use the same unlock code again.
LoneWolfz said:
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
Click to expand...
Click to collapse
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Tsun_Pooka said:
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Click to expand...
Click to collapse
Np
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337
xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial