Database Users

SAMSUNG-SM-G870A ROOT w/ towelroot

I want to be able to mod my phone so I can install SDFix, but I cannot figure out how to get root access. I downloaded the towelroot and installed it but it keeps saying that my device is not supported, yet I see in several threads that people have claimed that it is.
I did recently update the software from AT&T (before I knew I needed to get root access) so that might have something to do with it. If it does, can anyone tell me AND let me know if it is possible that it will be fixed in the future? Thanks.
P.S. I anyone know a work-around the SD card issue without root that would work too. This is mainly why I am rooting, so I can ACTUALLY use the extra storage that I installed.

ranthon007 said:
I want to be able to mod my phone so I can install SDFix, but I cannot figure out how to get root access. I downloaded the towelroot and installed it but it keeps saying that my device is not supported, yet I see in several threads that people have claimed that it is.
I did recently update the software from AT&T (before I knew I needed to get root access) so that might have something to do with it. If it does, can anyone tell me AND let me know if it is possible that it will be fixed in the future? Thanks.
P.S. I anyone know a work-around the SD card issue without root that would work too. This is mainly why I am rooting, so I can ACTUALLY use the extra storage that I installed.
Click to expand...
Click to collapse
Yes a recent update disabled towelroot. You might be able to work around this issue by flashing an older firmware in Odin or by trying this tutorial.

lingowistico said:
Yes a recent update disabled towelroot. You might be able to work around this issue by flashing an older firmware in Odin or by trying this tutorial.
Click to expand...
Click to collapse
Thanks. I will try that out when I get a chance! I will let you know what happens when I do.

FYI: Where to Start for Root Access
For anyone who may search this forum and find my mention of the G870A, and have no idea where to start (like I did) follow this thread: http://forum.xda-developers.com/showthread.php?t=2799754 I can confirm that this firmware (once installed following the steps) will allow towelroot to work if you updated (like I did) in mid-August 2014.
P.S. I did not wipe all of my data clean like the post mentions at the bottom, but I did downgrade the firmware without issue.

It Works!
ranthon007 said:
For anyone who may search this forum and find my mention of the G870A, and have no idea where to start (like I did) follow this thread: http://forum.xda-developers.com/showthread.php?t=2799754 I can confirm that this firmware (once installed following the steps) will allow towelroot to work if you updated (like I did) in mid-August 2014.
P.S. I did not wipe all of my data clean like the post mentions at the bottom, but I did downgrade the firmware without issue.
Click to expand...
Click to collapse
I've been looking for this for a while now... I'm glad I finally found it. Thank you!!! It worked like a charm!

KingRoot works

I tried the OS 4.5.2 rooting from the forum and that did not work. I tried KingRoot and its works. Can someone test this on OS 4.5.3 or higher OS please
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from HDX 7 OS 4.5.2 Rooted

Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.

Sometimes you have to tried several times the last time I fail too but the second works. I dont know what cause it
Sent from HDX 7 OS 4.5.2 Rooted

PsymH said:
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Click to expand...
Click to collapse
From what I've heard, 4.5.4 can't be rooted. If you have a 3rd generation HDX, then you have to first downgrade to 3.2.8 and then manually update to 4.5.2.

Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.

rabaker07 said:
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
Click to expand...
Click to collapse
You obviously understand the risk and assume you tried alternate (Moto) drivers along with different cables and host ports to confirm diagnosis. Note cables/ports that work on one device may not on another - especially finicky HDX hardware.
You're probabky not going to get a high confidence response to your KingRoot question as most take the full step of unlocking. Plus age of device and waning interest. Good luck.

Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul. The risks come in when you attempt to flash a ROM and it fails by partially loading and overwriting/erasing critical files without completing (loss of power mid flash!) or if the ROM is incompatible in some way and you are unable to flash your previous ROM. That's where bootloader recovery software comes in (TWRP and the like). So that you can access the system before loading (or failing to load) the ROM, and flash over it or flash a backup.
Moral of the story is that YES, Kingroot works on HDX 3rd Gen on 4.5.5.3. I tried it last night and it worked. I now have access to the root directory. Oh, the places you'll go!!
Sent from my Pixel 2 XL using Tapatalk

rabaker07 said:
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul.
Click to expand...
Click to collapse
Nope; root attempts can yield a bootloop or otherwise dysfunctional device. Glad all worked out for you.

Ouch. I didn't realize that. It always seemed very benign and I've never had it go wrong. I guess I'm used to devices that are designed to be accessible. Fortunately my HDX rooted without a hitch.

Samsung Galaxy J3 (SM-J320P) Virgin Mobile (or any carrier) Support???

