Database Info

[Completed] How do I unbrick my phone?

First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.

I have some good news. I managed to flash the firmware again and now I can access the phone again. However, the WiFi problem persists. I've tried looking on the internet for a solution, but I can't find one. I've tried flashing the modem and all that stuff, but it still doesn't work.
Oh, and by the way, I no longer have TWRP and I don't think I have root access anymore either (I had to do a data partition wipe as well).

I'd really appreciate a reply from someone. I've tried everything, but to no avail.

einwaliser said:
First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
Click to expand...
Click to collapse
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.

engloa said:
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
Click to expand...
Click to collapse
Hi engloa,
It's OK, I've fixed the problem now; I installed a different ROM and now it works fine. Thanks anyway though.

I think I bricked, not sure, need help. [Verizon GS3]

I think I screwed up big time.
I fist got my GS3 Verizon and rooted with Towelroot. Then I tried installing TWRP. I was unaware of the locked bootloader, and found out about SafeStrap. I never actually uninstalled TWRP. From there, I installed SafeStrap, then I tried installing CM 12.1 and I messed up. My phone won't boot up in any mode other than download mode. When I try to boot in to recovery I will get the "System Software not authorized by Verizon Wireless has been found on your phone." Message. I need to wipe and install stock ROM. Someone please help! (And if possible, maybe someone can walk me through having CM 12.1 on here? I really want it on, but I need a walkthrough)
Thanks guys!
P.S. I am running Android 4.4.2.

TacoTank said:
I think I screwed up big time.
I fist got my GS3 Verizon and rooted with Towelroot. Then I tried installing TWRP. I was unaware of the locked bootloader, and found out about SafeStrap. I never actually uninstalled TWRP. From there, I installed SafeStrap, then I tried installing CM 12.1 and I messed up. My phone won't boot up in any mode other than download mode. When I try to boot in to recovery I will get the "System Software not authorized by Verizon Wireless has been found on your phone." Message. I need to wipe and install stock ROM. Someone please help! (And if possible, maybe someone can walk me through having CM 12.1 on here? I really want it on, but I need a walkthrough)
Thanks guys!
P.S. I am running Android 4.4.2.
Click to expand...
Click to collapse
Your best bet may be using Odin to flash the stock 4.4.2 ROM.
I bought my i535 (Verizon SGS3/d2vzw) used as a device to develop modding skills. It came with the 4.4.2 rom already installed. I have learned from reading in this forum that options for you and I are very limited. Once your device is restored you can use SafeStrap but not TWRP, CWM, or Philz Recovery. There are only three roms available to us: Stock, SuperLiteRom, and PaulPizz ROM.
@ShapesBlue may have better advice, he actually used this device as a phone and has much more experience with what can be done with the i535 on the 4.4.2 bootloader (NE1)

First of all, thank you for ALL your help! I REALLY appreciate it! You are a lifesaver. Now, my question is, can I flash android 4.2 so the bootloader isn't locked? I know I am being a little picky, but this is the ONLY reason I bought it. But I was thinking, put my phone in download mode, flash 4.2 > root > install TWRP > wipe > Flash CM12.1 > and voila! Would that work, and if so, could you help?

TacoTank said:
First of all, thank you for ALL your help! I REALLY appreciate it! You are a lifesaver. Now, my question is, can I flash android 4.2 so the bootloader isn't locked? I know I am being a little picky, but this is the ONLY reason I bought it. But I was thinking, put my phone in download mode, flash 4.2 > root > install TWRP > wipe > Flash CM12.1 > and voila! Would that work, and if so, could you help?
Click to expand...
Click to collapse
Everything I have read indicates that we are stuck at 4.4.2 and can not downgrade. I didn't read the forums before purchasing mine and have not seen anything saying anyone has safely downgraded, or used any rom other than the three I mentioned.
I guess we could wish for Verizon to release a security update because of stagefright issues. I can dream, but I'm not holding my breath.

Okay, guys, I am starting to lose it.
I am having 0 luck fixing this damn thing. I have tried flshing every android version that exists for this phone and it won't work at all. KIES won't recognize so I used ODIN. ODIN never feels like working so IDK what to do. I used Safestrap to try and install CM 12.1, but it was stuck in a boot cycle, and since I had to use the Safestrap app to launch recovery, I am screwed. There is no way for me to get into my phone, I only have download mode, I need some help guys. What can I do!?!?! I just want anything that will work at this point. Even if I can't get CM12. I think I want to get android working on it and sell it. Pls help!!!

