Database Info

root for the rct6303w87dk w/ 5.0 lollipop

hey, i just registered here to inform you all that ive figured out a way to root the new rca viking pro, but i cant seem to get supersu to install its updated binaries... i went about it like this, i searched google for kingroot app, installed it, followed the instructions it came with, and for my own benefit, i ran it twice just to make sure it worked. and wala, root! but the downside is they have their own form of su called king user. and i hate it. i hope this info helps someone, as ive came to this site on so many occaisions and everytime something on here bailed me out of a jam, i figured it was bout time i gave to a site that contributed so much to me. i love xda, and i hope someone here can get some nice things going with this tablet. thanks for your time... May

info on the RCT6303W87DK
also, FOR YOUR OWN GOOD, DO NOT CHANGE THE GENERIC.kl file on this device!!! the keyboard that comes with it, and the volume and power buttons on the device will NO LONGER function!!! just got a replacement from wallyworld because of my epic failure.... YOU HAVE BEEN WARNED!!! :good:

I tried a few different methods last night to install supersu binaries effectively breaking root a few times all resulting in using king root to "reroot". The main issue I'm having is it immediately has an update to version 1.9.1 (tablet firmware).. To get around this prompt lock the tablet, turn screen back on but unlock it with camera (bottom right). After doing this you get home rows back. Now since root I'm getting failures to install the update and every time it comes on I'm promoted for the update multiple times. Any ideas?

reemobeens19 said:
I tried a few different methods last night to install supersu binaries effectively breaking root a few times all resulting in using king root to "reroot". The main issue I'm having is it immediately has an update to version 1.9.1 (tablet firmware).. To get around this prompt lock the tablet, turn screen back on but unlock it with camera (bottom right). After doing this you get home rows back. Now since root I'm getting failures to install the update and every time it comes on I'm promoted for the update multiple times. Any ideas?
Click to expand...
Click to collapse
you have to be unrooted to apply system updates... then re root. king root should have an unroot option in app, so un rooting isnt hard. or you can hook the tab to your pc and use kingo to unroot. it will unroot, but it wont root...

I can confirm that kingroot does in fact have an option to unroot. I can also confirm that it is able to reroot after the 1.9.1 update.
Mine updated to that the first time I turned it on and I lost the update file. Can anyone tell a difference before and after the update?
I'm going to do a full stock ROM dump tonight to share. Just in case me or anyone else screws theirs up. I want to install a custom recovery and don't want to take any chances with it. Locked mtk bootloaders are ugly. Especially on these newer chipsets which cannot be unlocked as easily as the old ones.
Btw, before I finally found kingroot I must have tried about thirty different ways to root this thing. I tried several on phone root apps and a bunch of ones which required a pc connection to work and I came up short.
I got partial root with iroot 1.7 something for PC. It installed kingroot and would say that it was granting root to apps but noting actually had root.
Finally I found the latest version of vroot. V1.8 something, it had the same root database number as the earlier iroot which I had, though. Then I installed the pdanet drivers and ran the vroot and it worked! Finally! I spent hours on the stupid thing.
I did try the kingroot (iroot) apk and it couldn't root it and suggested I try the PC version.
What I'm getting at is that possibly fw 1.9.1 is just a security patch that makes it harder to root. Because when I tried the apk it couldn't handle it and I had to use the PC version with pdanet drivers to get it to work. While the apk worked for you on v1.9.0 (mine updated the first time I powered it on).
So if you install the update you might want to watch out for that.
It may be possible to stop the forced ota with fotakill. Just Google the apk and place it in your /system/app folder, then delete it rename the update in your cache folder and restart.
That has always worked for me so far on all of my other Android devices.
Cheers,
-SS

Used titanium back up to freeze the updater. Went to Dev options, enabled show processor usage or something to that nature.. Watched for any thing popping up that said update. I don't remember the exact apk but a simple search with in titanium for the word update returns the only app containing it. This did indeed solve my problem about the constant update. Also another work around to bypass the update, tell it to "download and install" then immediately his stop/cancel download. This will be my last post for now on the device as I no longer own it.
Have a blessed day!

For those wanting wired controller support, tincore works wonderfully. Im using an official xbox360 control and it controls the ui and a majority of my games. Emulators as well. This is pretty much the only way to use a wired control on this tablet as far as i know. I've tried dozens of methods to no avail. Still trying to get su up and running as well. King root does function but id prefer something im used to. Anyone know of a custom recovery that'd work on this thing???

simstimstar said:
I can confirm that kingroot does in fact have an option to unroot. I can also confirm that it is able to reroot after the 1.9.1 update.
Mine updated to that the first time I turned it on and I lost the update file. Can anyone tell a difference before and after the update?
I'm going to do a full stock ROM dump tonight to share. Just in case me or anyone else screws theirs up. I want to install a custom recovery and don't want to take any chances with it. Locked mtk bootloaders are ugly. Especially on these newer chipsets which cannot be unlocked as easily as the old ones.
Btw, before I finally found kingroot I must have tried about thirty different ways to root this thing. I tried several on phone root apps and a bunch of ones which required a pc connection to work and I came up short.
I got partial root with iroot 1.7 something for PC. It installed kingroot and would say that it was granting root to apps but noting actually had root.
Finally I found the latest version of vroot. V1.8 something, it had the same root database number as the earlier iroot which I had, though. Then I installed the pdanet drivers and ran the vroot and it worked! Finally! I spent hours on the stupid thing.
I did try the kingroot (iroot) apk and it couldn't root it and suggested I try the PC version.
What I'm getting at is that possibly fw 1.9.1 is just a security patch that makes it harder to root. Because when I tried the apk it couldn't handle it and I had to use the PC version with pdanet drivers to get it to work. While the apk worked for you on v1.9.0 (mine updated the first time I powered it on).
So if you install the update you might want to watch out for that.
It may be possible to stop the forced ota with fotakill. Just Google the apk and place it in your /system/app folder, then delete it rename the update in your cache folder and restart.
That has always worked for me so far on all of my other Android devices.
Cheers,
-SS
Click to expand...
Click to collapse
When I first got the tablet, i let it update then got the kingroot apk, installed it and it rooted. The one i used is in chinese but it had instructions and i followed them to the t. It worked. And the back up of the rom would be greatly appreciated by ALOT of us trust me. Especially me...?

Overall, this is a pretty nice tablet to own. The space alone is worth the price of admission. The specs are decent as well. Quad core, mali gpu, one gb ram, the detachable keyboard, oh i could go on. Im a heavy gamer and this is perfect for me. I have all the power i need to run everything i use. And with a 32 gb sdcard and 32gb internal, thats plenty storage for pretty much anything. I recommend this device to anyone looking for performance on a budget. 10/10

Yes, I'ts very nice. I couldn't find anything else that would even come close to it in that price range. Even used ones....
I was able to edit some config files for mrkdroidtools and got it working properly with mt8127 for the most part. At least now it will create the proper scatter file (in the correct format) for mt8127. Even though it's working properly to create the scatter, you have to use Windows enabler to allow to click the greyed out scatter file button. Before if you did that it would create a scatter in the old format without correctly identifying partition types and even not setting the correct partition sizes in the scatter. Also the chip was identified incorrectly before and now it's not.
All of the mt8127 scatters I have seen use scatter v1.1.2 (not the old format) and now I got it to output that. With proper scatter you can manually pull each partition correctly in spft.
Mtkdroidtools will now partially work for backup. It will pull firmware.info, mounts.info, and phone.info. along with NVRAM and /system only. Can't pull the others because the partitionsions are locked. Even with insecure adb (root ADB) and selinux set to permissive.. You can get old style scatter from firmware.info and mtk studio, but better to let mtkdroidtools pull the correct one.
It will try to make the CWM recovery but fails out. Magic twrp will now create the correct recovery and push it to the phone (with files from spft backup) but the recovery won't work due to the locked loader.
At least I know my backup works now because I was able to reflash the original recovery with it (this is how I screwed up my first one, which ended up going back to Wal-Mart). That first one stopped booting, but it was still recognized by spft. I just had no backup to fix it with. If they rma it, I'm sure it can be reflashed with original firmware and resold.
I will be putting this all in a toolkit and uploading. This can benefit all devices with mt8127, not just us. I also have the latest spft and I even found the checksum.exe in another package somewhere. This can be used to generate the firmware checksums for spft so you don't have to flash with checksum turned off (safer).
Haven't tried to reroot with mtkdroidtools because I think the supersu is pretty old. Don't think it will work properly in lollipop.
I wish there was a way to unlock the bootloader. I poked around in my backup of it and it clearly references files from NVRAM. Files with checksums and lists. I would think that there would be some other tablet sold under a different brand which is unlocked out there
Somewhere which is the same as ours.
Gotta run. I'll try to upload the toolkit after work if there is time. I need to clean up my backup to remove personal files from data before uploading. If it's an emergency and someone needs backup without /data I can provide now. Don't know if it will work though because kingroot resides on data. Perhaps it will work just can't authorize root.
Cheers!
-SimStim

