Anyone there who could help... I've been get hype when i receive my first android device (galaxy tab P6200) so i search for tutorial on how to root and flash new firmawre.. i did everything in the tutorial but suddenly.. odin has stop working. when i boot my P6200 it turns out to be softbrick.. sorry i'am kinda new on android scene i've been on ios scene before o didn't think it would be harder to find a solution on android... ive spent 2 straight days finding downloading firmware ive even search xda for this matter but no luck... i can still access download mode but odin and Heimdall still give me such error that prevents me to fix my device... i'am kinda losing hope so i try to post here to see if its still a chance for me to recover my softbrick device... hope someone could help... insanely beggin....:crying:
userpjay said:
Anyone there who could help... I've been get hype when i receive my first android device (galaxy tab P6200) so i search for tutorial on how to root and flash new firmawre.. i did everything in the tutorial but suddenly.. odin has stop working. when i boot my P6200 it turns out to be softbrick.. sorry i'am kinda new on android scene i've been on ios scene before o didn't think it would be harder to find a solution on android... ive spent 2 straight days finding downloading firmware ive even search xda for this matter but no luck... i can still access download mode but odin and Heimdall still give me such error that prevents me to fix my device... i'am kinda losing hope so i try to post here to see if its still a chance for me to recover my softbrick device... hope someone could help... insanely beggin....:crying:
Click to expand...
Click to collapse
Need more info, exact model number firmware you were on, firmware file you were tryimg to flash, did you check, or uncheck anything in Odin? Download mode is good, you should be OK.
How do you know its softbrick? Bootloop, hang at logo? Which one?, as much data as possible will get you fixed faster.
I had same problem. You need a PIT file for p6200 and use it in odin together with the newest firmware from sammobile.com.
It works for me.
nabile said:
I had same problem. You need a PIT file for p6200 and use it in odin together with the newest firmware from sammobile.com.
It works for me.
Click to expand...
Click to collapse
I have limited knowledge on flashing, but as far as I know, If u r using a 'PIT' file, be sure to check on 'Repartition' Option in Odin (while flashing). If u Flash wid ONLY a md5 file, ensure that 'Re Partition' box is unchecked while flashing. May be u kept Repartition checked while you were not using a PIT file or vice versa.
If that is d case, try flashing again by following a correct process.
Hi, after a weekend of messing with my phone I managed to delete all my files
Plus all my backup files I have no recovery backup that's gone too, all root access has
Been Lost odin won't work supersu is asking for Binery files and won't work, I do have the latest Twerp Installed however I've got nothing to install with it and no recovery backup to install, odin won't open it says unexpected partition layout. I have a Samsung galaxy s3 GT-I9300, OH I can no longer connect to my Internet at home. Here's some more info don't know if it will help anyone who can help me.
WI-FIMAC ADDRESS 88:32:9B:63:5F:A8
SERIAL NUMBER 4df7298605262179
BASEBAND VERSION 19300XXUGMK6
KERNAL VERSION 3.0.31-2168382
BUILD NUMBER JSSISJ. 19300XXUGMK6
Any help, any ideas will be greatly appreciated
Thanks. Matt...... Newbe
delete dup post
mwelf74 said:
Hi, after a weekend of messing with my phone I managed to delete all my files
Plus all my backup files I have no recovery backup that's gone too, all root access has
Been Lost odin won't work supersu is asking for Binery files and won't work, I do have the latest Twerp Installed however I've got nothing to install with it and no recovery backup to install, odin won't open it says unexpected partition layout. I have a Samsung galaxy s3 GT-I9300, OH I can no longer connect to my Internet at home. Here's some more info don't know if it will help anyone who can help me.
WI-FIMAC ADDRESS 88:32:9B:63:5F:A8
SERIAL NUMBER 4df7298605262179
BASEBAND VERSION 19300XXUGMK6
KERNAL VERSION 3.0.31-2168382
BUILD NUMBER JSSISJ. 19300XXUGMK6
Any help, any ideas will be greatly appreciated
Thanks. Matt...... Newbe
Click to expand...
Click to collapse
try using a pit file with odin. im thinking it wouldnt have an error if you had the pit file.
to answer your question "what have i done?" it would seem, you changed things you didnt understand and didnt realize the consequences, resulting in a big @SS mess
dont do that
Like I said odin won't work because of unexpected partition layout.
I'm fully aware of the consequences however I will be the recipient
Of a Samsung galaxy note 4 next week so I was just experimenting
And I will definitely not be rooting that
mwelf74 said:
Like I said odin won't work because of unexpected partition layout.
I'm fully aware of the consequences however I will be the recipient
Of a Samsung galaxy note 4 next week so I was just experimenting
And I will definitely not be rooting that
Click to expand...
Click to collapse
ill just assume you dont know what a pit file is, and ill move on. good luck!
No need to assume, I'll be honest I've no idea what a pit file is or how to use one
Etc etc, however I'd be interested to learn if you can give me the basics, everybody has to start somewhere and the only way to progress is if people share the knowledge,
So what do you know that can help me??
mwelf74 said:
No need to assume, I'll be honest I've no idea what a pit file is or how to use one
Etc etc, however I'd be interested to learn if you can give me the basics, everybody has to start somewhere and the only way to progress is if people share the knowledge,
So what do you know that can help me??
Click to expand...
Click to collapse
go to your devices forum where the return to stock post is, and see if there is a pit file for whatever version you have. if not, try a search for pit over your general and q&a forums. im sure you will find some, just need to match them to the stock files.
on odin, there is a pit box, check it and link your pit file.
I'd just like to let you know I have managed to sort my phone out
I got a clockwork mod ,and now I'm using something called CyanogenMod
I'm not quite sure how I have managed to achieve this but I have my WiFi connected
to my phone again, Odin is installed and working with no unexpected partition layout
Problems, however my SD card won't mount and I can't seem to get Google playstore
But for now its a small price to pay considering where I was this afternoon. I think I've done well
So i'm really annoyed by 7.0 on my S6 and would like to go back to 6.0.1 um and i tried like a lot and i don't know how to go back for some stupid reason can someone help,bellow are pics of my "stuff"
Just go to sammobile, download the firmware for your device, flash said firmware through ODIN. Done.
Sent from my SM-G920W8 using Tapatalk
Are there any rules when choosing firmware ? I don't wait for a week to download wrong one Also when i tried fleshing some they either flash but no visible changes like nothing is deleted and stuff,or i get some error...
First, this is not the subforum to post these kind of questions...
Second, try here: https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/ (Your product name says SM-G920F) and download any firmware that you complies with your country/provider. The downloads are throttled as a normal (free) user, but it should not take more than 2-3 hours downloading. Flash with ODIN. Profit.
Do i put file i download in the AP part of odin,and sorry for posting in wrong place xD.
Yeah, depends on the version of Odin you have, but you can follow this tutorial (or any similar) and you should be ready to go
https://www.youtube.com/watch?v=tv0BnfpNxEs
TL;DR Yes, AP
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
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.