Database Info

Samsung S3 Verizon, might be bricked, dont know what to do URGENT

Hey guys, i was messing around with TWRP to get Marchmallow onto my phone, i when i did something with it whenever i boot my phone it gives me this "System software not authorized by Verizon Wireless has been found on your phone. Please turn of your phone and go to the nearest Verizon Wireless store for help" and on the top left corner of my screen it says in read, "SECURE FAIL: KERNEL"
I dont know what to do, i dont care about getting Marshmallow or recovering my data(already backed up all the things i needed on my computer) I just want to be able to get into my phone and use it like i use too. Please help urgently i need my phone back.
Also, i apologize if this is in the wrong place in your forums, this is my first time using it.

Trafalgar747 said:
Hey guys, i was messing around with TWRP to get Marchmallow onto my phone, i when i did something with it whenever i boot my phone it gives me this "System software not authorized by Verizon Wireless has been found on your phone. Please turn of your phone and go to the nearest Verizon Wireless store for help" and on the top left corner of my screen it says in read, "SECURE FAIL: KERNEL"
I dont know what to do, i dont care about getting Marshmallow or recovering my data(already backed up all the things i needed on my computer) I just want to be able to get into my phone and use it like i use too. Please help urgently i need my phone back.
Also, i apologize if this is in the wrong place in your forums, this is my first time using it.
Click to expand...
Click to collapse
Did you try to install another ROM,it might work out,there are many other ROMs with marshmallow,you should try that or if it doesn't work then use adb to flash a rom

Trafalgar747 said:
Hey guys, i was messing around with TWRP to get Marchmallow onto my phone, i when i did something with it whenever i boot my phone it gives me this "System software not authorized by Verizon Wireless has been found on your phone. Please turn of your phone and go to the nearest Verizon Wireless store for help" and on the top left corner of my screen it says in read, "SECURE FAIL: KERNEL"
I dont know what to do, i dont care about getting Marshmallow or recovering my data(already backed up all the things i needed on my computer) I just want to be able to get into my phone and use it like i use too. Please help urgently i need my phone back.
Also, i apologize if this is in the wrong place in your forums, this is my first time using it.
Click to expand...
Click to collapse
Verizon devices with newer firmware than 4.3 and up have a locked bootloader, you can't flash TWRP or custom ROMs and you can't unlock the bootloader, you also can't downgrade to an older version with unlocked bootloader. You're stuck with locked bootloader, anything you try to get around it will only brick your device.
If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service.

Droidriven said:
Verizon devices with newer firmware than 4.3 and up have a locked bootloader, you can't flash TWRP or custom ROMs and you can't unlock the bootloader, you also can't downgrade to an older version with unlocked bootloader. You're stuck with locked bootloader, anything you try to get around it will only brick your device.
If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service.
Click to expand...
Click to collapse
Hey, ive flashed my phone using Odin and i can now access my recovery mode. I am running Android 4.4.2. How can i unlock the bootloader?

Trafalgar747 said:
Hey, ive flashed my phone using Odin and i can now access my recovery mode. I am running Android 4.4.2. How can i unlock the bootloader?
Click to expand...
Click to collapse
Read my post that you quoted again and pay attention to the details and you'll get your answer. If you had paid attention to exactly what I posted then you wouldn't be asking that question.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE

Droidriven said:
Read my post that you quoted again and pay attention to the details and you'll get your answer. If you had paid attention to exactly what I posted then you wouldn't be asking that question.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
"If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service."
Sorry about that, could you elaborate more on my options? What do you mean by flash my stock firmware in Odin (sorry if thats sounds stupid i dont know about this) And what unbrick.img?

Trafalgar747 said:
"If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service."
Sorry about that, could you elaborate more on my options? What do you mean by flash my stock firmware in Odin (sorry if thats sounds stupid i dont know about this) And what unbrick.img?
Click to expand...
Click to collapse
You just said you flashed your device with Odin, why are you asking about how to flash your stock firmware, that's what you already did isn't it?
As for the unbrick.img, you need an unbrick.img pulled from a working device with your model number and your same stock android version (4.4.2), then there is a method for using that unbrick.img to boot from sdcard.
This information is here at XDA in the Verizon S3 forum if you take the time to look.
If you don't have sense enough to research your device model before you flash anything custom or if you don't know what you're doing and how to fix things when they go wrong then you should leave your device alone because flying by the seat of your pants and just assuming you can flash whatever you want is only going to cost you a lot of money in the end. You're lucky you didn't hard brick your device, that can't be fixed even by Samsung, if you had done your research you would know that. I suggest you stop where you are and start reading everything you can about the Verizon S3 i535 and what you can and can't do with it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE

Downgrade from 7.0 nogat and get Root to 5.1.1

First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.

Sharjeel.Khan said:
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Click to expand...
Click to collapse
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.

MrMike2182 said:
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
Click to expand...
Click to collapse
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.

Sharjeel.Khan said:
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Click to expand...
Click to collapse
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.. I've included in the file the eng kernel and eng sboot but there's different versions so this one in my file called boot.tar is from the eng kernel to the S6 G925V so if you're using G920V you need to get the eng kernel for that one.. Now first you put the phone into download mode and flash the eng kernel using odin and after the phone boots then using Windows command prompt navigate using the cd command to where the file is you downloaded called S6rootbyMrMike2182 once you're in there type installroot and the script should run and flash everything needed including busybox and then the phone will reboot (it will also boot just this one time without using the rootatboot because the same codes in this file too) now when you click on the SuperSU app it's going to say it needs to update su ignore it and go right to the play store and install/update the SuperSU from there and then the phone should be rooted and ready to go.. If you ever need to reboot for some reason connect the phone to your PC and open a command prompt in the same folder again and run rootatboot and it will set the phone as permissive again so it boots.. You can unplug it after you see the Verizon logo.. If for some reason you aren't near a computer and you really need to reboot then use terminal emulator from the play store and open it and type su and grant root access and then on the next line type pkill zygote and voila reboots without a computer
If you have KingRoot on your phone and you want to get rid of it to use SuperSU thanks to @Chainfire then use this script that I'm listing below.. Also keep terminal emulator open while you are doing this because you might(not all devices just some) get a continuous annoying popup that prevents you from doing anything (thanks to KingRoots junk) so you'll have to use terminal emulator to kill/end that process in order to continue and after you kill/end that process then go delete it immediately! Links to root with SuperSU and KingRoot removal are below!
S6EdgeRootByMrMike2182
KingRoot removal script
G920V ENG Sboot
By the way I nor XDA-DEVELOPERS is responsible for anything you choose to do to your phone! If something goes wrong, just reflash your original firmware but don't go blaming me nor XDA because I don't have to put this up so please do your research before messing with your phone and as always, make a backup of everything you wish to keep! And no this will not delete or wipe your phone unless you choose to! Links are above. You can change it or whatever just give props where it's due!!
SERIOUSLY MAKE A BACKUP OF ALL YOUR PICTURES ETC ETC BEFORE DOWNGRADING AND I'M NOT KIDDING!!!

MrMike2182 said:
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.....
Click to expand...
Click to collapse
great. you completed the thread :highfive:
Didn't know about script removing kr.. wil give it a try for sure. :good:

ok i'm getting confuse here. can you please provide exact files that needed to flash on g920V please ? i mean eng kernel and sboot ? and the file with odin says "G920A_Kernel_Root_5.1.1_S****.tar", A ? isn't A refers to at & t ?
i'm afraid if i may flash wrong file. can you please help me here with exact files needed for us (G920v) ?
and when i'm running installroot via cmd, it execute it goes like it created by you until daemon started successfully for like for five to 8 sec and then disappear. phone doesn't reboot. nothing happens. ,

can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks

Sharjeel.Khan said:
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrade to BOK7), then flash BOK7.
Click to expand...
Click to collapse
Muhammad Aliyan said:
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Click to expand...
Click to collapse
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.

Sharjeel.Khan said:
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Click to expand...
Click to collapse
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?

Muhammad Aliyan said:
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Click to expand...
Click to collapse
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:

Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)

LuisElListo said:
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
Click to expand...
Click to collapse
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.

Sharjeel.Khan said:
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Click to expand...
Click to collapse
So close, well better wait to safe method in stock room, or unlock bootloader. Thanks anyway.

Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..

Muhammad Aliyan said:
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Click to expand...
Click to collapse
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.

Sharjeel.Khan said:
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Click to expand...
Click to collapse
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.

LuisElListo said:
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
Click to expand...
Click to collapse
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.

Sharjeel.Khan said:
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Click to expand...
Click to collapse
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960

LuisElListo said:
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.

Sharjeel.Khan said:
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Click to expand...
Click to collapse
I try a shoot.
Its working, its ****ing working, I sacrifices FP, and Supersu but I dont mind i have xposed and a root.
imgur(dot)com/a/zLvrD
Edit1: bad news activated module xposed requeried reboot, soo the root is lost and requiered to root again with kingroot the problem is my percent is not advance 01%. Also every time I rooted the phone is slowing arriving a point where it restarted alone and is only 01%.
If i a factoy reset i lost xposed and root or better reflash the Rom OK7?

Already rooted Samsung J5 - general inquiry

Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.

luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn

ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.

ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?

luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.

luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.

Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.

luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.

luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/

-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.

luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.

luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.

luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?

Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .

luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I need to edit build.prop file on my J3 without root. Is it possible?

Hello team. I need to edit build.prop file on my J3 but I cannot root.
My understanding is that this is possible using custom recovery, just mount the system partition and push and pull the file file with adb. The problem is my handset (SM-J330FN) is running Android 8, and I think only custom recovery exists for Android 7. I tried installing the TWRP I found for Android 7, but the phone just boot loops, get stuck at Samsung logo and reboot. Don't think I can use this Android 7 TWRP with Android 8.
So next plan, I tried to wipe and install Android 7 firmware instead, but Odin said no. I take UK BTU firmware from updato.com the same way I do with Android 8 but it gets to the first stage and Odin says FAIL!
Can anyone provide a suggestion for how I can edit build.prop without root? I don't care how - maybe I can find a custom recovery for Android 8, maybe someone can help with why I can't install the Android 7 firmware, maybe someone knows of a way I can do a 1 time boot to recovery image (have used "fastboot reboot recovery.img" in the past but am aware that Samsung bootloader does not support fastboot). Maybe I can do it with root and remove the root after? Root needs to be not detected so I can use certain tools.
Any advice hugely appreciated

marshedpotato said:
Hello team. I need to edit build.prop file on my J3 but I cannot root.
My understanding is that this is possible using custom recovery, just mount the system partition and push and pull the file file with adb. The problem is my handset (SM-J330FN) is running Android 8, and I think only custom recovery exists for Android 7. I tried installing the TWRP I found for Android 7, but the phone just boot loops, get stuck at Samsung logo and reboot. Don't think I can use this Android 7 TWRP with Android 8.
So next plan, I tried to wipe and install Android 7 firmware instead, but Odin said no. I take UK BTU firmware from updato.com the same way I do with Android 8 but it gets to the first stage and Odin says FAIL!
Can anyone provide a suggestion for how I can edit build.prop without root? I don't care how - maybe I can find a custom recovery for Android 8, maybe someone can help with why I can't install the Android 7 firmware, maybe someone knows of a way I can do a 1 time boot to recovery image (have used "fastboot reboot recovery.img" in the past but am aware that Samsung bootloader does not support fastboot). Maybe I can do it with root and remove the root after? Root needs to be not detected so I can use certain tools.
Any advice hugely appreciated
Click to expand...
Click to collapse
You obviously ignored my reply I gave you yesterday.
As I already stated TWRP fully supports your device on Oreo.
Your issue is not reading the thread properly.
All you need to do is explained in the TWRP OP.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056

ashyx said:
You obviously ignored my reply I gave you yesterday.
As I already stated TWRP fully supports your device on Oreo.
Your issue is not reading the thread properly.
All you need to do is explained in the TWRP OP.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056
Click to expand...
Click to collapse
Hello, if you look at the times you will see that i made this post before I commented on yours!
I did not ignore your message, I just had not seen it yet.
As it turns out, you were right - I just tried again, taking extra care to follow instructions exactly and this time it works.
Leaves me with mixed feelings, because I am really grateful for the great development work you have done to help people like me, but also the way you are speaking to me above was a bit rude and I do not deserve that just for a small mistake. I was polite.
Thank you regardless.

marshedpotato said:
Hello, if you look at the times you will see that i made this post before I commented on yours!
I did not ignore your message, I just had not seen it yet.
As it turns out, you were right - I just tried again, taking extra care to follow instructions exactly and this time it works.
Leaves me with mixed feelings, because I am really grateful for the great development work you have done to help people like me, but also the way you are speaking to me above was a bit rude and I do not deserve that just for a small mistake. I was polite.
Thank you regardless.
Click to expand...
Click to collapse
There's a difference between being rude and being direct.
I am the latter.
Nothing personal was included in my reply nor was it intended to be.
You're upset, but I also get upset when people cannot seem to take the time to read the descriptive instructions I've included in my posts.
Trust me, it takes far longer for me to create this stuff than for yourself or anyone else to read and apply the instructions.
Don't be offended it's just frustration from my end manifesting itself in my posts.

Need help! Touch Screen not working.

I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.

It seems most phones shipping with android 10 lose touch response in TWRP. Yes you don't have TWRP but I think you're seeing the same behavior.
Plug in a USB c mouse and navigate with that should help you restore normal use.

try this thread https://forum.xda-developers.com/t/stock-rom-for-motorola-g-stylus-retail.4104451/

tatsunn said:
I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
Click to expand...
Click to collapse
Where did you get the boot.img? The non functional touch screen usually means the ROM version the boot.img came from doesn't match the version of the ROM running on the phone.
EDIT - Whoops, didn't notice the age of the post. Didn't mean to bring this back from the dead.