Hello everybody,
I am new here, but after many searches I found out that this forum can be quite useful. Unfortunately I couldn't find the answer to my problem. Here you go, I start very well for my first thread:
I just got a HTC one M7 international version GSM from a friend, very nice phone and it was already rooted and had Trickdroid installed on it. I started to talk to my friend and he told me I should install KIt Kat on the phone... and from there it went all wrong...
I tried to install a KIT KAT rom I found online, it didn't work and the phone wouldn't start anymore, I would just have access to recovery mode (CWM is installed) and fastboot/bootloader. From there, the phone wasn't recognized anymore by my pc when connected to USB. I then used a mini USB cable to connect a USB key with different .zip file to load them to the phone.
After many attemps, one file finally worked (all the other would abort installation), it was insertcoin M7 kustomizer... I know I should have had reloaded Trickdroid 11.0.0 on it, but it was taking ages to download and went the fast way... which was a really bad decision I guess.
After the installation of insertcoin, the phone rebooted and... rebooted...and keeps rebooting to the HTC white screen (with the red warning: this build is for...)... it goes on and on...
Only thing I can do is hold the volume down key when it reboots and then it takes me to fastboot/bootloader. From there when I try to go to recovery mode it goes to recovery mode for half a second and reboot directly to the white HTC screen over and over again....
Also, USB device is not recognized (but strange, HTC sync manager starts even though it tells me no phone is connected).
Now I have the Trickdroid 11 file ready (1.1GB) but there is no way to install it on the phone... I really don't see how to do it anymore, did I really screw up big time and my phone is more or less a dead weight?
I am going to Kuala Lumpur, Malaysia at the end of the week, maybe someone will be able to find a solution for me...
I shouldn't have touched a phone that was working very well....I know...
Nobody? So my HTC one is dead?
Is the all in one tool going to help? I installed it but since my phone is not recognized by the computer (windows 8.1) when connected via USB, I don't seem to be able to do anything...
sedoriku said:
Is the all in one tool going to help? I installed it but since my phone is not recognized by the computer (windows 8.1) when connected via USB, I don't seem to be able to do anything...
Click to expand...
Click to collapse
This is all if you can find a way to get files to your phone...
I'm not sure which recovery you have but when upgrading from Android 4.2.2, and 4.3 the recovery you are using needs to be updated to the most current version. For example if you are running TWRP recovery you need to be running TWRP 2.6.3.3 for everything to run smoothly. In order to do this though you will need to download your original ROM (No matter how long it takes). Then go google play store and download goo.im and update you recovery with openrecoveryscript and update from there and you should be fine. I would also like to note that it's fully recommended that when you flash 4.4 KK you do a full wipe. This means userdata/cache/dalvik cache wipe, otherwise you will run into problems. Let me know if I missed anything or if you have anymore questions!
Thank you, but unfortunately I still couldn't find a way to access the files on the phone, no matter what I do. The phone starts by itself to the HTC white screen when I connect it to the main to charge it... I can only access fastboot/bootloader... I feel useless...
I feel your pain
sedoriku said:
Thank you, but unfortunately I still couldn't find a way to access the files on the phone, no matter what I do. The phone starts by itself to the HTC white screen when I connect it to the main to charge it... I can only access fastboot/bootloader... I feel useless...
Click to expand...
Click to collapse
After my htc one freezing on the 'quietly trickdroid' loading screen my phone will now not turn on, AT ALL! I think it's screwed : S
I just arrived in Kuala Lumpur and took it to a little shop, they told me they will fix it for me by tomorrow for 50USD... I'll let you know tomorrow if they managed to make the magic happen. I think they would reinstall stock, but that's fine with me, much better than a bricked "rooted" phone. It will take me a while before I start to screw up with a phone again...
Related
So I rooted my sister's optimus v about a month ago. Today she installed a battery mod app from applanet and as soon as she chose which battery mod she wanted she had to restart her phone for the changes to be applied, but when rebooting the phone it would only get stuck in reboot. So I tried to start it up in recovery and got the blue screen that says fastboot mode started. I looked that up online and found a fix to it but I need it to go into emergency mode to fix it that way and it will not go into emergency mode, any combination of keys only takes it to either the blue screen with the fastboot mode message or it just reboots and gets stuck. So now what do I do? I really need to find a way to fix her phone. Thanks in advance to anyone who tries to help.
try to turn on the phone & use LGMobile update tool. That should recognise the phone & install original lg fw
tabs648 said:
So I rooted my sister's optimus v about a month ago. Today she installed a battery mod app from applanet and as soon as she chose which battery mod she wanted she had to restart her phone for the changes to be applied, but when rebooting the phone it would only get stuck in reboot. So I tried to start it up in recovery and got the blue screen that says fastboot mode started. I looked that up online and found a fix to it but I need it to go into emergency mode to fix it that way and it will not go into emergency mode, any combination of keys only takes it to either the blue screen with the fastboot mode message or it just reboots and gets stuck. So now what do I do? I really need to find a way to fix her phone. Thanks in advance to anyone who tries to help.
Click to expand...
Click to collapse
give a try to error guides over here http://forum.xda-developers.com/showthread.php?t=883314 it has done wonders for many flash in cs emergency mode from the flasher menu. Read detail guide in the link provided.
I am not sure if it works for optimus v but it does works for optimus 1. give it at try
I managed to finally get the phone into emergency mode. I had installed the LG mobile support tool and installed all the drivers and tried to go that route but it kept telling me I only had one of four drivers installed, even though I have installed several drivers. After all of that I had finally got it into emergency mode so I went back to trying KDZ. I'm supposed to select the rom where it asks for the KDZ file right? But when I go to browse for the rom file it doesn't show up in the folder I put it in. I've rooted 4 phones and have done so many other things with them and never bricked one, was always able to figure out everything I did and never had to ask any questions but I can't figure this out to save my life and it is driving me crazy. I do really appreciate you guys for the suggestions and thanks to your suggestions I have gotten this far.
Hey, I have the same problem. I rooted my phone then I installed that battery mod app on applanet. I installed it then when I had to restart my phone for it to apply it just got stuck and kept looping the reboot screen where it says "ANDROID". Did you get ur fixed yet?
tabs648 said:
I managed to finally get the phone into emergency mode. I had installed the LG mobile support tool and installed all the drivers and tried to go that route but it kept telling me I only had one of four drivers installed, even though I have installed several drivers. After all of that I had finally got it into emergency mode so I went back to trying KDZ. I'm supposed to select the rom where it asks for the KDZ file right? But when I go to browse for the rom file it doesn't show up in the folder I put it in. I've rooted 4 phones and have done so many other things with them and never bricked one, was always able to figure out everything I did and never had to ask any questions but I can't figure this out to save my life and it is driving me crazy. I do really appreciate you guys for the suggestions and thanks to your suggestions I have gotten this far.
Click to expand...
Click to collapse
I'm having the same issue right now, although at least you have managed to get it into emergency mode. How did you do it?
The other issue I'm seeing is that there is no .kdz for the Optimus V LGVM670. I found a .cab file that is supposed to be the newest update, but not even sure that will work with the the kdz manager.
It was my sister's phone and I had the same problem with kdz. Had the cab file so couldn't use it with kdz. My sister left her phone with me for a few days to try to fix it and when I couldn't she took it home and managed to fully brick it to where it would do nothing at all so she had to get a new phone. I got it into emergency mode by holding down the volume and it was either the back button or the home button I pushed at the same time, can't remember which. As I held those down I plugged in the USB cord that was connected to my laptop and it went right into emergency mode. Just make sure you disable that LG modem in the device manager on the computer before doing anything because my sister forgot to do that and that is how she fully bricked her phone. Good luck to you guys and if anyone figures out how to fix it I would be interested in knowing how you did it.
tabs648 said:
It was my sister's phone and I had the same problem with kdz. Had the cab file so couldn't use it with kdz. My sister left her phone with me for a few days to try to fix it and when I couldn't she took it home and managed to fully brick it to where it would do nothing at all so she had to get a new phone. I got it into emergency mode by holding down the volume and it was either the back button or the home button I pushed at the same time, can't remember which. As I held those down I plugged in the USB cord that was connected to my laptop and it went right into emergency mode. Just make sure you disable that LG modem in the device manager on the computer before doing anything because my sister forgot to do that and that is how she fully bricked her phone. Good luck to you guys and if anyone figures out how to fix it I would be interested in knowing how you did it.
Click to expand...
Click to collapse
hmmmmm, I don't remember completely how I did it, but there was a very helpful guide floating around XDA. I bricked my Mom's Optimus one as well . I actually had to go to the LG support site, type in my Phone serial number and find a list of all the firmware available. From there I right clicked the page and got the page source. From there I got my firmware and I entered it in the KAZ or LG B2I Agent ? - Dont quite remember. Anyways, it ended up working out for me, but I accidentally flashed the German firmware, but in the end, everything was all good LOOL.
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
Good day all
Need some help with my phone?
Blu studio G
The issue:
I had my phone rooted using kingroot.
I wanted to play Pokémon go and thought maybe a update to the os would make it work.
I forgot I had rooted the phone and did an ota update D:
my phone will boot only to the recovery screen.
So now I have the recovery screen and nothing more, will not load past it. I have tried getting the stock rom and placing it on the sd card however it fails to load ( will not update). I may not have the right rom? I thought also well F it I’ll pop on a custom rom one found on this site ( mystic os)
Again when placed on sd card and told to update from sd it does not work….
So I am lost as to what I can do. When plugged into my pc I hear it get auto detected then it dies and get auto detected again and keeps looping . I tried using fastboot but the phone seems to not be being picked up by windows right… also used the blu drivers for windows…
I am at a loss and am hoping someone has an idea of something for me to try…. I have the android sdk but no idea how to use it (was thinking I might need to use adb ???)
any and all help would be much appreciated
self bump :crying: