Hello,
I have my G watch R for a week and because there was no update, i've tried to install it by myself after reading some posts on XDA.
I've tried that :
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
All this works until the "sideload" part because ADB can't see my watch when it's on recovery mode.
So i have locked again the bootloader and i thought to give up, when yesterday, OTA arrived...
But it hasn't worked : a bar has loaded and it arrived on a red triangle with an exclamation mark, i've clicked on it and i had the recovery mode menu (reboot, install from adb, etc)
What can I do to make work this OTA ?
Thanx for help !
have you tried to flash the original recovery?
Yes, I've tried several times, I think that is why i can't update with OTA.
But is there a solution ? Is it possible to reinstall original recovery and will it solve my problem ?
Or must I install the update with ADB ? Because I still don't know how make the watch recognized when in recovery mode (not even recognized with a yellow triangle, like it was unplugged )
I had the same problem but with 4.4w.2 and I solved it flashing the stock recovery. unfortunately I can not find your recovery version, I would have linked. to manually update do not know ... I'm sorry. Find your recovery and flash it!
Thanx for your answer,
I thought to do that, but I neither have found 44w1 stock, i'm trying with 44w2 stock and it doesn't work.
I'll try to find 44w1 stock, thanx for confirmation about this way.
So, while I can't find 44w1 stock (i think nobody has uploaded it on the internet because nobody wants to put 44w1 on his watch ^^ ), I've tried TWRP Recovery
When I try to launch the 5.5.1 zip install , I have this error message on the watch in TWRP Recovery :
"this package is for device: lenok. this device is dory"
I've made some research and found that Dory is for G Watch and not for G Watch R, so what ?
I don't understand...
Anyway, if someone knows where to find 44w1 stock...
Did you enabled the debugging mode and gave permission for it on the watch?
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Have a look here... http://4pda.ru/forum/lofiversion/index.php?t647135-20.html.
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Genna7 said:
Did you enabled the debugging mode and gave permission for it on the watch?
Click to expand...
Click to collapse
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
2k4ever said:
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Click to expand...
Click to collapse
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
dunjamon said:
Have a look here... *url*
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Click to expand...
Click to collapse
Thank you but i have all those images, I think I need 44w1 recovery and only this one
Thank you all
what happens if you just flash the 4.4w2 full image? I remember there being issues with the 4.4 recovery and I had to manually update to the 5.0.1 recovery before then upgrading further.
edit...what drivers are you using? I think you need the adb composite ones and not the normal adb ones.
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Ze_Pend said:
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Click to expand...
Click to collapse
The OTA ones from my link.
Ze_Pend said:
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
Click to expand...
Click to collapse
flashing a recovery happens in fastboot mode, which requires an unlocked bootloader, but not enabling the debugging mode
sideloading however happens (once the recovery has been loaded) through ADB - and ADB requires the right drivers on your PC as well as the right tools/developer environment
try to connect your normally booted watch to your PC and run
PHP:
adb devices
if that lists your watch, you are good to go, otherwise ADB isn't set up properly
The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode.
That's what I said first
dunjamon said:
The OTA ones from my link.
Click to expand...
Click to collapse
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Ze_Pend said:
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Click to expand...
Click to collapse
Do you have the G Watch R (round) or the G Watch (Square)?
"The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode."
I had this problem too. When you're in recovery mode you have to open the windows device manager and windows should tell you something about an uninstalled driver. You need to right click this device and install the adb drivers.
Related
I need some help...I updated my firmware and I must of updated with the wrong firmware...did they one with stock recovery or something. Now my phone doesn't have a custom recovery and I do not have root. I tried to download the trwp tool and flash but it says I do not have root. Also when I try to adb connect to my phone it doesn't recognise that the device is there. I am running Insert Coin 4.4.4 version 5.03. Any help is much appreciated! Also I should mention the firmware was from Captain Throwbacks thread with the latest. I am also Soff.
Very strange @Captain_Throwback's firmware should not have stock recovery included.
You can fastboot flash twrp.
ADB = OS/Recovery
Fastboot = Bootloader
My computer won't even recognize my phone now so I can't flash anything through fastboot. The command prompt says waiting for device
kpahl1973 said:
My computer won't even recognize my phone now so I can't flash anything through fastboot. The command prompt says waiting for device
Click to expand...
Click to collapse
Are you in fastbootusb ?
Yes fastbootUSB and its in red letters
kpahl1973 said:
Yes fastbootUSB and its in red letters
Click to expand...
Click to collapse
Unplug phone
Uninstall everything HTC and reboot PC
Install these drivers
Plug phone in (drivers should install)
If not try this:
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Thanks that worked...flashed the recovery successful but wont let me go into it. I think its because I am not rooted. Do I just use the all in one tool to get root back?
kpahl1973 said:
Thanks that worked...flashed the recovery successful but wont let me go into it. I think its because I am not rooted. Do I just use the all in one tool to get root back?
Click to expand...
Click to collapse
If it flashed successfully you should be able to get into recovery.
Are you sure you flashed the correct version? There are several for the M8.
I ended up flashing another version and I got into recovery. Root Checker still says I dont have root so I am going to wipe and reflash my rom. Hopefully that will do it. Not sure what happened but I really appreciate the help with getting the drivers corrected so I could communicate with my device again. With out adb I didnt know what I was going to do.
Hello,
I tried to install the new andoird wear 5.1.1 from this guide: http://forum.xda-developers.com/g-watch-r/general/install-android-wear-5-1-1-to-lg-g-t3114528
and after step 4 i close the "fastboot flash system system_gwr_5.1.1.img" before the install is done (i wait an hour and nothing append).
And now i stuck on the LG logo.
I tried to install again by the guide, but i cant use fastboot, it's write "wating for device".
What to do?
Thanks!
Edit: now the watch reach to the Android system but I have problem with the touch screen that not response. And because of that I can reach to the bootloader and the recovery mode...
Try to hardreset the watch. When you start your watch up and see the LG logo wipe fron 11 to 4 accros the screen.
Genna7 said:
Try to hardreset the watch. When you start your watch up and see the LG logo wipe fron 11 to 4 accros the screen.
Click to expand...
Click to collapse
The touch screen doesn't work after I tried to update the Android wear.. So I can't go to the bootloader...
Someone? Please help!
I am willing to pay to the person that will help me find a solution.
Please help!
Have you figured this out yet?
Spyderekz said:
Have you figured this out yet?
Click to expand...
Click to collapse
No. You also have this problem?
There is a lot of people with this problem in this forum...
Someone know a place that specializes in android wear watches? (please send me, no one knows how to solve this problem here )
try the adb command "adb devices" and "fastboot devices"
I don't think the first one would work (because you are in fastboot mode), but the second should tell if the pc "sees" the watch!
I had to manually install the "android adb composite" device driver in the win device manager...
TML1504 said:
try the adb command "adb devices" and "fastboot devices"
I don't think the first one would work (because you are in fastboot mode), but the second should tell if the pc "sees" the watch!
I had to manually install the "android adb composite" device driver in the win device manager...
Click to expand...
Click to collapse
The computer does not recognize the watch at all...
same here
well, same here: no touch screen, device is not recognized (but boots up to welcome screen) => not able to get into bootloader. Guess, I have to activate developer/debugging mode in the Wear-settings to get it recognized. But how, without touch? Any ideas?
So do you think there is hope for unbricking the watch R from that state ? (mine is the same)
Maybe LGFlashtool will work ? maybe TOT firmware file will be available ?
I am having the same issue after trying to install the stock rom, probably a wrong rom. The watch boots onto a lg logo, stays for a minute or so and reboots into a a boot loop. There is no way to access bootloader or fastboot. Swipe to enter bootloader does not work, tried hundred times, it is like the screen were unresponsive. I have no idea what to do, seems it is bricked.
If I keep pressed the physical button then reboots but lg logo again after a long vibration. Drained the battery, put it on the cradle and then boots onto the lg logo.
anyone?
anyone here has found a solution for this issue?
I am also in the same situation. LG logo stuck after installing a new rom, unresponsive screen no mather if connected to the charger or not. Tried with different computers and OSses, the watch is not recognised.
had this problem as wrong I used the wrong kernel, but I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
Link to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this help.
johnnyle7 said:
had this problem as wrong I used the wrong kernel, but I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
["h**ps: //android. googleapis.com/packages/ota/lge_bass_bass/7252d535d6a18047daaf3bfd4745f1c86ef7e7f1.signed-bass-ota-2576000.zip"] to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video ["h**ps: //w*w. youtube.com/watch?v=ZmBY9KM1NE8"].
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this help.
Click to expand...
Click to collapse
There is no way to put watch into bootloader mode since screen does not respond.
jogo said:
There is no way to put watch into bootloader mode since screen does not respond.
Click to expand...
Click to collapse
did u watch the video in one of the posts above?
johnnyle7 said:
did u watch the video in one of the posts above?
Click to expand...
Click to collapse
I did. The screen does no respond to touch so 11 to 4 does not work either. I hace tried hundred times and even tapping with 2 fingers which I have seen working in any other vídeo around
same over here.
And this happened without tryng to hack anything (for once in my life)
any update?
Hello,
So I have a P7 at B126. I tried rooting it with kingroot and tried to install TWRP. I got to the part where you have to use fastboot to flash the img and it fails so I gave up. Now I am trying to get into recovery and I can't. It just either goes to a black screen or a Boot failed screen.
Thanks in advance
Hi, I'm a little confused right now. Explain what you did so far a bit more detailed, so we could help you.. Which instruction were you are following? What was the exact error? Is your bootloader unlocked? Can you boot normally?
l3Nni said:
Hi, I'm a little confused right now. Explain what you did so far a bit more detailed, so we could help you.. Which instruction were you are following? What was the exact error? Is your bootloader unlocked? Can you boot normally?
Click to expand...
Click to collapse
I can boot normally.
What I did was this.
I followed the guide to root my phone. Rooted it and then tried to install the TWRP custom recovery. It failed at the installing the recovery for some permission error. So I stopped trying to install it. Now I apparently don't have a recovery at all.
I also installed some root apps like SetCPU, Xposed(Which didn't work), SuperSU(Which didn't Work)
If I try to adb reboot recovery it just takes me to the boot failed screen with the android logo on it. If I try using the Power + Down button it just shows me the huawei ascent P7 screen and just go black.
Also when I go to the fastboot/rescure mode it says my bootloader is unlocked.
Thanks for the reply.
Ah okay. So, boot into the fastboot mode, put the recovery.img in the adb folder on your pc, run cmd and type 'cd c://..' (location of adb folder), then 'fastboot flash recovery [name of recovery.img]' (for example 'fastboot flash recovery recovery_twrp.img'). Now you should get a working recovery.
Are you sure you really got root access? Eventually due to this you got the permission error..
l3Nni said:
Ah okay. So, boot into the fastboot mode, put the recovery.img in the adb folder on your pc, run cmd and type 'cd c://..' (location of adb folder), then 'fastboot flash recovery [name of recovery.img]' (for example 'fastboot flash recovery recovery_twrp.img'). Now you should get a working recovery.
Are you sure you really got root access? Eventually due to this you got the permission error..
Click to expand...
Click to collapse
I do because adb has admin permissions but fastboot doesn't. I tried that with trying to flash twrp on my p7 but i get a failed error after like a second I the command. So I tried flashing a stock recovery and it throws the same error in fastboot.
When I type fastboot devices I get this
? fastboot
No id for my phone but adb sees it.
Ok, your pc does obviously not recognize the p7 in fastboot mode. Did you install the Hi Suite? Through this way you should get the correct drivers (maybe even update/reinstall). If this does not help, I think I can't help you, sorry. You may wait for more help or google what do when the device isn't recognized in fastboot.
Just flash the newest SuperSU.zip when you got a recovery.. That should fix problems with root apps/ the su binary.
Offtopic: I'm not sure if you noticed, but, you're running a pretty old firmware.. You may think about updating
l3Nni said:
Ok, your pc does obviously not recognize the p7 in fastboot mode. Did you install the Hi Suite? Through this way you should get the correct drivers (maybe even update/reinstall). If this does not help, I think I can't help you, sorry. You may wait for more help or google what do when the device isn't recognized in fastboot.
Just flash the newest SuperSU.zip when you got a recovery.. That should fix problems with root apps/ the su binary.
Offtopic: I'm not sure if you noticed, but, you're running a pretty old firmware.. You may think about updating
Click to expand...
Click to collapse
Hi Suite installed and correct drivers are loaded(I hope) and yes thats why Im trying to get this fixed because it wont even let me update firmwares
Try on another pc.. You could also try flashify (look in Google play), but in case of a softbrick you have real problem. Do this on your own risk, most times nothing bad will happen, but it could!
I would recommend to flash the stock recovery, update up to B621 and then installing a custom recovery.
can't boot into recovery
stoutrouge said:
Hello
So I have a P7 at B126. I tried rooting it with kingroot and tried to install TWRP. I got to the part where you have to use fastboot to flash the img and it fails so I gave up. Now I am trying to get into recovery and I can't. It just either goes to a black screen or a Boot failed screen.
Thanks in advance
Click to expand...
Click to collapse
Hi mate.
1. Use your pc, Go shuame.com and download "rom flash program".
2. Enter fastboot&rescue mode and connect your phone and PC
3. The program will recognize your phone.
4. Download anyrom and flash by the program.
The process will not complete but you will have Shuame recovery.
But my case it didn't work properly
5. I downloaded CWM from here "pan.baidu.com/s/1dDq0qcT" password :bttc
Start this program with connect your phone and press nomber 1 and ENTER.
I don't exactly remember my phone was on fastboot & rescue mode or recovery mode.
But I could get recovery and did rom flash so it was fixed.
*****from: Godfrey Peligrino ---sorry i dont know how to post BUT, this guide helped me with my p7 L10 B619..just connect it to pc and let it boot over and over and when pc acknowledge you phone..click rom and just wait if not do it again..hope this will help you too..the writings is on chinese so just copy the english thumbnails before you proceed to download...(QUOTE) THANKS TO THE GUY WHO POST THIS....HE IS TOMODACHI5..
Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4
When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.