Hello,
I have an LG G watch w100 that only boots to the LG logo. Initially I thought this to be a battery issue however it appears to be pulling correct power, and it also stays powered on while at recovery or fastboot screens. I do not know the entire story behind this as far as how it got to this point. I have been doing some research on here and other forums to figure out how to re flash it with stock firmware. Factory reset on the device does not do anything different. It recognizes in ADB when in "apply update from adb" mode. However I am having a gap of knowledge between this recognizing in ADB and me being able to restore it. I found a link to the original 6.0.1 software on here, but the video was using the round version of the watch. I have the MEC23G version, I saw a post here posting factory images but the link is dead. Not looking to root this by any means, just looking to get it working again. Any help greatly appreciated. I have tried to use the sideload command in ADB with the file I downloaded but it does not recognize that as correct syntax. I also cannot verify if usb debugging is on or off as the device cant boot fully. I have limited ADB experience .
Thank you in advance
Related
My Moto G XT1032 won't boot, it gets into the boot animation then goes to a black screen and does nothing, I can get into the fastboot and recovery menus however when I try to do anything through adb and fastboot it's saying either waiting for device or device not found. I wanted to return back to stock 4.4.4 so I could get the lollipop update, bootloader is unlocked. When I connect my phone to the PC is makes the sound that it's connected but it won't show the internal storage, the drivers are there since I checked in device manager.
Is my phone bricked?
Any helped will be gladly appreciated!
Thanks!
iscopesiz said:
My Moto G XT1032 won't boot, it gets into the boot animation then goes to a black screen and does nothing, I can get into the fastboot and recovery menus however when I try to do anything through adb and fastboot it's saying either waiting for device or device not found. I wanted to return back to stock 4.4.4 so I could get the lollipop update, bootloader is unlocked. When I connect my phone to the PC is makes the sound that it's connected but it won't show the internal storage, the drivers are there since I checked in device manager.
Is my phone bricked?
Any helped will be gladly appreciated!
Thanks!
Click to expand...
Click to collapse
Your phone is soft-bricked, but since it boots to all those modes, should be easy enough to get going. Not sure why you would expect the internal storage to show up if the device isn't booting...? Do you have a custom recovery installed? You didn't mention what you did before it stopped booting correctly either, which could be helpful info for troubleshooting. Are you sure the correct drivers are being loaded? Are you using adb and fastboot when the phone is in the correct mode to receive the commands? Fastboot doesn't work in recovery, adb doesn't work in bootloader mode, etc. Worst case scenario, just restore with RSD Lite. If you are still having issues connecting to it, then uninstall all Moto drivers, reboot the PC, then reinstall them most recent Motorola Device Manager and try again.
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Hi,
I earlier had cyanogen mode installed in my lg l9 P765. I also had clockwork mode recovery installed for doing the same. Recently i saw a post to flash android lolipop to my phone by artas in http://artas182x.tk/android-projects/android-5-0-lg-optimus-l9-aosp/. I installed TWRP . But since i couldnt proceed to enter TWRP recovery, i just tried using `reboot recovery` via terminal. This got my phone bricked as i cannot access my device using ADB or Fastboot. All i see when restarting is the LG logo. And all i can access is the software upgrade mode. Since i had came across such a situation earlier and overcame it using the method to flash new rom offline, i followed the guide given in forum.xda-developers.com/showthread.php?t=2085344 by @cmahendra. But i always got the process stopping at 15% telling that the phone and usb arent connected. I couldnt download any of the roms listed in the same page as the links seems broken. Is there a possible way to get out of this issue?
Thanks
HI. Do you already solved the problem?, If not. Check you have correctly installed the drivers of L9 and using the "LG Flash Tool" ( http://forum.xda-developers.com/showthread.php?t=2797190 ) Install your KDZ... if it shows any errors during the process, allowed to continue in the background, do not close the error window.
Hi,
I need the LGAS323 firmware kdz file(which i have not found). I've been trying with the MS323 kdz through the LG flash tool but it doesn't work(error).
So this is what happened:
I tried to install CWM recovery after unlocking boot and installing fastboot. So after all that I put the command to start transfering the cwm file and the phone got bricked. Now it doesn't even show up the LG logo. It just power up the screen which people call "purple screen" or black... It vibrates one time whenever I connect it to the PC or push the power button.
This is what I've tried:
I have tried all methods I have found on forums and YouTube. I tried with Linux on the terminal fixing the aboot.img and also on PC with the LG FLASH TOOL and other apps but nothing works. Folks help me with this please. I think the only thing that would fix it is using Jtag or something like that you know the boxes(riff, octocplus...). But without the exact firmware it wouldnt work anyway.
Any expert here?
Thanks.
The phone wont go into download mode! BTW.
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
xor512 said:
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Click to expand...
Click to collapse
same here, we are two now.
Don Pedro! said:
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
Click to expand...
Click to collapse
your phone cannot be trusted loooooop, cannot goto download and fastboot mode...
If you don't manage to enter download mode you have probably indeed bricked the phone. If what I've written above doesn't work for you I know of no other way to resurrect it, sorry.
This is because you cannot burn TWRP to the Flash plus there's no tool available to bootstrap an LG phone with a completely naked or corrupted Flash. There must be something like that, because a freshly manufactured phone has by definition a naked Flash.
With Samsung phones you have Odin and with it it is possible to burn a software to a completely dead phone. So it is almost impossible to hard brick it. With LG unfortunately it is different. Plus this phone is somehow crippled, it has only a very, very limited amount of Flash. So I would recommend to not care for this phone anymore, it's not worth it, and instead get a current one with a decent amount of memory.