greetings. i need help with my lg v10 f600s which is now hard bricked. the story go so, when i go the phone . it was running on marshmelow no issues or problems.then i installed termux and when i wanted to update or download packages it kept on giving me errors.o googled around and found out it had to o the it no longer been maintained on mm software.so i searched around and found an update for the phone to nougaout firmware, so i downloaded it and updated the phone and thats when all my problems started .first my speaker phone stoped working , the major issue was the phone would randomly turn off at 40, 50, 60 percent charge.so i donwloaded the stock mm firmware to downgrade back to mm used lg up but it would not work and kept giving error.tried several other lg flash tools to no avail. then so a video about using qfil, then i built a qfil flashable firmware and managed to get the phone in to edl mode but while flashing i got these errors
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then i switched to miracle tool and kept gettint this error even with the system.img file present
all throug this process my phone was boot up but all of a sudden when i tried turning it on ,it would not boot up or charge again. i can still enter the edl mode by shorting test points, and also the pcd would heat up when i enter edl mode.pleas how do i solve this.
The V10 was a flagship with known bootloop & heat issues. LG extended it's warranty by 2yrs. Try https://duckduckgo.com/?q=xda unbrick v10
ok thanks let me check it out
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
ǀcey said:
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
Click to expand...
Click to collapse
tried the link but could not find any solution, and i cant clear cache even if the phone was on because i had booted in to recovery but there were no cammmands, and it does not boot into fastboot mode.and i am in cameroon so ebay is not an option.this phone is realy giving me a headache and right now i am not in the position to buy a new PHONE NOW.if only i had access to a box that would make things easier .there is also one thing i noticed when i disassembled the phone it written on the board F600L__EAX66751701_1.1_MAIN. I THINK THIS MEANS I ACTUALLY HAVE BUT AN F600L AND NOT F600S.BUT THEN ON LGUP IT SHOWED F600S
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
ǀcey said:
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
Click to expand...
Click to collapse
i managed to flash all other partitions using MIRACLE except the SYSTEM partition by editing the RAWPROGRAM0 XML file and removing the line of code that enables flashing SYSTEM partition which got rid of the error "CAN NOT FIND SYSTEM.IMG".now i am trying to flash the system partition alone
i am getting "sahara_rx_data:194 unable to read packet header.only read 0 bytes"
using qfil
finally flashed the system partition using MIRACLE TOOLl but phone wont still turn on.i think it realy is an f600l and not f600s.i will build a different firmware using the f600l kdz and flash it see if that works
greetings i have flashed the f600l firmware but still no change phone is still dead. even flashed the firmware dump that i took before the phone got bricked but still no change.and the firehose file only works with miracle tool when i use qfil it keeeps given me errors.pleas can some one help me with a firehose file that will work with qfil
Related
Hey there.
First post. I used Odin 3.1 to flash Froyo 2.2 on my Vibrant that was running Eclair 2.1, and Odin showed a successful completion. The phone then turned off and instead of re-booting, has become totally, utterly unresponsive.
I have tried a number of ways to get it to work, or at least get in to Download or Recovery mode, including the "remove everything, then re-insert battery while holding down volume up/down keys" and any number of key combinations. I've trowled the forum and haven't found a single solution for a completely unresponsive Vibrant. even the USB jig seems to be for those phones that at least show the Vibrant Logo or the "S" at start-up, while mine doesn't do anything.
The only encouraging thing has been posts by people who claim to have lefft their unresponsive Vibrants plugged in for several hours only to have them miraculously revive, but that seems like a long shot to me.
Have I managed to do the impossible and brick an unbrickable phone? I'd really appreciate help as I just got the phone last week and don't want to declare it a dead loss so soon.
Cheers!
Utterly, haha
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thinking.. above was a joke...
What ODIN files did you flash? Link to them?
What version of ODIN, the latest?
When you say nothing... you mean you can't see anything on the phone, regardless of the action?
rofl OMG is that chick half naked hahaha seriously is she in her undies milking a cow WTF! LMFAO!
- so the phone won't turn on huh?...... no power at all?....... how about plug in the cord, do you see the batt charge?
haha utterly.. when you say put in the battery while holding the volume keys, did you put in the battery or plug in the USB??
I had to replace mine. Been good ever since.
Sent from my GT-I9000 using XDA Premium App
Here's the long story. My phone was getting the 'device unrecognized' error in Kies and Kies Mini, so I used Odin 3.0 to flash it, using the "T959UVKA6_REV05_home_low_CL860813.tar.md5" file.
After flashing, my phone wouldgo into recovery mode and the following error.
"E:Cant mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed."
Next I followed the steps detailed in this post . When I flashed my phone according to the 'Gauranteed Solution', my phone turned off at the end of the flash and has stayed off ever since.
And when I say nothing, I mean nothing. No battery symbol, no sound, no Samsung Vibrant logo, nothing. Just a blank screen.
I tried plugging in the phone and then putting in the battery with the volume keys pressed and I also tried it without plugging in the USB. Either way, nothing happens.
As you can probably guess, I'm a n00b of the first order and I fear I might have killed my phone.
If you do manage to revive your phone back.. You better flash roms via cmw. Not that odin isn't great but cmw never caused any problems(to me).
Make a jig to force download mode then reflash stock os and install rom manager to flash roms. P.m for more Info.
Sent from my SGH-T959 using XDA Premium App
Thats funny, the last post in the link you referenced is someone having the same problem as you........ why would you try to do that? and the .tar is some I9000 file being that the (fix) was in the I9000 forum. Neither of these probably have anything to do with your problem now i just thought it was funny. I mean why wouldn't you just use the T959UVJFD.tar in ODIN?
It seems that the "E:cant mount" error is a fairly common issue and from what i am seeing alot of the people having this issue after using samsung kies are getting replacements fairly easily although it is a last resort for many. I would not think its an issue with your drivers or anything like that, probably just ODIN being weird. Don't give up on ODIN i would assume that it will recognize the phone eventually as most "DEAD" vibrants do after time. I'll keep looking into it for you. Hope you find a fix soon. Good luck!
You can also restart the computer and f8 and turn off driver signing and see if that helps. Once again I don't mind helping on a more personal basis. P.m me.
Sent from my SGH-T959 using XDA Premium App
have you ever actually tried a usb jig ?
http://cgi.ebay.com/ws/eBayISAPI.dl...83134&ssPageName=STRK:MESELX:IT#ht_723wt_1139
Hello all,
I have a LG 850, bought in Belgium (carrierless), it was running latest LG nougat stock software when I started fiddling. (This was on the 6th of Jan)
TL;DR: What I did: rooted, installed TWRP and custom ROM (on Nougat 7.1). Worked fine. Then wanted to revert back to stock since it didn't solve the issues I had beforehand. Tried to figure out LG UP, LG Bridge, LG Flash Tool, in the end I managed to install a KDZ file through LG UP (using Uppercut), but it must've been the wrong one because the phone always defaults to recovery mode when booting.
How do I solve this? I can access download mode (LG UP sees the phone), I can use fastboot, and managed to reflash TWRP recovery so I have that too.
Long version: I had GPS and screen burn-in issues. I tried sending the phone back for repair , but LG simply put my phone on an earlier software version, no help. I can't really miss my phone for work (takes 2 weeks) so dealt with it. In the end it bugged me a lot, so decided I should try a custom ROM: installing this went fine. I ran Fulmics for a while, but it didn't solve my problems: must be a hardware issue. That's when I decided to revert back to stock and relock the bootloader to be able to send it back again (I'm using a nexus 5X as backup now). I'm not sure if they'll accept the return (since I've unlocked the phone's bootloader by using LG's dev website), but it's worth a try.
The process in the other direction went south really quickly: I think I accidentally erased the wrong partitions, so I ended up with a phone that only had download mode. I managed to install a KDZ file through LG UP (used the upgrade button, not refurbish, as it was the only one that worked). This didn't help, so I used fastboot to reflash recovery with TWRP.
After this, I tried a bunch of different KDZ files, as I'm not sure how to figure out which one is the correct one for my phone... When I begin to install a KDZ file the log in download mode shows me LG H85020a on the third line, is this the value representing my phone? IMEI lookup tells me: Location code: N, Network Code: NLD, Carrier: NLD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The refurbish button has never worked, I always get the error "Refurbish is not available for this device". Refurbish often ends in "Invalid command response code".
Can anyone point me in the direction of the correct KDZ file, or a way to reset the phone? If not, it's going to be one expense frisbee...
Thanks all!
Greetz from Belgium.
so you successfully flash the KDZ to the phone using LGUP and when it finishes the phone reboots itself, right?
and when it boots.. it boots into stock recovery each time.. which is wiping data? and then it reboots and goes right back into stock recovery?
I'm confused as to what's happening EXACTLY after the KDZ flashes and the phone reboots.
and once you install TWRP... no matter what the phone just reboots back into TWRP and never into Android?
in TWRP try the following:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
reboot
and see if android boots this time after the reboot.
Okay. Weird stuff happened.
I'd like to thank you for your answer, but I ended up not using it.
I decided, while waiting for an answer, to retry all KDZ files in my possession. I started LG UP through Uppercut, and tried H85020a_00_VDF_COM_OP_1030.kdz which in theory shouldn't work, because it's a lower android version than the one I had before. Refurbish didn't work, but the Update button did the trick! Not sure what happened differently this time...
He reset everything, gave me stock software. He did the same thing as before: erasing phone (round shiny ring), message about unlocked bootloader, show LG logo, then the moving logo with music, and rebooted. But right after the moving logo it showed a white screen with text I couldn't read fast enough before it rebooted again. After a while I figured out it was something about an encrypted phone and a pasword mismatch, and that my device needed to be wiped. It did that (had to be quick to click it), it erased itself, and the thing booted up just like that.
I relocked the bootloader using fastboot and it works fine. Ready to be shipped back to LG
I'm running V20a-EUR-XX it says in the settings, I guess that's fine.
Thank you for the help anyway. I hope this explanation helps other users too...
You can find the KDZ files for most H850s at the following link: http://lg-firmwares.com/lg-h850-firmwares/
While I don't see Belgium as one of the many listed regions, you might be running the NEU (Northern Europe) version. Good luck!
thanks for your reply. You can see above i retraced the steps I already tried, and somehow now the phone works.
I ended up using H85020a_00_VDF_COM_OP_1030.kdz which did the trick!
Hello,
My LG-D280N is bricked... i think... every time it boots it goes on a purple screen called Demigod crash handler, it also does the same thing when i try to factory reset it
So i had no choice but to flash a new room to hopefully fix it, THANKFULLY it does go to download mode without crashes and it does show up on my device manager as "Android bootloader interface" but even so the flashtool says port(USB or Serial) not found, here is what the phone says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As i was writing all that, it actually booted to android!!!! but there are infinite " app stopped" messages, it's impossible to go to settings and try to hard reset or rather it's impossible to go anywhere, looks to me like re-flashing a brand new stock rom is the only choice
i should say that i put this phone in my closet two months ago and it was fine! when i tried to use it today it was like that but anyway, is there anything i can do? I really need to fix that phone
Thanks alot, i really appreciate any help
An update... the phone responds to fastboot commands from ADB tools, it doesn't show up on "adb devices" list though
Wonder if there is a way to use to use fastboot commands to flash a kdz file?
More updates... i used a tool to extract everything from the KDZ file and reflashed the following files like this:
fastboot flash boot boot.bin
fastboot flash factory factory_475136.bin
fastboot flash factory recovery.bin
fastboot flash aboot aboot_144384.bin
fastboot flash aboot abootb_150528.bin
Now i could of have done something either right or extremely stupid BUT ever since i did that factory reset mode actually worked! no more demigod crash handlers and i also stopped seeing those small "boot verification errors" in the corner and the phone actually booted and saw the initial welcome screen, so it actually factory reseted! BUT even though it did I STILL saw the sea of "*instert app here* has stopped" which makes it impossible to navigate the phone
But for whatever reason, it's now stuck on the startup logo after a reset, well even if i screwed up badly, download mode still works like before sooo it's not much different, at the very least i got rid of the stupid demigod crash handler
I've been working on that phone for hours now... been researching on google with little to no information about this at all, most solutions involve the flash tool WHICH doesn't work so i had to come up with my own ideas... and to make matters worse nobody here has gave me clues on how to fix it which is why i give these updates, maybe all this information will help you come up with a solution
Another update... i was wondering why it wouldn't be detected by my flashtool... until it hit me... the download mode itself has problems, thankfully fastboot still worked and i was able to reflash it using one of the files i extracted from the KDZ file
After this, my download mode now works correctly, it displays everything right and is now recognized by the flashtool! finally some real freaking progress, working on this thing is such a pain but finally im getting somewhere, but it's not over yet, right now im waiting for the device to reach 40% of charge before i flash the rom, hopefully no errors will occur as it has already been a HUGE pain and time consuming
Final update... i have successfully flashed the stock rom, after a whole day of trial and error i did it, let me summarize
My problem was mostly that the download mode itself needed to be reflashed, for whatever reason it was broken or not properly configured but whatever the case, it needed to be reflashed using fastboot in order to work correctly and be recognized by the LG Flashtool, after i reflashed it, it was fine and the LG Flashtool FINALLY recognized my device, but the LG Flashtool would CRASH whenever i clicked the "Read Phone Information" button, not sure why but i tried 4 times until it finally worked, not sure what happened there but who cares, it worked out, then it finally started flashing until it said "error connecting to the server", took me sometime and research to realize that it's SUPPOSED to do that and that i should ignore the message and NOT close it because if i do the whole flashtool stops, after this i let it sit in the background and do all the flashing, it was fine until 77%, it gave me an error message and said that i should try to reset my device back into download mode, then it retried doing the whole process all over again AND THANKFULLY this time it successfully did it, the phone now boots to Android as normal, the sea of "app stopped" message is also gone thankfully and so that's pretty much it...
My absolute stupid mistakes and problems with this could help other people avoid those same mistakes and problems so i won't delete the post since as i said, it can prove to be useful to others
My $20 hoot huawei p20 pro CLONE (here a link /w info about the phone with false specs full of bugs)https://www.freebrowsinglink.com/hoot-p20-pro/ got bricked a week ago after I left it connected to a Windows computer with internet access.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The story starts with when I tried to root the phone with KingoRoot, eventually ads started popping up, facebook, dating or porn sites and malware like that. I uninstalled KingoRoot and installed some anti spam software like avg and avast, but that did not help, ads kept coming. The phone has Android 5.1 Lollipop on it and after I left it connected to a Windows Laptop, like I said before, error messages with 'UI has stopped working' and 'other stuff stopped working' started popping up in a whole sequence of error messages so it rendered the phone unusable.
Next I started messing with it via platform-tools and wanted to flash TWRP on it and eventually a different OS like Lineage, but now the phone is totally shot and I can not use recovery any longer. The only thing that seems to work is fastboot mode, but it doesn't let me install a custom recovery like TWRP. Unlocking the bootloader seems to work, like shown in the attached pix, but other commands like 'fastboot devices' give a funny looking device name: '0123456789abcdef'. Other commands like fastboot erase -w and oem info show failure only; reboot-bootloader works and so on.
Any advice on this one? I'm just trying to learn about phones and android and this seems like a perfect opportunity, unless this cloned smartphone is piece of a worthless brick, which most assuredly is.
Try to flash corect stock firmwares for your device , check which one is yours .
https://hellostockrom.com/huawei-clone-p20-pro/
Yo TeddyLo, I tried already a similar website and after 2 hours of downloading through a slow internet connection the files were encrypted WinRaRs and probably useless anyway...thanks bro.
Hard Bricked Hoot P20 pro Clone
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Clone_Cat said:
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Click to expand...
Click to collapse
hi, i had the same problem, and i found this forum , it solved the issue ....
forum.gsmhosting.com/vbb/f296/clone-welcome-huawei-p20-pro-firmware-2574709/
Regards
Is there a way to remove the HD from broken G5 to a working G5 and put it in another? (It won't turn on at all) I have some very important pics on one of my old G5's that will not turn on at all. I have 2 other G5's that work perfectly.
For HD you mean the internal memory? In that case, it should be unsoldered and soldered again on another G5, and SMD soldering requires specific tools and skills.
I think it would be easier, before trying the transplant, to track down the issue and see if the faulty G5 can be repaired.
Maybe you have already tried everything, but otherwise, have you tried to switch the chins and batteries between the faulty G5 and the other phones? If it doesn't work, you can then open the faulty device and post a picture of the board: sometimes it can be very easy to spot a broken fuse or resistor that can be much more simple to be replaced by a technician than a whole memory chip.
tremalnaik said:
For HD you mean the internal memory? In that case, it should be unsoldered and soldered again on another G5, and SMD soldering requires specific tools and skills.
I think it would be easier, before trying the transplant, to track down the issue and see if the faulty G5 can be repaired.
Maybe you have already tried everything, but otherwise, have you tried to switch the chins and batteries between the faulty G5 and the other phones? If it doesn't work, you can then open the faulty device and post a picture of the board: sometimes it can be very easy to spot a broken fuse or resistor that can be much more simple to be replaced by a technician than a whole memory chip.
Click to expand...
Click to collapse
I did try 2 other batteries and the chins. It just keeps flashing the start screen.
I just tried it again and it turned on! But after 5 minutes of use, it crapped out again. It tries turning on but the start screen only goes on for about 30 seconds then goes black for 2 seconds and back to start screen for 30 seconds... SMH... I just want the pics out of it!!! It's garbage after that.
Before throwing it away: when you try to turn it on and then it shuts down, are you using a charged battery or are you charging it at the moment? The G5 requires a lot of power to turn on (and do any other operation that requires reading or writing the internal memory), and if the battery is not charged enough, or if you're using a 500mA USB port for charging, it will just try to turn on and then it will miserably fail.
Try charging the battery in one of the other G5s and then use it to boot the broken one. Or, if you have a custom recovery, to boot in recovery: it takes less time and energy than booting into Android. But do not attempt booting into recovery if you're not sure if you have a custom recovery: the default recovery just erases the whole internal memory.
I tried all that and nothing. It won't boot in recovery either.
Not even fastboot?
tremalnaik said:
Not even fastboot?
Click to expand...
Click to collapse
What is fastboot and what will it do?
Fastboot is an emergency method for booting the phone. You have to turn off the phone, keep the Vol- key pressed and then connect the USB cable to power. From there there's not a lot you can do, but if the bootloader is already unlocked (don't unlock it if it's locked, if you do that the internal will be erased) you can send TWRP to the phone and boot it without installing it in the recovery partition (the command should be something like fastboot boot "C:/location_of_twrp_on_pc/twrp.img"). You can also install TWRP with fastboot flash recovery "C:/location_of_twrp_on_pc/twrp.img", but still you need an unlocked bootloader.
If the bootloader is unlocked, this is what you should already see on boot, right after the LG logo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just tried it again this morning and it turned on but only for a few minutes. It felt like it was a little warm on the back of the phone when it shut down. I could not find the pics in that time.
Next time I get it going, I will try uninstalling all apps possible and see what happens.