I know this is not the best way to do so but I successfully got my G850A AT&T variant rooted using Kingroot 4.8.0.
Also when I boot up the phone, the lock icon turned into an open lock icon with the text "custom." Does that mean my bootloader has been unlocked?
I would like to install custom ROMs but had no luck installing twrp. Any ideas? I can try anything since this is a dead phone to me anyway.
If it is true, try SLTECAN twrp
echo124 said:
If it is true, try SLTECAN twrp
Click to expand...
Click to collapse
That didn't work out. "SECURE DOWNLOAD" is enabled in download mode and when I try to flash the recovery it tells me "check fail: recovery." I guess the bootloader is still locked. Is there any way I could still install a custom ROM? Root is working fine.
Try install flashify app then try twrp with it
echo124 said:
Try install flashify app then try twrp with it
Click to expand...
Click to collapse
There's no recovery image for it. The SLTECAN is only flashable via Odin which is not possible with the G850A.
Although I think we could get custom ROMs using Flash Fire if someone can port the ROMs to 850A. See: http://forum.xda-developers.com//at...tmas-heres-t3516196/post70011921#post70011921
You can create .img from tar or .tar from .img
Open tar.md5 with 7zip, extract .img to phone and use flashify, tell us if worked
Everyone thumbs up the post
vadosnake said:
I know this is not the best way to do so but I successfully got my G850A AT&T variant rooted using Kingroot 4.8.0.
Also when I boot up the phone, the lock icon turned into an open lock icon with the text "custom." Does that mean my bootloader has been unlocked?
I would like to install custom ROMs but had no luck installing twrp. Any ideas? I can try anything since this is a dead phone to me anyway.
Click to expand...
Click to collapse
This works on Lollipop too ?
---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------
echo124 said:
You can create .img from tar or .tar from .img
Open tar.md5 with 7zip, extract .img to phone and use flashify, tell us if worked
Click to expand...
Click to collapse
Flashing 850W TWRP soft-bricks the device with the message "System software not authorized by Verizon Wireless has been on the device ..." blah blah blah. I think a Safestrap recovery is better suited for this phone.
vadosnake said:
I know this is not the best way to do so but I successfully got my G850A AT&T variant rooted using Kingroot 4.8.0.
Also when I boot up the phone, the lock icon turned into an open lock icon with the text "custom." Does that mean my bootloader has been unlocked?
I would like to install custom ROMs but had no luck installing twrp. Any ideas? I can try anything since this is a dead phone to me anyway.
Click to expand...
Click to collapse
Can you give us a tutorial guide on how to do it. Most of us (including me) have tried the version of king root that your using and it fails to root.
However, you have given us stuck with the AT&T variant of this phone a little bit of hope, as you confirmed it can be rooted.
KingOfTheNet said:
Can you give us a tutorial guide on how to do it. Most of us (including me) have tried the version of king root that your using and it fails to root.
However, you have given us stuck with the AT&T variant of this phone a little bit of hope, as you confirmed it can be rooted.
Click to expand...
Click to collapse
I have posted a tutorial for anyone interested in rooting
KingOfTheNet said:
Can you give us a tutorial guide on how to do it. Most of us (including me) have tried the version of king root that your using and it fails to root.
However, you have given us stuck with the AT&T variant of this phone a little bit of hope, as you confirmed it can be rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com//at...tmas-heres-t3516196/post70011921#post70011921 I used this guide, with Kingroot 4.8.0 instead of Kingroot 4.8.1 but I don't think it matters. The guide did say that you should keep trying until you get it to root. I got root successfully first try, twice, however.
PopTartKing said:
This works on Lollipop too
---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------
Flashing 850W TWRP soft-bricks the device with the message "System software not authorized by Verizon Wireless has been on the device ..." blah blah blah. I think a Safestrap recovery is better suited for this phone.
Click to expand...
Click to collapse
I got the same thing. I've heard AOSP ROMs are not going to work because of the locked bootloader. And TouchWiz ROMs will work if you port in an AT&T boot image making it "authorized."
PopTartKing said:
This works on Lollipop too
---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------
Flashing 850W TWRP soft-bricks the device with the message "System software not authorized by Verizon Wireless has been on the device ..." blah blah blah. I think a Safestrap recovery is better suited for this phone.
Click to expand...
Click to collapse
And there's an S5 version of Safestrap but it only works with a Kitkat kernel. It might work with the Alpha since they have basically the same specs. I might try it in the future.
Does the Kingroot version matter? I tried this with Kingroot 5.0.0 instead of 4.8.0, and while it seems to initially fail, it actually does work. Verified with Root Checker and Kingroot itself was able to give root access to apps. However, it appears to cause certain apps like Camera (Samsung's) and S Health to fail. Uninstalled Kingroot and everything was working again (albeit unrooted).
AlphaEcho35 said:
Does the Kingroot version matter? I tried this with Kingroot 5.0.0 instead of 4.8.0, and while it seems to initially fail, it actually does work. Verified with Root Checker and Kingroot itself was able to give root access to apps. However, it appears to cause certain apps like Camera (Samsung's) and S Health to fail. Uninstalled Kingroot and everything was working again (albeit unrooted).
Click to expand...
Click to collapse
You have to use 4.81 because later versions do not allow you to remove it and replace it with SuperSU.
OMG
IT ACTUALLY WORKED! I tried it twice and on the second time it worked. I am so happy! Now to find a custom rom for it!
I reverted to KitKat and rooted it so that I could use Xposed lol
PopTartKing said:
I reverted to KitKat and rooted it so that I could use Xposed lol
Click to expand...
Click to collapse
I want to revert to kitkat too
Can you help me?
ifgiovanni said:
I want to revert to kitkat too
Can you help me?
Click to expand...
Click to collapse
My AT&T Galaxy Alpha is running KitKat right now. I'll post the firmware as soon as I can (probably somewhere around 12:00PM Eastern) tomorrow up to mega.nz for all to use
Edit: Firmware now up: https://forum.xda-developers.com/galaxy-alpha/general/samsung-galaxy-alpha-att-sm-g850a-t3535938
Mine lost root access after a couple of days.
cjskevans said:
IT ACTUALLY WORKED! I tried it twice and on the second time it worked. I am so happy! Now to find a custom rom for it!
Click to expand...
Click to collapse
Related
@Chainfire has released his CF-Auto-Root for the SM-G900T (T-Mobile US) Galaxy S 5.
I take no credit whatsoever for this, just posting a link to his main thread for all to see.
Please go and thank Chainfire!
With this root accomplished, we can confirm that the T-Mobile bootloader is UNLOCKED.
ROMS/Kernels/Recovery will soon follow from our awesome devs here on XDA.
Link to CF-Auto-Root Main Thread(Multi-variants)
THIS WILL TRIP KNOX COUNTER TO 0x1
ODIN Instructions - Copied from Main CF thread
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Click to expand...
Click to collapse
Download links taken from main thread:
SM-G900T (T-Mobile US): CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
Other models
CF-Auto-Root is not yet available for all models - one stock firmwares for these models become available, let me know, and I'll make the corresponding CF-Auto-Roots.
Click to expand...
Click to collapse
Good stuff, downloaded the zip, just waiting for my device to get here....we have to run the update the Kies first, right? Also, any word about CWM or TWRP? They've already made recoveries for the international versions.
stevew84 said:
Good stuff, downloaded the zip, just waiting for my device to get here....we have to run the update the Kies first, right? Also, any word about CWM or TWRP? They've already made recoveries for the international versions.
Click to expand...
Click to collapse
You can run the auto-root on both the updated version from kies, or straight outta the box.
I am trying to get in touch with the developers about TWRP and CWM, but I am sure they are busy trying to get all variants working.
I wouldn't Odin the international TWRP or CWM though. I would wait for a version for us.
idtheftvictim said:
You can run the auto-root on both the updated version from kies, or straight outta the box.
I am trying to get in touch with the developers about TWRP and CWM, but I am sure they are busy trying to get all variants working.
I wouldn't Odin the international TWRP or CWM though. I would wait for a version for us.
Click to expand...
Click to collapse
For sure, I don't want to brick the damn thing. Luckily I've been here before!
ill wait for a none trip counter version or triangle away to come out. should be to long.
khshapiro said:
ill wait for a none trip counter version or triangle away to come out. should be to long.
Click to expand...
Click to collapse
I wouldn't count on it. at least the Triangle away...Knox still hasn't been figured out for previous devices on how to reset it, so I wouldn't count on it for this device. As for getting root without tripping knox, Maybe kingo will update, or root-de-la-vega....who knows at this point.
khshapiro said:
ill wait for a none trip counter version or triangle away to come out. should be to long.
Click to expand...
Click to collapse
There basically won't be a way of resetting Knox.
Because of it being more a hardware flag, once it is tripped it is not reversible.
There might eventually be a way to do it without tripping it, but I wouldn't expect that for a while.
Got my S5 and ran the CFAuto worked like a champ... Rooted in 30 seconds.. Yes it tripped Knox but I really don't care.
Sent from my SM-G900T using XDA Premium 4 mobile app
Come ooonnnnn customer recoveries!
Edit: This is such great news, I'll be buying this version and unlock it to use it on T-Mobile.
Sent from my Nexus 7 using Tapatalk
tankmurdock said:
Got my S5 and ran the CFAuto worked like a champ... Rooted in 30 seconds.. Yes it tripped Knox but I really don't care.
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Now just to see if WiFi tether for root users works.
He he
And Y_E_S tethering works like a chiz-amp!
Sent from my SM-G900T using XDA Premium 4 mobile app
Since we have root, does that mean 100% that we can flash recoveries and ROMS? Both TW and AOSP?
Worked perfectly.
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
stevew84 said:
Since we have root, does that mean 100% that we can flash recoveries and ROMS? Both TW and AOSP?
Click to expand...
Click to collapse
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
I may start working on a custom TW kernel myself once Samsung uploads the source...
zaventh said:
Worked perfectly.
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
I may start working on a custom TW kernel myself once Samsung uploads the source...
Click to expand...
Click to collapse
Wait, CF custom recovery has nothing to do with root? I thought that was the point of CF "autoroot", am I missing something?
TheArtiszan said:
Now just to see if WiFi tether for root users works.
He he
Click to expand...
Click to collapse
Do u have a link to this?
Sent from my SM-G900T using XDA Premium 4 mobile app
Tmo warranty
Hi,
I'm debating if I should upgrade to SGS5, now that we can root the phone.
Does anyone knows for sure that a tripped Knox means no warranty with T-mo? I'm under the Jump plan and the idea is that I will be able to have warranty on the device if something happens to it (and I do have some apps that must use root...)
Thanks,
Gil.
zaventh said:
Yes, though root has nothing to do with this. The bootloader is unlocked, which is why root was obtainable via Chainfire's custom recovery. We have no restrictions on flashing custom ROMs/kernels/recoveries/etc.
Click to expand...
Click to collapse
Are we 100% certain that the bootloader is indeed unlocked. I know that chainfire stated this (although he currently doesnt own the s5).
I just came from HTC, and it states when you boot whether the bootloader is locked or unlocked. Im assuming there is no simple way of knowing whether the bootloader is locked or unlocked like the HTC devices
Phew glad to see the bootloader is not locked. Gonna root as soon as I get my replacement S5. Can't wait for the custom ROMs
Sent from my SM-G900T using XDA Premium 4 mobile app
el7145 said:
Are we 100% certain that the bootloader is indeed unlocked. I know that chainfire stated this (although he currently doesnt own the s5).
I just came from HTC, and it states when you boot whether the bootloader is locked or unlocked. Im assuming there is no simple way of knowing whether the bootloader is locked or unlocked like the HTC devices
Click to expand...
Click to collapse
There are reliable sources saying yes it is unlocked and there are reliable sources saying no it still hasn't been confirmed until someone successfully flashes a custom rom/kernel/recovery.
The consensus around here seems to be that it is unlocked but its just people repeating the words of the original few that debated it. And of course since we all want it to be unlocked, it is easier to believe that it is.
I personally don't want to jump to conclusion so i want there to be more discussion on the matter. Therefore i requested the "boot loader un/locked" thread to be reopened in Q/A.
i want to walk down to the store and buy one right now but until its confirmed im waiting it out. $650 bet!
Hey everyone. How are you guys able to keep root with 5.1? After the update, towelroot didn't stick. Nor could I reinstall it. Supersu doesn't have access either. What do you guys recommend?
You have to re root.
MikeyLee said:
You have to re root.
Click to expand...
Click to collapse
I used towelroot before, but now it says it can't support my device. How did you re-root your device? Did you do it within 5.1? Also, did re-installing TWRP work for you? I lost mine.
This is method I used before. tr.apk
http://forum.xda-developers.com/show...&postcount=376
lowao said:
I used towelroot before, but now it says it can't support my device. How did you re-root your device? Did you do it within 5.1? Also, did re-installing TWRP work for you? I lost mine.
This is method I used before. tr.apk
http://forum.xda-developers.com/show...&postcount=376
Click to expand...
Click to collapse
I think someone said you have to use ADB to flash the new TWRP that is compatible with L on our devices and then flash SuperSU.
I just went back to 2.8.0.0 and it worked for me. Is there a newer version of TWRP?
lowao said:
I just went back to 2.8.0.0 and it worked for me. Is there a newer version of TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=61577016&postcount=303
It pretty easy to get root and TWRP. Here are the instructions, taken from another thread. (Do you guys even read this stuff?)
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks, I'll try it tomorrow. It's a bit hard to keep track of like 5 threads and 10 new pages in each thread each day.
Does it matter which SuperSU ZIP version we use? Chainfire website shows 2.46.
ScoobSTi said:
Thanks, I'll try it tomorrow. It's a bit hard to keep track of like 5 threads and 10 new pages in each thread each day.
Does it matter which SuperSU ZIP version we use? Chainfire website shows 2.46.
Click to expand...
Click to collapse
kimtyson said:
3. Install supersu-2.49.zip (even though I didn't lose root)
Click to expand...
Click to collapse
I was wondering the same thing. Could someone provide us with a link to a tested supersu-x.xx.zip so we may have it in one thread.
At this time it would be best to not flash twrp. Instead fastboot boot twrp.img then install beta.SuperSU. 2.49
Sent from my MT2L03 using XDA Free mobile app
Lollipop will check the recovery partition and if it isn't stock it will put it back. In order for TWRP to stick you must boot TWRP after you install to allow it to patch the lollipop rom. TWRP must not be read only or else it cannot install supersu nor patch.
You guys got a lot to learn, but this is good, because now maybe some of you will pick up some experience and grow while here on XDA
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
In addition, do not use TWRP from the official twrp website until Dees_Troy gets around to updating his personal device tree since they do not accomondate for the changes seen in Lollipop. You have been officially warned. Unless you like sweats, tears, and heartaches.
lowao said:
Could someone provide us with a link to a tested supersu-x.xx.zip so we may have it in one thread.
Click to expand...
Click to collapse
Here, https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip.
kimtyson said:
Here, https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip.
Click to expand...
Click to collapse
Thanks for the link!
deleted
Just got notified from sammobile
Sent from my SM-G900T using XDA-Developers mobile app
g900ptuvu1gpe1 installing now with kies 3
Mega link
https://mega.nz/#!IIN3ASqC!bTmftP3U-8fTh1WLxQ60c0HvWvUkkHEpxFbdnL0EYTI
Is it Marshmallows?
Sent from my SM-G900T using XDA-Developers mobile app
Yes 6.01
Sent from my SM-G900T using XDA-Developers mobile app
Update
http://www.sammobile.com/firmwares/download/72008/G900TUVU1GPE1_G900TTMB1GPE1_TMB/
ashraf sharif said:
Yes 6.01
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
hey man, is your bootloader locked?
Terr20114 said:
hey man, is your bootloader locked?
Click to expand...
Click to collapse
i don't know for sure but probably not. I have had the phone for two years now and the bootloader was never locked previously
I wish I had that link about an hour ago, but figured out how to use the SamFirm Tool posted in another thread. Happy Flashing everyone
Also. First boot is taking ages
I'm so excited! AH. I need to get Odin now -.-
How does everyone like it so far?
Also, does anyone know if it would be a good idea for me to flash back to the stock Lollipop rom and then flash the update via Odin? I'm on a custom rom right now and I don't know if that will mess things up.
I was rooted on FOL1, flashed the marshmallow update via odin. Make sure you factory reset to set the binary status as offical, because I'm having booting issues
ashraf sharif said:
i don't know for sure but probably not. I have had the phone for two years now and the bootloader was never locked previously
Click to expand...
Click to collapse
tmobile didnt usually lock their bootloader but they locked the one for the galaxy s7 so im worried that this one will be locked. I wanna flash a s7 port as soon as i get this updated.
Seems like the phone has been super fast
misican said:
Seems like the phone has been super fast
Click to expand...
Click to collapse
Have you been able to Root? Please share your experience. Can't wait really!
I'm still waiting on the update to boot.
Hmmm, after rebooting and upgrading the "google Play Services" app, Google play finds an update for Samsung Voice Recorder which won't update and crashes with an error code 505. Will try and mess with the permissions for that app.
Decided to flash the stock rooted rom and update via Kies. As of right now it is optimizing app 105/273
Update: It rebooted after optimizing the last app and now its been hanging out at the T-Mobile screen for the last four or so minutes
Update 2: FINALLY got it to boot :3 I ended up flashing the image again through Odin~
Update 3: Rooted (followed this thread http://forum.xda-developers.com/tmo...sm-g900t-firmware-t3358190/page4#post66995024)
Yay~ Marshmallows
Edit: It looks like some people are having trouble with this update so I'm going to give a quick rundown of what I did and how I got everything to go smoothly. Now I'm not saying this is the correct way to things because most likely it isn't, but this is is just what I did that worked (for me, hopefully for you too).
Step 1. I flashed the stock rooted rom on my phone and unrooted it (not sure if this part is necessary) and then connected it to Kies to let it update that way (I was too lazy to mess with Odin tbh).
Step 2. After realizing I had been stuck on the T-Mobile splash screen for about 20 minutes to long I downloaded the image from the Mega link provided on this thread. Booted the phone into download mode, flashed via Odin, phone booted properly in no time.
Step 3. Installed Custom Recovery and Rooted the phone following the method in the link posted above.
MARSHMALLOW PARTY~
So I installed via Odin and as I was going through the initial setup it asks about WiFi and I turn it on and it keeps turning itself off after a few seconds.
UPDATE: Rebooted and was able to get WiFi to stay on.
---------- Post added at 08:41 PM ---------- Previous post was at 08:21 PM ----------
What root options should we be trying? CF Auto Root?
I installed this over the top of Lollipop using Odin. all my data carried over and everything seems to be running just fine. Installed TWRP and SuperSU, roots working just fine as well.
Only issue I'm coming across is an update to the Samsung voice recorder in the Play Store keeps failing with error 505.
Sent from my SM-G900T using Tapatalk
I had rooted latest firmware and i ve downloaded marshmallow, flashed through odin i lost root. its unrooted now
Alipk52 said:
Have you been able to Root? Please share your experience. Can't wait really!
Click to expand...
Click to collapse
well yes i got the same issue too
Chas10 said:
Hmmm, after rebooting and upgrading the "google Play Services" app, Google play finds an update for Samsung Voice Recorder which won't update and crashes with an error code 505. Will try and mess with the permissions for that app.
Click to expand...
Click to collapse
I successfully rooted marshmallow with flashing twrp (latest version) via odin 3.11.1 then flashing superSU 2.74 in twrp = profit?!?!
Next I may try a debloat script I found around xda then viperfx4android. Thank you T-Mobile
Playb3yond said:
I successfully rooted marshmallow with flashing twrp (latest version) via odin 3.11.1 then flashing superSU 2.74 in twrp = profit?!?!
Next I may try a debloat script I found around xda then viperfx4android. Thank you T-Mobile
Click to expand...
Click to collapse
I'm running it now, haven't even bothered to root it... found a non root app to backup and restore my sms/mms/calllogs so I'm not in a hurry to root. Might be fun to actually be able to use the fingerprint for payment options now...
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
OP, is it okay if I don't have original factory sync cable in hands?
volibyro said:
OP, is it okay if I don't have original factory sync cable in hands?
Click to expand...
Click to collapse
Yeah its ok you just run into less issues with original cable.
**Working on updating links I have a slow upload speed though.
HideTheCookies said:
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
Click to expand...
Click to collapse
If u want to switch to SuperSu from KingoROOT, the best and easiest method would be backing up ur phone and performing a soft reset. Afterwards simply install SuperSu, the superuser binary is already installed from kingroot - no worries, just update it normally via SuperSU and disable KNOX after the update is complete.
That switch idea of yours might get you bricked
Confirmed it works now we need a recovery so we can just flash su
SuperSUme works really really well lol, this phone is 32bit only any1 wanna try 4 a recovery?
Thxx bro
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
gravyd316 said:
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
Click to expand...
Click to collapse
Agreed about flashing the recovery, but you need to be rooted with KingOroot to get SuperSUme to work, & it helps to just keep the screen timeout turned off thru this process , after it says "complete" I downloaded SuperSU & installed, updated, "disabled" knox, & I can also use flashfire although its pretty worthless for anything other than backups, as the little AROMA shell emulator thingy does run after the verizon logo is showing, which indicates to me yea its locked down pretty solid lol.
I tried Safestrap & it gave me a /SS folder in my /etc so I looked into that but I can't manage to figure out how I should go placing the files to make it work lol. But i do know this thing is 32bit ONLY, so compiling the j100H twrp for instance will NOT flash no matter what we do to the bootloader, it will bootloop since the architecture is for a 64bit SoC, we need someone to compile the j100H twrp in a 32bit only compatible architecture, & then you can easily flash it like cake, & TWRP should do the rest like all other Samsung phones O.O
its gotten to the point these are all the apps I have when i restore haha, if you wanna PM me about working together to get this thing a little more flexible I'm always open to ideas . I only use this thing as a hotspot but would totally like to see a recovery at least make it over & from there I could definitely start the ROM bringup
Will I get bricked by doing this with Verizon
Weegee1 said:
Will I get bricked by doing this with Verizon
Click to expand...
Click to collapse
you cant hard brick this device, restore with ODIN start over.
LilAnt530 said:
you cant hard brick this device, restore with ODIN start over.
Click to expand...
Click to collapse
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
LilAnt530 said:
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
Click to expand...
Click to collapse
THANKS! sorry last noob question, will I lose root if I turn my phone off
Weegee1 said:
THANKS! sorry last noob question, will I lose root if I turn my phone off
Click to expand...
Click to collapse
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
LilAnt530 said:
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
Click to expand...
Click to collapse
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Weegee1 said:
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Click to expand...
Click to collapse
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
LilAnt530 said:
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
Click to expand...
Click to collapse
And with SuperSU, is that one more stable
Hello All,
I have a galaxy note 3 N9005 LTE with 4g option unavailable unless I modify a data file and change its value from 0 to 1 (I don't remember the exact file name right now!), however, I can't change that file value unless I have my device rooted.
I have rooted my device before and had my 4G option enabled successfully before I perform a factory reset.
Currently, I am trying to root it again using Chainfire cf auto root file and Odin.
Although the Odin gives a successful process, the phone doesn't get rooted after bootup.
Model Number:
SM-N9005
Android Version:
4.4.2
Baseband version:
N9005XXUGNG1
*I have tried all auto root application available like kingo root and others and they do not work.
*If you know a method to unlock the 4G option in this device, it might be enough for me and no need for rooting.
(I have no clue why should they disable the 4g option in the first place !! )
Thank you for helping!
I've rooted that thing before using kingoroot and then flashed twrp and then flashed supersu zip and then flashed cyanogenmod 13. So I guess you do the same Btw, I did all that without a computer, by flashing twrp using the flashfire thing from gstore.
ramiabouzahra said:
I've rooted that thing before using kingoroot and then flashed twrp and then flashed supersu zip and then flashed cyanogenmod 13. So I guess you do the same Btw, I did all that without a computer, by flashing twrp using the flashfire thing from gstore.
Click to expand...
Click to collapse
Thank you for your reply!
But as mentioned up there, kingoroot failed to root my device. Therefore, I am looking for other alternatives.
igaber said:
Thank you for your reply!
But as mentioned up there, kingoroot failed to root my device. Therefore, I am looking for other alternatives.
Click to expand...
Click to collapse
Can you re-download this (http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip)? It is possible that you have downloaded and flashed the one for the 4.2 bootloader, which obviously won't work.
Good luck
ramiabouzahra said:
Can you re-download this (/CF-Auto-Root-hlte-hltexx-smn9005.zip) It is possible that you have downloaded and flashed the one for the 4.2 bootloader, which obviously won't work.
Good luck
Click to expand...
Click to collapse
It is that exact one I have used, although I know it is for Android 5.0. I have no idea why it doesn't work with my cell phone.
Also, I have used Odin v3.10.6 and v3.07.
igaber said:
It is that exact one I have used, although I know it is for Android 5.0. I have no idea why it doesn't work with my cell phone.
Also, I have used Odin v3.10.6 and v3.07.
Click to expand...
Click to collapse
It's for android KitKat. Hmm, interesting, I'd backup stock ROM and reflash the 4.4.2 and then try the cf auto root. So I suggest you do the same