Again, with the new one I got I couldn't root with the latest iRoot from the PC until pdanet was installed on the phone. Then it worked fine.
Without pdanet it will get temp root, then restart and when kingroot automatic root check runs it says no root and will try again and again in a loop.
With pdanet, temp root, reboot, and it's permanent root.
Just in case anyone is trying to root via this method.
Cheers!
-SimStim

simstimstar said:
Again, with the new one I got I couldn't root with the latest iRoot from the PC until pdanet was installed on the phone. Then it worked fine.
Without pdanet it will get temp root, then restart and when kingroot automatic root check runs it says no root and will try again and again in a loop.
With pdanet, temp root, reboot, and it's permanent root.
Just in case anyone is trying to root via this method.
Cheers!
-SimStim
Click to expand...
Click to collapse
You may be right... The first one i had i let kingoroot on the pc download and install some drivers. And i used pdanet awhile ago for a previous rca tab and never deleted the drivers, so maybe thats why it worked flawlessly the second time. If you have a custom recovery installed, which did you use and how'd you install it?

I tried the "magic" auto-build of CWM and TWRP, but neither one works because of the locked boot loader.
Which also makes me wonder if my backup would work on someone else's tab... The 7" RCA tab on here with the prerooted ROM works because they found another tablet which was the same and had an unlocked bootloader. At least that's what understood from it. I could be wrong though. I didn't read all 35 pages (or however many).
I'll try and double check that
Cheers,
-SimStim

simstimstar said:
I tried the "magic" auto-build of CWM and TWRP, but neither one works because of the locked boot loader.
Which also makes me wonder if my backup would work on someone else's tab... The 7" RCA tab on here with the prerooted ROM works because they found another tablet which was the same and had an unlocked bootloader. At least that's what understood from it. I could be wrong though. I didn't read all 35 pages (or however many).
I'll try and double check that
Cheers,
-SimStim
Click to expand...
Click to collapse
any progress yet? ive been searching hi and lo for custom recoveries that work to no avail. i want to try and unlock the bootloader but im afraid i may screw somthing up if i cant restore a backup. i guess its a chance im willing to take if it furthers development on this tablet. i honestly want to rip lollipop off of here and run jb 4.2.2. personally i think thats the best version of android yet. at least with funcionality. and the fact you can just plug and play on that version is a plus for me!!! hope you come across something....
may

I'm planning to return mine. I started looking around at tablets in this price range and have decided to buy a Pipo M9S instead. The price is pretty close and it absolutely spanks this device in hardware specs.
I'm somewhat biased, because I have an Android tv device based on the RK3288 and I know how fast it is. The hardware video decoder is the best I've seen yet. Plus it is so nice not to have to deal with the locked bootloader.
I wanted an RK3288 based tablet before, but was put off by the $200-300 price range which I had seen on the Pipo P9 and the P1. Then just recently I found that I could get a p7 for ~150 and an M9S for ~$175, so I've decided that I would much rather go that way(M9S).
I will hang on to my backup of this device in case it will come in handy for anyone else in the future.
Cheers,
-SimStim