TacoTank said:
Okay, guys, I am starting to lose it.
I am having 0 luck fixing this damn thing. I have tried flshing every android version that exists for this phone and it won't work at all. KIES won't recognize so I used ODIN. ODIN never feels like working so IDK what to do. I used Safestrap to try and install CM 12.1, but it was stuck in a boot cycle, and since I had to use the Safestrap app to launch recovery, I am screwed. There is no way for me to get into my phone, I only have download mode, I need some help guys. What can I do!?!?! I just want anything that will work at this point. Even if I can't get CM12. I think I want to get android working on it and sell it. Pls help!!!
Click to expand...
Click to collapse
If your device was ever on 4.4.2 you may as well give up on the idea of installing CM 12.1, or any ROM other than the three I mentioned. (If you have found something stating differently please share.)
Some of these threads may be of help:
[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
[GUIDE][ML1/NC1/NE1] TW 4.4 and 4.3 Sticky Roll-Up Thread (7-10-14)
[INDEX] TW 4.4 Download List (7-10-14)
That last one is a bit dated but still worthwhile. The second is not quite as dated. The first may be what helps you.

So, I need like, a tutorial or a link on how to fix this. I want to fix my recovery as well if that's possible. Just so I can have stock recovery. If I flash Android 4.4.2 it should fix that though. Plus, a working download link would be MUCH appreciated.

Alright. So, I followed the instructions on this http://forum.xda-developers.com/showthread.php?t=2581166&nocache=1 and had no luck, when I flash on ODIN, it gets the error when flashing the "aboot". That's when it fails. Any suggestions? I tried deleting it, but 7zip won't let me.

TacoTank said:
Alright. So, I followed the instructions on this http://forum.xda-developers.com/showthread.php?t=2581166&nocache=1 and had no luck, when I flash on ODIN, it gets the error when flashing the "aboot". That's when it fails. Any suggestions? I tried deleting it, but 7zip won't let me.
Click to expand...
Click to collapse
Odin gives an error at that point when you are trying to flash an incompatible bootloader. If you used any rom with a bootloader older than 4.4.2 (NE1) it prevents you from flashing to avoid a bricked device.
Which image did you use from the site you linked?
None of the images from the OP of that thread are for flashing with Odin. They are to burn to an external micro sdcard from which you boot the device and then restore your bootloader, and recovery if necessary.
Please detail the exact steps you performed.

Oh, I flashed an image from something else, my bad on that one. Uh, so I tried putting that thing on my SD card with Win32DiskImager, and every time I do it, after multiple writes and phone boot-ups, I had no luck. It always tells me "Firmware upgrade encountered an error. Please use Software Repair Assistant & try again." So, I don't know what to do. Ad I also wanted to thank you for your speedy replies, I know mine are always delayed, I have finals and stuff, it's hectic. But, I need my phone back already so I'll jump back to reply ASAP! Thanks!

TacoTank said:
Oh, I flashed an image from something else, my bad on that one. Uh, so I tried putting that thing on my SD card with Win32DiskImager, and every time I do it, after multiple writes and phone boot-ups, I had no luck. It always tells me "Firmware upgrade encountered an error. Please use Software Repair Assistant & try again." So, I don't know what to do. Ad I also wanted to thank you for your speedy replies, I know mine are always delayed, I have finals and stuff, it's hectic. But, I need my phone back already so I'll jump back to reply ASAP! Thanks!
Click to expand...
Click to collapse
I am not in the least familiar with "Software Repair Assistant." I do know it is a Verizon process. You can give it a try if you wish.
Other than that you are back to the debrick image process. That process can take a number of attempts. You should use either a 16 or 32 GB class 10 card. It sometimes works with a slower card, but best bet is with a class 10. It would be an oddity for something samller than 16 GB to work. Also, you may need to try several cards. A card that works for this in one phone at times does not work in a different SGS3.

Alright, here's what I just did. I needed a new SD Card anyay so I bought a Kingston Digital 16 GB microSDHC Class 10 UHS-1 Memory Card 30MB/s with Adapter (SDC10/16GB) off of Amazon and it should be here by Thursday. And then, I'll tell you how things go. I am praying this works, because, even though I am getting a HTC One M9 (I'd like your thought on that, if you think it's a good phone to run CM 12.1 off of) I need a phone for now.

TacoTank said:
Alright, here's what I just did. I needed a new SD Card anyay so I bought a Kingston Digital 16 GB microSDHC Class 10 UHS-1 Memory Card 30MB/s with Adapter (SDC10/16GB) off of Amazon and it should be here by Thursday. And then, I'll tell you how things go. I am praying this works, because, even though I am getting a HTC One M9 (I'd like your thought on that, if you think it's a good phone to run CM 12.1 off of) I need a phone for now.
Click to expand...
Click to collapse
A quick check at the VZW development thread for the M9 shows they have root and custom recoveries. A quick glance at a number of the custom ROMs their had all of them based on stock, either saying stock or sense.
Another check at CM shoes development open for the himaul HTC One M9. I don't know which carrier that is for, but it is a GSM device instead of cdma. The AT&T M9 is code named hima so I am not convinced it is theirs.
Otherwise, I don't know much about the M9 outside of what I see in the reviews. Being that my daily driver is still my SGS3, I would think I would be satisfied with the M9 performance.

Well, I am screwed. I tried using my 16GB SD and it didn't work. I did everything right, I don't know what to do. I kinda think flashing something via ODIN would work, but I don't know what to flash. Help?

TacoTank said:
Well, I am screwed. I tried using my 16GB SD and it didn't work. I did everything right, I don't know what to do. I kinda think flashing something via ODIN would work, but I don't know what to flash. Help?
Click to expand...
Click to collapse
From what I have read in the debrick threads, you may have to try several cards to find one that works in your phone. Also, it is 16 and 32 Gb class 10/U1 cards that are most likely to work.

So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?

TacoTank said:
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
Click to expand...
Click to collapse
I don't recall seeing anyone report attempting to do this with a 64GB card, not to say it wouldn't work, I just haven't seen anyone saying they tried one.

TacoTank said:
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
Click to expand...
Click to collapse
dawgdoc said:
I don't recall seeing anyone report attempting to do this with a 64GB card, not to say it wouldn't work, I just haven't seen anyone saying they tried one.
Click to expand...
Click to collapse
You may just need a SanDisk version versus the Samsung one. I have ran across threads with people having success with them. Definitely try a 32gb sd card as dawgdoc suggested
Nexus 6 running SSHD or Cataclysm

http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Sent from my Nexus 5 using Tapatalk

Please what's the confirmed rooting method for Samsung galaxy s3 Verizon i-535 running 4.4.2 I tried rooting with towelroot & kingroot, also flashed cwm recovery from rom manager respectively then rebooted to recovery but got black screen with yellow triangle error. I have a friend at the Samsung store in bestbuy that have reflashed the phone twice & is still willing to restore the phone again but I wanna know the working root method for this device without screwing up recovery?

[Completed] Currently panicking: root gone wrong

First of all, sorry if I am posting this in the wrong thread or wrong area.
I'm seriously depressed and deprived of sleep because I finally rooted my phone and everything went wrong.
Yeah, I fell in with that crowd. Shame on me, i know ,_,
Samsung Galaxy Note 3 SM-N900W8 is the victim. I downloaded CF AUTO ROOT HLTECAN HLTEUB SMN900W8 which, apparently, should have had no problem. Used Odin 3.07 on my laptop and the process was smooth and quick. Buuuut of course my phone got mostly wiped (no surprise here, totally worth the root). Along with that wipe came the rage of Google and Samsung.. don't know why but most apps just force close when I try to open them.
Long-story short I need to regain access to my Google account, my messages (so I can, you know, message my grandmother so she can pick me up at the university) and the ability to have a functional good phone.
I've learned my lesson, I'm leaving this rooting stuff to the more apt. However I need guidance on how to what I believe is called "flash" the system back into having all the permissions it used to have. Not sure what I'm talking about any more.
If it is possible to keep the root and somehow fix the problem (regain access to basic services such as messages and play store) that'd be nice. But really, I just wanna travel back in time and forget this ever happened so late at night that it's almost morning and my feelings are extra hurt.

Hello Dear ,
Its ok just re install the official rom for ur device n900w8 after that just do a full for ur device through stock recovery then install twrp through odin in AP tap from this link
https://twrp.me/devices/samsunggalaxynote3canada.html
After that boot ur phone to custom recovery then install supersu from this link
https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
That's all for rooting ur device mate
Thank You ,

Thanks for the help! But I'm still a bit lost. I did as you suggested and found the 5.0 stock firmware, which I am currently downloading. I will open Odin, plug in my phone, put the firmware file in the AP slot and install it from the download screen on my phone. Same process as the rooting that failed earlier.
However, I don't get the TWRP part.
"after that just do a full for ur device through stock recovery then install twrp through odin in AP tap from this link"
Is that step necessary, or is it just in case I want to try rooting my device again? Also, in the list you provided doesn't seem to be 5.0/lollipop for the phone. But then again, I'm not entirely sure how all that works.
Thanks again!

Installing the Stock firmware did not work. Once the phone boots, everything stops working unexpectedly.
Oh well, I guess it's time to take it to a store ,_,
Thanks anyways!

I am in utter shock. For some strange reason, factory reset worked and my phonne is ok. Not sure how... but it actually worked!

Nice to hear that mate congrats then

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

(HELP!) Phone Stuck In TWRP

Hello,
the long and short of it is that I tried to root my phone and then install Lineage, but ended up with no OS and now I can't use my phone. I simply want any OS so that I can use my phone. Any help would be greatly appreciated. I am a bit new to this kind of stuff, so I apologize in advance if I don't know some of the technical terms.
I am using a Samsung Galaxy S7 SM-930W8.
A bit more in detail:
I used two videos on youtube. 1 to teach my how to root, which got me into an OS. Then I used a video to teach me how to install Lineage, and that's when it all failed. After this, my phone was stuck in a never-ending loop of a circle going across a line and it never recovered.
I still have access to the TWRP when I hold down Vol-Up, Power and Home but when I try to reboot, it tells me there is no OS installed. I can't even use the recovery option, since I believe I deleted all the previously installed recoveries.
I feel silly for being in this predicament, but I would be so grateful for any help, folks!
-New2S7

New2S7 said:
Hello,
the long and short of it is that I tried to root my phone and then install Lineage, but ended up with no OS and now I can't use my phone. I simply want any OS so that I can use my phone. Any help would be greatly appreciated. I am a bit new to this kind of stuff, so I apologize in advance if I don't know some of the technical terms.
I am using a Samsung Galaxy S7 SM-930W8.
A bit more in detail:
I used two videos on youtube. 1 to teach my how to root, which got me into an OS. Then I used a video to teach me how to install Lineage, and that's when it all failed. After this, my phone was stuck in a never-ending loop of a circle going across a line and it never recovered.
I still have access to the TWRP when I hold down Vol-Up, Power and Home but when I try to reboot, it tells me there is no OS installed. I can't even use the recovery option, since I believe I deleted all the previously installed recoveries.
I feel silly for being in this predicament, but I would be so grateful for any help, folks!
-New2S7
Click to expand...
Click to collapse
Hello, no need to panic, the blue circle over the line was Lineage first boot up, it can take 10-15 mniutes on the first time. If you waited longer than this then maybe there was a problem.
If the Lineage ROM is on your SD card you can try to flash it again and see if it boots this time, sometimes it needs to be flashed twice to work. You must make sure it's the right one for your device.
If it still doesnt work then you will need to flash the stock firmware back to your device with ODIN. This is the firmware for your device >>>>HERE<<< Pick your network provider or an "unknown" version which is unbranded stock firmware. The download is a little slow but it's free.
There's lots of guides how to flash firmware with Odin, it's very easy.
I forgot to mention TWRP is a much better Recovery Option so yes when you instal TWRP the stock recovery won't boot.

cooltt said:
Hello, no need to panic, the blue circle over the line was Lineage first boot up, it can take 10-15 mniutes on the first time. If you waited longer than this then maybe there was a problem.
If the Lineage ROM is on your SD card you can try to flash it again and see if it boots this time, sometimes it needs to be flashed twice to work. You must make sure it's the right one for your device.
If it still doesnt work then you will need to flash the stock firmware back to your device with ODIN. This is the firmware for your device. Pick your network provider or an "unknown" version which is unbranded stock firmware. The download is a little slow but it's free.
There's lots of guides how to flash firmware with Odin, it's very easy.
I forgot to mention TWRP is a much better Recovery Option so yes when you instal TWRP the stock recovery won't boot.
Click to expand...
Click to collapse
Hello cooltt,
I was able to fix my problem an hour or so ago, but thank you for your calming post anyway.
For future threads, here is what I did:
1. I downloaded a stock OS and then extracted all the md5 files. (There is an md5 file for the "BL", "AP", "CP" and "CSC" fields in Odin.)
2. I then used Odin and after it detected my device, I plugged the 4 files in the appropriate fields.
3. I then hit start and it restored my phone back to a functional state.
Though I spent the last 20ish hours in a panic, I actually managed to achieve the goals that prompted me to try and install a custom rom: fewer stock apps and no Samsun Account bothering me all the time.
Thank you all for your concern.
-New2S7
(P.S. I do not know how to mark this as solved. If an admin comes across this, please mark this as solved!)