I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
dferrey said:
I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
Click to expand...
Click to collapse
I have seen this happen before that you can retain some permissions with certain apps but not really remain rooted its a 50/50 shot its odd but not totally uncommon results. Generally it has something to do with apps that had su permissions prior to the update adding new su permissions don't usually occur after
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Sometimes it won't push the files if they already exsist
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
dferrey said:
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
Click to expand...
Click to collapse
No its always worked like a charm for me maybe go to the market and install su from there to see if that doesn't change its strange though that prime is still detecting it. This method only works on rooted stock from what I have seen. Each time delete backup when you restore root. You can also give a shot at fixing permissions. I believe that ota rootkeeper ask for permissions to maybe at some point it was denied and it stuck.uninstall ota and reinstall hope you get er fixed
dferrey said:
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Click to expand...
Click to collapse
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
Note: I have never been a superuser on this kindle before, this is my first attempt at rooting - but the 2nd try at rooting is throwing the above error. I can see the file renamed as check_rooted.bak in the dir but cant rename with ES_FileExplorer utility as I dont have write permissions
TIA
harbinger13 said:
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
TIA
Click to expand...
Click to collapse
Download root checker from the market its free if you like make sure you gift the developer a buck
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
When I used kfu the last time it took 2 times to stick don't try much until you know its rooted and you have twrp installed and fff boot loader and have made a backup you can restore if something goes gunny.
---------- Post added at 03:02 AM ---------- Previous post was at 02:51 AM ----------
If you have done everything right it should reboot a couple of times the last thing you will see is twrp screen with a big reboot button click reboot and your done you will then see the fff splash screen of the boot loader it should eventually boot into the os
---------- Post added at 03:10 AM ---------- Previous post was at 03:02 AM ----------
The same rules apply for 6.3.1 watch nat3mil do it http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US
So I decided to try to run ubuntu touch on my Samsung Galaxy Nexus(verizon). All went well, but now it seems I cant start the phone, can only get into fastboot mode. Can anyone please walk me through the steps of putting stock android back on my phone? I have adb and fastboot installed on my computer. There's a guide here that walks you through the process of returning the phone to stock software/firmware, but it requires USB debugging to be on, which I can't turn on because the phone won't boot up. I greatly appreciate any help!!!
Phone Info(what's written in fastboot):
PRODUCT NAME-Tuna
VARIANT- toro 32GB
HW VERSION- 9
BOOTLOADER VERSION: PRIMELC03
BASEBAND VERSION- I515.FK02 CDMA-I515.FK01
CARRIER INFO- NONE
SIGNING- production
LOCK STATE- UNLOCKED
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
ashclepdia said:
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
Click to expand...
Click to collapse
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
vsp3317 said:
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
Click to expand...
Click to collapse
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
https://developers.google.com/android/nexus/images
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
ashclepdia said:
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
Click to expand...
Click to collapse
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
vsp3317 said:
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
Click to expand...
Click to collapse
No problem buddy
That's what these forums are for, learning, helping, development, all that good stuff! Just happy it went smoothly for ya.
I think it used to be named .exe, at least it shows as exe on my laptop but I use Linux so it could just be seeing it differently(since I have wine installed)
There is usually a windows executable and a Linux .sh script that can be executed from the terminal to start the process.
See, it's not all THAT bad now is it? Especially since now you know how to do it, messing up the device isn't such a daunting thing anymore lol.
As for keeping status 7 from happening again I highly recommend bookmarking the TWRP or CWM official sites so that before flashing things in the future, you can make sure you have the most up to date custom recovery installed by comparing what is available vs what you have installed(booting into recovery mode will usually have the version info somewhere on the main screen) and of course having a recent nandroid backup made within your current custom recovery. I prefer TWRP but it's a personal choice to each user which they use
Just don't be afraid to play around
Congrats again on your first soft brick&restore! Lol
It's such a relieving feeling once you bring device back from the dead ain't it?
Can anyone tell me why I can't flash a stock recovery using fastboot commands ?
The device is found because I get the serial number when I type 'fastboot devices' but I get a message along the lines of 'cant open file...' when I type 'fastboot flash recovery recovery.img' after renaming the file and putting it in 'sdk platform tools'. Same problem with zip files too.
Commands work when flashing custom recoveries, it only seems to be stock recoveries.
On my current m8, and previous m7, I can only get stock recoveries flashed using a toolkit. Everything works ok when it's flashed but would like to know why commands won't flash them.
Thanks
Have you checked setting on your PC to be sure hidden file extensions are shown? Sometimes renaming these files messes up when that happens. Such as becoming recovery.img.img
KJ said:
Have you checked setting on your PC to be sure hidden file extensions are shown? Sometimes renaming these files messes up when that happens. Such as becoming recovery.img.img
Click to expand...
Click to collapse
Thanks for reply, how do I check that ?
Edit.. Checked 'properties' then 'details' and you're right, file is called recovery.img.img.
How do I change that ?
Thanks
10rdan said:
Thanks for reply, how do I check that ?
Edit.. Checked 'properties' then 'details' and you're right, file is called recovery.img.img.
How do I change that ?
Thanks
Click to expand...
Click to collapse
Ok, thanks
10rdan said:
Edit.. Checked 'properties' then 'details' and you're right, file is called recovery.img.img.
How do I change that ?
Click to expand...
Click to collapse
In Windows, go to Control Panel>Folder Options>View and deselect the option "Hide extensions for known file types"
I can't imagine who would want this option selected. Presumably for grandmas that wouldn't know a file extension if it bit them on the leg.
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
KJ said:
Have you checked setting on your PC to be sure hidden file extensions are shown? Sometimes renaming these files messes up when that happens. Such as becoming recovery.img.img
Click to expand...
Click to collapse
Nice catch. I've seen this trip up folks on XDA before, but always forget about it.
A perfect example of how a seemingly complicated problem can be caused by something very simple.
redpoint73 said:
In Windows, go to Control Panel>Folder Options>View and deselect the option "Hide extensions for known file types".
Click to expand...
Click to collapse
Done it, thanks
redpoint73 said:
In Windows, go to Control Panel>Folder Options>View and deselect the option "Hide extensions for known file types"
I can't imagine who would want this option selected. Presumably for grandmas that wouldn't know a file extension if it bit them on the leg.
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
Nice catch. I've seen this trip up folks on XDA before, but always forget about it.
A perfect example of how a seemingly complicated problem can be caused by something very simple.
Click to expand...
Click to collapse
Only caught that cause it just, I mean a few days ago, was brought up in the N5 section. Lol
I forget who it was, but they were the smarty pants's , not me. ?
I got caught by it on my Moto X awhile ago too. Lol
I bought a Nexus 7 for my son (so he would stop tying down my phone with playing games) everything has worked perfectly and all apks have installed fine but one...Hungry Shark Evolution. When I try to install from the Playstore I get the 505 error, when I try to install a downloaded apk I get "app not installed" my unknown sources box is checked and I have tried clearing cache. It is running stock Android 5.1.1, any help or pointers would be greatly appreciated. I am to the point of considering rooting, custom recovery, and flashing a rom if I have to. I just didn't feel like having to mess with his tablet on top of my and my wife's phone all the time (both our devices run custom roms). That is why I went with a Nexus so it got the new software in a timely manner.
Sent from my A0001 using XDA Free mobile app
do you have a file manager installed, You need to go into the file manager and find the APK that you sideloaded and then manually hit the install button
---------- Post added at 10:38 AM ---------- Previous post was at 10:28 AM ----------
I use Es File Light the free version, When I sideload an APK (Load it directly from my laptop into my tablet directory) I have to go to the local tab on Es File and find the APK (It should be down the bottom of the screen), Click on the one I want installed, then in the box that opens up, click package installer, then click accept and it will install for you
gmfirebird said:
do you have a file manager installed, You need to go into the file manager and find the APK that you sideloaded and then manually hit the install button
---------- Post added at 10:38 AM ---------- Previous post was at 10:28 AM ----------
I use Es File Light the free version, When I sideload an APK (Load it directly from my laptop into my tablet directory) I have to go to the local tab on Es File and find the APK (It should be down the bottom of the screen), Click on the one I want installed, then in the box that opens up, click package installer, then click accept and it will install for you
Click to expand...
Click to collapse
Yes I have a file manager, it looks like it is installing then at the end says "app not installed"
Sent from my A0001 using XDA Free mobile app
this looked interesting,
https://ohthehugemanatee.org/blog/2015/05/29/troubleshooting-android-error-505-from-google-play/
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