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
Related
hi, this is my first post....
i have spent the last few days searching this site with no luck, so here goes...
i have a motorola defy android 2.1(stock rom)
it was running great (rooted and overclocked at 1200) until i downloaded a freezing program (freezes orig phone apps, telstra ect)
anyhow i turned off my phone and then when i turned it back on i had no home screen??? (so couldnt access my apps,settings,msgs,calls, nothing)
i could slide the unlock across but after that it was just black with the status bar at the top....
i have done a hard reset (hold volume down and turn on, then wipe data/factory reset)
now my stupid motoblur acc will not let me log in, or create a new account (i have been successful loging into the motoblur website, just not on my phone), it loads almost to the end of the progress bar, then just sits there and does nothing at all, i even left it over night!!!
i have installed these files, in the hope of flashing a new rom (2.3 or 2.3 would be sweet)
Motodrivers131
RSD Lite 4.9
i installed rsd first, and could see my phone (in download mode) but every time i tried to flash a .sbf file i got the message "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected" so i installed Motodrivers131, and now my phone wont even show up in rsd???
im in melbourne, victoria, australia 3133...
im going insane here, any help would be very appreciated...
james
Bump
bump
bump
Uninstall everything, reboot the pc, install Motorola Drivers, install rsd, remove the battery, press and hold VOL UP and put the battery again. Open RSD and try to see your phone now. If it fails, try to press the power button (continue holding VOL UP).
If everything fails, maybe you are out of battery, and the only thing to do is mcgyver trick (see wiki).
ok, i have managed to get into google while in the motoblur sign in thingy, and rooted my phone and used clockwork to flash an update from my sd card
2 problems tho, first one is that im in australia and ive flashed t-mobile 2.2 (usa)
and the second is that everytime i put an sd card into the phone it begins to mount the sd card, then instantly says "sd card is safe to remove" i have tried formatting it on the phone but it says to remove it before i get a chance..... (i have tried 2 diff cards) and have wiped them on my computer!
this is rather annoying as i cant flash it with blueginger like i wanted to, or use a fair few apps or the camera without the sd card present????
any thoughts?
Maybe the drivers are corrupted?
Are you using a T-Mo US Defy unit or an unbranded one?
nah my defy is a telstra branded one from australia......
there has to be a way around this problem...
Does anybody else have problems trying to use PC Companion's Backup and Restore function?
It just will not work for me.
I fire it up and then choose the items I want to back up (regardless of what I choose will cause failure - I even tried selecting just basic items, which comes to about a backup the size 600KB and STILL it fails)
Basically after I select the items and click OK, it will then sit there for ages "preparing" - there's a small animation of dots going from PC to phone and vice versa.
Then after a very long time, a screen comes up specifying the size of the backup (as above, it could be 600KB or if I include photos too it will be over 1GB) and the file name I want to call it. When I click next, the progress bar starts to go up as the backup is made (again, very slowly) But it will then always randomly freeze, the PCC app goes into a state of "not responding" and the workspace of the app goes black. It then does nothing.
It's not a case of it's doing something and I have to wait, as I have waited, a VERY long time whilst it's been in this state, but nothing happens. Sometimes I get a screen saying backup failed, or sometimes it just stays black. But I can see nothing is happening as there are no I/O read/writes to the hard disk going on in Task Manager.
I've tried this on 3 different PCs, Windows 7, Windows 8 and Windows XP, all with the same result. I've also tried factory resets of the phone with no luck.
Does anybody else have this??
Thanks
Haii,
I think it is a problem that lots of people are dealing with.
i've got the same problems with the Sony PC Companion.
I never use that tool again, and do the factory resets on my phone and copy everything thrue the browser.
I have had trouble with PC Companion also.
It communicates with my xperia s when attempting to backup, and then when I ask it to start it stops responding and crashes.
I just don't bother with it...
Sent from my LT26i using xda app-developers app
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
still no results
To no avail I have tried everything! I have seen some changes but nothing that tells me that its fixed! I have tried qpst, but either I don't know how to run it or it wont connect properly, as a matter of fact I dont think it connects properly to any of the programs I run on it. It doesn't help that the only way the computer recognizes it is when it is on demigod mode.has anyone out there in android land had some experience or any idea of how to format the internal sd and start over from scratch?
shiftykidd said:
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
Click to expand...
Click to collapse
You managed to fix it?
am facing the same issue.
Not yet i am thinking about just sending it back to lg. It's mixed up partitions, due to power surge from unauthorized power cords.
Do you have your phone rooted and with a custom recovery?
If yes,
Give this a try:
1.Enter recovery
2.Wipe data
3.Wipe cache
4.Wipe dalvic cache
5.Reboot
I've had the same problem with an LG L9 ii and this one fixed it.
So i really hope this will help. Inform me after doing this.
Greetings.
About five months ago I was able to access recovery but nothing was functional, now I cant even turn it on, if you left it on a different charger, kernal crash handler popped up half the time. Before it quit turning on the lg boot logo started going fuzzy, logic leads me to believe its a messed up Q C mother and the partitions are scrambled due to me using a non-oem charging cord and block, I also suspect the power button mounted to the back, on top of mother might have caused some hw problems. But those are just theories, it could simply be a bad battery!
I've searched thru many posts but did not see one close enough for my comfort, excuse me if I'm double posting.
First time poster, long time supporter, apparent noob who can't root with KingRoot... I ran the desk top version on my LG G3 D851 v10c or e. Idk. Fresh out of the box refurbished from the $130 Woot.com special last month. I used that to experiment before rooting thru my pc because it's faster, easier and it takes an idiot to brick a device like that... I removed some bloatware and most of the GApps and everything was fine before\after reboot. Then I went into core and took out a few that I know I have removed from other devices before, and it was running smooth until I opened (curse it) the Play Store. I get:
Unfortunately, Google Play services has stopped.
And forces me to reset. It starts in the initial setup boot menu, can't find a way out thru the menus anywhere so I try to just run it thru init setup. At this point, I do not believe that I actually permanently removed any files, just first step. But I obviously may be wrong.
Start >WiFi login>skip LG SmartShare (Lg's NFC\WiFi transfer protocol) setup:
Unfortunately, Google Play services has stopped.
So I try the SmartShare setup:
Unfortunately, Google Play services has stopped.
I try no\both wifi\data on\off, KingRoot on\off, everything I could think of. So I factory reset. No change.
So my factors are:
I can supposedly transfer files thru SmartShare because when I try to transfer from G3>G4 it said file type not recognized I believe. I'm not with the device now, but it does not recognize it. I can also send files to the G4, when in transfer mode, if I tap the G3's screen, it seems G4 to Play Store but to unknown address. I can use WiFi\data. I did not set the device into debug mode and do not have drivers or recovery installed. The device was factory fresh when I crashed it, so there's nothing to worry about losing.
My question is:
What is my next step? Try computer debug? I was thinking maybe try file transfer the Play Store and Service files since I could use SmartShare. Or skeet shooting? Add it to my wall of shame with the $40 RCA tablets (Not my fault! If it's not supposed to be cracked, then why is it encrypted?)
Anyways, I'd appreciate any help, advise, more questions, and answers, definitely answers. Thank you in advance.
Tags: Tmo, Tmobile, T-Mobile, LG, G3, 10c, 10e, D851, 5.0.1, bootloop, boot unlock, bootloader, brick, root, twrp,
Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash
Hello all - I'm hoping someone can provide some assistance / suggestions...
A few months ago, my son's tablet went for a quick swim (dropped into the toilet ) Unfortunately, I wasn't at home (on a business trip) to immediately power it down and pull the battery. I'm not sure if it was turned off / back on / off again or what, but it was quickly put into a bag of rice to try and minimize the damage until I came home to review.
Inspection of the tablet confirmed it was dead - no response to either buttons or plugging in the charger. Found the ifixit how-to, and after obtaining some tools I popped the back case off to see what was what. Disassembly revealed an nice scorch mark on the underside of the motherboard, right where the main chip was, so it was pretty obvious what the failure was.
I decided that I'd give repairing it a go, and bought a replacement motherboard from ebay a couple of weeks ago. Swapping the board over was no problem, and I was happy to see that after letting it charge fully, it booted up and went into the 'Setup' routine.
However, this is where the problems started - as it was working through the setup (language / wifi / copy apps/data from other device etc) there were numerous "Unfortunately, xxx has stopped" messages. I kept 'ok'ing them, and the tablet made it to the point where it was starting to download the saved apps etc from the playstore before it rebooted.
When it powered back up, the 'Unfortunately" pop ups were worse than before, so after doing some searching I decided to try flash a factory image (razor-mob30x) , as per the link on the Nexus help forum. The flash seemed to work (no errors in fastboot mode, laptop was communicating with the tablet) but the pop ups were still as plentiful as before. I have tried the flash multiple times, even going back to lollipop, but with no real improvement. The last thing I tried tonight was to start the recommended flash process from step 1, re-downloading and installing all the required programs, but without success.
I'm not sure what else to try, as the factory image reflash should erase all the installed files.
My only thought is maybe trying to sideload the correct gapps / play services / etc in fastboot mode?
Any suggestions appreciated,
Roadie73
Update..
So, because I'm a glutton for punishment, I've been playing with the N7 again this evening...
Grabbed my old laptop, and went through the complete routine again - loading adb and fastboot onto the laptop, then the N7 factory image - and ended up with basically the same result - the tablet will look like the files have taken, but almost immediately after restarting and loading to the blue set up screen, the "Unfortunately..." messages start again.
I was able to get all the way through the set up, and have it copy and start to download the files off the tablet I was using previously, but the pop ups persisted, and it gets to a point where it is looking for a google play services update, and the process comes to a screeching halt.
I found another 'How To" and tried sideloading a rescue OTA update, which might be a little better, but the messages persist....
I'm almost wondering if it's worth reflashing the factory image back to whatever the N7 shipped with, and then trying updates from there, as it seems to be the play services / store / apps that is the issue.
The other strange thing is that when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Still trying...
Roadie73 said:
it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Click to expand...
Click to collapse
Interesting, please post the output of the 2 commands...
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run:
fastboot getvar all
fastboot oem gpt-info
If you can, also attach logs...
download get-logs.zip to a FAT32 flash drive
connect the flash drive to your N7 with OTG adapter
download TWRP to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run: fastboot boot twrp-3.1.0-0-flo.img
when TWRP is up, go: install/select-storage/usb-otg/get-logs.zip/flash
logs.tgz will be saved on the flash drive
attach logs.tgz here
It's simpler if you have TWRP already installed. You can also use get-logs.zip from internal storage.
Hi k23m,
I ran the two commands you suggested (getvar all and oem gpt-info) , and grabbed the outputs of both as screen captures and dumped them into a ppt file (which I can't seem to attach - there is no 'manage attachments' option I can see )
I installed TWRP on the N7, but was unsuccessful in creating / grabbing logs.tgz file - which might have to do with the USB connector on the N7 being flaky - if the otg cable wasn't held in exactly the right way it wouldn't recognize the flash drive.
If I can figure out how to add the attachment I will in a separate post, or I can always email it to you direct.
Thanks,
Roadie
Hello k23m,
Finally ad a couple of minutes to play with the N7 again - copied the get-logs file over to the tablet (that was behaving for once).
Unfortunately, despite copying the file off the N7 onto the laptop, a *.tgz file can't be attached. So I did the next best thing and copied the screen caps into an excel doc, which is one of the valid extension.
Please see the attached file - I had a look at the output, but it means nothing to me...
Thanks,
Roadie
added 'logs.tgz' file run previously - please rename from *.xls
Hopefully it might provide some insights into why the N7 is mis-behaving.
Thanks,
Roadie
The logs are OK.
Roadie73 said:
when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013
Click to expand...
Click to collapse
If you have followed the factory image installation instructions and you see the error messages before setup's initial sign in, then your hardware is faulty.
If it happens after sign in, then perhaps Google has corrupt account data ("it shows as a Nexus 7 2012"). Try a new account. Try a custom ROM with Gapps.
Ok, thanks.
Just tried a factory reflash as per the link, but fastbooted the individual files (boot / recovery / system / userdata / cache) separately as from what I have read using the 'flash-all' batch file has intermittent results.
Looked like the files loaded in successfully, but I'm still getting the "Unfortunately.." messages popping up on the initial sign in screen for set-up
So, based on k23m's assessment above, it sounds like it's a hardware problem
As far as I know the touch screen is ok (it's responsive in all areas, as far as I can tell). The daughterboard is not the original (that took a swim) - it was swapped out of another N7 when the charging port started to spread (and that tablet was issue free) So it looks as if the issue is in the replacement motherboard.
I guess I could try removing and reinstalling it, on the off chance it's a flaky connection somewhere.
I will also check to see if there was any sort of gaurentee / replacement policy for the replacement mobo, but it sounds like I'm out of luck
Any other suggestions / checks I can perform to see if I can narrow down where the issue lies?
Thank you,
Roadie