Related
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
So I rooted my Note 2 and installed rom manager to so I could install a zip File and the phone rebooted and I got this massage:
System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help
Volume up/home/power just boots to this message every time. So does Volume down/home/power.
It will not boot into Download mode or odin mode.
Please help.
Thank you.
Sounds like you tried to use ROM Manager to install CWM, an alternate recovery before unlocking your bootloader.
What version of software did you have - 4.1.2 or 4.3?
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
By the by, your phone IS recoverable, but the surefire method (Verizon Software Update) will also force you to upgrade to 4.3 and you will be locked into the new, secure bootloader. No exploit to unlock this bootloader has been found, so no custom ROMs can be installed once you have 4.3.
If you already had the official 4.3 OTA, you're locked already and it won't change anything to use Verizon's software to restore your phone.... though you undoubtedly tripped the KNOX counter trying to flash a custom recovery in that case.
I was able to get in to odin mode but it gets allmost done and it fails its saying unsupported version
I am running ota 4.3
Sent from my SCH-I605 using xda app-developers app
As far as I know there is only one method top root that works on 4.3 right now but it doesn't unlock the boot loader
Sent from my SCH-I605 using xda app-developers app
I've accidentally done what OP did too, having been unaware of the changes to prevent custom recoveries.
I've tried using Odin to flash back to stock 4.1.1 but apparently that didn't work, and I guess the custom recovery is still triggering the error.
Is there a way to reset the recovery to stock now or at least bypass Verizon's system check?
I have had this happen as well. Is there any way to unlock this phone using any methods on here? Thanks.
Same issues, anyone have any luck on 4.4.3?
Trouble installing CWM/TWRP on rooted Note 2 SCH-i605 4.4.2
BrianAnim said:
Same issues, anyone have any luck on 4.4.3?
Click to expand...
Click to collapse
No luck on 4.4.2 -- Trouble Installing CWM/TWRP on Rooted Vz Note 2 SCH-i605 4.4.2
The title of this post summarizes my present challenge ... I have not been able to successfully install CWM or TWRP using any popular method. For example ODIN attempts fail each time, no matter what I try, e.g. swapping USB ports, reloading drivers, removing batteries, sim cards, SD card, changing cables, turning virus protection on/off, battery charge level (50 thru 100%) ... and various combinations of these approaches. ROM Mgr and other Flash apps don't get it done -- well, to be fair, they may be getting it done, but on reboot I receive an error message "System software not authorized by Verizon Wireless has been found...." blah, blah, blah. --SO, does anyone have any thoughts or approaches they might recommend? I'm really stumped. And to make it all the more vexing, I'm a novice or whatever is just before novice. I've enjoyed getting this far and have recovered from a few soft bricks along the way. The first time was worrisome, but now I don't worry so much. I've lucked out and found a lot of great guidance on forums, like this one and others. But so far, I haven't landed on the trick of getting past 'whatever roadblock(s)' are in place on this Note 2 SCH-i605 4.4.2 set-up. I'm stumped.
fibertowner said:
No luck on 4.4.2 -- Trouble Installing CWM/TWRP on Rooted Vz Note 2 SCH-i605 4.4.2
The title of this post summarizes my present challenge ... I have not been able to successfully install CWM or TWRP using any popular method. For example ODIN attempts fail each time, no matter what I try, e.g. swapping USB ports, reloading drivers, removing batteries, sim cards, SD card, changing cables, turning virus protection on/off, battery charge level (50 thru 100%) ... and various combinations of these approaches. ROM Mgr and other Flash apps don't get it done -- well, to be fair, they may be getting it done, but on reboot I receive an error message "System software not authorized by Verizon Wireless has been found...." blah, blah, blah. --SO, does anyone have any thoughts or approaches they might recommend? I'm really stumped. And to make it all the more vexing, I'm a novice or whatever is just before novice. I've enjoyed getting this far and have recovered from a few soft bricks along the way. The first time was worrisome, but now I don't worry so much. I've lucked out and found a lot of great guidance on forums, like this one and others. But so far, I haven't landed on the trick of getting past 'whatever roadblock(s)' are in place on this Note 2 SCH-i605 4.4.2 set-up. I'm stumped.
Click to expand...
Click to collapse
As far as I know if you do official OTA 4.3 and above update you bootloader is locked/secure and you cannot install a custom recovery therefore no custom roms. at least the old fashion way.
My phone does not have these issues so I haven't looked into whats out there. You may be able to still root the phone at least, and as for custom roms I would look into the safestrap options if there are any.
If one gets a note 2 like warranty replacement or for some other reason in the recent past or future check immediately when turning on if you are 4.1 or 4.3 and dont take any OTA. You may get lucky and have old software on it.
Edit: Looking around maybe this will help you. http://forum.xda-developers.com/note-2-verizon/help/finally-safestrap-recovery-v3-72-nd7-4-t2968273
I had updated to the official OTA 4.3 and the only way heard of was to send your phone into mobiletechvideos and they will downgrade your phone back to 4.1.2 I don't know the details on what they do, but it involves taking your phone apart. I sent my GN 2 in on a Wednesday and I had it back by the following Thursday. I re-rooted and I am back running cm12. I talked with Josh on the phone regarding replacing my rear housing at the same time. Nice guy, very helpful. I ordered the rear housing and sent it with the phone. They changed it out at no cost.
Sent from my SCH-I605 using Tapatalk
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
i have this model but i updated it before I knew it would prevent me from rooting it... any way you could upload a backup of your firmware that I can use to downgrade to?
How can you beat a $9 phone
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
Just picked this phone up too, any luck on getting a ROM for it?
I picked one up....couldn't resist for just $9.82. I didn't let it update, so I was able to root it with Kingroot 4.6. Quite snappy after all the bloatware was removed. Have about 1.5gb of internal memory left, but added an 8gb microSD. I haven't been able to findy any recovery, doubt one exists. Nice little emergency phone to have in the car or backpack.
Just picked this phone up as well, and KingoRoot doesn't work. I wasn't prompted for a firmware update when I first cranked it up so I guess I'm on some version that isn't supported? Can anybody clarify what the status of this device is currently? I've got the Tracfone version.
I just rooted my LG L15G tracphone with KingRoot and it worked immediately. Great!
Next step is to get this 10 dollar phone unlocked.
By the way, my firmware version is: Android 4.4.2
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (http://www.imei-unlocker.com) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
anuraj1 said:
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: **Link removed**
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (**Linked Removed***) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: **link removed **]
Click to expand...
Click to collapse
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Root with Root Genius
I have root my LG L15G (Android 4.4.2, kernel 3.4.0+, software version LGL15G10f) with Root Genius for PC v3.0.85.
Of cource, before rooting "Developer options" must be unlocked (5-8 taps on Settings>About Phone>Software information>Build number) and turned on; in "Developer options" must be selected "USB debugging".
After this connect phone to PC. All phone drivers must be installed.
Run Root Genius. When program will ready and say about connect with LG L15G - press one button. After 2-3 minutes root is enabled.
Titanium Backup works. But I have no ideas for unlock the phone to make a possibility work in other GSM-networks, except TracFone's.
Hmm, I had tried Root Genius and that didn't work for me (and yeah I did enable USB debugging. I apparently was using an older build of Root Genius. But I found and used the build you used and still get the unsupported model error. ). My software version is as follows:
Android Version: 4.4.2
Baseband version: M8610B-AAAANAZM-1.0.6060
Kernel version: 3.4.0+
Build number: KOT49I.LGL15G11a
Software version: LGL15G11a
There does appear to be some differences in the software version of mine vs the post above me. I'm guessing they changed something. But that's odd as my phone was brand new just like yours assuming you got it around the same time as me.
EDIT. Ok some bad news. Looks like there was a newer software update (that my phone apparently came with) that blocks root and even prevents download mode from working. (I had attempted to boot into download mode but none of the button combinations work and even the root scripts I've tried can't get it to reboot into download mode)
Seems I'm stuck with a phone I probably can't ever root.
It seems it can still be forced into download mode by using a "56k/130k/910k cable" cable (special cable with resistor on one of the data lines). But they are running for $18 on ebay and way to damn expensive for a simple cable with a resistor installed. Resistors are probably only worth pennies each, so they are way too expensive to be charging that much for it.
If I had a such a cable, the root script I had tried awhile back might have worked as it needs to get the phone into download mode to finish the process.
There seems that there's little hope for your phone but I may have a solution. My LG Sunrise got updated as well and got root access with the update. You can use King Root but not Kingo.
Look it up on Google. So far I've had no success on getting to the recovery mode.
I've tried rooting with KingRoot. It will just say it failed after 20% (sometimes it goes higher, but always end with it saying this).
Note that unlike your phone, mine already had the latest update out of the box.
Apache Thunder said:
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Click to expand...
Click to collapse
If you still haven't got root yet,for me it was McAfee that's been blocking Kingroot every since Nov.
Even though I never set up an account,it was the culprit..I opened the McAfee app created the account and Disabled.
Went to settings,ALL apps,then opened McAfee..Scrolled down to ''manage space'' and deactivated and hit force stop.
Then I ran KingRoot version 4.8.0 from this site.My device rebooted at around 30%,went back to KingRoot and it finished rooting.
THANK YOU!
It took a few tries, but after disabling McAfee's root protection (It completely skipped my mind that this stupid app would have a feature that would interfere. ) KingRoot definitely did it's thing. (I had to re-attempt twice because once it rebooted and failed. So I had to kill the app again and try again. That time it rooted without restarting).
I've already uninstalled McAfee and a few other system apps I need to get rid of. (McAfee on a $10 phone? Yeah..... No.... I'll take my chances. )
I also replaced KingRoot with SuperSU and uninstalled Purify and the KingRoot app that installed the root. After cleaning out unneeded bloatware, this phone is pretty responsive now! It used to lag a little and not register touches some times. But after cleaning out the bloatware (McAfee was probably the main source of the lag) it runs pretty well now!
EDIT:
Ok minor issue. I can't seem to uninstall Chrome (since it's a system app on this phone). It keeps reinstalling it self. It won't stay gone. What would be causing that? I wanted to move Chrome to SD so it doesn't take up space. But this particular phone won't let me.
Seems to happen with Polaris Office as well. Not a big deal at the moment. I can just freeze this app so it won't take up any CPU time/ram. Freezing it seems to work fine. Uninstalling it just results in it mysteriously reinstalling it self....
Does yours lose root after rebooting? I tried to run 'adb reboot recovery' for giggles and SuperSU no longer had root when it failed to start the local and booted normally.
---------- Post added at 04:27 AM ---------- Previous post was at 04:19 AM ----------
anuraj1 said:
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
Click to expand...
Click to collapse
I have the Android SDK installed on my desktop but the TWRP porting guide by Dees_Troy is a little bit too vague for a first timer. I was able to extract the stock recovery using dd this afternoon.
I haven't tried to reboot mine into recovery mode. But root sticks when doing normal reboots.
recovery/rom LG-L15G
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
DroidHost said:
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
Click to expand...
Click to collapse
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
anuraj1 said:
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
Click to expand...
Click to collapse
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
DroidHost said:
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
Click to expand...
Click to collapse
That's fantastic. If it would help, I have one of those variable resistor cables that some LG phone requires for supporting baseband or entering the bootloader.
This is the cable I have: http://m.ebay.com/itm/131321398015
It is described here as well: http://forum.xda-developers.com/showthread.php?t=2069564
Ok I really did it this time. Here is what i stupidly did. my phone was on the 35b update so I used the tot method to take it back to 10b. I rooted and then used the ota updates to upgrade to 12b, and I believe to more times (of course after telling supersu to stay active thru the updates) until I got to the update that would take me over into lollipop. I downloaded the update, but then needed to charge my phone i noticed, so I told it to postphone the update. After I had a somewhat decent charge I told my g3 to update and it immediately went to twrp recovery. Thinking this odd I tried to reboot and it started to bootloop inside twrp. I tried getting it to do a recovery of a save that i had previously had downloaded to my ext sd before I lost root taking the 35b update and it went all the way thru and said success. But as soon as it rebooted into what should have been the system, It instead started bootlooping at the lg logo and hasnt stopped since. I not have got it to go to recovery but it is stock and twrp is now gone but every option results in simply restarting the bootloop. I plugged into my computer to try both tot and kdz only to have them both fail because now my computer no longer recognizes my device. During the stage that I was in recovery trying to use different predownloaded roms is when I realized that my imei has also been erased, which is why I assume my computer cant recognize it anymore. I know I probably have a list of mistakes that could have been avoided but I tried to do this myself and I admit i simply need the vast knowledge of the xda. Please someone guide me in the right direction to fix my phone. I don't have alot of money to spend to replace it and just really need to fix this one please.
ronnieshane1 said:
Ok I really did it this time. Here is what i stupidly did. my phone was on the 35b update so I used the tot method to take it back to 10b. I rooted and then used the ota updates to upgrade to 12b, and I believe to more times (of course after telling supersu to stay active thru the updates) until I got to the update that would take me over into lollipop. I downloaded the update, but then needed to charge my phone i noticed, so I told it to postphone the update. After I had a somewhat decent charge I told my g3 to update and it immediately went to twrp recovery. Thinking this odd I tried to reboot and it started to bootloop inside twrp. I tried getting it to do a recovery of a save that i had previously had downloaded to my ext sd before I lost root taking the 35b update and it went all the way thru and said success. But as soon as it rebooted into what should have been the system, It instead started bootlooping at the lg logo and hasnt stopped since. I not have got it to go to recovery but it is stock and twrp is now gone but every option results in simply restarting the bootloop. I plugged into my computer to try both tot and kdz only to have them both fail because now my computer no longer recognizes my device. During the stage that I was in recovery trying to use different predownloaded roms is when I realized that my imei has also been erased, which is why I assume my computer cant recognize it anymore. I know I probably have a list of mistakes that could have been avoided but I tried to do this myself and I admit i simply need the vast knowledge of the xda. Please someone guide me in the right direction to fix my phone. I don't have alot of money to spend to replace it and just really need to fix this one please.
Click to expand...
Click to collapse
im fairly knowledgeable with the g3, but im not sure i can help you
the consequences of the minor mistake you made (you cant take an ota with twrp on) are unusually severe.
we have a zip to flash that would have fixed it, but it needs to be flashed in twrp, and i dont believe i have ever seen twrp get removed while making this error.
im thinking the only fix is flashing stock. i would try different usb ports, re-install the drivers, and even try another pc, to get it recognized so you can flash it.
if there is some other fix im forgetting maybe someone else will suggest it, but in a bootloop with no twrp to flush the update, i believe your in a bad spot if you cant figure out how to get it to flash.
sorry
that is how my luck goes, thanks for looking into my problem.
bweN diorD said:
im fairly knowledgeable with the g3, but im not sure i can help you
the consequences of the minor mistake you made (you cant take an ota with twrp on) are unusually severe.
we have a zip to flash that would have fixed it, but it needs to be flashed in twrp, and i dont believe i have ever seen twrp get removed while making this error.
im thinking the only fix is flashing stock. i would try different usb ports, re-install the drivers, and even try another pc, to get it recognized so you can flash it.
if there is some other fix im forgetting maybe someone else will suggest it, but in a bootloop with no twrp to flush the update, i believe your in a bad spot if you cant figure out how to get it to flash.
sorry
Click to expand...
Click to collapse
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
ronnieshane1 said:
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
Click to expand...
Click to collapse
I don't know if trying LG Flash Tool 2014 with a 10B KDZ would work any better than the TOT method without an IMEI.
ronnieshane1 said:
got my computer to see it but now i cant flash back because I have no imei. Any fix I can do from download mode?
Click to expand...
Click to collapse
there is a thread here in help somewhere on how to fix your imei. you would have to look into that, i really dont know how its done or whats possible.
This is a beta release of the tools I use to unbrick LG G3's (vs985 only). If you have tried everything and your VS985 LG G3 seems dead, this is a good "last resort" option (not dangerous, just can be a PITA). It includes many publicly available files, including common stock KDZ's and such. Most of it to be frank is just a repackage of existing things with an "instructions.txt" inside for your viewing pleasure, but there are a few tools (most notably BoardDiag) that have seen personal tweaks by me to support newer hardware, and some tools seldom seen anywhere else. This kit is particularly useful for reflashing stock 47A to ANY Vs985, including the new rollback unfriendly variants that seem to be popping up as I noted here.
It's a big (nearly 4GB file), so expect some download time.
The readme follows below, unhide to get an idea of the process. You WILL end up with 47A at the end of this, and all that entails. But it is better than a dead phone.
Here is the procedure to debrick basically any LG G3 vs985.
1.) Load the qualcomm drivers, and latest LG/Verizon drivers for your device. Make sure the drivers actually load, that's easiest on W7. Otherwise you will need to some fancy stuff this guide does not cover.
2.) Follow this guide, using the included "TOT" folder for the target dir instead of extracting your own:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Use the boarddiag v2.99a first, and if that does not work, try unchecking the emmc test. If that still does not work, use the v3.99c variant folder and also try it without emmc test.
Once that is done, do this yet:
3.) open "G3_fix." Run "androidbrick_G3_fix" inside.
4.) Now AFTER the app launches, connect your phone in qualcomm 9008 mode (note your port #). If you don't have it in that mode already, you will need to short a test point. Follow this:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
5.) Now, from the drop down select "LGVS985_AVRZ_VRZ" It will ask if you can fix or something similar if it finds issues. Say "yes" and point it to the subfolder G3_fix > AP_Chip > MSM8974_G3 > Recovery
6.) It will finish and reboot. You should be done with the hard part, now flash the 47A KDZ included in the download using download mode which should now work! You will be at 47A stock btu you will have a phone again!
47A Flash tool is included in the folder "LG Flash Tool 2014." The KDZ is inclucded as the file "VS98547A_01_0314_ARB01.kdz." Use the following guide to flash it:
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Yes, it is a beta, mostly because my instructions are probably not totally "newb-friendly" yet. The tools themselves work fine and are largely peer tested repacks with small tweaks. Comments on how to improve the process/documentation are welcome.
Here is the link:
https://www.androidfilehost.com/?fid=24651442761498806
Oh, and shameless plug: If all else fails, I do buy software bricked LG G3's of any type of brick provided cosmetics are "Fair" or better and the ESN is clean. Or, I also offer commercial debricking services. I charge about $35.00 per debrick and include return shipping to the domestic US in that bill. If you want to give that a try, contact me. I offer you complete refunds if I can't fix it!
Heatware below to prove my reputation elsewhere and here:
http://www.heatware.com/u/63621
Nice work. Having one place for everything is pretty handy.
R-T-B said:
This is a beta release of the tools I use to unbrick LG G3's (vs985 only). If you have tried everything and your VS985 LG G3 seems dead, this is a good "last resort" option (not dangerous, just can be a PITA).
Click to expand...
Click to collapse
can you look at my post here and see if you think you unbrick method my phone? Thanks
http://forum.xda-developers.com/verizon-lg-g3/help/recovery-problem-please-help-t3429052
sorry, deleted post,
It should work, but you'll likely have to open your phone and short some test points... that's why I consider this kit "last resort"
simpson1190 said:
can you look at my post here and see if you think you unbrick method my phone? Thanks
Click to expand...
Click to collapse
Hi!
It's general forum etiquette not to quote the entire first post (once or twice ? ) or at least edit to quote exactly what you're replying to. Just wanted to let you know.
I agree and a double post and the full quote was a mistake. I was a bit impatient with my computer and Internet and clicked the post button a bunch of times. I apologize.
simpson1190 said:
I agree and a double post and the full quote was a mistake. I was a bit impatient with my computer and Internet and clicked the post button a bunch of times. I apologize.
Click to expand...
Click to collapse
No problem! Just wanted you to be aware. Thanks for editing your post!
Hey R-T-B,
From the other thread. Here's my deal. My PC is windows 7 with test mode enabled. Qualcomm and LG drivers installed. I don't have the original LG charge cable but am using a good quality one, I think anyway. I have 2 phones that are bricked. Neither are "k" variants. One is black. One is white. The black one, I bought off eBay from someone who just got it warranty replaced. It had 47a on it. I tried to KDZ downgrade with special DLL. Ever since, it's been stuck in hard brick. I tried many people's boarddiag's and the android_g3_fix. I tried to follow many posts on XDA and other sites. My PC recognizes it as Qualcomm 9008. All versions of boarddiag get the "error device not found in dload trying flash programmer" or PMIC error when "AP check" is not checked. So, I thought I'd buy another phone(the white one) that has a broken screen and swap the motherboards. The original owner of white one took a 47a update and got boot loops. It was cheap so o bought it thinking I could downgrade or flash the 47a KDZ to fix it. It rebooted during the flashing and now gets detected as "androidnet USB serial port" and "androidnet modem" in my PC. I have not shorted the pins on it in fear that it will act like the black one. I also have given up on these for about a month now until you brought out your fix that I just tried but didn't work for me. Might be that cable. Any other details I left out or forgot, let me know.
I would definently try shorting the pins on the white one. In my experience, it can't make things worse.
Alternatively, you can try forcing qualcomm mode by going through the "download mode motions" Sometimes (rarely) this'll trigger qualcomm in my experience.
If you want a pro to take a look at your phones, I would be willing. I do not charge if I can't debrick, and it's generally $30.00 per phone.
I'll give it a try when I get a chance. I did end up buying a G3 with kitkat on it so I was able to root that and now have a working backup phone. I just feel I wasted the money on the other phones so I might want you to take a look at it. I will let you know. Thanks.
danbest82 said:
I'll give it a try when I get a chance. I did end up buying a G3 with kitkat on it so I was able to root that and now have a working backup phone. I just feel I wasted the money on the other phones so I might want you to take a look at it. I will let you know. Thanks.
Click to expand...
Click to collapse
Feeling like I "wasted my money" is what got me into refurbing, be careful, it can be dangerous, as the pay isn't all that great... lol.
R-T-B said:
Feeling like I "wasted my money" is what got me into refurbing, be careful, it can be dangerous, as the pay isn't all that great... lol.
Click to expand...
Click to collapse
That's kinda why I ended up with 3 backups. Broke one, bought another to try to fix it, broke it. Bought a third that I knew I could root. Too bad that Groupon deal didn't come up sooner.
Thanks man I owe you huge time. My phone resurrected by your kit. Thank you so much
alich3451 said:
Thanks man I owe you huge time. My phone resurrected by your kit. Thank you so much
Click to expand...
Click to collapse
No problem! Glad to have saved at least one phone with this! Thanks for reporting your results.
R-T-B said:
No problem! Glad to have saved at least one phone with this! Thanks for reporting your results.
Click to expand...
Click to collapse
Hey RTB am I safe to downgrade my G3 like I did a couple weeks ago by tot and a special dll file? I mean there's no problem in doing that after coming back from brick... .
alich3451 said:
Hey RTB am I safe to downgrade my G3 like I did a couple weeks ago by tot and a special dll file? I mean there's no problem in doing that after coming back from brick... .
Click to expand...
Click to collapse
You can try. Some recent models will refuse to downgrade after being on 47A, but that's probably not the case if you were able to downgrade before.
At worst, you can always run through this again. It seems the only thing that is consistent with LG G3's though is their inconsistency, so I can't promise anything!
R-T-B said:
You can try. Some recent models will refuse to downgrade after being on 47A, but that's probably not the case if you were able to downgrade before.
At worst, you can always run through this again. It seems the only thing that is consistent with LG G3's though is their inconsistency, so I can't promise anything!
Click to expand...
Click to collapse
tried and succeeded...
Do you know that you can debrick a LG G4 VS986 with your Tools?
Sent from my VS985 4G using XDA-Developers mobile app
Time of Awakening said:
Do you know that you can debrick a LG G4 VS986 with your Tools?
Sent from my VS985 4G using XDA-Developers mobile app
Click to expand...
Click to collapse
Unlikely, sorry.
EDIT: Or is this a report and not a question? If it works, I'd be shocked, but I've heard stranger.