Related
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app
Hello guys, I tried to flash Dirty Unicorns ROM
I have a brand new nexus 6p
At first I went through this tutorial:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
First stuck was when I tried fastboot devices in cmd, those USB drivers from sdk manager didn't seem to work, so I downloaded some other driver, which seemed to work
Now I am stuck here:
How To Install A Custom Recovery On Your Device
fastboot flash recovery <filename>.img
So in my CMD I did this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16932 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.827s
and after fastboot reboot, the device is still the same, still the same bootloader, when I hit "recovery mode", there is just the green android robot lying on his back with red ! and after a while the device just starts like normal
also when I start I see "your device software cant be checked for corruption. Please lock the bootloader......" etc and Google logo with unlocked lock in the bottom, but I guess it's normal
any advice please?
solved, /thread
bejek said:
solved, /thread
Click to expand...
Click to collapse
Please post how you solved your issue so it's here for someone searching for an answer in future.
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
bejek said:
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
Click to expand...
Click to collapse
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Heisenberg said:
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Click to expand...
Click to collapse
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Jammol said:
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Click to expand...
Click to collapse
Ofc I did.
I am not sure where did I see it for the first time, but this step was definitely in more guides than just this one.
for example here:
https://devs-lab.com/root-install-twrp-in-nexus-6p.html
and this is the step I am talking about:
Prerequisites:
Unlocked Nexus 6P bootloader.
ADB USB Drivers
Minimal ADB Package
TWRP Recovery: Nexus 6P.
SuperSU (For Root): Download.
Modified Boot.img: Download.
Installing TWRP Recovery in Nexus 6P:
1. Launch command.bat file & type:
fastboot flash boot boot.img
bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Heisenberg said:
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Click to expand...
Click to collapse
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
bejek said:
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
Click to expand...
Click to collapse
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Instead try out,
fastboot boot twrp_src_name.img
(Where twrp_src_name is your TWRP file name)
That should directly boot you to the TWRP. Else try custom TWRP builds like the one with MultiROM.
Heisenberg said:
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Click to expand...
Click to collapse
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
bejek said:
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
Click to expand...
Click to collapse
If you don't boot into recovery right after flashing it, the standard recovery will overwrite it. If you want to prevent this, after flashing TWRP, boot directly into TWRP. Flash latest SU to root it (This will prevent the system from overwriting twrp on reboot.)
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.