Related
I've been searching while at work trying to find someone with a similiar issue and have not met any luck.
I've tried the 2 different 1 touch root programs to no avail. I am able to unlock my device fine, but once it tries to push the img for CWM the Nexus 7 becomes unresponsive. It will lock up. The only way to get out is to hold the power button until it powers off.
After a few attempts with both 1 click tools I gave up and just decided to use ADB and do it myself.
What I can do:
lock/unlock the device.
reboot to and from the boot loader.
install apk's while in the Android OS
What I cannot do:
Push any file to the Nexus 7 while in the boot loader.
Once I try to push the img for CWM the device locks up, becomes unresponsive, and the fastboot devices command does not show any devices connected anymore.
Currently using Windows 7 Ultimate x64 and OTA 4.1.1. I've tried numerous known working USB cords and the OEM cord. I've used both sets of drivers included in the 1 click root tools, the "naked" drivers, and the set of drivers that work for numerous devices.
I'm a complete newb with ADB and don't know much about it. is it possible to copy the CWM img to my internal storage and install it from the internal storage rather than pushing it over USB?
I'm currently at work, and do not have admin on this PC or I would try again and see if I have the same problem on a different system. Tonight when I get home I will try my girlfriends PC, and I do have a dual boot of linux I can try from as well. But if her PC and linux both fail I'm probably going to have to return it claiming I have display issues and get a new one.
Intentionally deleted.
Using root tool kit make sure you have stock ROM selected before you select root. Once you have stock ROM selected you should be able to root.
mcdermott1 said:
Using root tool kit make sure you have stock ROM selected before you select root. Once you have stock ROM selected you should be able to root.
Click to expand...
Click to collapse
When using either root tool, as soon as the tool starts pushing the custom recovery over the Nexus becomes completely unresponsive. The device itself locks up. At this point it does not show up as a connected ADB device anymore on my PC. I need to hard power it off and reboot for my PC to see it again.
Both tools boot it into the bootloader fine, and both tools can unlock the bootloader fine. I can do it with ADB manually as well. But as soon as any of them start actually pushing the CWM img file over that's when the Nexus locks up. Volume up/down do nothing, power does nothing, my pc doesnt recognize the device anymore either. All I can do is hard power it off by holding the power button.
At this point I'm convinced it's either some strange issue on my PC, or the nexus itself. I'll know for sure once I try it again on my girlfriends computer tonight.
roblol said:
When using either root tool, as soon as the tool starts pushing the custom recovery over the Nexus becomes completely unresponsive. The device itself locks up. At this point it does not show up as a connected ADB device anymore on my PC. I need to hard power it off and reboot for my PC to see it again.
Both tools boot it into the bootloader fine, and both tools can unlock the bootloader fine. I can do it with ADB manually as well. But as soon as any of them start actually pushing the CWM img file over that's when the Nexus locks up. Volume up/down do nothing, power does nothing, my pc doesnt recognize the device anymore either. All I can do is hard power it off by holding the power button.
At this point I'm convinced it's either some strange issue on my PC, or the nexus itself. I'll know for sure once I try it again on my girlfriends computer tonight.
Click to expand...
Click to collapse
If what your describing is when you go to push custom recovery screen locks up should be black screen with Google on it then your computer says can't find device something like that. Mine did the same thing, in the tool kit upper left corner it ask for model type, make sure you have correct Android selected. I selected custom rom by mistake and it just hung there on the black screen. It should list custom ROM, Android 4.1, or Android 4.1.1 Select what you have and it should work....hopefully.
mcdermott1 said:
If what your describing is when you go to push custom recovery screen locks up should be black screen with Google on it then your computer says can't find device something like that. Mine did the same thing, in the tool kit upper left corner it ask for model type, make sure you have correct Android selected. I selected custom rom by mistake and it just hung there on the black screen. It should list custom ROM, Android 4.1, or Android 4.1.1 Select what you have and it should work....hopefully.
Click to expand...
Click to collapse
Unfortunately not. I have selected the right options. It freezes on the bootloader screen. It never even makes it to the boot stage. I've tried to flash a recovery permanently and temporarily boot from a recovery as well. It freezes either way.
Additionally if I boot to the boot loader, and select recovery it will not boot into the stock recovery at all... It just sits at the google splash screen with the unlocked padlock.
roblol said:
Unfortunately not. I have selected the right options. It freezes on the bootloader screen. It never even makes it to the boot stage. I've tried to flash a recovery permanently and temporarily boot from a recovery as well. It freezes either way.
Additionally if I boot to the boot loader, and select recovery it will not boot into the stock recovery at all... It just sits at the google splash screen with the unlocked padlock.
Click to expand...
Click to collapse
I have the same problem on my nexus... it just freezes.
Roc1992 said:
I have the same problem on my nexus... it just freezes.
Click to expand...
Click to collapse
Did you get this fixed? I have the same issue
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
Hello folks, last night I was trying to go back to stock using MiFlash, the flash worked ok (though it didn't automatically reboot) so I powered it on and off and it ended up in a endless bootcycle where I would get a black screen and then a half second flash of the Android Guy on the operating table with the words "no command” and some small text at the bottom of the screen I was unable to read.
I couldn't power it off , it just kept cycling through black screen, Android Guy on operating table for split second, then blank screen.
I left it to run over night to see what would happen, this morning the battery was completely dead, I plugged it in, let it charge for a while and turned it on, this time I just got this screen, the "warning your devices bootloader is unlocked screen"
https://ibb.co/1GTBkrG
The 5 seconds is a ruse, it's been on that screen for hours, the phone isn't warming up at all so it's not working in the background, I can't force power down with any combination of buttons.
And suggestions what I should do, I really liked this phone and I got it for a steal brand new
jonathonsunshine said:
Hello folks, last night I was trying to go back to stock using MiFlash, the flash worked ok (though it didn't automatically reboot) so I powered it on and off and it ended up in a endless bootcycle where I would get a black screen and then a half second flash of the Android Guy on the operating table with the words "no command” and some small text at the bottom of the screen I was unable to read.
I couldn't power it off , it just kept cycling through black screen, Android Guy on operating table for split second, then blank screen.
I left it to run over night to see what would happen, this morning the battery was completely dead, I plugged it in, let it charge for a while and turned it on, this time I just got this screen, the "warning your devices bootloader is unlocked screen"
https://ibb.co/1GTBkrG
The 5 seconds is a ruse, it's been on that screen for hours, the phone isn't warming up at all so it's not working in the background, I can't force power down with any combination of buttons.
And suggestions what I should do, I really liked this phone and I got it for a steal brand new
Click to expand...
Click to collapse
do the same again, just enter EDL and reflash the package with miflash, but this time check the "clean all" option on the bottom. maybe it'll work
Otherwise you can do a couple other things. If your phone is unlocked you can flash any TWRP via EDL Tool and format data (I assume this is your problem); if it is not unlocked there's a very old signed TWRP that will do just fine too.
Choose an username... said:
do the same again, just enter EDL and reflash the package with miflash, but this time check the "clean all" option on the bottom. maybe it'll work
Otherwise you can do a couple other things. If your phone is unlocked you can flash any TWRP via EDL Tool and format data (I assume this is your problem); if it is not unlocked there's a very old signed TWRP that will do just fine too.
Click to expand...
Click to collapse
Do you mean "Flash All" ? I'm using MiFlash 2016.04.01
jonathonsunshine said:
Do you mean "Flash All" ? I'm using MiFlash 2016.04.01
Click to expand...
Click to collapse
idk. The newest one works, so you can just get that one instead of the 2016 one
Also try EDL Tool? I think you can wipe stuff with it. not sure
Yeah the problem is either you formated a partition to f2fs and never went back to ext before your miflash or you have some partition that is messing up the flash (residual files). So what I would do is get back into twrp and make sure everything is in the right format and everything is formated.
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you
need b11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
stevecaboose said:
Yeah the problem is either you formated a partition to f2fs and never went back to ext.
Click to expand...
Click to collapse
That was it. Formatted to EXT4 and booted right up.
jonathonsunshine said:
That was it. Formatted to EXT4 and booted right up.
Click to expand...
Click to collapse
Glad that worked
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?
Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?
Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..
No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.