simstimstar said:
Yes, I'ts very nice. I couldn't find anything else that would even come close to it in that price range. Even used ones....
I was able to edit some config files for mrkdroidtools and got it working properly with mt8127 for the most part. At least now it will create the proper scatter file (in the correct format) for mt8127. Even though it's working properly to create the scatter, you have to use Windows enabler to allow to click the greyed out scatter file button. Before if you did that it would create a scatter in the old format without correctly identifying partition types and even not setting the correct partition sizes in the scatter. Also the chip was identified incorrectly before and now it's not.
All of the mt8127 scatters I have seen use scatter v1.1.2 (not the old format) and now I got it to output that. With proper scatter you can manually pull each partition correctly in spft.
Mtkdroidtools will now partially work for backup. It will pull firmware.info, mounts.info, and phone.info. along with NVRAM and /system only. Can't pull the others because the partitionsions are locked. Even with insecure adb (root ADB) and selinux set to permissive.. You can get old style scatter from firmware.info and mtk studio, but better to let mtkdroidtools pull the correct one.
It will try to make the CWM recovery but fails out. Magic twrp will now create the correct recovery and push it to the phone (with files from spft backup) but the recovery won't work due to the locked loader.
At least I know my backup works now because I was able to reflash the original recovery with it (this is how I screwed up my first one, which ended up going back to Wal-Mart). That first one stopped booting, but it was still recognized by spft. I just had no backup to fix it with. If they rma it, I'm sure it can be reflashed with original firmware and resold.
I will be putting this all in a toolkit and uploading. This can benefit all devices with mt8127, not just us. I also have the latest spft and I even found the checksum.exe in another package somewhere. This can be used to generate the firmware checksums for spft so you don't have to flash with checksum turned off (safer).
Haven't tried to reroot with mtkdroidtools because I think the supersu is pretty old. Don't think it will work properly in lollipop.
I wish there was a way to unlock the bootloader. I poked around in my backup of it and it clearly references files from NVRAM. Files with checksums and lists. I would think that there would be some other tablet sold under a different brand which is unlocked out there
Somewhere which is the same as ours.
Gotta run. I'll try to upload the toolkit after work if there is time. I need to clean up my backup to remove personal files from data before uploading. If it's an emergency and someone needs backup without /data I can provide now. Don't know if it will work though because kingroot resides on data. Perhaps it will work just can't authorize root.
Cheers!
-SimStim
Click to expand...
Click to collapse
if you still have it, can you upload that stock image and the tools you have? or send them to me via email? ive done something terrible and i wish to go back to stock until i figure something else out. if you can do it via email, heres my [email protected]- thanks

How can I contribute
While I haven't had any issues with my DK on v1.9.1, I'm always interested in the latest and greatest Android ROM. I've got my fingers crossed for you on making restore images so you can get another ROM built on this. So, if I can contribute, even if it is paypal'ing $20 to pay toward a second tablet for you to work on, let me know.
Regards,
David

Is anyone working on unlocking the bootloader of this device? Fastboot allows me to see the "press volume up key to unlock" screen using fastboot oem unlock, however it does not respond to volume keys. Being that I got that far could it possibly succeed if it didn't have to prompt for permission?

It's going to be really tough to try and crack it. The RCA 7" tablet here on xda that got an unlocked loader because they found out that there was a Cube branded tablet which was identical, except it had an unlocked boot loader.
RCA is not the actual manufacturer (I forget who is, but cpu-z will tell you I think). Perhaps if someone were to contact the manufacturer and find out which other companies they OEM that tablet hardware to. Then check them out for unlocked bootloaders.
I would be willing to bet that they may not reveal that info so easily, so try looking around for similar hardware.
I found on a benchmarking site that the RCA 10" which doesn't have the keyboard is also the same spec and model number as a model sold by gigabyte. I don't know the status of the bootloader, though. If you flash it you risk bricking your tablet.
MTK is pretty much the opposite of rockchip, who has made their devices nearly brick proof. MTK devices with locked bootloaders are very likely to brick because of the security measures built in, odd and often encrypted filesystems with specific hashes for certain partitions, write protection on the main system partions. It's really a massive pain in the neck. Those are the reasons why I decided to get rid of mine.
It's rooted and someone who doesn't want to build custom ROMs will be perfectly happy with it. Me, I want full access! Really the tablet is pretty nice. Just not if you want custom recovery, kennel, unofficial ROMs, etc.
I'm still looking. It's probably out there somewhere. I'll be sure to post if I see anything.
Cheers,
-SS

How do you know the bootloader is locked? I see walmart has cut the price on them, I haven't seen any rca tablets with bootloader locked.

Giving this phone away...

Hi everyone,
I am giving this phone to my mom since I don't need it anymore (bought Samsung S6 few months ago)! Phone is currently on Android 4.4.4 kangkat 5.1 and is customised pretty nicely( no Ads, working fast , no FC ,pretty snappy).
Should I update to Marshmallow before I give it to her or should I just leave it the way it is? She is just the regular user and will not use anything more that dialer, sms, browser, weather, calendar, calculator, camera, etc.. So just basic apps and I will strip this phone to bare minimum but was just wondering should I get her Android 6 on this (at least battery live maybe inproved?)
Any thoughts or ideas will be appreciated.

If you have the knowledge to do it, then yes, it's probably worth installing MM as stock and leaving it like that - no custom recovery, no root. That way she can get the regular security updates with the minimum of fuss. The uninterested user doesn't need the hassle of a rooted device. And easier for you in not having to strip the phone - a new installation will do that for you anyway, and will allow her to sign in as herself and properly own the phone.

