Related
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Not at the moment. There is a root method, but no factory image to flash back to.
http://forum.xda-developers.com/showthread.php?p=43890414 check here for recovery updates.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
sheek360 said:
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Click to expand...
Click to collapse
We all just have to be patient! It's not the end of the world, rooting it allows you to remove some bloatware, then you can install themes and launchers to make it a little better!~
You can still tweak the device so it's enjoyable!
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
jd1639 said:
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
Click to expand...
Click to collapse
You get around alot, have you seen any update to the MF3 bootloader issue?
TheAxman said:
You get around alot, have you seen any update to the MF3 bootloader issue?
Click to expand...
Click to collapse
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Tons and tons of uninformed people are messing up their phones. You're right, it's sad.
It will be great when people can comfortably root their device knowing there is a way back when all is said and done.
In the mean time, to the OP, playing the waiting game will not kill anyone in this situation.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Agreed, if most would have read just a little, they would not be having this issue. For me, I always wait until a dev gets a hold of an update and does their thing, and then I update to the newest...I have NEVER updated direct on the phone, even with all the phones I have ever owned.
Not happening OP, do a search on MF3 in the search bar you will find all kinds of things related to it.
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
ThePerson98 said:
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
Click to expand...
Click to collapse
I just wanna plus 1 that for the OP
Sent from miPhone using XDA Premium HD app
As long as you're a smart cookie and don't go around attempting to mod your twframework and other important inner system files, I wouldn't get too disheartened and held back from touching the partition. Simply be intuitive and anything you intended on replacing, rename instead to the file with a *.temp extension. Wouldn't be that hard to roll back then (as long as you can still boot). Rooting itself mods the system, so people have already jumped ship in that regard.
Just don't go around trying to enable verbose boot or flash a recovery from some kind of mobile ODIN or GooManager.
BE SMART, not eccentric and living by the standards of yolo.
I've been searching these forums for the last few hours and there seem to be many mixed answers about this. Will it hard brick my phone?
It's probably an incredibly stupid thing to do, but I'm willing to do whatever (other than returning to stock) to get more security. I've lost too many phones
Anyway, I have a feeling changing the recovery.img will cause a locked bootloader to reject boot, but what about boot.img (which is used for root, magisk, etc)?
Is there anyone here that knows how the boot process works in detail? would appreciate the feedback and I'm sure people will appreciate it. Thanks
htko89 said:
I've been searching these forums for the last few hours and there seem to be many mixed answers about this. Will it hard brick my phone?
It's probably an incredibly stupid thing to do, but I'm willing to do whatever (other than returning to stock) to get more security. I've lost too many phones
Anyway, I have a feeling changing the recovery.img will cause a locked bootloader to reject boot, but what about boot.img (which is used for root, magisk, etc)?
Is there anyone here that knows how the boot process works in detail? would appreciate the feedback and I'm sure people will appreciate it. Thanks
Click to expand...
Click to collapse
How will relocking the bootloader add security? Are you secretly the President asking this question?
Jokes aside. Apparently it will cause you to brick because the boot.img needs to be secure. Having twrp or any other form of custom anything I assume has to have an unsecured boot. So when the bootloader lock command is processed and the boot isn't able to be secured, brick occurs?
htko89 said:
I've been searching these forums for the last few hours and there seem to be many mixed answers about this. Will it hard brick my phone?
It's probably an incredibly stupid thing to do, but I'm willing to do whatever (other than returning to stock) to get more security. I've lost too many phones
Anyway, I have a feeling changing the recovery.img will cause a locked bootloader to reject boot, but what about boot.img (which is used for root, magisk, etc)?
Is there anyone here that knows how the boot process works in detail? would appreciate the feedback and I'm sure people will appreciate it. Thanks
Click to expand...
Click to collapse
No offense, but this would be an incredibly stupid thing to do. There is always a trade off between convenience and features (i.e. root, etc.) and security. It's always either or, at least to a very large extent. Pick full stock or pick root/unlocked. The trade-off is highly weighted towards root as.long as you use reasonable care with your device, but feel free go for it if you're needing a new metal doorstop!
I've been rereading jcaduono post on installing twrp and rooting the us996. It seems pretty straight forward with all the adb commands.. It's returning to stock, IF I run into a problem, that I'm really confused about. I've read, in a couple threads, that system.img and boot.img is all we need.. but I just read another thread where the OP has instructions to download all the recovery images. I dont even know where to download the recovery images. I have system and boot images. Can someone shed some light on this? I have the unlocked US996. Not the US cellular. I'm really missing root right now.
tripey said:
I've been rereading jcaduono post on installing twrp and rooting the us996. It seems pretty straight forward with all the adb commands.. It's returning to stock, IF I run into a problem, that I'm really confused about. I've read, in a couple threads, that system.img and boot.img is all we need.. but I just read another thread where the OP has instructions to download all the recovery images. I dont even know where to download the recovery images. I have system and boot images. Can someone shed some light on this? I have the unlocked US996. Not the US cellular. I'm really missing root right now.
Click to expand...
Click to collapse
i'm kinda in the same boat..i keep going to root then stop evreytime i see someone with issues lol. i should just pull the plug already. US996 unlocked here, too. can't you NOT go back to a locked bootloader, though? that's what LG said anyway.
For what Its worth, i had to send my phone back to LG because of a twrp recovery bootloop, which appears to be caused by a bad board. They switched it out on the paperwork anyway. But ,as long as its under warranty, they didnt give me any problems about servicing it. So if you're gonna try, do it before the warranty is up just in case.
jayochs said:
i'm kinda in the same boat..i keep going to root then stop evreytime i see someone with issues lol. i should just pull the plug already. US996 unlocked here, too. can't you NOT go back to a locked bootloader, though? that's what LG said anyway.
Click to expand...
Click to collapse
From everything I've read, you can go back... but there will be indication that it was unlocked.
Bubba Fett said:
For what Its worth, i had to send my phone back to LG because of a twrp recovery bootloop, which appears to be caused by a bad board. They switched it out on the paperwork anyway. But ,as long as its under warranty, they didnt give me any problems about servicing it. So if you're gonna try, do it before the warranty is up just in case.
Click to expand...
Click to collapse
Nice, that's good to know!
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
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
I don't think there is a revert method (inside or outside the store). I know it's after the fact, but on your next device, you may want to figure out exactly what you'd want to do with root before you go through with it. I typically only do it for TB backup purposes and XPOSED, but I've found that I can back up in other ways, and I dig stock enough not to risk rooting. I don't knock you for rooting (there are plenty of good reasons to), this is just my advice going forward. In the meantime, you should look around XDA, you may find your golden goose app that you can leverage root for. Good luck.
bgibson72 said:
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
Click to expand...
Click to collapse
hey sorry to hear that your having issues,
but you and the other poster are correct, sprint never released a restore file that wasn't encrypted.
And to my knowledge the repair centers would not be able to fix this issues, and sadly lg would more then likely deny a
warranty claim as this was modifications done by the end user.
A good chance in the future that we will get the files needed or a process to revert back to stock, but currently there is no SAFE method to try, and pushing the stock aboot and system.img back to the device WILL hard brick the device.. @me2151 attempted the restore process once, and failed, so please be careful as you may have issues.. The red warning triangle is due to your aboot "bootloader" being swapped for the debug version and will never go away, unless we get a dev willing to risk his device for a .png swap of the warning RED img. Other wise its there forever.
The static on boot up can be removed using a custom kernel but be aware it WILL break things in return. Typically update to prl and profile
fm radio, comfort view and a few other little things..
Hey, thanks for the reply. I can deal with the red warning screen, I just get a little anxious when I can't use the touchscreen or my cellular data gets hosed. As long as there are fixes here (which there have been--thanks to all) and I can use my phone, we're good. I figured if someone could break encryption on government files then why would an encrypted KDZ file be such a challenge? At any rate, I appreciate the help. I'll just keep my fingers crossed for a PNG swap!