Related
Hello guys,
Today I am presenting stable rooting method for D5322_19.3.A.0.470_Lollipop 5.0 without any old FTF requirement or fear of data loss etc.
Requirements
D5322 with Unlocked bootloader
Current firmware version should be 19.3.A.0.470
Flashtool with updated fastboot and flashmode drivers
50% Battery and a Safe backup (In case of error)
Happy mind
Downloads
1. Recovery kernel (Please download DUAL_RECOVERY_D5322-LP.img for best result) ====>> Here (16 MB)
(Recovery kernel credits goes to our respectable XDA Recognized Contributor @abcdjdj)
2. SuperSU.zip ===> Here (Tested)
3. Download BusyBox ===> Here Tested v1.23.1-Stericson.zip
Rooting procedure
Move SuperSu.zip, BusyBox.zip to your devices and turn off it.
Put downloaded D5322_19.3.A.0.470_Lollipop 5.0.ftf in flashtools firmware folder
Open Flashtool and connect your device in FASTBOOT mode by holding volume UP key.(Blue LED)
Flash recovery kernel in fastboot mode and disconnect the device.
Turn on device,press volume down button continusly when you see pink LED.
Flash SuperSU and BusyBox
Wipe cache and delvik
Turn on device -- Rooted + No read write issue + No SD card problem
Rare issue
=> Some users may face system app removal problem ==> Fix Here
=> Flashtool Cannot unbundle files (Very rare) ==> Fix Here
Feel free to ask questions ......
Not able to perform step 10.
error as :
Click to enlarge image
10/010/2015 18:10:29 - INFO - Selected Bundle for Sony Xperia T2 Ultra (D5322). FW release : 19.3.A.0.470. Customization : Lollipop 5.0
10/010/2015 18:10:29 - INFO - Preparing files for flashing
10/010/2015 18:10:29 - ERROR - Cannot delete C:\Users\'@#&\.flashTool\firmwares\prepared\boot
10/010/2015 18:10:29 - INFO - Cannot open bundle. Flash operation canceled
---------- Post added at 06:45 PM ---------- Previous post was at 06:12 PM ----------
any help?
---------- Post added at 07:18 PM ---------- Previous post was at 06:45 PM ----------
stuck at step 10, help me buddy.. I am waiting
Buddy, It seems your end problem == user account permission // corrupt download // file is using by another process
what to do?
no process is running or using any file..
---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------
all I think is problem is with this file only
4. D5322_19.3.A.0.470_Lollipop 5.0 kernel (9MB)
can you reupload or send me this file? 5.0 or 5.0.2 kernel so I can start my device
---------- Post added at 07:58 PM ---------- Previous post was at 07:30 PM ----------
step 10 problem SOLVED
Figured it out! thnx to @ kentexcitebot
I went through C:\Users\name\.flashTool\firmwares and deleted the "prepared" folder under the folder "firmwares".
That fixed the problem, apparently.
Now device is about to boot.. waiting for boot complete
I went through C:\Users\name\.flashTool\firmwares and deleted the "prepared" folder under the folder "firmwares".
That fixed the problem, apparently.
Now device is about to boot.. waiting for boot complete
Click to expand...
Click to collapse
Similar to "FILE IS USING BY ANOTHER PROCESS" Delete means you forced to terminate the process..
rrajesh said:
Similar to "FILE IS USING BY ANOTHER PROCESS" Delete means you forced to terminate the process..
Click to expand...
Click to collapse
yes... my bad.. you need to update steps.. as someone else might get same problem.
root access worked properly. :good:
now my problem is xposed installer.. how to install?
tried flashing zip, but device won't boot.
Xposed is not not available for our device yet...Wait until it fixed for our device. .. You can delete all xposed files to get rid on bootloop.
Solution
1. Flash recovery kernel from #1 post
2. Get rid on Xposed bootloop HERE manually : no flash required
I am not being harsh
I am just letting know what is happening, sorry if I sound harsh
already uninstalled xposed.
ok, so finally I manage to get it working,
1st performed clean installation of 5.0.2 ftf
then followed steps 1 to 9
then deleted the "prepared" folder under the folder "firmwares", (If existed).
then followed step 10 & 11.
started device & updated everything.
I got proper root access & everything is working fine :good:
Thank you :good:
Only problem is, cant boot in Recovery now, after everything is done successfully.
Hw u managed to work xposed on our phne its nt possible as it is not working anymore @rrd84
Thanks bro, root successful but cannot remove/uninstall system apps please help
Check Dis thread @joseph LR http://forum.xda-developers.com/showthread.php?t=3096863
pvnsai73 said:
Hw u managed to work xposed on our phne its nt possible as it is not working anymore @rrd84
Click to expand...
Click to collapse
NO, xposed is not working, bootloops, I said I managed to fix my problem of step 10.
you misunderstood me
---------- Post added at 08:03 PM ---------- Previous post was at 07:56 PM ----------
joseph LR said:
Thanks bro, root successful but cannot remove/uninstall system apps please help
Click to expand...
Click to collapse
yes.. preinstalled apps are not uninstalling by this root method, everything else is good.
but kingo root method can uninstall them, kingo root is chinese root tool,
but I am not able to replace kingo root SuperUser with supersu,
thats y I am sticking with this thread root method.
---------- Post added at 08:11 PM ---------- Previous post was at 08:03 PM ----------
pvnsai73 said:
Check Dis thread @joseph LR http://forum.xda-developers.com/showthread.php?t=3096863
Click to expand...
Click to collapse
I am having this problem, any help?
whichever option I select, mobile either reboot or poweroff
click image to enlarge
joseph LR said:
Thanks bro, root successful but cannot remove/uninstall system apps please help
Click to expand...
Click to collapse
Dear joseph LR,
You can download following apps from PlayStore
Download R/W Checker from HERE
[Open and tap to R/W, if successful your root is with r/w is ok]
System App remover (Using since 2012) Download
Enjoy!!
Dear @rrd84,
I worked on recovery and Xposed with different methods whole Sunday,,,but not working.. RC LED blinks but phone boot normally always
I think we should wait until @Nut (XZ Developer) fix it..
.
@ rrajesh
Thanks for R/W Checker
working perfectly now
yes.. we should wait until @Nut (XZ Developer) fix it..
No Recovery Mode D5322 since rooted Kitkat 4.4.3
I am not able to do Step 6 as my device doesn't boot into recovery mode. Is there any other way of flashing SuperSU and BusyBox? Please help me. Can I flash them using flashtool?
Thank you
badboy_0077 said:
I am not able to do Step 6 as my device doesn't boot into recovery mode. Is there any other way of flashing SuperSU and BusyBox? Please help me. Can I flash them using flashtool?
Thank you
Click to expand...
Click to collapse
No, you can't flash them using Flashtool
Read 1st post carefully for recovery mode...
????
about step no. 4 Flash recovery kernel in fastboot mode and disconnect the device can any one tell me what to do exactly in pic if possible
rustynail1985 said:
about step no. 4 Flash recovery kernel in fastboot mode and disconnect the device can any one tell me what to do exactly in pic if possible
Click to expand...
Click to collapse
#Download recovery kernel an put it on C:\Users\[ UR NAME] \.flashTool [latest flashtool]
#Connect your device in fastboot mode ( Hold volume up and now inset usb...Wait 15Sec)
#Open flash tool ,, click on Flash Device (First icon)
#Select fastboot
#Select flash kernel (Browse downloaded file. change file type sin to img in explorer)
#OK
rrajesh said:
No, you can't flash them using Flashtool
Read 1st post carefully for recovery mode...
Click to expand...
Click to collapse
I did all the steps successfully . But im not able to use flodermount. It gives error unable to write to sd. Root explorer also not mounting to r/w. NextappSd also showing error. Phone is successfully rooted. Please help
Root is no longer working on MM update.
Don't suppose anybody knows how to get to recovery with hardware button?
hecksagon said:
Don't suppose anybody knows how to get to recovery with hardware button?
Click to expand...
Click to collapse
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
CSX321 said:
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
Click to expand...
Click to collapse
You are a hero. I have looked for the better part of 2 hours for this. Anyway I'll sideload the LP update and start over. Hopefully somebody can make use of the recovery and boot pulls and get us a working recovery.
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
nethead72 said:
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
Click to expand...
Click to collapse
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
CSX321 said:
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
Click to expand...
Click to collapse
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
File Types?
hecksagon said:
The latest Windows version of kingroot works on the zenwatch. I currently have root that persists after reboot and I am working on pulling the boot.img and recovery.img. Not sure what to do after that, hope somebody can pick up on this.
Recovery.img
https://drive.google.com/file/d/0BxOsuCVqSlnfVzVGRWo4bmZZZHc/view?usp=docslist_api
Boot.img
https://drive.google.com/file/d/0BxOsuCVqSlnfLVp4Z19EQ0owdTQ/view?usp=docslist_api
Click to expand...
Click to collapse
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
hecksagon said:
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
Click to expand...
Click to collapse
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
Click to expand...
Click to collapse
You have to download the normal phone apk from apkmirror or some other site and use adb to sideload it. Google sideloading apps to Wear, should work the same for any watch. Otherwise you can buy Apps2Wear on the play store. I have done that because its more convenient.
Ok, went through the whole process, is there a way to check root access using ADB?
You should have KingRoot app installed on your watch. That will tell you if you have root. I imagine you could try to pull some files from /system or something that would normally not be accessible. I wouldn't recommend writing to system yet. I soft bricked by watch just by pasting a modified build.prop over the original, trying to turn off low bit depth ambient mode.
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
nethead72 said:
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
Click to expand...
Click to collapse
Make sure you have adb debugging and adb bluetooth debugging enabled on watch. Make sure you have usb adb debugging turn on on phone. Then make sure you have bluetooth debugging turn on in Wear app. Make sure you do these in that order because the toggle in the wear app wont show up unless you have debugging enabled on phone first.
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
Click to expand...
Click to collapse
Sorry, they are .img. They were pulled using Flashify. The extension must have been stripped when I uploaded them to Drive.
nethead72 said:
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
Click to expand...
Click to collapse
Sometimes it fails once and works when you retry. Not sure why.
hecksagon said:
Sometimes it fails once and works when you retry. Not sure why.
Click to expand...
Click to collapse
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
nethead72 said:
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
Click to expand...
Click to collapse
Maybe 10-15 mins when I did.
hecksagon said:
Maybe 10-15 mins when I did.
Click to expand...
Click to collapse
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
nethead72 said:
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
Click to expand...
Click to collapse
Did you confirm the apk was good? I'd try installing it on your phone. I don't think KingRoot has file management capabilities.
On a side note, I would advise against uninstalling anything. I just went to flash the previous OTA and it failed because I didn't have Jawbone installed.
I've just got a LG G4 after owning a G3 for ages.
It's LG G4 H815 UK.
I'm trying to unlock bootloader and root + install recovery.
It was easy on G3....but i'm having HUGE problems with the G4.
All the steps in the how to guide from here, go well, until I attempt to get device ID.
It just keeps coming up with the same old errors as you can see below.
Please, help me out...i've literally been trying for the last 3 hours non stop...lol.Hey, i'll even send a donation to beer money if somebody can pleeeeeezzz help me out.:good:
**********************************************
C:\adb\LG Root>adb.exe devices
List of devices attached
C:\adb\LG Root>adb.exe devices
List of devices attached
LGH8159460c7f1 device
C:\adb\LG Root>adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh
/data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
2958 KB/s (1048328 bytes in 0.346s)
1137 KB/s (9319 bytes in 0.008s)
3711 KB/s (4017098 bytes in 1.057s)
C:\adb\LG Root>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
Couldn't open the port \\.\COM4
C:\adb\LG Root>Send_Command.exe \\.\COM5
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
FAIL
#
FAIL
#^C
C:\adb\LG Root>id
'id' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>#ID
'#ID' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>#id
'#id' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=552
96 count=529920 of=/dev/block/mmcblk0
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-Supe
rSU-v2.46.zip /data/local/tmp/busybox
'sh' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>
*******************************************
Many thanks
Matt
Your port is closed, please check device manager>port and instead of com4 that being request why send command on com5?
Not entirely sure what you mean?
When I click on ports.bat in my adb folder it says it sees the device on port 5.
I'm lost.....please help:crying:
Here's another screenshot with it showing port 4....but still it fails to get the ID of the phone to enter into LG website to get code.
I get to this point in the screenshot below, where i have to enter "id" but nothing happens...just a blinking cursor when i enter id and press enter.
Any ideas?
thanks
Matt
fails on the last line....
matthew33 said:
fails on the last line....
Click to expand...
Click to collapse
Hi buddy are you using the right com port because you need to choose the diag1 com port not the other one , also ignore what it says in device manager just use the com port from the lg root tool which is diag1... And one last thing are you on marshmallow or lollipop??
matthew33 said:
fails on the last line....
Click to expand...
Click to collapse
try this
Code:
Send_Command.exe \\.\COM4
Xceeder said:
Hi buddy are you using the right com port because you need to choose the diag1 com port not the other one , also ignore what it says in device manager just use the com port from the lg root tool which is diag1... And one last thing are you on marshmallow or lollipop??
Click to expand...
Click to collapse
I'm using diag1 and am using the com port from lg root tool.
My phone has Android 6.0 installed.
Any ideas?
thanks
Matt
This is the latest error i got....
I get to the point where i see
"Type "id" and press enter (no quotes)."
But when I type in the word "id" on the next line comes up the word "Fail"
wtf??
matthew33 said:
I get to the point where i see
"Type "id" and press enter (no quotes)."
But when I type in the word "id" on the next line comes up the word "Fail"
wtf??
Click to expand...
Click to collapse
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
---------- Post added at 10:18 AM ---------- Previous post was at 10:12 AM ----------
Xceeder said:
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
Click to expand...
Click to collapse
Can i just ask which version of MM are you on is it 20a , 20b , 20c etc ?? You can find out this information by going into settings/about phone/software info/software version...
Xceeder said:
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
---------- Post added at 10:18 AM ---------- Previous post was at 10:12 AM ----------
Can i just ask which version of MM are you on is it 20a , 20b , 20c etc ?? You can find out this information by going into settings/about phone/software info/software version...
Click to expand...
Click to collapse
Thanks mate...really would appreciate it if you could find the links.
Below is screenshot of my phone info:
free uploader
matthew33 said:
Thanks mate...really would appreciate it if you could find the links.
Below is screenshot of my phone info:
free uploader
Click to expand...
Click to collapse
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
---------- Post added at 12:14 PM ---------- Previous post was at 12:03 PM ----------
Xceeder said:
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
Click to expand...
Click to collapse
Right if you haven't already flashed twrp then do that first then download the file on this page and flash it in recovery
https://download.chainfire.eu/696/supersu/
If you need help to install twrp just quote my post , this method should work ....
---------- Post added at 12:27 PM ---------- Previous post was at 12:14 PM ----------
P.s if this method does not work then just flash this kernel in recovery
https://www.androidfilehost.com/?w=files&flid=46800
Flash the 1.4.7 version...
Xceeder said:
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
---------- Post added at 12:14 PM ---------- Previous post was at 12:03 PM ----------
Right if you haven't already flashed twrp then do that first then download the file on this page and flash it in recovery
https://download.chainfire.eu/696/supersu/
If you need help to install twrp just quote my post , this method should work ....
---------- Post added at 12:27 PM ---------- Previous post was at 12:14 PM ----------
P.s if this method does not work then just flash this kernel in recovery
https://www.androidfilehost.com/?w=files&flid=46800
Flash the 1.4.7 version...
Click to expand...
Click to collapse
Thnaks for taking the time to help me mate....I really genuinely appreciate it.
If you could tell me exactly how to flash TWRP etc, it would be super appreciated.
I can't enter recovery on my phone.
thanks
Matt
Download twrp 3.0.2.0 and save it in the same place as your adb files , then open a command window by holding shift and right mouse click and do these commands -
adb devices
(This will check if the device is connected you should see a number next to device)
adb reboot bootloader
(This simply reboots your phone ready to flash)
fastboot flash recovery twrp-3.0.2-0-h815.img
(Make sure the twrp name is the same as the command)
Hit enter and you should have twrp installed on your device...
Xceeder said:
Download twrp 3.0.2.0 and save it in the same place as your adb files , then open a command window by holding shift and right mouse click and do these commands -
adb devices
(This will check if the device is connected you should see a number next to device)
adb reboot bootloader
(This simply reboots your phone ready to flash)
fastboot flash recovery twrp-3.0.2-0-h815.img
(Make sure the twrp name is the same as the command)
Hit enter and you should have twrp installed on your device...
Click to expand...
Click to collapse
Done exactly what you said, and this is what i got...see screenshot.....
imageupload
matthew33 said:
Done exactly what you said, and this is what i got...see screenshot.....
imageupload
Click to expand...
Click to collapse
Go to the settings of your phone and press on build number around 8 times until it says you are a developer then enable USB debugging and tick the box that says enable OEM unlock and try again , also make sure when you connect the phone to the PC select mtp connection for USB ...
Xceeder said:
Go to the settings of your phone and press on build number around 8 times until it says you are a developer then enable USB debugging and tick the box that says enable OEM unlock and try again , also make sure when you connect the phone to the PC select mtp connection for USB ...
Click to expand...
Click to collapse
Well, I'm getting somewhere....after hours of trying i've definitely 100% unlocked the bootloader.
BUT, how do i install TWRP and superuser plus how do i boot into recovery?
thanks
Matt
I tried to reboot into recovery using adb fastboot command reboot recovery.....it renooted to a black screen with a green android laying down with, i think a red mark??
Any ideas?
thanks
Matt
Hey everyone, i saw the new galaxy j6+ an i liked it. It's cheap with good specifications. Just wanna ask if there's a compatible twrp, root and xposed released for this device. If not i guess I'll wait an extra month or buy another device.
I tried to patch the boot image via magisk but it didn't work as well
mhailart said:
I tried to patch the boot image via magisk but it didn't work as well
Click to expand...
Click to collapse
Hey man, i rooted my j6+ with magisk and removed bloatware, working perfectly, i can help if you got any errors
dope77 said:
Hey man, i rooted my j6+ with magisk and removed bloatware, working perfectly, i can help if you got any errors
Click to expand...
Click to collapse
That's a good news, may kindly share your experience, so that we can also root our j6+.
Rooks said:
That's a good news, may kindly share your experience, so that we can also root our j6+.
Click to expand...
Click to collapse
I rooted my j6+ with magisk patched boot.img
Im sure you know the steps but just in case,
1. Do a full backup, cz you'll need to reset your device after rooting
2- go to dev options and turn on oem unlock
3- download magisk manager
4- download the rom of your device, extract it, then open ap with 7zip,extract the boot.img.lz4 with 7 zip standard
5- place the boot.img on your j6+
6- open magisk manager, it'll ask you if you want to install, press no thanks.
7- go to magisk settings, scroll down to patched image output format, select img.tar
8- go back to main menu, select install, then select boot.img file, then select the img you placed on your device.
After it finish patching, go to download mode and flash the patched img through Odin.
This worked for me
dope77 said:
I rooted my j6+ with magisk patched boot.img
Im sure you know the steps but just in case,
1. Do a full backup, cz you'll need to reset your device after rooting
2- go to dev options and turn on oem unlock
3- download magisk manager
4- download the rom of your device, extract it, then open ap with 7zip,extract the boot.img.lz4 with 7 zip standard
5- place the boot.img on your j6+
6- open magisk manager, it'll ask you if you want to install, press no thanks.
7- go to magisk settings, scroll down to patched image output format, select img.tar
8- go back to main menu, select install, then select boot.img file, then select the img you placed on your device.
After it finish patching, go to download mode and flash the patched img through Odin.
This worked for me
Click to expand...
Click to collapse
4- Firstly, downloaded .zip file has many files (AP, CP, BL, HOME_CSC). Which file contains 'boot.img.lz4' file and how to extraxt from .md5 file?
5- How to get boot.img from boot.img.lz4 file? Will renaming the file work?
6- Does magisk work on a no-rooted device?
1.Extract the zip, then open ap as zip, copy boot.img.lz4 to desktop
2.download 7 zip standard, it can extract the lz4 archives.
3. After your extract the image, place it on your device
4. Download magisk manager and launch it
5. When You launch magisk, it will ask if you want to install, press no.
6. go to settings in magisk, scroll down to patch boot.img format, select img.tar
7. Go back to magisk, uncheck preserver force encryption, select install, then choose patch boot.img
8. Magisk will ask to locate your boot img, choose the img you placed on your device.
9. After magisk finish patching, the new img will be placed in downloads folder.
10. Move it to your pc, launch odin and choose ap and choose the patchedboot.img .
11. Go to download mode and flash the img
12. Device will reboot and ask to reset to factory settings. Reset it and after it finish booting, you'll see magisk installed
Some notes :
1.Do full backup bcz you'll have to reset to factory settings your device after rooting
2. Unlock OEM in developer options
3. Magisk doesn't need root, it will root your device.
4. DOWNLOAD 7 ZIP STANDARD, IT CAN EXTRACT LZ4 ARCHIVES
---------- Post added at 02:03 AM ---------- Previous post was at 02:00 AM ----------
Link of 7z standard
https://github.com/mcmilk/7-Zip-zstd/releases/tag/18.05-v1.3.7-R2
Press on assets and select the one compatible with your Windows (64 or 32 bits)
ORRRR METHOD 2 WHICH IS EASIER A LOT
Dial *#1234# and post the screenshot here
I already have j6+ and patchedboot.img, just wanna
Check if we have same device (mine is sm-j610f not sm-j610fn) and I'll upload the img and you'll only have to flash it
dope77 said:
1.Extract the zip, then open ap as zip, copy boot.img.lz4 to desktop
2.download 7 zip standard, it can extract the lz4 archives.
3. After your extract the image, place it on your device
4. Download magisk manager and launch it
5. When You launch magisk, it will ask if you want to install, press no.
6. go to settings in magisk, scroll down to patch boot.img format, select img.tar
7. Go back to magisk, uncheck preserver force encryption, select install, then choose patch boot.img
8. Magisk will ask to locate your boot img, choose the img you placed on your device.
9. After magisk finish patching, the new img will be placed in downloads folder.
10. Move it to your pc, launch odin and choose ap and choose the patchedboot.img .
11. Go to download mode and flash the img
12. Device will reboot and ask to reset to factory settings. Reset it and after it finish booting, you'll see magisk installed
Some notes :
1.Do full backup bcz you'll have to reset to factory settings your device after rooting
2. Unlock OEM in developer options
3. Magisk doesn't need root, it will root your device.
4. DOWNLOAD 7 ZIP STANDARD, IT CAN EXTRACT LZ4 ARCHIVES
---------- Post added at 02:03 AM ---------- Previous post was at 02:00 AM ----------
Link of 7z standard
https://github.com/mcmilk/7-Zip-zstd/releases/tag/18.05-v1.3.7-R2
Press on assets and select the one compatible with your Windows (64 or 32 bits)
ORRRR METHOD 2 WHICH IS EASIER A LOT
Dial *#1234# and post the screenshot here
I already have j6+ and patchedboot.img, just wanna
Check if we have same device (mine is sm-j610f not sm-j610fn) and I'll upload the img and you'll only have to flash it
Click to expand...
Click to collapse
Appreciated, for this detailed info shared with us. 10x on the way.
Amytime man, if you need anything else lemme know
dope77 said:
Amytime man, if you need anything else lemme know
Click to expand...
Click to collapse
Next question, where to find TWRP recovery for SM-J610F?
---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------
I did not try this method. But, i'm gonna do it soon, because i did it from AndroDef's thread.
He already uploaded for ARJ3, but i had ARIM. But, i'm switching back to ARIM and will surely try this method and will share my experience.
There isn't any custom recovery released for this device yet,but i already submitted a request in TwrpBuilder project a month ago, hope they'll do it soon, you can check it here, it's at the buttom (47,it's the 3rd oldest request)
https://twrpbuilder.github.io/downloads/twrp/#tab=inQueue
Also you can check the completed builds to see if the twrp building for the device is finished.
dope77 said:
There isn't any custom recovery released for this device yet,but i already submitted a request in TwrpBuilder project a month ago, hope they'll do it soon, you can check it here, it's at the buttom (47,it's the 3rd oldest request)
https://twrpbuilder.github.io/downloads/twrp/#tab=inQueue
Also you can check the completed builds to see if the twrp building for the device is finished.
Click to expand...
Click to collapse
So, it's time to wait then.
How do you remove bloatware?
Rooks said:
So, it's time to wait then.
Click to expand...
Click to collapse
If you're interested, could you try this out? Just make sure you have the stock firmware to hand in case of any issues.
https://androidfilehost.com/?fid=11410963190603862888
.
dope77 said:
There isn't any custom recovery released for this device yet,but i already submitted a request in TwrpBuilder project a month ago, hope they'll do it soon, you can check it here, it's at the buttom (47,it's the 3rd oldest request)
https://twrpbuilder.github.io/downloads/twrp/#tab=inQueue
Also you can check the completed builds to see if the twrp building for the device is finished.
Click to expand...
Click to collapse
I don't know, if you check the link above or not, but i do it on regular daily basis.
TODAY, it's gone...........................................
---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------
ashyx said:
If you're interested, could you try this out? Just make sure you have the stock firmware to hand in case of any issues.
https://androidfilehost.com/?fid=11410963190603862888
.
Click to expand...
Click to collapse
This one seems to be for "J610", not for "J610F".
Will it work............................................................................
I'm eager to try that one................
---------- Post added 1st December 2018 at 12:01 AM ---------- Previous post was 30th November 2018 at 11:59 PM ----------
Rooks said:
So, it's time to wait then.
Click to expand...
Click to collapse
It's rejected..................
# 25 in the list
---------- Post added at 12:16 AM ---------- Previous post was at 12:01 AM ----------
ashyx said:
If you're interested, could you try this out? Just make sure you have the stock firmware to hand in case of any issues.
https://androidfilehost.com/?fid=11410963190603862888
.
Click to expand...
Click to collapse
If it fails (i hope, it won't), it will take me long to setup my device again.
---------- Post added at 12:33 AM ---------- Previous post was at 12:16 AM ----------
ashyx said:
If you're interested, could you try this out? Just make sure you have the stock firmware to hand in case of any issues.
https://androidfilehost.com/?fid=11410963190603862888
.
Click to expand...
Click to collapse
It's a partial success:
SUCCESS
1- Recovery flash is success (odin did not boot into recovery, instead loaded os).
2- After loading android, did a boot into recovery, it loads twrp recovery
FAILURE
3- TWRP recovery does not respond to touch or hardware keys
4- Device keeps booting into twrp recovery
5- Seems to be stuck in recovery mode
Brilliant.................................................................
---------- Post added at 12:39 AM ---------- Previous post was at 12:33 AM ----------
ashyx said:
If you're interested, could you try this out? Just make sure you have the stock firmware to hand in case of any issues.
https://androidfilehost.com/?fid=11410963190603862888
.
Click to expand...
Click to collapse
Reverting to custom recovery, done.
Device is normal again.
A partial success though.
Might be issues with kernel, or something else.....
With your skills and my device, it can be done in a blink of an eye.
Click to expand...
Click to collapse
Rooks said:
I don't know, if you check the link above or not, but i do it on regular daily basis.
TODAY, it's gone...........................................
---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------
This one seems to be for "J610", not for "J610F".
Will it work............................................................................
I'm eager to try that one................
---------- Post added 1st December 2018 at 12:01 AM ---------- Previous post was 30th November 2018 at 11:59 PM ----------
It's rejected..................
# 25 in the list
---------- Post added at 12:16 AM ---------- Previous post was at 12:01 AM ----------
If it fails (i hope, it won't), it will take me long to setup my device again.
---------- Post added at 12:33 AM ---------- Previous post was at 12:16 AM ----------
It's a partial success:
SUCCESS
1- Recovery flash is success (odin did not boot into recovery, instead loaded os).
2- After loading android, did a boot into recovery, it loads twrp recovery
FAILURE
3- TWRP recovery does not respond to touch or hardware keys
4- Device keeps booting into twrp recovery
5- Seems to be stuck in recovery mode
Brilliant.................................................................
---------- Post added at 12:39 AM ---------- Previous post was at 12:33 AM ----------
Reverting to custom recovery, done.
Device is normal again.
A partial success though.
Might be issues with kernel, or something else.....
Click to expand...
Click to collapse
I'm pretty sure I can fix the touch issues.
Is ADB functional?
ashyx said:
I'm pretty sure I can fix the touch issues.
Is ADB functional?
Click to expand...
Click to collapse
Not sure about adb, did not try it
Rooks said:
Not sure about adb, did not try it
Click to expand...
Click to collapse
If adb works could you do:
adb pull / tmp/recovery.log
Rooks said:
How do you remove bloatware?
Click to expand...
Click to collapse
Well if you need custom recovery for xposed, there's xposed module in magisk that can be installed without twrp. I'm already using it and have multiple modules (gravitybox, xprivacy and greenify), all running without problems. For debloating, after your root the device, go to google play and download an app called system app remover, it'll show you all apps on your j6+. Select the apps you want to remove and press uninstall. After uninstallation is done, reboot your device
ashyx said:
If adb works could you do:
adb pull / tmp/recovery.log
Click to expand...
Click to collapse
Sure, but never worked with samsungs. It's my first regular samsung device. Never liked exynos and cortex combo, but it's different.
Last time tried to push recovery.img via adb and it did not work. I have root and root explorer app installed. Where is that log located in system partition. I'm not an skilled linux coder guy but i have serious history with androids and palms.
---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------
dope77 said:
Well if you need custom recovery for xposed, there's xposed module in magisk that can be installed without twrp. I'm already using it and have multiple modules (gravitybox, luck patcher, xprivacy and greenify), all running without problems. For debloating, after your root the device, go to google play and download an app called system app remover, it'll show you all apps on your j6+. Select the apps you want to remove and press uninstall. After uninstallation is done, reboot your device
Click to expand...
Click to collapse
Forget debloating, i can deal with it now.
Get back to twrp recovery.
BTW, did you waych 'Venom'or not? Coz i'm watching right now.
---------- Post added at 01:00 AM ---------- Previous post was at 12:38 AM ----------
Could not find /tmp/recovery.
But did find /cache/recovery folder, that contains last_log.1 and last_log.2 files
MAGISK FULL GUIDE (APK for install and other mods coming soon!)
The bootloader unlock is pretty similar to any other phone.
Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer Options. Make sure to enable OEM unlocking.
(On PC) "adb reboot bootloader", "fastboot flashing unlock_critical", use volume to select unlock. THIS WILL ERASE ALL CONTENT ON YOUR DEVICE.
IF YOU DONT WANT TO DO THIS FROM SCRATCH, SKIP TO PART 2
Go to https://support.microsoft.com/en-us/surfacerecoveryimage
Select Surface Duo from the drop down
Enter your serial number and download the file
Extract the firmware .zip
Extract the Payload file
Moved bootloader to root
Installed Magisk Manager apk and patched bootloader image
Attempted to flash which resulted in "cannot write to partition_b"
PART 2:
download the patched magisk_boot.img from here https://drive.google.com/file/d/1-7NWj8_jFH8AtpTTpXITOv1eh-wo7xlz/view?usp=sharing
adb reboot bootloader
fastboot boot magisk_patched.img
PART 3 - All right, lets make it permanent!
Place magisk_patched.img on your sd root
adb shell
su
cd /dev/block/by-name/
chmod 777 boot_a
chmod 777 boot_b
DEV=$(ls /dev/block/by-name/boot_b); echo $DEV
dd of=$DEV if=/sdcard/magisk_patched.img
DEV=$(ls /dev/block/by-name/boot_a); echo $DEV
dd of=$DEV if=/sdcard/magisk_patched.img
Reboot and we are good!
I am working on an app to streamline the process as well as provide additional mods and addons to the device. I hope to have something for you guys by the end of the week.
I do plan on streaming some of this stuff (twitch.tv/goingh0st), and am working on a section of my discord for the same thing (World of Gh0st)
https://www.patreon.com/GoinGh0st
Thank you for your support and I cant wait to get more stuff to you guys!
Would you mind sharing the patched Boot?
Everything you posted is spot on, try switching partitions.
Perseu5 said:
The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Select oem bootloader unlocking. Adb reboot bootloader, fastboot flashing unlock, use volume to select unlock. This will erase all content on your device.
Go to https://support.microsoft.com/en-us/surfacerecoveryimage
Select Surface Duo from the drop down
Enter your serial number and download the file
Extract the firmware .zip
Extract the Payload file
Moved bootloader to root
Installed Magisk and patched bootloader image
Attempted to flash which resulted in "cannot write to partition_b"
Attempted to boot the patched boot image which resulted in a bootloop.
Out of town for the time being but will be attempting something different when I get back in a day or so.
Click to expand...
Click to collapse
I tried the same and I had the same issue. Seems the the boot partitions, both a and b, are not writable or erasable even with the bootloader unlocked.
I even went as far as unlocking critical and still the same issue.
Sent from my Surface Duo using Tapatalk
really????
try different USB CABLE! DO NOT USE type C to C.
Use USB-A to C
So anyone tried my method? Should work
avetny said:
really????
try different USB CABLE! DO NOT USE type C to C.
Use USB-A to C
Click to expand...
Click to collapse
Haven't had time to try, but I was using c to a cable
Sent from my Surface Duo using Tapatalk
bxmoney181 said:
Haven't had time to try, but I was using c to a cable
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
u mean usb type A to C?
avetny said:
u mean usb type A to C?
Click to expand...
Click to collapse
Yup
Sent from my Surface Duo using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
avetny said:
So anyone tried my method? Should work
Click to expand...
Click to collapse
Have you confirmed successful flash of partitions??
Sent from my Surface Duo using Tapatalk
bxmoney181 said:
Yup
Sent from my Surface Duo using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
Have you confirmed successful flash of partitions??
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
ok I'll try it tomorrow after work my self
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Perseu5 said:
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Click to expand...
Click to collapse
im still at work....
Please try it out....I remember in my pass that was a issue with many phones
Perseu5 said:
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Click to expand...
Click to collapse
How did it go?
Just tried with a to c cable with same result unfortunately. Sending successfully, writing boot_b gives flashing not allowed to this partition. Also did a critical unlock and verified with fastboot oem device-info
wtf!!!!!!!!
---------- Post added at 09:21 PM ---------- Previous post was at 09:11 PM ----------
...... I will return this phone man.
I'm not sure with anything about unlocking and rooting (noob atm) but i noticed in developer settings that the default USB configuration is set to "No data transfer"
Is that by any chance causing the write issues?
panzercool said:
I'm not sure with anything about unlocking and rooting (noob atm) but i noticed in developer settings that the default USB configuration is set to "No data transfer"
Is that by any chance causing the write issues?
Click to expand...
Click to collapse
Nah that's not it. I was once that's there too lol. Keep reading and keep learning.
Sent from my Surface Duo using Tapatalk
bxmoney181 said:
Nah that's not it. I was once that's there too lol. Keep reading and keep learning.
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
Would you post the patched boot image?
I want to try this myself without going through the prerequisite hoops.
Updating the main post now. I figured it out guys!
Perseu5 said:
Updating the main post now. I figured it out guys!
Click to expand...
Click to collapse
oh broo tell us whats happening
Perseu5 said:
Updating the main post now. I figured it out guys!
Click to expand...
Click to collapse
Tell us!!!