dahawthorne said:
If you have the knowledge to do it, then yes, it's probably worth installing MM as stock and leaving it like that - no custom recovery, no root. That way she can get the regular security updates with the minimum of fuss. The uninterested user doesn't need the hassle of a rooted device. And easier for you in not having to strip the phone - a new installation will do that for you anyway, and will allow her to sign in as herself and properly own the phone.
Click to expand...
Click to collapse
I do have knowledge (well maybe I might remind myself a little using Google). I am running Xposed on this build and like I've said phone is super stable with this build but also pretty simple to use for basic /regular user. Future updates are just going to confuse her.. The only thing I would like for her is maybe improved battery live and that's why I would go to MM. I was also thinking to maybe get new battery on this one(don't know how hard is to change it?). Anyway thanks for responding ,

Flash latest 6.0.1 MM on it and lock bootloader... give it to her barebones and let her enjoy it...
just did that with my oldest brother who lost his phone to a muggin.... and its the easiest way for them to stay up to date on latest security patches, etc

"maybe get new battery on this one(don't know how hard is to change it?)"
It's actually pretty simple: https://www.youtube.com/watch?v=VSGNUrpwIno
Though there's another thread that I read just today that shows there's a certain risk: http://forum.xda-developers.com/google-nexus-5/help/nexus-doesnt-boot-fastboot-t3282033

chaco81 said:
Flash latest 6.0.1 MM on it and lock bootloader... give it to her barebones and let her enjoy it...
just did that with my oldest brother who lost his phone to a muggin.... and its the easiest way for them to stay up to date on latest security patches, etc
Click to expand...
Click to collapse
I actually never gone back to stock so I don't know how hard is it and how time consuming is it? I am on TW recovery v2.7.0.0. should I just flash nandroid or do I have to flash factory image first and than lock bootloader?

dahawthorne said:
"maybe get new battery on this one(don't know how hard is to change it?)"
It's actually pretty simple: https://www.youtube.com/watch?v=VSGNUrpwIno
Though there's another thread that I read just today that shows there's a certain risk: http://forum.xda-developers.com/google-nexus-5/help/nexus-doesnt-boot-fastboot-t3282033
Click to expand...
Click to collapse
You are right , I am not going to mess with battery replacement. The old one should be OK for some time ...

I would also not bother relocking the bootloader. How many threads in these forums contain wails from people who have cacked their devices and there is no way to recover because the bootloader is locked?
This thread actually refers to the Nexus 6, but since Nexus devices are so similar in many ways it's probably still relevant, and should put you off taking this unnecessary step: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Stock is extremely simple. Download the factory image (Google "factory image"), unzip and run flash-all - obviously after you've got all your drivers set up to communicate with the device. If you haven't yet, I'll bore you again with recommending Wugfresh's Nexus Root Toolkit, which has a really helpful button to walk you through the driver setup. If the flash-all script doesn't work (it doesn't for some people), you can unzip all the components, put them in your ADB/fastboot directory and flash each component separately.

dahawthorne said:
I would also not bother relocking the bootloader. How many threads in these forums contain wails from people who have cacked their devices and there is no way to recover because the bootloader is locked?
This thread actually refers to the Nexus 6, but since Nexus devices are so similar in many ways it's probably still relevant, and should put you off taking this unnecessary step: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Stock is extremely simple. Download the factory image (Google "factory image"), unzip and run flash-all - obviously after you've got all your drivers set up to communicate with the device. If you haven't yet, I'll bore you again with recommending Wugfresh's Nexus Root Toolkit, which has a really helpful button to walk you through the driver setup. If the flash-all script doesn't work (it doesn't for some people), you can unzip all the components, put them in your ADB/fastboot directory and flash each component separately.
Click to expand...
Click to collapse
I just updated Wugfresh Nexus Root Toolkit since I had old version on my laptop. Should I use RESTORE/UPGRADE/DOWNGRADE option and than FLASH STOCK + UNROOT?
P.S. DONE.. Running MM now on it.
Thank you all

roundel.... easy to do
make sure u have latest ADB installed on your PC.... so open SDKManager and run it so it updates...
download the latest Factory Image
extract the image, place it on the platform tools folder of your SDK and double click the flash.all.bat file... let the magic happen
google returning back to stock, there are tons of tutorials out there showing how to do this.

chaco81 said:
roundel.... easy to do
make sure u have latest ADB installed on your PC.... so open SDKManager and run it so it updates...
download the latest Factory Image
extract the image, place it on the platform tools folder of your SDK and double click the flash.all.bat file... let the magic happen
google returning back to stock, there are tons of tutorials out there showing how to do this.
Click to expand...
Click to collapse
I did it and phone is running MM now. I am amazed with battery life now, it is crazy good comparing to KK!
So I am now back to stock unrooted but I left bootloader unlocked. Will she (my mom) get any updates if this Nexus get OTA updates?

A stock unrooted rom with stock recovery is all that is needed for ota updates. The bootloader can remain unlocked for ota updates.

Update it now and give her. I was doing the same stuff with my mom and she denied which then later made me try this phone out. Overall it's good but battery sucks.

D6616, Possibly the worst phone to mess with! Hard bricked, absolutely lifeless!

I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!

hash054 said:
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
Click to expand...
Click to collapse
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.

arikdahn said:
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
Click to expand...
Click to collapse
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..

hash054 said:
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
Click to expand...
Click to collapse
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171

arikdahn said:
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
Click to expand...
Click to collapse
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe

hash054 said:
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
Click to expand...
Click to collapse
Well I guess I'll be doing that then. Thanks. So how do you flash that file without a recovery?
I do not know how to handle flash tool since I have only heard of it and never used it. It appears I'll be using it to get rid of kingroot. How does one learn how to handle it so's one doesn't go and mess anything up?
My bootloader is also unlockable but I don't wanna screw with all the things that unlocking it does to the phone so I'm leaving it alone. I like those features
Also did you ever try to remove bloat on the stock ROM? Everything I remove via titanium backup just reinstalls immediately after removal.
Sorry for all the questions instead of answers for you. You are one of the few still messing with this device and I appreciate all your help very much. All of the info on this forum is mostly applicable to when the phone came out. This means almost all of it only applies to android 4.4 or it doesn't apply to the T-Mobile variant b/c T-Mobile was less popular when this phone was a flagship and uses Wifi text/calling which requires special planning. That and the fact that the threads are several hundred pages long makes following along impossible and makes this site all but useless for these phones now.

Beginner in need of help with rooting and some clarification on Magisk/TWRP/recovery

Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!

DampDeceiver said:
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
Click to expand...
Click to collapse
Look in the forums of how to unlock, root and install TWRP recovery. I actually enjoy system wide black themes so this is what I would recommend.
You need to unlock your bootloader if you had not done so already. In the forum I suggested, under the rooting section, you need to grab the bootable Magisk file. You will have to put your OP6 into fastboot mode and open up a command prompt and type- fastboot boot "name of img file" to boot using that img file.
All these instructions are in the forum regarding unlocking and rooting the device. If you are only interested in obtaining a system wide black theme while also keeping everything in good shape, you need to unlock your bootloader and root with Magisk. Do not worry about installing TWRP as you do not need this for your certain needs. After you root with Magisk, you can use an app call Adaway to block ads. To obtain a system wide black/dark theme, you need to go to the Google Play Store and download an app called "Substratum" after you obtain root. It will only work with root. Also download an app called "Swift Black". This is the theme you will be applying.
I would look at the forums again, the one I am talking about is up there at the top of the page when you look at the OP6 forums. It is clearly labeled for unlocking, rooting and installing TWRP recovery. You are only interested in unlocking your bootloader and installing Magisk, that's it. It has all the instructions you need. Once you are there, install the apps above from the Google Play Store and apply the theme using Substratum. Hope this helps!

DampDeceiver said:
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
Click to expand...
Click to collapse
you should totally root it!
This is how I did it!
Note u will break warranty, and unlocking bootloader will completely wipe ur phone(even the storage memory)
Download the following:
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3791316 (install this on computer)
and https://drive.google.com/open?id=15mXZz4OrwRGXz5JCKeYjwukQf0raWnOb
in your phone go to settings> about phone>Select "Build number" 4 times.
Then in Settings>Developer Options> turn on "OEM unlocking", "USB debugging" and for convenience "Advanced rooting".
Click reboot and Select "Bootloader"
Plug your phone to your computer and open the software you installed and click "check device" Then unlock, on your phone you will have to use volume buttons to go up and down and then the power button to select.
(Note, never relock with custom firmware or root on it, recommend u only lock it when 100% stock or u can permanently brick if something happens when ur rooted.)
Now on that software, you had click advanced options and click "Open a free terminal with adb and fastboot privileges".
Extract that zip file and move it to your desktop.
Type: cd "C:\Users\Bradley Gregory\Desktop" or if its in the folder: cd "C:\Users\Bradley Gregory\Desktop\All files for TWRP"
Then type: fastboot flash boot_a twrp.img , (Your using the same twrp.img)
Then again: fastboot flash boot_b twrp.img
After this look at your phone and use the volume buttons till it says recovery and press power button.
If it asks for a password type ur pin in from phone, and change language before pressing checkmark.
Then copy everything from that zip onto ur phone(when ur in the temporary recovery)
Then click install, find file location of where u put your stuff on. bottom right button click (img file) then click "boot.img" then select boot.
Now click the bottom right button to change back to zips.
Flash zips in this order
1. Flash TWRPWorkingInstaller.zip
2. Flash TWRP-BLUE-FIX.zip
3. Flash Root.zip or you will bootloop
after you can reboot your phone. Open magdisk app >settings and under update settings change update channel to beta. then you can go to the app home and install directly the new update.
(optional) in magisk select download and search busybox and click install
Hope this helps!
PM me for any questions!
(don't factory reset with custom boot. also in recovery, u can now make backups of your entire phone if error happens)
I recommend u download this file:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
if u ever hard brick this will wipe ur phone and make it normal again(wipes internal memory)

Personally, I would hold off on doing anything until we have an official twrp and more development. Right now, the solutions we've got are unforgiving. People are bricking their phones right and left because they missed a step, and the unbricking process is more involved than other android phones at the moment.
Also, before you do anything, I would take a moment to assess your computer literacy and comfort with mucking around in the system files of your devices. If you're used to things that "just work" like on iOS, you may not like what you find once you cross over into modding. If you do enjoy that kind of stuff, good, but the tradeoff for greater freedom is more work in keeping your phone updated and operational.

Don't do it!! Hold off,. I am an old hat, since 2005, and I spent the whole day yesterday fixing the brick that I turned my OnePlus 6 into. It's a pain and very easy to do.
Just wait two weeks.
Sent from my ONEPLUS A6003 using Tapatalk

Personally, I would hold off on doing anything until we have an official twrp and more development. Right now, the solutions we've got are unforgiving. People are bricking their phones right and left because they missed a step, and the unbricking process is more involved than other android phones at the moment.
Click to expand...
Click to collapse
Agree. I've been rooting and modding devices (mostly Oneplus) the last couple of years, but with the OP6 things have changed. A/B partitioning have made it somehow more complicated, at least compared to what I'm used to.
Personally I pulled the trigger anyway, i.e. not waiting for an official version of TWRP. I got TWRP and root with the method described in post 70 here: https://forum.xda-developers.com/showpost.php?p=76633618&postcount=70
If and when you do that too I recommend you to install:
* Adaway (from XDA forum) to get rid of ads
* Substratum theme engine (from Play Store)
And then some Substratum themes:
* Ozone (from Play store) to theme Oneplus OS and apps
* Swift Black (from Play store) to theme other apps
And finally some Magisk modules:
* Youtube Vanced Magisk black themed (from Magisk repo) to get themed You tube, adfree and with picture-in-picture
* Viper4Android FX (from Magisk repo) to get much better audio
* OP_AlwaysOnDisplay_enabler (from OP5T XDA forum) to enable settings for Always On Display (if you want that)
https://www.xda-developers.com/enable-always-on-display-oneplus-6-oneplus-5-5t/
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
Click to expand...
Click to collapse
I strongly recommend you to use a custom recovery (TWRP) if you root and install rooted apps. If you don't it will be difficult or impossible to recover if you get in trouble. For example, it is easy to uninstall Magisk modules or Substratum themes from the recovery in case they cause bootloops. And additionaly you can make full backups of your system in TWRP. A small hint for backups is to copy them to a safe place (computer or USB stick) in case you get into trouble with the internal storage on your phone.

The A/B partitioning has definitely made things more complicated, especially with respect to flashing. I've been rooting and modding here for 5+ years, and I'm taking it very slowly so far. Right now, you can't just fix things with a quick reflash of your rom. Even factory resets can brick you. This is not a phone for noobs at the moment.

iElvis said:
The A/B partitioning has definitely made things more complicated, especially with respect to flashing. I've been rooting and modding here for 5+ years, and I'm taking it very slowly so far. Right now, you can't just fix things with a quick reflash of your rom. Even factory resets can brick you. This is not a phone for noobs at the moment.
Click to expand...
Click to collapse
There is an unbrick tool and fastboot ROMs to recover, but u r right, u just can't screw around with things like we used to due to u need a computer avail even if u bootloop

That, and there are some conflicting instructions flying around and some disagreements amongst the devs about how to do things. I would not want to be starting out with rooting on this phone tbh.

I agree with most posts here.
I've been flashing ever since the HD2 back in the days. I've really spend alot of nights fixing my phones from hard/soft bricks, never actually really broke one though.
But untill there are some stable recovery/root methods, I wouldn't want to start my android rooting experience with this phone right now. As some said, wait a couple of weeks.

Thank you everyone for replying! You've been a great help.
I figure I will wait for the official TWRP and a guide to install it by that time.
Until then I'll keep a close eye on these forums to keep learning. Cheers!

All of these guys are spot on with advice. I too have been doing this for awhile, however this is my first A/B partition phone. You definitely want TWRP. I can't count how many times I've installed a root program or tweaked a system file and messed up my device. Recovery is your friend! Make backups often!! (Once you get TWRP installed of course)

I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!

DampDeceiver said:
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
Click to expand...
Click to collapse
This is what I did. Unlock the bootloader to save from data loss later, but no recovery or root until things are a little more understood.

DampDeceiver said:
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
Click to expand...
Click to collapse
Yes, you can unlock your bootloader and not root. You're correct that it will erase your data, but once it's unlocked you will be ready to root once official twrp and magisk root comes out.
You'll want to use Magisk because it keeps you compatible with Safety net, has root hide and really good modules as well to add stuff.
If you want a dark theme for now you can download Andromeda from the Play store, and hen substratum. It doesn't need root just some commands from your pc and adb. However it is a few dollars, so if you don't want to pay for that then you can just wait to root. The theme you'll want is swift black, but I use ozone as well. Swift black for some apps to be black theme, but ozone to get a custom accent color and dark theme for OOS quick settings, settings app, etc.

NateDev said:
Yes, you can unlock your bootloader and not root. You're correct that it will erase your data, but once it's unlocked you will be ready to root once official twrp and magisk root comes out.
You'll want to use Magisk because it keeps you compatible with Safety net, has root hide and really good modules as well to add stuff.
If you want a dark theme for now you can download Andromeda from the Play store, and hen substratum. It doesn't need root just some commands from your pc and adb. However it is a few dollars, so if you don't want to pay for that then you can just wait to root. The theme you'll want is swift black, but I use ozone as well. Swift black for some apps to be black theme, but ozone to get a custom accent color and dark theme for OOS quick settings, settings app, etc.
Click to expand...
Click to collapse
That is what i was about to type, use andromeda from play store and use substratum to theme whatever you like.

Unlocking the bootloader is required if you want root and/or custom recovery(TWRP).
Custom recovery is optional and root does not depend on it, nor does custom recovery depend on root either. What custom recovery gives you are mainly two things:
1. More features than a stock recovery.
2. Able to flash unsigned zip.
So if neither of these two really means something to you then you can stay with stock recovery.
The root procedure could be a bit different depends on whether you use a customer recovery or not.
If you do, then the root procedure usually is just as simple as flash a Magisk installation zip.
If you do not use a custom recovery, stay on the stock recovery, then the root procedure is different because the stock recovery does not allow you to flash an unsigned zip. The procedure is:
1. Obtain the stock boot image.
2. Install Magisk Manager and use it to patch the boot image.
3. Boot the phone with the patched boot image(fastboot boot patched_boot.img command), thus you get a temporarily rooted phone. Temporarily means you lost root after reboot because the patched boot image is not actually written to the ROM of your phone.
4. Now on the (temporarily) rooted phone, you have all the power to install the root permanently, by Magisk Manager.

Help rooting Samsung galaxy j3 (sm-J337a)

It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.

Right?
I'm having the same issue. I can't figure out how to root mine either and I've got the same phone and carrier.

nickthekid said:
It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.
Click to expand...
Click to collapse
Details of your current ROM Please..?
Build number etc...

Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB

iamoz said:
Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB
Click to expand...
Click to collapse
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Yes I would be interested in having those files please... Either upload them here or I can give you an email if you prefer... Let me know..

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.

NonStickAtom785 said:
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.
Click to expand...
Click to collapse
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there

rip21skinz said:
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there
Click to expand...
Click to collapse
I do not have the option to OEM Unlock the phone period. It is not in my developer options unfortunately. If you do find something of that nature please do contact me. Also if you would like a TWRP for your device I'd be up to developing it, although I wouldn't be able to maintain bugs... All I need is the kernel and I can get it done.

Any updates on this?