Anyone have success installing CleanROM (or other) on 4.3? - Verizon Samsung Galaxy S III

Looks like the CleanROM thread is closed and therefore I can't ask questions there. I'm going to take a risk and ask here:
After installing CleanRom I began the boot process but it get's stuck on the screen that says Samsung and the blue LED is on. Have to remove battery to reboot back into Safestrap and activate the stock rom and boot into that.
At this point I think I should be asking a different question. Is there a noob tutorial/guide that takes someone with no knowledge through all the steps? I read so many things and everywhere I go I keep finding that our particular Galaxy s3 from Verizon is so specific and can only use certain tools.
To anyone who's willing to help me, this is what I've done so far:
1. I flashed the baseband (modem?) from VRUCNC1 to VRUCML1
2. Rooted with Towelroot
3. Installed Safestrap
4. Reboot into Safestrap.
5. Create ROM-Slot-1
6. Wipe ROM-Slot-1
7. Installed CleanROM-8.2 on ROM-Slot-1
8. Reboot into system. (This is where it get stuck on the Samsung logo and black screen)
I didn't do anything with firmware. I don't even know which firmware I have. But I did download d2vzw_VRBMF1_firmware.zip
Any help would be appreciated. Thanks!

Related

Rooting the Verizon GS3 - Questions

