Related
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
boathead said:
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
Click to expand...
Click to collapse
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
Why can't you get into recovery?
Are you choosing recovery mode via the bootloader menu? I didn't think it was POSSIBLE to wipe recovery from within recovery.
Even if you can't, trust me, Doing a factory img restore, or using fastboot to flash custom recovery again is VERY easy. To get the SDK that has needed fastboot tools, go here http://developer.android.com/sdk/index.html#ExistingIDE
And grab the needed exe for your setup(windows 64 or 32bit). Make sure you are getting the "ADT bundle" it's what has needed platform tools. Then just run the exe and follow instructions.
Now u COULD also just Google search for Wugfresg toolkit, and download and use that. Its very easy to use as well. I just prefer to have adb and fastboot installed to my computer so that I can always be good to go. Plus I use Linux so Im not able to use Wugfresh, but knowing how to just use fastboot and adb also makes ya feel like a boss(even though is pretty simple lol)
Don't worry, there is hope, and it's not gonna be difficult. You'll be up again in no time.
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
boathead said:
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
Click to expand...
Click to collapse
Of course!
I'm always checking in these forums, and I use Tapatalk, and have actually grown fond of Tapatalk notifications, so I SHOULD get a notif if you post back or PM(though I prefer to keep in thread, that way someone else searching for answer to similar issue can find a helpful thread as well)
Yea it sounds like your little one got into twrp and most likely wiped all of /data and /system. Instead of just a regular factory reset which would have left your stuff like flashable zips and all still in /sdcard. That sucks! I've actually done that on accideHahaha
hile back(a mistake you only make once to wipe all of /data AND /system lol, even though can pretty easily be fixed)
Sounds like you could use adb sideload or push to get ROM/gapps zips back on the device, or just go with a total device factory restore, whichever you choose at this point should work just fine.
I'm not sure if there is a way to do this yet, but I've always wanted to put a pin code lock for TWRP. That way if my nephew ever did find his way into there when using my phone, he wouldn't be able to do any damage. If it's not a part of custom recovery yet (I haven't looked actually lol) it would be awesome if someone found a way to add that feature in. Could save a lot of us the hassle in cases like this! Hahaha
I'll check back in the morning and randomly tomorrow (some of the day I won't have a connection, I use Gnex strictly on WiFi) to see if you need any help/tips/clarifying of any steps needed. Once you do this restore process once, you'll be amazed at how easy it can be, and as long as you keep the files on your laptop, you'll be ready to go if you ever need to do it again.
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
boathead said:
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
Click to expand...
Click to collapse
That temperament is something that is gained. MOST of us have been in that "oh holy crap what do I do now?!?! Im not prepared for this!!" Moments (my first one was on my birthday back when I had DroidX2, and didn't have my own computer to restore it using RSDlite sbf flash.. I accidentally flashed something that didn't work, and was left with no OS stuck in bootloop with no way to get into the bootstrap recovery we had...was without device for 3 days until I could get to a coworkers laptop!! Lol!!!) But the stress goes WAY down after you've restored device once or twice and have the tools at the ready with basic understanding of the steps at least
And as for drivers, I apologize for not warning/informing about that. I forgot that you mentioned you had multiple driver packages downloaded and i was going to clarify which to use(on a Linux setup you don't need drivers and it been a while since I used windows for my device so drivers aren't usually on my mind lol) I think a lot of people use the PDAnet drivers. But if you are connected to internet and just put device in fastboot mode and connect to computer, I think it will automatically find and install the correct drivers needed for fastboot/adb access.(the toolkit can also be used to install correct drivers I believe)
And don't worry, I wouldn't call using toolkit the "cowardly way". SOME people detest/despise use of toolkit since they think it takes away from learning and understanding how to do it without a toolkit. But when you use a toolkit you usually see command prompt correct? (Or at least a setting so you can SEE what it is running as far as commands) so you get to see what its doing, which helps beginners start to grasp the concepts of what it is doing.
Trust me, if you can use the toolkit correctly, you can easily transfer that knowledge to just using fastboot or adb commands.
by the way, fastboot is what's used for factory image restore. ADB is for pushing/pulling files, taking logs, sideloading a ROM/gapps zip that isn't on device, taking/restoring adb backups of system and or data, things like that. Think of adb as the "taker and giver". And fastboot as the "img installer/booter"...imgs being anything from system img files, to data partition img files, boot.img(aka kernel), recovery.img, bootloader update img, radio imgs. Things like that
The reason the knowledge from using toolkit easily transfers over to using just straight up fastboot for example is because of how they word the choices and menus. You will see it says something like "use fastboot to flash new recovery img", which the fastboot command for that in command line equates to "fastboot flash recovery "NameOfRecoveryImage.img" "
(With no quotes of course, and replace "NameOf...." With the actual file name of the recovery.img you have downloaded, and you can rename the downloaded recovery img file to something easier to type out if you want to also)
Basic structure of using fastboot command would be as follows:
fastboot[space]command[space]partitioname[space]filetobeused
Which after used once or twice is very easy to grasp basic usage
So are you able to at least boot into OS now? Also, make sure if you are trying to flash a KitKat ROM, that you install the 2.7TWRP recovery, anything earlier won't work correctly for 4.4based ROMs.
Again, any trouble feel free to ask.
(And apologies for the long rambling posts lol)
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
boathead said:
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
Click to expand...
Click to collapse
what security do you use on your router? if WEP try changing it. the gnex has issues sometimes with using WEP secured WiFi AP's
also, if using a 5ghz network, I can only get mine to connect to that on channel 153. there are only a certain number of 5ghz channels supported.
might also want to just try forgetting WiFi network and re add?(if it restored the access points by any means including Google backup/restore)
and make sure your router isn't rejecting the Mac address for some reason(and some people will suggest reboot of the router to see if that helps fix it, which I've seen fix many connection issues)
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
boathead said:
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
Click to expand...
Click to collapse
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
ashclepdia said:
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
Click to expand...
Click to collapse
wpa2...but i've even disable all security to see....i've disable firewalls...nothing. it is an arris router that time warner cable provided when i moved to my new place.
and i my phone does show me as connected to my network...just can't get into google. and the phone works just fine at my work. as you know, i've been through several roms and an entirely new OS...so it cannot be the phone...can it?
been through this entire threads, and no joy.
http://forum.xda-developers.com/showthread.php?t=2110225
if you have any ideas, post away. i will be away from access to the internet for a few days, so i won't even have a chance to check in here, but any info in the meantime would be most thanked.
boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
my samsung s5 had the same problem. i wiped out everything and it says i have no os no nothing. i hope if anyone can help, i will be pleased.
the only question is that "how can i get an os and get my phone working"
ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
The same thing happened to me right now, while I was installing CM13 in my Lenovo Zuk Z1. I took a backup from TWRP and copied the same to my pc. Then I wiped all the data from my phone using TWRP. Then I plugged in the Usb back to copy the downloaded files of CM13 to my phone but my pc is not showing the Internal Memory of my phone. I am so freaked out right now. I dont have an OS in my phone and I am unable to restore what I backed up. I am just stucked in TWRP. Guide me through to install CM 13 or atleast revert back to where I started. Any help is appreciated.
Hey XDA,
So I need your help with something. This morning I woke up to my LG G3 D855 v10i stuck in a bootloop, for no apparent reason. I'd set an alarm to go off, and it did but only for a second and not the full 10 seconds it should have, and then it shutdown and went into a boot loop with the LG Boot Animation and the notification light was flashing yellow. I pulled the battery out, put it back in, and then restarted it. I got the same boot-loop except the notification light was alternating between blue and green as it should have been, but it was still stuck. So I pulled it out, tried again twice more, until the phone finally decided to boot. Then the phone boots, and I see my customized lockscreen with my lockscreen image and lock code, and then it goes to the screen to setup the phone completely again; Like it's a brand new phone with nothing on it, except that some of my apps were opening/running and I could see them doing things while on the setup screen. At this point I knew something was up, and I suspect a corrupted file or something on the phone, and then I started getting a whole bunch of errors on the phone itself, such as "Gmail has stopped working", "com.google.gapps has stopped working" "YouTube has stopped working" and basically all the Google apps had stopped working, but mine were still running fine.
So, after a whole day of trying to flash a new KDZ in Normal Flash mode to the phone using the LG Flash Tool 2014 here on the forums, and failing over and over (Yes, the phone was in download mode, COM port on the PC was set to 40 and I tried port 41 as well, I even put the .kdz file itself in the LG Flash Tool 2014 folder as it says to do, but nothing worked and I kept getting all this http://gyazo.com/158044ffe14287157a4388a2a42680c0 ) So I just decided to do a hard factory reset on the phone itself. I've now updated it and everything's fine, it's just a vanilla LG G3 with none of my apps on it.
Now I'm onto my current predicament. I've installed LG PC Suite when I first got the phone and since then I've done 2 full backups of the phone using it, as seen here ( http://gyazo.com/cebada2d6b06cd116afce22d8caad8bc ) but LG PC Suite recognizes NONE of them as seen here ( http://gyazo.com/3359f520739ab229334d9fa9d4e1edd2 ). In the area down the bottom where it should list the backups I've done, it doesn't list anything, even though the backups are in the correct folders themselves. Since factory resetting the phone wiped the internal memory, I lost all 32GB of my Apps, Photo's, Videos, and all my App Data. I NEED a way to get LG PC Suite or something else (Even ADB?) to push the backup/backup files to the phone and restore it. As you can see here, when LG PC Suite backs up the phone, it creates all of this data ( http://gyazo.com/a62ad1efa0e127c1b5830562965ed50a ) but in LG PC Suite's Backup/Restore device area when my device is plugged in, it shows no backups. I've even tried changing the directory the backups are in, re-installing PC Suite, everything.
I just really need a way for the PC, ADB or LG PC Suite to push all the files onto the phone and restore them, copying the files to the phone and using the G3's built-in restore app doesn't work either; All backups done by the phone were on the internal storage which was wiped with the factory reset
If someone could come up with a solution to this, I would be eternally grateful; You would save me an immense amount of time having to re-download my 32GB on my internet (Which is slow here in AUS) and I'd be eternally grateful. I'm not sure if it's the LG Software just being crap like their Android App Code, or if it's just an error or if the backups need to be in a specific place, I'm not sure. I just need a way to push them onto my phone and restore it. Thank you SO much to anyone that comes up with ideas or a solution!
TL;DR: I need a way to get LG PC Suite to recognize my backups I've done so I can push them to the phone.
iDefalt said:
the op
Click to expand...
Click to collapse
try This, I am sorry to say but you will have to redownload the 1gb file if this doesn't work esspecially since imei is motherboard depended'(imei error that you get) I guess you have a faulty motherboard you will have to bring your phone in for repairs
It has taken me many days to find a tool to flash KDZ AND TOT since many people show an error at 4% of FlashTool and there is no solution so this is your Post.
LGUP is a tool used by Lg for phones that still have a guarantee such as a system error or a software error.
Compatible with Windows vista/7/8/10 No macOS No Linux
Thanks to DroidTH for giving me a link
ok let's start
Renember: All will be erased in the internal memory.
Your warrantly is now avoid
Visit [How-to] Flash firmware KDZ G2 G3 G4 by LGUP On Youtube to the link
Remember that it is not channel advertising, it's just that I can not add external links
Steps to follow
Make sure you have the drivers installed correctly
Download The KDZ / TOT
Connect Lg g3 to pc (No need to enter download mode manually)
Unzip (LGUP-G2-G3.ZIP)
First install (LGUP_8974_DLL_Ver_0_5_CODEFIRE)
Second Install (LGUP_Install_Ver_1_14_3)
Enter the LGUP program that is probably hosted on your desktop
Select the Upgrade box and select the KDZ / TOT file
Wait for the process to finish (Do not disconnect the phone)
At 80% the phone will restart (not yet to be disconnected)
When you reach 100% the phone must have turned on or starting on the TMO logo
If it does not start
-------------------------------------------------- -------------------------------------------------- ----
If it does not start
---------------------------------------------- -------------------------------------------------- -----
If it restarts constantly and does not enter the system (It restarts before reaching the optimizing application)
Turn off the phone completely and remove the battery
Wait 10 seconds. And put it back
Press Vol- and on when logo is released and press them again.
Give you everything
EYE: all files on the internal SD card will be erased
A factory reset will be made and then it must be turned on normally.
If it still does not start, remove the chip (SIMCARD)
Well that's all if you have any questions please write
Sorry if I needed something, it's just that I'm new and I do not know anything about xda
I hope you understand.
When I run LGUP it says Model is Unknown, then gives an error telling me I have to choose a known Model. Drivers are installed, USB debugging is enabled, not sure what else there is missing. Please help.
my phone: (T-Mobile lg g3 d851 30e)
dricialg said:
error Unknown model.!!
my phone: (g3 d851 30e)
Click to expand...
Click to collapse
sorry you had problems
the error is one of the drivers lg
you should plug it into one of the main USB ports on your PC.
or rather entering device manager and re-assign drivers to ports.
Have you downloaded the lgup for lg g3 and g2?
Drivers are installed, USB debugging is enabled, LG PC Suite OK.not sure what else there is missing.
Download : lgup-g2-g3.zip
Solve it FIX
good after I found the problem LGUP
roms apparently change the model of the device as it changes cm11 to build Cyanogenmod 11 xx
AOSP - to AOSP rom 2 etc.
the solution would be to install a stock rom clean no matter if v10 v30 etc. The important thing is not having changed the model number and manufacturer.
I hope I have helped and sorry
that includes cloudy fa's roms
minicm94123 said:
It has taken me many days to find a tool to flash KDZ AND TOT since many people show an error at 4% of FlashTool and there is no solution so this is your Post.
LGUP is a tool used by Lg for phones that still have a guarantee such as a system error or a software error.
Compatible with Windows vista/7/8/10 No macOS No Linux
Thanks to DroidTH for giving me a link
ok let's start
Renember: All will be erased in the internal memory.
Your warrantly is now avoid
Visit [How-to] Flash firmware KDZ G2 G3 G4 by LGUP On Youtube to the link
Remember that it is not channel advertising, it's just that I can not add external links
Steps to follow
Make sure you have the drivers installed correctly
Download The KDZ / TOT
Connect Lg g3 to pc (No need to enter download mode manually)
Unzip (LGUP-G2-G3.ZIP)
First install (LGUP_8974_DLL_Ver_0_5_CODEFIRE)
Second Install (LGUP_Install_Ver_1_14_3)
Enter the LGUP program that is probably hosted on your desktop
Select the Upgrade box and select the KDZ / TOT file
Wait for the process to finish (Do not disconnect the phone)
At 80% the phone will restart (not yet to be disconnected)
When you reach 100% the phone must have turned on or starting on the TMO logo
If it does not start
-------------------------------------------------- -------------------------------------------------- ----
If it does not start
---------------------------------------------- -------------------------------------------------- -----
If it restarts constantly and does not enter the system (It restarts before reaching the optimizing application)
Turn off the phone completely and remove the battery
Wait 10 seconds. And put it back
Press Vol- and on when logo is released and press them again.
Give you everything
EYE: all files on the internal SD card will be erased
A factory reset will be made and then it must be turned on normally.
If it still does not start, remove the chip (SIMCARD)
Well that's all if you have any questions please write
Sorry if I needed something, it's just that I'm new and I do not know anything about xda
I hope you understand.
Click to expand...
Click to collapse
Where are downloads
minicm94123 said:
good after I found the problem LGUP
roms apparently change the model of the device as it changes cm11 to build Cyanogenmod 11 xx
AOSP - to AOSP rom 2 etc.
the solution would be to install a stock rom clean no matter if v10 v30 etc. The important thing is not having changed the model number and manufacturer.
I hope I have helped and sorry
Click to expand...
Click to collapse
Hi !
How do I do all the above ?
My PC recognize the phone without problem, but LGUp won't start unless I "select a known model"... (LGUp window shows : Model = Unknown ; COM Ports = [COM5, CloudyG3] )
Problem is that my phone is softbricked after installing a new ROM, and I can only enter download mode (not even recovery). I just want to downgrade it and reflash a LG's stock ROM (or whatever ROM that would make my phone actually work !!! )
Can you help me do that ?
raf1978 said:
Hi !
How do I do all the above ?
My PC recognize the phone without problem, but LGUp won't start unless I "select a known model"... (LGUp window shows : Model = Unknown ; COM Ports = [COM5, CloudyG3] )
Problem is that my phone is softbricked after installing a new ROM, and I can only enter download mode (not even recovery). I just want to downgrade it and reflash a LG's stock ROM (or whatever ROM that would make my phone actually work !!! )
Can you help me do that ?
Click to expand...
Click to collapse
Do you still wanting help?
minicm94123 said:
Do you still wanting help?
Click to expand...
Click to collapse
YEEEESSSSSS !!!!
Please.... ?
(My phone is currently used as a toy by my 6 yo daughter ? )
LGUP "UNKNOWN" and FlashTool failure with LG G3 (and possibly others)
When I downloaded and installed LGUP with the DLL installer stated to be for the LG G3, the program did not recognise the phone, reporting it as "UNKNOWN". The LG FlashTool also failed, reporting the IMEI and PID as NULL. After spending a lot of time on this, I twigged that the DLL file in the LGUP model directory was for the 8994 processor; but the G3 has an 8974, quite different and incompatible. I located the DLL installer MSI file for 9874 devices, uninstalled LGUP and the DLLs from Windows add/remove programs, ran the 9874 DLL installer and reinstalled the LGUP program, and everything worked.
The file is, amongst other places, on https://uptoandroid.com/download-lg-up-tool-for-lg-smartphone-latest/. Do not download DLL files for LG G4, LG V10, LG G3, LG Stylo, filename LGUP_Common_DLL_Ver_1_0_28_5 .msi, but instead For LG phones based on Qualcomm Snapdragon 800 MSM8974 SoC, filename LGUP_8974_DLL_Ver_0_5.msi:.
HTH
23 Aug 19: I find that I've rediscovered the wheel. Exactly what I said was posted in 2016 - if I'd found it, it would have saved me a lot of time!
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
FILES USED IN THIS POST>https://forum.xda-developers.com/g4/general/vs986-ls991-firehoseprogrammer-raw-t3670375
Having trouble?
gratefuldeaddougie said:
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.
It appears as if some body else has stumbled upon this 4 months befor I did, back in May. Here is his Guide> http://forum.gsmdevelopers.com/showthread.php?t=28897&highlight=VS986+REPAIR
I understand the guide, but I'm confused on what you mean by "don't rename the laf.img file" because when I got the needed files from the kdz file, I got a laf.bin file but not a laf.img file. Do you mean rename the laf.bin to laf.img?
gratefuldeaddougie said:
FILES USED IN THIS POST>https://forum.xda-developers.com/g4/general/vs986-ls991-firehoseprogrammer-raw-t3670375
Click to expand...
Click to collapse
I need help with LS991ZVI
gratefuldeaddougie said:
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
Click to expand...
Click to collapse
Hi!
I need to know if I can go back to the original fastboot mode of my lg vs986 because the flashed one is from the ls991, and that's a problem bacause when you plug the device to the pc staying in fastboot mode it won't be visible, I think is a driver problem that cause incompatibility, I've lost my imei after try with other tutorials and that's why I need to restore it, I need to entry on fastboot mode (done), I'm actually using "usu unlock" tutorial, It has unlocked fastboot mode but still being the ls991 one.
the other points are nicely explained but I AM little confused in one point in which you mentioned don't rename the files what is its mean please help me to understand that point.
Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .
you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.