Hello,
I have an LG G3 AS990 (Ntelos). I would like to root and flash a different ROM, but am having trouble finding my variant as Ntelos is a smaller carrier. Does anyone have any advice on compatibility between any other variants? Any advice would be greatly appreciated.
Thank you
I've continued to search, but haven't found anything. Just hoping someone may have some information.
Same Boat
Snakemanc6 said:
I've continued to search, but haven't found anything. Just hoping someone may have some information.
Click to expand...
Click to collapse
I've been researching this as well. You could try finding the beta version of CM for Sprint's LS990. I would try it just for the fun of it, but I'm nervous that I don't have the stock rom for AS990 to revert back to. I have my system backed up, but I'm not comfortable enough to rely on that to save my phone if I brick it trying to install CM.
Bump. I have the same problem here, except that mine got pushed an OTA patch that prevents stump and others. So far no firmware I have found is compatible with this device to even downgrade in order to root in the first place. If anyone has succeeded with as990 NTelos please help.
Bumping the necro in hopes of support. XD my software says as99020a but the writing on the back under the cover says us990... So I'm not sure what I'm supposed to do especially since I can't even find a place to download the firmware for manual updates.. Etc. :-[ Damn ntelos
AS990 Recovery?
Has anyone found a recovery that works with the AS990?
I have an option
I've posted a way to use TWRP and ROMs for the LS990 on the LG G3 subreddit, I need 10 helpful posts before I can post it here because I have a few xda posts and downloads linked.
AS990 experience
Hi all,
I have tried different roms on my as990 (Carolina West Wireless) by using the method on reddit (HERE) and everything works just a few things to keep in mind
To get your sim to work on a custom rom you may need to change the build.prop ro.build.target_operator=, and ro.afwdata.LGfeatureset=
Take note of these settings before you try to reflash the phone. If you change one, change both if applicable.
Remember to backup your old build.prop
Backup all apns before you start using method found (HERE)
Backup build.prop
Oh and did I mention backup build.prop
The restore files can be found (HERE) and use the guide found (HERE) replacing the files mentioned with the ones in the post. If you use this method to restore you phone, the build.prop from the reddit post will not work so use the old build.prop that I'm sure by now you have backed up or you will have to get the custom .dll file elsewhere to restore.
For all who have taken the ota update, the restore method works for that too
Your carrier files are automatically restored if you use the firmware in the above post. That is to say they were for me but if anyone else test this
no guarantees but it did work flawlessly for me.
Also I am currently working on a recovery for AS990 if anyone has any ideas feel free to chime in
A couple of side notes
The method by tybskinner may also work if you flash to US990 as well, but I have not tried this yet. To do so you would need the custom .dll or the build.prop for US990
Users have reported that SIM unlock is possible by changing the the build.prop ro.build.target_operator= to global or open however I have not tried this yet
If anyone has a method to change the PRL on the device please let me know I have tried several options but no method I have tried will allow the PRL to stick
P.S. not trying to steal your thunder tybskinner just making it easier for people to find the links
Thanks for the info guys. At this point I'm having issues just trying to root the thing. Lost root with Lollipop, and for some reason I cant seem to regain it. Oh well. The price you often pay for having a smaller carrier (I actually work for nTelos, so its my work provided device).
Thanks again. I hope you guys are able to get yours setup the way you like. :good:
Snakemanc6 said:
Thanks for the info guys. At this point I'm having issues just trying to root the thing. Lost root with Lollipop, and for some reason I cant seem to regain it. Oh well. The price you often pay for having a smaller carrier (I actually work for nTelos, so its my work provided device).
Thanks again. I hope you guys are able to get yours setup the way you like. :good:
Click to expand...
Click to collapse
Currently there is no root method for the AS990 device on the newest ROM however if you follow the guide posted you can downgrade to the previous version and go from there.
Have a look here...I found a way around the whole super secure as990 crap
http://forum.xda-developers.com/lg-g3/help/how-to-as990-custom-recovery-roms-t3216133
It may seem like a bit much but it works like a champ!
HI
bobo040 said:
bump. I have the same problem here, except that mine got pushed an ota patch that prevents stump and others. So far no firmware i have found is compatible with this device to even downgrade in order to root in the first place. If anyone has succeeded with as990 ntelos please help.
Click to expand...
Click to collapse
you need to download iroot on your computer then connect your phone on the portable usb outlet make shure your phone is debbugged then open iroot it will read your phone wait wor a while and you are golden
yorimoto1987 said:
you need to download iroot on your computer then connect your phone on the portable usb outlet make shure your phone is debbugged then open iroot it will read your phone wait wor a while and you are golden
Click to expand...
Click to collapse
You can still use the method in this post to downgrade.
hi need help
thjubeck said:
Hi all,
I have tried different roms on my as990 (Carolina West Wireless) by using the method on reddit (HERE) and everything works just a few things to keep in mind
To get your sim to work on a custom rom you may need to change the build.prop ro.build.target_operator=, and ro.afwdata.LGfeatureset=
Take note of these settings before you try to reflash the phone. If you change one, change both if applicable.
Remember to backup your old build.prop
Backup all apns before you start using method found (HERE)
Backup build.prop
Oh and did I mention backup build.prop
The restore files can be found (HERE) and use the guide found (HERE) replacing the files mentioned with the ones in the post. If you use this method to restore you phone, the build.prop from the reddit post will not work so use the old build.prop that I'm sure by now you have backed up or you will have to get the custom .dll file elsewhere to restore.
For all who have taken the ota update, the restore method works for that too
Your carrier files are automatically restored if you use the firmware in the above post. That is to say they were for me but if anyone else test this
no guarantees but it did work flawlessly for me.
Also I am currently working on a recovery for AS990 if anyone has any ideas feel free to chime in
A couple of side notes
The method by tybskinner may also work if you flash to US990 as well, but I have not tried this yet. To do so you would need the custom .dll or the build.prop for US990
Users have reported that SIM unlock is possible by changing the the build.prop ro.build.target_operator= to global or open however I have not tried this yet
If anyone has a method to change the PRL on the device please let me know I have tried several options but no method I have tried will allow the PRL to stick
P.S. not trying to steal your thunder tybskinner just making it easier for people to find the links
Click to expand...
Click to collapse
Iam actually stuck in the in blue screen and a red number 2 factory status everytime i turn on my phone it says miniOS icant actually find any stock firmware for my lg g3 as990 it really does sucks doe becouse i had a lot of stuff in my phone that really needed but if you can help i will be really regretful ive been trying for a weak now
yorimoto1987 said:
Iam actually stuck in the in blue screen and a red number 2 factory status everytime i turn on my phone it says miniOS icant actually find any stock firmware for my lg g3 as990 it really does sucks doe becouse i had a lot of stuff in my phone that really needed but if you can help i will be really regretful ive been trying for a weak now
Click to expand...
Click to collapse
You need to hold the power button and press normal boot
The as990 stock rom is http://forum.xda-developers.com/lg-g3/general/lg-g3-as990-firmware-as99010a-t3183928
Related
I am new to xdadevelopers and this is my first thread.
I was just wondering if anyone has tried the new method of rooting our device?
Apparently, you can download GalaxyS2RootNew.zip. Unzip the file and install runme.bat.
This is supposed to work on all variants of the Galaxy S 2. You will get ROOT access but this method does not install a new kernel with recovery so you can't install custom ROM's.
Please advise if anyone has heard of this method, has tried it, does it work?
Found it on GalaxyS2Root.com website. Thanks.
just follow the stickies that's about the easiest and safest method ever
AllGamer said:
just follow the stickies that's about the easiest and safest method ever
Click to expand...
Click to collapse
I have followed the stickies and have watched videos on how to root the device using ODIN. That method works very well, but you need to back everything up first which requires a Micro SD card. I don't have a Micro SD card at the moment so can't use that method.
I was just wondering if anyone has tried the alternative method on the T989 model. It seems a lot more user friendly, easier, safer and you have no chance of bricking your phone. Thanks for your reply.
You don't need to backup anything but it is recommended in case you screw something up. Probably not going to happen if you don't flash a new rom, and stick to smaller changes like theme, or maybe a new kernel.
I've done odin method and seems pretty foolproof to me. I don't see how it can get less of a change to brick unless some other physical hardware problem intervenes in the process in mid-flash.
AllGamer said:
just follow the stickies that's about the easiest and safest method ever
Click to expand...
Click to collapse
My mistake, the stickies did refer me to the same method I was mentioning in this post. Found what I was looking for in the below thread. Thanks again, sorry I'm still new and getting the hang of the site
http://forum.xda-developers.com/showthread.php?t=1321582
Chochiwpg said:
I am new to xdadevelopers and this is my first thread.
I was just wondering if anyone has tried the new method of rooting our device?
Apparently, you can download GalaxyS2RootNew.zip. Unzip the file and install runme.bat.
This is supposed to work on all variants of the Galaxy S 2. You will get ROOT access but this method does not install a new kernel with recovery so you can't install custom ROM's.
Please advise if anyone has heard of this method, has tried it, does it work?
Found it on GalaxyS2Root.com website. Thanks.
Click to expand...
Click to collapse
Tried it last night on my new T-Mo GS2 (followed the galaxys2root.com instructions), it did not work for me. Plus side is that nothing bad happened to my phone even thought it didn't root successfully.
I have the U.S. based T-mo phone... so not sure if that's different than the phones used in Canada.
lithium133 said:
Tried it last night on my new T-Mo GS2 (followed the galaxys2root.com instructions), it did not work for me. Plus side is that nothing bad happened to my phone even thought it didn't root successfully.
I have the U.S. based T-mo phone... so not sure if that's different than the phones used in Canada.
Click to expand...
Click to collapse
I think the Tmobile (T989) and Telus (T989D) version of the phone are the same. Unless you are running version 2.3.6, then the zergrush exploit doesn't work.
Backups are overrated (lol). I never do them and completely ignored it and went ahead and ODIN flashed the recovery and then flashed Juggernaut immediately.
Took me literally 2 minutes to do.
Chochiwpg said:
I think the Tmobile (T989) and Telus (T989D) version of the phone are the same. Unless you are running version 2.3.6, then the zergrush exploit doesn't work.
Click to expand...
Click to collapse
Right - my phone did come with 2.3.6. I ended up using another method to root - which was relatively easy also.
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!
General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.
Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.
I recently installed TWRP's custom recovery on my V495 AT&T but trying to boot into recovery gives me an error and not being familiar with Flashify I missed the step to backup the stock recovery.
Can someone be kind enough to please send me the stock recovery for the AT&T V495 that is made and Flash able through Flashify? Thank you all!!
PS> Warning for others with V495 that want custom Recovery. = Once rooted you can install flashify and the instructions for V496 custom recovery all work without errors but once you try to install TWRP and reboot things may go wrong.
Can someone please upload the stock (v495) recovery created by or flashible through flashify?
I have a new/ rooted v495 that I have not messed with the boot loader. If you can point me in the right direction on getting you a copy of the stock boot loader I would certainly be happy to.
---------- Post added at 07:39 AM ---------- Previous post was at 06:57 AM ----------
I figured it out. I sent you a message with the link. You can repost it if you would like. I still do not have my 10 post quota yet to be able to provide external links.
ksimmons1571 said:
I have a new/ rooted v495 that I have not messed with the boot loader. If you can point me in the right direction on getting you a copy of the stock boot loader I would certainly be happy to.
---------- Post added at 07:39 AM ---------- Previous post was at 06:57 AM ----------
I figured it out. I sent you a message with the link. You can repost it if you would like. I still do not have my 10 post quota yet to be able to provide external links.
Click to expand...
Click to collapse
do you mind sending a copy my way. My stock recovery is also broken TIA
https://www.dropbox.com/s/xjtxfcc9f3t23k4/v495 Stock Recovery?dl=0 Courtesy of ksimmons1571 --- Thanks Buddy..
I have not tested it yet as I just saw it today and I'm at work. If you get it going please let us know. Thanks.
soft bricked v495 on stock recovery
I'm soft bricked on 5.0.2 lg support tool says I'm not in need of update at this time.so I can wait for next update but who knows when that will be lol. Will I be able to flash this stock recovery if I'm on stock recovery. ? I dont think I can thow. I'm thinking I'm going to have to extract my kdz file n use flash tools 2014. Unless I can get on twrp well I'm soft bricked n flash a ROM. But I don't see any Roms for device. Well any help will be much appreciated. Thanks in advance also if I figure it out I'll post back.
can anybody extract kdz or tot file like @Player1211 said or can anybody extract their system folder?
m_reyna_16 said:
can anybody extract kdz or tot file like @Player1211 said or can anybody extract their system folder?
Click to expand...
Click to collapse
If there's a KDZ or TOT available, you can extract it on Windows with WindowsLGFirmwareExtract-ver.1.2.5.0, available at http://forum.xda-developers.com/showthread.php?t=2600575.
My tablet is messed up, stays stuck on att logo after I manually tried extracting and installing xposed framework files. I cannot extract anything on mine.... Unless ure telling me the tot file is on that other forum? Sorry I'm on my phone and driving, can't check in detail
EDIT: read your post right this time, like I said I was driving... No, there's no tot or kde file for my tablet
Hi my friends, I am looking for a STOCK RECOVERY for my LG G Pad F 8.0 AT&T (V495). I was trying to do an OTA upgrade to 6 but after the Download and restart the installation is giving me an error because i am ROOTED. I need to flash stock recovery to be able to install new OTA upgrade to Marshmallow 6. Is someone have a 5.0.2 STOCK Recovery or maybe another idea on how can I do and upgrade to Marshmallow 6 I will appreciate any help. Thanks
Anyone leak a V495 KDZ yet? Mine is toast without a way to flash stock recovery. Bootloop of death.
Tikerz said:
Anyone leak a V495 KDZ yet? Mine is toast without a way to flash stock recovery. Bootloop of death.
Click to expand...
Click to collapse
Haven't seen one. Just the TOT without the necessary .DLL.
roirraW "edor" ehT said:
Haven't seen one. Just the TOT without the necessary .DLL.
Click to expand...
Click to collapse
Arghghghhg
Tikerz said:
Arghghghhg
Click to expand...
Click to collapse
I understand. Although there were at least KDZs for my VK810, we didn't have a known tested TOT until a few months back when a fellow user was nice enough to purchase, test and share the TOT for the VK810 from this site http://www.lgbbs.com:41/thread-838-1-1.html. Since we had KDZs available, we were able to extract the necessary .DLL from one of them.
I know someone else recently looked on that site for V495 stuff but you might want to look again and/or use Google Chrome to translate the site (slow but effective enough), and maybe even there's a section to put a request or a bounty up for a .DLL or at least KDZ, which you'd be able to extract the .DLL from. It appears the standard prices of items is $10 U.S., from what I could tell.
Not advocating the site or the fact that they sell the stuff, but when there's no other option, and at least it's not an arm and a leg.
suspected root.
trying to update after root, what exactly do we need to do to get this Update going? btw i only have a little experience rooting. and that was an HTC about 4 years ago. So far i have Flashfire installed which says can Flash OTA updates but LG is untested. im not going down that road without unlocked bootloader and a rom to pull my ass out of the bricks, unless someones has success already.
So far i haven't heard of an unlocked bootloader for The V495, can we do that yet?
i'm hearing about flashify, never used it, what does it do, how does it work?
Is there a way to remove root evidence with Android studio?
Why don't penguins Fly, do you suppose they miss it?
Sleeper0013 said:
trying to update after root, what exactly do we need to do to get this Update going? btw i only have a little experience rooting. and that was an HTC about 4 years ago. So far i have Flashfire installed which says can Flash OTA updates but LG is untested. im not going down that road without unlocked bootloader and a rom to pull my ass out of the bricks, unless someones has success already.
So far i haven't heard of an unlocked bootloader for The V495, can we do that yet?
i'm hearing about flashify, never used it, what does it do, how does it work?
Is there a way to remove root evidence with Android studio?
Why don't penguins Fly, do you suppose they miss it?
Click to expand...
Click to collapse
I can only address some of your questions.
Flashify simply flashes stuff like kernels and recoveries, but it's limited as to what it can flash and I doubt if you'd be able to flash an OTA with it. There are other apps that do the same thing with the same limitations. Also, just because it can flash something doesn't mean that's all that's required to get it to work. What I mean is, to use an example that doesn't necessarily apply to you or the V495, some LG devices require a certain older version of the bootloader (aboot) in order to be able to get into TWRP, so if you're rooted on a later release of the stock ROM (with newer bootloader) you could flash TWRP with Flashify, but you either still won't be able to actually get into it, or you might not even be able to boot at all after.
Flashfire is reasonably early in its development - having only yesterday been updated to v0.51. I've only tested a little bit. On the Verizon LG G Pad 8.3 VK810, backups seemed to work okay, but I haven't tested restoring through Flashfire. I was able to successfully flash a ROM made from the stock tablet ROM but no matter what it doesn't keep root, even when the ROM includes the necessary SuperSU.zip and flashes/roots fine in TWRP. Flashfire's Everroot option, or having Flashfire flash SuperSU.zip separately didn't work on that device either. @Chainfire said there were segfaults in the log and has no way of determining what's causing them.
I would say you are wise not to try to flash anything without having a way to recover - there are enough people on here with broken V495s with no recovery option already.
Regarding removing root evidence: From Lollipop on (at least on LG), OTAs check to see if your system (and possibly other not normally modifiable) partitions have ever been modified. It doesn't explicitly check for root, but rooting your device usually modifies the system partition. Before Lollipop, OTAs commonly only checked if the files the OTA would update have been modified from their original. OTAs don't normally contain copies of the entire files that will get updated - it contains a "delta", which is basically a list of "change this into that", as quite often files don't need to change completely - only be modifed to be up to date.
You can't reasonably "unmodify" your system manually. Only by flashing a 100% stock unrooted ROM.
*If* or when Flashfire works, it could conceivably get around a modified system partition, but it'll be challenging and might take some time for @Chainfire to support all or most OEMs/models working as smoothly as it does for the #1 primary devices he's testing it on, which I believe are Nexus devices.
I talk to penguins all the time and they do miss flying, especially when they're the prey.
roirraW "edor" ehT said:
You can't reasonably "unmodify" your system manually. Only by flashing a 100% stock unrooted ROM.
I talk to penguins all the time and they do miss flying, especially when they're the prey.
Click to expand...
Click to collapse
Ok so where do we look about getting stock rom?
And poor penguins and all their bricked devices. :crying:
Sleeper0013 said:
Ok so where do we look about getting stock rom?
And poor penguins and all their bricked devices. :crying:
Click to expand...
Click to collapse
LOL re: penguins!
I have a link for where to keep an eye out or possibly request in the post right above yours. tl;dr There's only a TOT available for the V495 that anyone's found so far. It's available in one of these threads in these G Pad 8.3 sections and I've even uploaded it elsewhere just in case the only source I noticed for the link goes down. The bad news is that there's no .DLL available to use with it, which makes it at minimum partially or mostly, at maximum fully useless.
It's fully useless without the .DLL because you can't use the normal TOT flashing software to flash it to your V495 - you need the .DLL (as I've recently written somewhere, maybe above in the post I reference or nearby), the .DLL that's necessary would probably be able to be extracted from the KDZ for the V495 - but there's no KDZs that've been made available. KDZs include the .DLL necessary, TOT's require an external .DLL.
It's partially or mostly useless in that the TOT can still be extracted to obtain the individual partitions. It's conceivable that Flashfire might be able to flash either those partitions or a flashable zip made out of them as long as you're successfully rooted, although I have no idea if Flashfire works with anything but SuperSU - I believe it specifies that SuperSU is required but there's a chance it'll work with Kingroot or another root app.
I'm fully willing to make a flashable zip out of the TOT for anyone who wants to test it - just be aware of the dangers that you might end up with a brick with no way to recover since I'm guessing that there's no TWRP for the V495 and I don't even know the root capability since I don't have that device and I only follow the threads regarding it just to help where I can. If you do have root it's at least somewhat comforting that Flashfire worked fine for flashing the stock ROM on the LG G Pad 8.3 VK810, albeit without being able to re-root it as part of the process. Let me know if you're rooted and want to test such a flashable zip with Flashfire (which would probably be the safest/most trustworthy app that has capability of flashing zips).
I don't have enough knowledge to know how to figure out how to root any device that there's no established method for, nor have I ever made TWRP for any device.
I do know that Kingroot is very invasive and is sometimes only a temporary root, requiring re-rooting every time you reboot. It puts things on the system partition that run in the background - all sorts of things not necessary for simply rooting or keeping root, so who knows what kind of calls home it makes and with what data. I've only used it before as a temporary root in order to establish an alternate way to get TWRP installed on the Verizon G3 VS985 without fully downgrading the stock ROM to a more easily rootable/TWRPable version, and ultimately my method leads you to flash a ROM that uses SuperSU so that Kingroot is completely gone anyway.
roirraW "edor" ehT said:
I understand. Although there were at least KDZs for my VK810, we didn't have a known tested TOT until a few months back when a fellow user was nice enough to purchase, test and share the TOT for the VK810 from this site http://www.lgbbs.com:41/thread-838-1-1.html. Since we had KDZs available, we were able to extract the necessary .DLL from one of them.
I know someone else recently looked on that site for V495 stuff but you might want to look again and/or use Google Chrome to translate the site (slow but effective enough), and maybe even there's a section to put a request or a bounty up for a .DLL or at least KDZ, which you'd be able to extract the .DLL from. It appears the standard prices of items is $10 U.S., from what I could tell.
Not advocating the site or the fact that they sell the stuff, but when there's no other option, and at least it's not an arm and a leg.
Click to expand...
Click to collapse
If I buy another V495 do you think I could use the KDZ/TOT extractor here to fix our V495s?
http://forum.xda-developers.com/showthread.php?t=2600575
Or maybe someone with functioning V495 could extract the KDZ/TOT or DLL for us?
Tikerz said:
If I buy another V495 do you think I could use the KDZ/TOT extractor here to fix our V495s?
Or maybe someone with functioning V495 could extract the KDZ/TOT or DLL for us?
Click to expand...
Click to collapse
Having another V495 wouldn't get you a KDZ or TOT. The KDZ/TOT extractor takes an existing KDZ or TOT file and extracts it into the separate partitions - it has nothing to do with making a KDZ or TOT out of an existing device. There's currently no way to do that. And the .DLL isn't available except inside a KDZ, it's not on anyone's running V495.
Hi, I'm note sure if I'm asking this in the right area its been a while since I've asked anything. Anyway, I'm glad to have root on N930 All devices. However I have a N930V, both root method and combination firmware. I want gain root on the combination firmware but I really don't know how. First I tried flashing the rooted Sprint Leaked firmware, rooting it perm and then flashing the combo and even vice versa. I did alot of splitting files etc etc. Still no luck. I even cracked out Linux because I'm trying to discover how does this Sprint leaked file has root on it anyway but I believe its the "user-debug" kernel. Anyway can anyone elaborate on this? And kind of guide and help me out with this I'd really appreciate it. Please don't ask me why I'm doing this I'm looking for assistance not interrogation. Thanks Vell123
I don't know much about the technical issues, but you tried the Hydra method?
Vell123 said:
I'm trying to discover how does this Sprint leaked file has root on it anyway
Click to expand...
Click to collapse
I don't believe it has root but it doesn't block ADB from pushing SU. Directly after flashing the sprint firmware before even booting it you run ADB and push the superuser.apk so it is rooted at that point. Then you flash the partial VZW firmware which doesn't include the recovery and maybe bootloader. The VZW recovery doesn't even allow ADB to push anything so replacing the recovery is a key step. Why the PH1 firmware allows you to replace it with the Sprint firmware is a mystery to me.
I know right. I havent tried the hydra method @cigars
@jellyhead I'm not trying to root. I just want to make a combo file that has root in the system because it does have a permissive kernel but doesnt have SU access
Vell123 said:
Hi, I'm note sure if I'm asking this in the right area its been a while since I've asked anything. Anyway, I'm glad to have root on N930 All devices. However I have a N930V, both root method and combination firmware. I want gain root on the combination firmware but I really don't know how. First I tried flashing the rooted Sprint Leaked firmware, rooting it perm and then flashing the combo and even vice versa. I did alot of splitting files etc etc. Still no luck. I even cracked out Linux because I'm trying to discover how does this Sprint leaked file has root on it anyway but I believe its the "user-debug" kernel. Anyway can anyone elaborate on this? And kind of guide and help me out with this I'd really appreciate it. Please don't ask me why I'm doing this I'm looking for assistance not interrogation. Thanks Vell123
Click to expand...
Click to collapse
Hi my name is Gary was curious if you ever got answers to your question or if you ever figured out an answer.I belong to a group trying to find root for phe fimware was wondering if you had figured anything out thanks
Sent from my SM-N930V using XDA-Developers Legacy app
garyinskeep1 said:
Hi my name is Gary was curious if you ever got answers to your question or if you ever figured out an answer.I belong to a group trying to find root for phe fimware was wondering if you had figured anything out thanks
Sent from my SM-N930V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi Gary unfortunately no I have not found way to 1. root the phe firmware besides using combination files and 2. my answer hasnt been answered either. I'm assuming your device Note 7 device has been blacklisted or blocked via the imei and model number. it sucks i know but I'm still looking and if not anything I'm considering building on the combination file because with combination file you can call and text but you literally have to install all your apps with adb and or sd card if you have one. its a bit of a pain but you also can root and change the model number too
Vell123 said:
Hi Gary unfortunately no I have not found way to 1. root the phe firmware besides using combination files and 2. my answer hasnt been answered either. I'm assuming your device Note 7 device has been blacklisted or blocked via the imei and model number. it sucks i know but I'm still looking and if not anything I'm considering building on the combination file because with combination file you can call and text but you literally have to install all your apps with adb and or sd card if you have one. its a bit of a pain but you also can root and change the model number too
Click to expand...
Click to collapse
I have been able to root one of my note 7 i had an original first gen that was able to be rooted can you hit me up on messenger i would like to ask you a question.
Sent from my SM-N930V using Tapatalk
i dont know how to see your messenger. just email me [email protected]
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Lee KZN said:
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Click to expand...
Click to collapse
You will need to get hold of the stock firmware from somewhere like Sammobile and flash back to stock using ODIN. There's tons of guides knocking about on here for the step by step. The damage is done though as far as any Knox related features go, it's like a fuse that blows when you root and you can never fix that.
Having said that, biometrics should have never been affected by rooting so that's a bit unusual. Flash stock and set up from scratch then go from there, could be faulty also
Thanks for the guidance Dave. I'll search the forums for the steps.
For clarity, when I say biometrics didn't work, it works allow me to record etc, but when I tried to enable it, like on my banking app, it wouldn't allow me. This is how I eventually figured out my phone was rooted. While I know the benefits of being rooted, a normal everyday user like myself, certainly won't benefit from it.
I've had a Samsung my entire life, and always saw the secured by knox logo... When you say damage has been done, does this mean that all my security in the device, such as my banking details etc, may be compromised?
Jees. I hope not. As this would really freak me out...
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Lee KZN said:
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Click to expand...
Click to collapse
The last letters are the region/operator of the Rom. Not necessarily has to be the exact description, the really important are the first that indicate model number.
Ok. So have downloaded Odin and am busy downloading the flash firmware.
May I please be so bold as to ask someone on here to please share a link tot he step by step guide that I will need to follow in order to flash my phone back to the original boot thingie :silly::silly::silly:
I have tried to search but seem to only come up with a nexus thread with no mention of Odin.
~Sorry to ask, but little overwhelmed LOL and want to make sure I do this properly and not screw up my phone.
REAL noob here, so apologies if I come across lazy and getting others to do the work, but am really grateful for the help.
Maybe I'm searching incorrectly???
I found this somehow....
Is this it?
https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
**fingers crossed**
Can you unlock your phone with biometrics? Im guessing only the banking apps don't work because it's rooted. If i remember correctly most banking apps and maybe Google pay(not sure about that) stop working after rooting because the phone is "compromised" and it's not safe. You have to hide your root status from these apps and they will work properly then. Maybe someone else can help you with that because i do not remember how to do it.
Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????
Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????
if the phone was bought as new, go back to the dealer and demand a new one that is not rooted.
could also be that your husband rooted the phone and installed software that keep tabs on what you do.