I am preparing to root my Verizon GS3. The process looks pretty simple, but I still have a few questions I would like to have cleared up first just to make sure everything goes to plan.
I have downloaded the following files as instructed to in one of the threads on how to ROOT the GS3:
- USB Drivers
- Odin (unzipped with Winzip)
- Stock rooted system image (mirror link)
- CWM
My first question is whether or not I am supposed to unzip the stock rooted system image. The post says I should have a file named "rooted.system.img.tar" to select in the PDA section of ODIN, but the name of the file I have is just "rooted.system.img."
The second question I have is which custom recovery should I choose? I downloaded both, but don't know if one is better than the other or if it just comes down to personal preference. Also, do I need to unzip either one of those files? And if I choose not to push a recovery now, can I push it later if needed to flash a new ROM that I like. I ask this because the only real reason I want to root right now is to disable the ridiculous wifi notification in the notification bar and the pop up that you get when opening a "high data usage application."
Another concern I have is returning to stock. On my DROID X2, all I had to do was use RSD Lite and flash back to stock. I have downloaded the stock kernel and stock ROM off of one of the threads on here (I can't find it for some reason), but was just wondering how I would go about using that to get back to the way it was out of the box.
Thanks for the help!
Edit: As far as the first question goes, I selected the rooted.system.img in ODIN and it shows it as rooted.system.image.tar at the end, so I'm guessing no unzipping for that file is necessary, correct?
Don't unzip that tar you are good with that system image. Install the usb drivers and put your phone into download mode. Start Odin then set that to pda plug in your phone and wait for the drivers to install correctly. Remember you should have a full battery before flashing. Browse to your image then flash the system image, it might take a while to flash so be patient and don't move the computer or phone.
Just pick the recovery you like they are really up to personal preference. I like cwm because I used it in my og droid and dinc. You can always change recoveries in the future if you find a different one you like more.
You don't need to install cwm in the old way, just download it from the play store after you are rooted. When you install the recovery from the app choose Verizon galaxy s3 from the list. It will ask for root before trying to install cwm recovery. When you install cwn it will make your phone say custom when you boot up so if you don't want that skip the recovery for now.
I have never returned a phone to stock but I think to return to stock flash the stock Verizon image with Odin.
Down with Verizon for locking my bootloader
manchild83 said:
Don't unzip that tar you are good with that system image. Install the usb drivers and put your phone into download mode. Start Odin then set that to pda plug in your phone and wait for the drivers to install correctly. Remember you should have a full battery before flashing. Browse to your image then flash the system image, it might take a while to flash so be patient and don't move the computer or phone.
Just pick the recovery you like they are really up to personal preference. I like cwm because I used it in my og droid and dinc. You can always change recoveries in the future if you find a different one you like more.
You don't need to install cwm in the old way, just download it from the play store after you are rooted. When you install the recovery from the app choose Verizon galaxy s3 from the list. It will ask for root before trying to install cwm recovery. When you install cwn it will make your phone say custom when you boot up so if you don't want that skip the recovery for now.
I have never returned a phone to stock but I think to return to stock flash the stock Verizon image with Odin.
Down with Verizon for locking my bootloader
Click to expand...
Click to collapse
Sorry for the late reply. I went out to eat with the fam.
Thanks for clearing that stuff up for me! Can't wait to root my GS3 in 7 days after my return policy is used up!
Thanks again!
You're welcome good luck with the phone.
Down with Verizon for locking my bootloader
So I am officially getting ready to ROOT my GS3. Is there anything I need to do to prepare for the process? I have seen people say you need to enable any of the bloat you have disabled and I have also seen wiping the cache thrown around a few times, so I would just like to know if there is anything along those lines that I need to do before I start.
DROIDLOVERX2 said:
So I am officially getting ready to ROOT my GS3. Is there anything I need to do to prepare for the process? I have seen people say you need to enable any of the bloat you have disabled and I have also seen wiping the cache thrown around a few times, so I would just like to know if there is anything along those lines that I need to do before I start.
Click to expand...
Click to collapse
I'd follow this to root. Don't need to do anything else but what it says there.

Full on Noob, need help if possible.

Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:
I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9
Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:
Goodluck! :laugh: :good:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt

[Completed] S3 ATT Like to know how to unlock bootloader, root the phone, and install custom ROM

Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Hi
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I would invite you to post your request in the below forum as our team mates there should be able to help you:
AT&T Galaxy S III Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Click to expand...
Click to collapse

[HELP THREAD] Ask any questions [NOOB FRIENDLY]

Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!​
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Going back versions?
Ok, I'm pretty good on flashing ROMs and using TWRP. But I was thinking of trying a 5.1.1 Rom, I am rooted running just the stock Rom 6.01 currently. I have a SM-N900W8, so I assume I'll likely have to get the modem too depending on what ROM I choose.
My only concern is going backward, I don't know what kernel I might need to flash? Should be able to keep the answer simplistic in explanation, I just need the warnings and a basic checklist of what to do when going backward. And if I can complete this using just TWRP or whether I need to flash something with Odin or whether Flashfire might work.
Thanks in advance. Sorry I'm not a guy who has time to learn code. I try to donate if I'm going to use someone's work though. Just nice to have my phone run fast and smooth and be able to tinker...
Jetmerritt said:
Ok, I'm pretty good on flashing ROMs and using TWRP. But I was thinking of trying a 5.1.1 Rom, I am rooted running just the stock Rom 6.01 currently. I have a SM-N900W8, so I assume I'll likely have to get the modem too depending on what ROM I choose.
My only concern is going backward, I don't know what kernel I might need to flash? Should be able to keep the answer simplistic in explanation, I just need the warnings and a basic checklist of what to do when going backward. And if I can complete this using just TWRP or whether I need to flash something with Odin or whether Flashfire might work.
Thanks in advance. Sorry I'm not a guy who has time to learn code. I try to donate if I'm going to use someone's work though. Just nice to have my phone run fast and smooth and be able to tinker...
Click to expand...
Click to collapse
Hi
What do you mean by 'going backward'? Do you wanna downgrade your device from Marshmallow to Lollipop? If yes, refer to this thread.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Ok, if going back to a earlier version of Android, then flash the factory full ROM of that version through Odin, then flash custom ROM of same version. Got it, thanks. Sounds like the easiest way.
Jetmerritt said:
Ok, if going back to a earlier version of Android, then flash the factory full ROM of that version through Odin, then flash custom ROM of same version. Got it, thanks. Sounds like the easiest way.
Click to expand...
Click to collapse
Yeah. Welcome!
Regards,
PoseidonKing
Stuck N915G
Am using a N915G , it was rooted with CW recovery , since yesterday it would go in restart loop , so i went into recovery and did a reset , still the loop would not go , so i took into a service center they tries kies and it would intall lollipop but half way through it will show " erasing " and then go back to boot loop , now at this point when i re checked the phone there is no CW recovery , so i tried Odin with Marshmallow to flash the system , it shows PASS but during installation " System updating .. erasing " then goes back to reboot so i flashed new set of Pit files , but still the phone stays in boot loop , vibrates then goes off to loop , what am i doing wrong
Won't power on after normal power off.
Hi,
i mean; when i turn of the phone with normal shutdown menu, device power off normally.
But when i attempt to turn on device again, it won't turn on. nothing happens when i press or hold the power button.
only the way to turn on again, "plug a charge cable or usb cable"
after it detects the charge, and shows charging. after then i can turn on the device normal.
but, not possible to turn on without plug the cable once.
so; what can be my device's problem. (there is no another problem) except fast battery drain.
my opinion; humidity damage? or something like that.?
can any oxidation causes this problem?
please reply for help.
thanks.
Bump
Sent from my Motorola XT1080 using XDA Labs
Hello, I rooted my Samsung Galaxy Note Edge (N915T) Tmobile way back in 2014, I have since then forgot how to root again. I know that my phone is still rooted because I have SU.
My phone specs right now:
Bootloader: N915TUVU1ANJL
OS Version: KitKat 4.4.4
CPU: ARMv7-A (armeabi-v7a)
Kernel version: 3.10.0-2990579
I saw a post here in XDA about new Custom ROM (7.1.2 AOKP Nougat) and I would like to install custom ROM, and reading the instructions it states that it requires Bootloader 6.0.1 and Modem. I have no idea how to install bootloader and modem up to 6.0.1 on my phone. Kindly please guide me how to identify my current bootloader and how to upgrade up to 6.0.1. Thanks!
Hello,
I am using Odin v3.12.7 and I tried to select (twrp-3.0.2-0-tbltetmo.img) from Odin, but is not selectable because it does not have (.md5) or (.tar), where can I find a TWRP in those file formats?
What custom rom can i flush with my note edge sc-01g docomo japan,
Corrupt microsdcard and otg devices
Hi,
This is about my note edge N915G and what will follow has strangely happened with every kind of rom for the device stock rooted, aokp, customized stock, and slimroms.
What happens is
scard shows as corrupted after busybox/magisk7viper mods I mean the card is fine when I install busy box and magical and viper then in stall viper drivers and it is still good but when I reboot to activate the viper mods my card shows as corruption. I another thing that happens is when the card shows as corrupt, I I can try another card and still shows corrupt and strangely even the devices I connect through otg all show as corrupt. Ii think it is busy box which is needed for viper that does it, but am not sure.
Another guess is that maybe some embedded file on the phone has been deleted or corrupted and that is causing me the trouble. I have installed the Enhanced rom this evening and had set it up with closed root and magical. I it was all fine. I then I installed busy box using smart install and after that opened viper fx 2.5 and viper xhi=fi and each prompted to install drivers and they installed successfully and advised a reboot. It is after reboot that I opened my music player and found no songs which was be aise it is showing my card as corrupt. I strangely even if I reverse the process and uninstall viper drivers then viper apps and finally busybox it still does not change the status of the card. It is either that I install the rom again dirty or restore a system backup that was made while there were no add ons.
I would really appreciate if anyone can help figure this out as I do have the workaround of restoring system but it is tedious as I have to install all apps etc.
I would like to reiterate that this is not the kind of issue associated with Samsung phones in general where they are said to kill microsdcards. This is not the case and the card works flawlessly in a different phone which I did to check. My laptop too has no issues with same card it is a Samsung evo 64 gb card I'm using. Maybe they key is that even other as cards whether I put them in the card slot or in a card reader for otg it shows any card I use as corrupt and even my otg drives show up as corrupt. I think it is something I have never seen happening yet.
Thanks for reading this and for your suggestions and advice. I will look forward to your thoughts and inputs, knowledge and experience.
Regards
Centaur31
anybody install android 7 on note edge ?
please describe the method
i have been tried a lot to root the device but fail with error
in my phone in the developer setting there is no OEM unlock option
in all guide mentioned to this option
my phone model is: N915F
if possible please help me
At&t Samsung Note Edge N915A 6.0.1
Hi I'm a noob. Last phone I "jailbroke" was a IPhone 3gs. Could you link me in the right direction to root my Samsung note edge from At&t 6.0.1 a list of procedures would be great, also a list of downloads. Anything & Everything I need on my phone or my Laptop to complete the process. All input would be appreciated. I just paid a large chunk of $ to Samsung to have my screen replaced and I am the original owner of my device which I paid a lot of money for in 2014, so I would hate to brick my device. Thanks
Hello
I have Samsung Galaxy Note edge n915F and i want to to flash n915g stock rom in it
is it possible. .?
Or if possible any problem will occur. .?
Thanx in advance

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

Categories

Resources