Elite thanks in advance. No, seriously, thanks. I'm a broke single parent of 2 kids and I realized my phone is about my only guilty pleasure after giving my kids 200% of my time and money. Any help would be appreciated.
I have an LG G2 that I apparently bricked by using an app to "freeze" the latest OTA software update that was pushed to my ATT LG G2 about a month + ago if not slightly longer. I unfroze the process and the update suddenly appeared and said it would reboot the phone and or apply the update it in 30 seconds. I panicked and held the power button in to turn the phone off.
Once the phone was turned back on I was greeted with tiny white text that said "error: Boot certification verify" From here I was unable to get into down load mode, do a hard reset. I was able to see fast boot mode but wasn't sure what to do with it. I was able to see the phone in Windows 7 Pro Sp1 device manager but it was listed as QHSUSB_BULK
After initially freaking out which lasted about 20 mins, I was able to compose myself and start researching my new seemingly serious problem. After a few hours of reading a dozen or so treads / hundreds of replies it seemed I would have to load into Ubuntu and push some files to my LG G2.
I followed this guide - http://forum.xda-developers.com/showthread.php?t=2582142
I was very careful to follow this guide to the letter and everything went as expected the first, 2nd and 3rd time only the results were worse and worse and worse.
The first time I lost fast boot, the 2nd time I lost the boot certification verify error, After the 3rd attempt I get a split second LG Logo and that's it. What did I do during those 3 attempts? The first time, the 4 files and the recovery as directed. The 2nd time, the same files, plus the boot.img and a different recovery. The 3rd time, all the files and yet a different recovery. All the files were pulled from here - http://downloads.codefi.re/autoprime/LG/LG_G2/D800
The other recovery.imgs were for the correct model, just older, newer variants. I was very careful to push the right files to the right partitions.
I can still see the phone via Ubuntu. I'm scared to do anything else along the lines of what I've been doing. In fact I'm lost as to what to do next.
Can anyone here help me push more / different files via Ubuntu that would help bring my phone back to life? I'm completely dead in the water. Or perhaps an exe package / program that can fix my problem? If I sound stupid, it's because this is all new to me.
Thanks in advance, Tom
@rthefley Go back to the autoprime downloads and get the boot, aboot and laf image. Follow the ubuntu guide and flash those images only.
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
rthefley said:
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
Click to expand...
Click to collapse
In that case, you should try to push a recovery image, too!
Raymonf said:
In that case, you should try to push a recovery image, too!
Click to expand...
Click to collapse
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
rthefley said:
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
Click to expand...
Click to collapse
Did you lokify them?
Raymonf said:
Did you lokify them?
Click to expand...
Click to collapse
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
rthefley said:
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
Click to expand...
Click to collapse
Okay, are you now able to go into download mode?
1127
Art Vanderlay said:
Okay, are you now able to go into download mode?
Click to expand...
Click to collapse
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
rthefley said:
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
Click to expand...
Click to collapse
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Art Vanderlay said:
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Click to expand...
Click to collapse
Yes I'm pretty sure it's completely powered off. I will try again but I've held the power button in for several several seconds and saw the screen go solid black. I've flashed those 3 files just as instructed. Nothing is working sadly. Maybe I am missing some key procedure others take for granted that I just personally do not know about
Is there anything else I could try doing? I'm going in circles here.
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
LilDemon124 said:
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
No they are different, I actually gdisked all of the different letters but I have an sda,c,b and e, I even have have an sde1. All the numbers follow sde however up to 42 or 43. So when I gdisk -l /dev/sde that's when I see all the files.
I've tried to gdisk sdb but I get a mbr / gpt or something error saying something is corrupted so I just leave it alone.
Should I be looking at a different letter then? If so, I can't seem to get into any of them other than the one I mentioned, sde
Guys, I'm now offering a $40 paypal bounty directly to your pocket or a donation to this web site for help allowing me to get back into my phone.
I will try my best to help you. Im at work, but will be home soon so that I can do some snooping.. From what your saying you MIGHT have a corrupt storage OR you might have a corrupt file.
Sent from my LG-LS980 using Tapatalk
Im going to have to work on this a bit later. Worked all day. I'm still here and around just need to get a little sleep before I even think of trying to dive into this again. Thanks.
Related
After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic.
Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.
Many thanks in advance for any suggestions/fixes!
Phillip
Its not bricked if it boots...
That is strange though. May have to reflash stock images.
Try bringing everything back to stock?
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Gr3yghost said:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Click to expand...
Click to collapse
No push the images using adb
I figured it could be done. Could you please point me to a thread explaining how to push images using adb?
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).
Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.
[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
djsaad1 said:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
Click to expand...
Click to collapse
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!
Sent it back
Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
srkmagnus said:
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
Click to expand...
Click to collapse
You definitely need to do an RUU. No way around it. know it sucks starting fresh again but it'll solve all these problems you have. If your s-off you can also do the RUU from Hboot but it's better to do it from PC as I have learned. Good luck man.
thanks a lot! om going to give it a try later tonight when i have access to a pc. Im not so much worried about starting fresh than I am losing the phone and using my upgrade now... I have a curve laying around and started to thing about using that for a while until I see something I like.
i will report back tonight or tomorrow when i am up and running again.
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
williams1978 said:
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
Click to expand...
Click to collapse
Thanks. I will give it a look.
I read through the thread and it looks like you passed the black htc screen and got to the white one. I can't get passed the black and adb doesn't pick up the phone at this point. I'm still waiting to try the RUU and see if HTC sync picks up the device.
Very resourceful thread and I'll be sure to give all the suggestions a try before giving up.
HTC sync won't pick up the device and I don't think any other option will work since I don't have ADB access. I'm just gonna bite the bullet and look into a replacement.
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
dastin1015 said:
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
srkmagnus said:
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
Click to expand...
Click to collapse
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=804692
I used a flashable RUU based off Flipz source and still no luck. I will give your RUU a try later tonight... Thanks
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
srkmagnus said:
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
Click to expand...
Click to collapse
i had same kinda deal from a bad radio flash
if you still have fastboot do
"fastboot erase system -w"
"fastboot oem boot heroc.hboot-1.46.2000.zip"
you may need to rename the file to HBOOT.
if that dose not work unzip the file take the hboot img and place on sdcard and place where your fastboot files are like in android/platform-tools.
this made a deference for me.
then try fastboot flash img hboot.img
this is what i went through here
http://forum.xda-developers.com/showthread.php?t=1086125
good luck if i can help let me know.
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
srkmagnus said:
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
Click to expand...
Click to collapse
you are welcome i have been there before.
your phone may not recognize ADB but it may still take fastboot commands. that was one thing that drove me crazy is that i could fastboot but not adb. let us all know how it goes.
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
srkmagnus said:
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
Click to expand...
Click to collapse
i still have one of my hero's that i let people play with when the come over. it still runs off wifi so they can play games yous gtalk what ever be nice to get it up and running for experience and fun lol now that your not in a have to mode.
do you have a nan back up from a sd card any place like on your pc if so look for your clockworkmod folder look for backups and you should see your backups open one of them you will see
boot
system
data
recovery
sd-ext
cache
they will be img files you can place them on your sd card and fastboot them back to the phone
"fastboot flash img boot.img"
"fastboot flash img system.img"
and so on
or
"fastboot boot img boot.img"
"fastboot boot img system.img"
and so on
or you can let it RIP
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
srkmagnus said:
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
Click to expand...
Click to collapse
will the charge light come on when plugged in if not there is a trick take a old usb cable cut one end off on the battery there are
= and - becare full connect the red wire to + and black to - tap them down so they dont move. let it set for 2 1/2 hrs should be good to go.
Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James
I could sure use some help. I rooted my VK810, then...using ROM Toolbox....I changed the start up animation. That was the wrong thing to do. Now every time I restart the tablet, in portrait mode, the screen stays black. In landscape mode, only the right 1/3 of the screen is visible (the rest is black). It does not matter how I turn the tablet, it's always the right side that is black. I have tried several Master Resets. Occasionally that will bring the screen back (tho usually not), but every time I restart, I'm right back to square one. I really need to reset it back to stock, but I'm finding VERY little information on how to do this. Any help would be GREATLY appreciated.
btw....the tablet did upgrade to 4.4.2, before it was rooted.
Thanks,
Dan
ddodge68 said:
I could sure use some help. I rooted my VK810, then...using ROM Toolbox....I changed the start up animation. That was the wrong thing to do. Now every time I restart the tablet, in portrait mode, the screen stays black. In landscape mode, only the right 1/3 of the screen is visible (the rest is black). It does not matter how I turn the tablet, it's always the right side that is black. I have tried several Master Resets. Occasionally that will bring the screen back (tho usually not), but every time I restart, I'm right back to square one. I really need to reset it back to stock, but I'm finding VERY little information on how to do this. Any help would be GREATLY appreciated.
btw....the tablet did upgrade to 4.4.2, before it was rooted.
Thanks,
Dan
Click to expand...
Click to collapse
One or two of any of these will get you there. By the way, have you tried restoring a backup in TWRP recovery?
http://forum.xda-developers.com/showthread.php?t=2698401
http://forum.xda-developers.com/lg-g-pad-83/development/vk810-4g-altev-verizon-lg-g-pad-8-3-t2990481
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-verizon-lg-g-pad-8-3-to-stock-t2800857
http://forum.xda-developers.com/lg-g-pad-83/general/vzw-lg-g-pad-return-to-stock-easy-t2930373
roirraW "edor" ehT said:
One or two of any of these will get you there. By the way, have you tried restoring a backup in TWRP recovery?
http://forum.xda-developers.com/showthread.php?t=2698401
http://forum.xda-developers.com/lg-g-pad-83/development/vk810-4g-altev-verizon-lg-g-pad-8-3-t2990481
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-verizon-lg-g-pad-8-3-to-stock-t2800857
http://forum.xda-developers.com/lg-g-pad-83/general/vzw-lg-g-pad-return-to-stock-easy-t2930373
Click to expand...
Click to collapse
I have been unable to get TWRP installed.
ddodge68 said:
I have been unable to get TWRP installed.
Click to expand...
Click to collapse
Doh me! Sorry, forgot you were the one with TWRP not installed yet.
roirraW "edor" ehT said:
One or two of any of these will get you there. By the way, have you tried restoring a backup in TWRP recovery?
http://forum.xda-developers.com/showthread.php?t=2698401
http://forum.xda-developers.com/lg-g-pad-83/development/vk810-4g-altev-verizon-lg-g-pad-8-3-t2990481
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-verizon-lg-g-pad-8-3-to-stock-t2800857
http://forum.xda-developers.com/lg-g-pad-83/general/vzw-lg-g-pad-return-to-stock-easy-t2930373
Click to expand...
Click to collapse
The first option certainly appears to be the easiest option, though the VK810 is not mentioned anywhere in the thread?
Thank you very much for your help!!
ddodge68 said:
The first option certainly appears to be the easiest option, though the VK810 is not mentioned anywhere in the thread?
Thank you very much for your help!!
Click to expand...
Click to collapse
It's not specifically only for the VK810. It's an LG tool for the PC for downloading whatever appropriate newest ROM is for the particular device that's hooked up to the PC.
The downside of this option is that unless you take extra measures, it'll delete what it downloads after it's flashed your tablet. What it downloads is the same as what I put I think in the second link (my upload of the 23A KDZ). If you either download the KDZ manually using another tool in one of the other threads, or save what it downloads (you can copy the file while it's doing the flashing), then you can use that other tool to reflash it again if it becomes (hopefully not) necessary in the future. No sense repeatedly downloading the same large file(s).
It'll get you there no matter what, though.
And you're welcome!
Since I was already in the process of downloading the kdz file, I am just using "option 3" from your list. When I get to step 14, it says "Then open shttps folder and run http". I found the folder, and the file "http.cfg", but when I attempt to run it, I get the attached message. Am I missing something?
ddodge68 said:
Since I was already in the process of downloading the kdz file, I am just using "option 3" from your list. When I get to step 14, it says "Then open shttps folder and run http". I found the folder, and the file "http.cfg", but when I attempt to run it, I get the attached message. Am I missing something?
Click to expand...
Click to collapse
I haven't had to use the offline fix stuff so I'd consider that optional. Sorry, didn't realize that the link in that third post led to more complicated instructions than what I've used. All you need is the KDZ, the LG USB driver for the VK810 4G, and the LG Mobile 2014 tool.
Sent from my VK810 4G
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:
I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying
Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)
MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...
Have you tried flashing a stock ROM with the qcom download tool
abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.
Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.