Wondering if anyone in the know has heard of any development going on for this device? I recently bought one and it's not a bad phone for the price, but I've seen absolutely -nothing- on it anywhere online for the most part. It's barely root-able with what I've been able to find, and no custom recovery or really anything custom has popped up that I've seen.
Not sure if it's just that it's been only a few months since the phone came out, or if it's just not that great a phone. I upgraded from an HTC Desire 510 to this, and it was heavily customized/rooted/etc, and I want so badly to get back to where I was with it on this phone I cant stand it!

I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.

triiuzii said:
I also want to root my Galaxy J3! I just want to root it so I can use AdAway and Titanium Backup.
Click to expand...
Click to collapse
Right now rooting isn't the problem so much as keeping root. Because apparently the colonel has protection and will remove root whenever you reboot. That means things that require root on boot like backups, Xposed and a lot of other things won't work for us until someone complies a kernel with root protection removed. You can do some debloating and possibly the AdAway but that's about it right now.

*kernel. Damn voice to text.

That sucks. I upgraded from an LG Volt and I was able to do a whole bunch of stuff on it. The J3 is still very new, so hopefully development will happen soon.

I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.

mallamike said:
I just got this phone if there is anything i can do to help move this along let me know. I have the virgin mobile one.
Click to expand...
Click to collapse
I guess that would depend on what you have experience with and what you can do. Thus-far root has been able to be achieved with Kingroot, though it wont stick through a power cycle (reboot/power off/etc), and using any of the methods available (at least that I'm aware of, only found two legitimate ones) to replace Kingroot with SuperSU (to facilitate having root stick past the reboot hopefully) causes a soft-brick every time forcing a re-flash of stock firmware through Odin.
At the very least make your voice heard, if nothing else hopefully more popularity will come this devices way and we'll see some development for it. My roommate is considering writing something for it, but it is a long process working solo, so anyone who has experience working with kernels or editing stock rom/writing custom roms feels up to helping out, shoot me a message and I'll get it over to him. He's a fairly experienced programmer and picks up what he doesn't already know pretty quickly.

Got one recently too. Would also appreciate any more information on rooting.

I have a J320A (AT&T) came stock with 6.0.1, can help test if needed

http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach

coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Will this version of TWRP work on the Att variant running 6.0.1? Is there a way to root that device yet?

coolbeans2016 said:
http://forum.xda-developers.com/android/development/recovery-teamwin-recovery-project-3-0-2-t3356616
I know this is an old thread, just making my rounds looking for anything on the J3 myself (SM-J320P Boost, Virgin, etc...) and have found TWRP & permanent root with Chainfire's SuperSU (system-less though). Everything is great except a lag issue with supersu. There is an exposed by wanum that works as well. Only app that has root issue so far is ES File Explorer. If anyone is still looking hope this helps.
zach
Click to expand...
Click to collapse
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.

TechShui said:
Anything yet for J320A/Z models? (AT&T/cricket)
This version of TWRP won't work will it? Totally different phone?
EDIT: just realized the guy above has the same question... something tells me we won't see root on the ATT/cricket variants for a while.
Click to expand...
Click to collapse
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.

what about the
SM-J320VPP = the verizon pre paid planversion. any working roots for me yet?
oh pretty pleeeeeez

Azhero said:
Try official TWRP of galaxy J2. Your variant shares the same specs as J2. Others also did this to galaxy On5, it works 100%.
Click to expand...
Click to collapse
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?

AnierinB said:
So can you confirm this method works? Does OEM unlock setting in dev options unlock the bootloader on AT&T variant? If so couldn't I temp root and flash TWRP via Flashify?
Click to expand...
Click to collapse
It doesn't work tried it 3 times. I even tried other ones no luck. They locked this thing down. Im surprise chainfire haven't tried this phone yet.

Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?

Gotbootloopedtoomuch said:
Hi, guys! I understand it was an old thread, but I was referred here from Reddit. I have a Galaxy J3 (SM-J3109) purchased in Mainland China (Service provider is China Telecom). I rooted it with Kingo Root. Kingo Root stated that it successfully rooted the device, but the phone OS had given me warnings about unauthorized access to the device or something.
One week later (I did *not* reflash the phone nor install any applications after I rooted the phone) I found the phone stuck in an annoying bootloop. The device status is still "official" and the Knox counter is still set at 0x0.
Now that it's bootlooping I'd like to know if it's possible to take the applications and files off the phone before I factory reset it. It's not looking hopeful as I read similar threads from 2012 saying that once other Android devices bootloop, getting stuff off of them is impossible. I tried using ADB to take data off the phone (while Odin3 was detecting it being connected to the PC) but ADB doesn't detect the phone. Should I try a different cable?
Click to expand...
Click to collapse
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.

darknaio said:
Best advice would be to try flashing the stock firmware with odin. That shouldn't delete any of your data and will usually fix a bootloop. You can Google your phones stock firmware and see if you can download it.
Click to expand...
Click to collapse
Thank you so much! I tried using Odin to flash a software update and it worked perfectly. The phone is back up and running and all of the files are still there!

Right now i have TWRP 3.0.2 with supersu and i havent lost root yet also had no problem switching between backups, xposed working fine and also overclock too with setcpu, im currently running 5.1.1 using j320FN but TWRP was from j320F, i will put up links to the files if any of you are willing to try its up to you.
TWRP flash through odin : http://www.mediafire.com/download/blk7qa90vs6wik3/TWRP_3.0.2-0_SM-J320F.tar.tar
Supersu flash through recovery then update through playstore then install busybox after through playstore : http://www.mediafire.com/download/cpv2c71cp11x41f/UPDATE-SuperSU-v2.76-20160630161323.zip
Remember to turn on usb debugging and turn on oem unlock before flashing recovery, also if you manage to get recovery press they grey box on the right to change language to english. Hope this might help somebody on here because we really need full root for everyone.

Which root method works for Moto X Pure 6.0

On the other threads, I saw people who used the method lost wifi, etc.
Are there any working methods to root without losing anything?

jdugery said:
On the other threads, I saw people who used the method lost wifi, etc.
Are there any working methods to root without losing anything?
Click to expand...
Click to collapse
Yes... Use the latest TWRP and SuperSU 2.62-3 or latest and the manual systemless method. I have rooted at least 6 or 7 Moto devices on MM with ZERO issues. I don't know how people are losing WiFi or other connectivity when they do this.
There are a few rooting threads for Moto devices in my sig, rooting the MXPE is identical except the TWRP needs to be for this device... TWRP is available directly from https://twrp.me look for device "clark"

Download TWRP v3.0.2-0 and SuperSU v2.78 SR3, flash twrp recovery into device via fastboot, reboot into recovery, in twrp go to advanced and open terminal, input this command (without the quotes) into terminal and press enter:
"echo SYSTEMLESS=true»/data/.supersu"
flash supersu, it will flash systemless supersu, otherwise the device would bootloop, reboot, the device may reoboot once or twice, its normal, profit!

kadopt said:
Download TWRP v3.0.2-0 and SuperSU v2.78 SR3, flash twrp recovery into device via fastboot, Start TWRP and allow changes to system, reboot into recovery, in twrp go to advanced and open terminal, input this command (without the quotes) into terminal and press enter:
"echo SYSTEMLESS=true>>/data/.supersu"
flash supersu, it will flash systemless supersu, otherwise the device would bootloop, reboot, the device may reoboot once or twice, its normal, profit!
Click to expand...
Click to collapse
This... exactly this... if done properly will work without messing with WiFi, mobile data, or anything else, and TWRP will stick.

acejavelin said:
This... exactly this... if done properly will work without messing with WiFi, mobile data, or anything else, and TWRP will stick.
Click to expand...
Click to collapse
I have no idea how to flash stuff. Any noob guide with step by step instructions?

jdugery said:
I have no idea how to flash stuff. Any noob guide with step by step instructions?
Click to expand...
Click to collapse
Did you look at the tutorials in my sig?

acejavelin said:
Did you look at the tutorials in my sig?
Click to expand...
Click to collapse
That seems to be for Moto G.
Any guide for the Moto X running 6.1.

jdugery said:
That seems to be for Moto G.
Any guide for the Moto X running 6.1.
Click to expand...
Click to collapse
I hinted at it in an earlier post in this thread, but I will get more blunt... Every 3rd and 4th Generation Moto device on Marshmallow is identical from a rooting perspective, the only difference is you must use the proper TWRP for your device, every thing else is the same, the commands, the unlocking, the SuperSU, etc. It doesn't matter if it's a Moto E, G, Z, or X, the process is identical.

acejavelin said:
I don't know how people are losing WiFi or other connectivity when they do this.
Click to expand...
Click to collapse
I think the folks who are losing wifi are flashing patched boot images instead of just plain old systemless supersu and letting the installer automation do the boot image patching. They get an XT1572 boot image on an XT1575, or even on an XT1572 running a different system version and radios break.
That level of hackery hasn't been necessary since M and systemless root were in their infancy, but there are still how-to threads on here than push people in that direction.
The number of people who lose wifi or get stuck booting system after botching rooting this phone is surprising. At least this phone is pretty forgiving and you can fastboot your way out of trouble. I have another phone where mismatched firmware has been known to require jtag or even motherboard replacement to recover from.

jason2678 said:
I think the folks who are losing wifi are flashing patched boot images instead of just plain old systemless supersu and letting the installer automation do the boot image patching. They get an XT1572 boot image on an XT1575, or even on an XT1572 running a different system version and radios break.
That level of hackery hasn't been necessary since M and systemless root were in their infancy, but there are still how-to threads on here than push people in that direction.
The number of people who lose wifi or get stuck booting system after botching rooting this phone is surprising. At least this phone is pretty forgiving and you can fastboot your way out of trouble. I have another phone where mismatched firmware has been known to require jtag or even motherboard replacement to recover from.
Click to expand...
Click to collapse
Hmm... that makes sense. I half-jokingly said in another thread I should write a "new" how to root guide for this device similar to my existing ones for the Moto G 3/4 devices, maybe I should actually do that, but getting ANOTHER guide might just add to the confusion of users.

acejavelin said:
Hmm... that makes sense. I half-jokingly said in another thread I should write a "new" how to root guide for this device similar to my existing ones for the Moto G 3/4 devices, maybe I should actually do that, but getting ANOTHER guide might just add to the confusion of users.
Click to expand...
Click to collapse
Might help if you could get it stickied.
If the OP of the Heisenberg thread were updated, and the ivcarlos thread got pulled down I think we'd see a lot less soft bricks. The users who started all the guide and resource threads seem to have all moved on.
The Q&A is full of "help I borked my MXP rooting it" threads. Can't be good for the confidence of a new user. At least they're easy to fix.

jason2678 said:
Might help if you could get it stickied.
If the OP of the Heisenberg thread were updated, and the ivcarlos thread got pulled down I think we'd see a lot less soft bricks. The users who started all the guide and resource threads seem to have all moved on.
The Q&A is full of "help I borked my MXP rooting it" threads. Can't be good for the confidence of a new user. At least they're easy to fix.
Click to expand...
Click to collapse
Yeah... I'll work on it over the next day or so. It's frustrating, I think I've helped recover and root at least a dozen devices in the last week alone.

Any custom ROMs available yet for the H915 Canadian Version (Freedom Mobile)?

LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!

Considering the 915 isn't even a supported device no. If someone has gotten the 915 please let me know.

Until FREEDOM Mobile allows the LG V20 LOCKED bootloader to be UNlocked, there will be no FREEDOM to have a custom ROM anytime soon
That is what I got the T-mobile version with the unlockable bootloader which works great on NON-freedom.
lumberguy1028 said:
LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!
Click to expand...
Click to collapse

Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know

markbencze said:
Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know
Click to expand...
Click to collapse
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.

lumberguy1028 said:
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.
Click to expand...
Click to collapse
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.

markbencze said:
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.
Click to expand...
Click to collapse
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.

me2151 said:
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.
Click to expand...
Click to collapse
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12

markbencze said:
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12
Click to expand...
Click to collapse
Lol Im the dirtysanta dev. I have a LS997. Not a 915.

me2151 said:
Lol Im the dirtysanta dev. I have a LS997. Not a 915.
Click to expand...
Click to collapse
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.

markbencze said:
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.
Click to expand...
Click to collapse
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.

lumberguy1028 said:
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.
Click to expand...
Click to collapse
Correct but it's useless to use since the phone doesn't function properly afterwards. If there was a confirmed way to have data and signal working then that would be great but there is nothing confirmed to work yet.

I've just moved to a V20 from a Note 4. All my Note4 ROMS were T-Mobile versions. I believe Rogers/Fido phones are basically the same as T-Mobile, which uses freq. channel 66 as well.
Has anyone tried a T-Mobile (918) ROM on the 915 yet? Might just work...

no root yet for freedom????/

whats the method
whats the method to root the lg h915

diehard2013 said:
no root yet for freedom????/
Click to expand...
Click to collapse
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.

GerardSamija said:
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.
Click to expand...
Click to collapse
Why Wouldent you just use the secret # in the hidden menu to change bands to get signial. Also you could try searching for exsisting bands that are near by, this dont require the hidden menu.
Sent from my [device_name] using XDA-Developers Legacy app

Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?

GerardSamija said:
Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?
Click to expand...
Click to collapse
Oops my bad i was sleeping while i read that. You can fix your sim card reader just use a soder tool. Also there maybe a root for this phone but i don't think it is safe enough yet.
Sent from my [device_name] using XDA-Developers Legacy app