Hello,
Am I the only one with a boot-loop problem after the .14 update download and install ?
Since then, my tablet has been into a boot loop, and none of the methods found to find in the forums worked sor far.
1) Tried pinhole reset
2) Tried recovery data swipe
3) Tried the "EP201_SDUPDATE.zip" method. It just goes to a screen with a blue diamond in the droid. Then after 20 seconds, the droid is on the floor with a "!" red symbol. After 30 seconds, the device goes back to boot-loop ...
Nothing worked. I tried to root it via adb but somehow I can't install the drivers on my computer, my computer doesn't even see the device via USB since it's stuck in the boot loop.
Did someone had this kind of problem earlier ? I did nothing special, the device is not rooted, nothing ... and had 0 problem with .11 firmware, worked perfectly ...
Thanks for any advice you could have !
I'm having a similar issue since the 14 update. My TP was perfect until last night when the 14 update arrived; but has been suddenly re-booting and getting frozen on the reboot screen since. However, pinhole restart did work, at least temporarily. I'm tempted to try rolling back the firmware.
Likewise, my device is not rooted or altered in any way.
Can't believe they have rolled out a firmware upgrade that actually corrupts a fully functional device! Who are these jokers?
Will update if I find a solution; please do likewise!
I am experiencing the exact same issue since yesterday and so desperate about it since I had no problems at all before. .
So frustrating.
Some more info I found :
During the night I let my device on, rebooting etc ...
I've noticed yesterday it wasn't really a boot loop because sometimes it'd go to the screen with a grey asus logo and a spinner, sometimes it was even going to the screen where the system updates and tries to optimize applications. Each time I went to this screen, it was updating a couple apps then crashing and going back to boot.
So, I figured out that maybe if it was on all night, it owuld update all apps, and boot eventually ...
This morning, the screen was off ... pushed the power button and OH ! I was on the "First start" screen, where I had to choose my keyboard language. Did it, then chose wifi and .... back to boot !
So, it's not technically a boot loop, it's a MASSIVE reboot defect, the .14 firmware totally killed it, the OS doesn't have time to boot, it crashes before ? How can it be ?
I think I'm good for RMA, will try to contact ASUS also ...
Again, same problem for me .
Except the application optimization was made yesterday (not as it should be, I had one reboot after 1/87 applications optimized then the whole optimization).
Since then, sometimes (once in a blue moon), the tablet reboot completely as yours, and then after a few seconds/minutes "playing" on it, it reboots itself.
Etc...
adinava said:
Again, same problem for me .
Except the application optimization was made yesterday (not as it should be, I had one reboot after 1/87 applications optimized then the whole optimization).
Since then, sometimes (once in a blue moon), the tablet reboot completely as yours, and then after a few seconds/minutes "playing" on it, it reboots itself.
Etc...
Click to expand...
Click to collapse
I think our only hope is to recover it using the EP201_SDUPDATE.zip and be lucky enough for the tablet not to reboot during the recovery ... but it might take a lot of tries and it's boring to do ...
I think so. But is it possible to do so without root-access ? What does this method consist of exactly ? Where does this file come from ?
I downloaded the .11 update zip archive from Asus support, isn't it the same ?
adinava said:
I think so. But is it possible to do so without root-access ? What does this method consist of exactly ? Where does this file come from ?
I downloaded the .11 update zip archive from Asus support, isn't it the same ?
Click to expand...
Click to collapse
From what I read root is not required
Yes, it's the good file. Unzip it, inside there will be another zip file.
Rename this : EP201_SDUPDATE.zip
Put it in the root of a microSD card and then put the microSD in the Prime.
Once you've done that, reboot the prime (anyway yours will reboot quickly lol) by holding power and Volume Down button at the same time. Hold it until the first screen of boot comes up and until text appears on the top left.
As soon as you see the text, release everything, then press Volume UP.
It'll say "Booting recovery kernel image" "Signature Match".
If the tablet doesn't reboot before actually starting the recovery, you'll go to a screen with a droid with a blue diamond and then a "dead droid" with a "!" red symbol. I never passed this step as my device reboots before the end of the recovery ...
Good luck
I'm going to try that .
Have you seen testimonials of successful attempts ?
I mean, is it a valid method ?
---------- Post added at 02:18 PM ---------- Previous post was at 02:09 PM ----------
What should I do when I see the dead droid with the exclamation mark ? Wait ?
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
Again, I don't think it's possible without root-access
---------- Post added at 02:22 PM ---------- Previous post was at 02:19 PM ----------
Damn, after a few seconds/minutes,it's rebooting again and stuck at Eee pad logo again
adinava said:
I'm going to try that .
Have you seen testimonials of successful attempts ?
I mean, is it a valid method ?
---------- Post added at 02:18 PM ---------- Previous post was at 02:09 PM ----------
What should I do when I see the dead droid with the exclamation mark ? Wait ?
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
Again, I don't think it's possible without root-access
---------- Post added at 02:22 PM ---------- Previous post was at 02:19 PM ----------
Damn, after a few seconds/minutes,it's rebooting again and stuck at Eee pad logo again
Click to expand...
Click to collapse
It's supposed to work, look here : http://forum.xda-developers.com/showthread.php?p=22768294
I think the problem we're having is that our tablet randomly reboots during the process ...
Yes and no.
As I thought, elsewhere in the post (I already read partially), they said you must have a root-access. Maybe (and I think) the tablet will be unrooted again after that but I'm p***ed off with the idea to root my tablet for a problem I am not responsible for...
adinava said:
Yes and no.
As I thought, elsewhere in the post (I already read partially), they said you must have a root-access. Maybe (and I think) the tablet will be unrooted again after that but I'm p***ed off with the idea to root my tablet for a problem I am not responsible for...
Click to expand...
Click to collapse
They're talking about two different things I think, one thing is to flash the firmware with command line, this requires root of course.
Just wondering if anyone experiencing these reboots has captured a logcat? Seems to be a good first step in figuring out the problem.
Sent from my GT-I9000 using Tapatalk
Maybe, it's not clear out there. And I'm not sure to understand anything anymore.
Perhaps you should ask them to confirm this method doesn't need a root access.
xxbeanxx said:
Just wondering if anyone experiencing these reboots has captured a logcat? Seems to be a good first step in figuring out the problem.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I'd love to, but I'm unable to get adb access to the prime, it reboots before my computer can even install the drivers
Ok so, once plugged with USB to my computer, and when finally the device wants to boot and stays on the "android configuration screen", windows is able to access the TF201 folder system ... but not luck with ADB, I guess that's because the debug option is not activated on the device and I can't pass the first configuration screen, it always reboots before the end of it
Another update : using the EP201_SDUPDATE.zip method, I was able to install the US .14 firmware, but result is the same, reboots like crazy.
I'm currently trying to get the .11 US firmware to try to downgrade, but it's hard to find, asus removed all the older US firmwares from their servers, god knows why
EDIT : found the 11.1 firmware, doesn't work ... I'm stuck with .14 firmware
anthonyalberto said:
Another update : using the EP201_SDUPDATE.zip method, I was able to install the US .14 firmware, but result is the same, reboots like crazy.
I'm currently trying to get the .11 US firmware to try to downgrade, but it's hard to find, asus removed all the older US firmwares from their servers, god knows why
EDIT : found the 11.1 firmware, doesn't work ... I'm stuck with .14 firmware
Click to expand...
Click to collapse
did you try this for downgrade? http://forum.xda-developers.com/showthread.php?t=1492887
cyberguest said:
did you try this for downgrade? http://forum.xda-developers.com/showthread.php?t=1492887
Click to expand...
Click to collapse
I can't use it, no adb access ...
anthonyalberto said:
I'm currently trying to get the .11 US firmware to try to downgrade, but it's hard to find, asus removed all the older US firmwares from their servers, god knows why
Click to expand...
Click to collapse
here old firmwares for prime
Related
Hello,
I got a weird problem after unlocking my phone's bootloader and flashing the kernel:
When I power off the phone, it gets into a state where I cannot control it by itself (black screen, no charging light if connected to a power source, does not react in any way to any key).
However, I am able to access it via adb over USB. Using adb, I can put it into some other state (reboot, reboot bootloader, etc) and again gain control over it (also through its own keys). When I select the "power off" function of the bootloader, it enters this state again.
I can even reboot the phone (also into recovery/bootloader/fastboot) from any state
So I can use the phone, but I can't power it on by itself, which isn't a good situation when I don't have a computer around.
device: HTC One S
ROM: CyanogenMod 10 (device is officially supported by CM10; I used the version I found in the Wiki.)
kernel: The one included in CM10 (had to be flashed manually via fastboot because of restrictions by the device; I flashed the kernel before flashing the ROM)
Does anyone can tell me something more about this (or even a solution)? I don't even know how to call this state
Really no-one?
*push*
It's a really annoying state that I'm depending on a pc when my phone shuts down (which may happen when the battery is empty)
*push*
I really don't know what's wrong with your device. but I have a solution. You can download an app or a widget to turn off your device.
did u checked the md5 of the zip file with the md5 in cyanogenmod site?
RavinduSha said:
I really don't know what's wrong with your device. but I have a solution. You can download an app or a widget to turn off your device.
did u checked the md5 of the zip file with the md5 in cyanogenmod site?
Click to expand...
Click to collapse
Thank you for your reply.
An app or widget should also just call the system's shutdown signal, shouldn't it. And since this also happens when I just turn it off without shutdown (power+volDown), the same happens.
Yes, I checked the md5sum.
sylar_5 said:
Thank you for your reply.
An app or widget should also just call the system's shutdown signal, shouldn't it. And since this also happens when I just turn it off without shutdown (power+volDown), the same happens.
Yes, I checked the md5sum.
Click to expand...
Click to collapse
I have used many apps having shut down option. they are going on a different process
---------- Post added at 08:10 PM ---------- Previous post was at 08:04 PM ----------
in my device power+voldwn = screenshot. don't really know what that command do in HTC device.
RavinduSha said:
I have used many apps having shut down option. they are going on a different process
---------- Post added at 08:10 PM ---------- Previous post was at 08:04 PM ----------
in my device power+voldwn = screenshot. don't really know what that command do in HTC device.
Click to expand...
Click to collapse
Sry, i meant volUp, which turns the power off (crash)
However, the problem has been solved somehow (even though I don't know how). I haven't shut it down for a while to avoid this, so I don't know what I might have done. (Without the purpose of solving this issue)
But again, thank you for your help
if it has been solved, nothing to worry. cheers!!!
Is your device s-on [at the top of the bootloader]? Probably not, but that's supposed to prevent the flashing of a kernel. Sounds like a kernel issue. Did you wipe cache(s) and factory reset after flashing?
bodh said:
Is your device s-on [at the top of the bootloader]? Probably not, but that's supposed to prevent the flashing of a kernel. Sounds like a kernel issue. Did you wipe cache(s) and factory reset after flashing?
Click to expand...
Click to collapse
It is s-on.
I wiped cache and dalvik cache and made a factory reset.
BTW: It's not solved, as I previously thought. Looks like it takes some time to enter this "unbootable"-state, and during this period (about half a minute, maybe less) I can boot the phone as it should be.
As I have frequently done without issues, I was flashing a ROM and got stuck into some sort of bootloop.
Here are some details..
I was on a 4.4.2 KitKat ROM (Gummy Nightly) and decided to try out SlimKat 4.4.2. I wiped (advanced wiped System, Data, Cache and Dalvik Cache). I proceeded to flash the ROM and then the gapps file. Nothing out of the ordinary.. I rebooted and noticed I was at the samsung custom screen for a little longer than normal.. I didn't begin to worry too much because sometimes this screen can appear for a little bit before continuing when first booting into a fresh ROM install. Well.. quite some time passed and it became apparent that it wasn't going to go any further, I restarted the phone and consistently got stuck. I tried booting into TWRP and couldn't/can't get past the TWRP Blue Loading screen. I tried letting it sit for a long ass time (1 hour +) and same with regular rebooting at the Samsung Custom screen (1-2 hours +) with no luck or change.
I have a backup but can't get to it obviously. I'm quite frustrated and am confused/worried about attempting any drastic measures because all of the different phone versions/bootloader discussions/issues. I don't want to mess up the phone by bricking it or something when trying to flash the wrong file. I believe that right now the only thing I can do, if anything, is connecting my phone to my computer via a usb cable and running that ODIN program? I'd be inexplicably grateful and appreciative if someone can just give me some steps/instructions so that I can get my phone back up and running. I'm without a phone right now and am stressed out, so I'm hoping that I haven't made too many people upset with me if there's already somewhere this is answered. I searched but can't find someone with the exact variables my situation contains.
To Recap:
Phone will not progress past samsung custom warning screen as well as TWRP Blue Logo screen no matter how much time passes (Have let sit at either screen for hours)
Was flashing SlimKat nightly (the most recent two days ago) coming from Gummy nightly (1-12, I believe).
The samsung custom screen comes up and then the phone reboots 2 seconds later and comes up again etc..
I never had to use 'safestrap' or whatever. When I got my s4, I was able to avoid the update and was always able to flash ROMs without any worry or concerns.
Please XDA, Help me out here.. I'm completely stressed and worried and don't know where to go from here.. What files to I manually push from my computer.. I don't see how I can solve this without a computer because recovery wont load and ROM won't either
Can you plug it into a pc and get Odin to see it? If so, you can odin back to your stock firmware and start over.
I am having this same problem
a.demarco said:
Can you plug it into a pc and get Odin to see it? If so, you can odin back to your stock firmware and start over.
Click to expand...
Click to collapse
Hey I am having the same problem after trying to flash the latest version of hyperdrive, and my phone got stuck on the Samsung custom screen and I'm not able to get back into recovery even. I saw what you said and plugged my phone into my pc to see if odin could see it, but odin didn't recognize it and I even tried on Kies and it wasnt able to connect to my device either. Is there anything else I can do? or any solution?
If anyone can help I would really appreciate it!
This happened to me several times when i was using Gummy a few weeks back. I just kept doing battery pulls and restarting and was eventually able to get into TWRP. Try this some more and then odin.....
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
ccert said:
Hey I am having the same problem after trying to flash the latest version of hyperdrive, and my phone got stuck on the Samsung custom screen and I'm not able to get back into recovery even. I saw what you said and plugged my phone into my pc to see if odin could see it, but odin didn't recognize it and I even tried on Kies and it wasnt able to connect to my device either. Is there anything else I can do? or any solution?
If anyone can help I would really appreciate it!
Click to expand...
Click to collapse
I'm having your same problem, except mine was with RLS 13.
fafinaf said:
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
Click to expand...
Click to collapse
Just picked up an mdk s4 which was doing the same thing. I odin back to stock and booted into the phone to make sure everything was good. Then I went back into odin and flashed the md2 pre release kernel then booted again into stock and proceeded to use motochopper.
You shouod have 3 files. The mdk tar file and the two kernel files. Worked like a charm for me you sure you're doing the steps correctly?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
Also when mine was doing that it was TWRP 2.5.0 and I threw the newest TWRP on after rooting and its much faster rebooting .
Sent from my SCH-I545 using XDA Premium 4 mobile app
fafinaf said:
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
Click to expand...
Click to collapse
How are you trying to get into recovery?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Power + home +volume up. Then as soon as the phone cuts on let go of Power. Continue to hold the other 2.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mightycaptain said:
How are you trying to get into recovery?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Power + home +volume up. Then as soon as the phone cuts on let go of Power. Continue to hold the other 2.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You don't have to to finger Olympics on s4 like other devices... Just vol up and power
Anyone who can answer,
I own a Swipe Legend. Its specifications are listed below.
I last did 2 things due to which it may have happened.
1. I was using ROM Toolbox Pro to change my font and backup old. I didn't like the new font so restored my old one. But there were too many fonts in the backup, so I thought they were in different uses. I selected all and rebooted. My battery suddenly dropped to about 25% from 48% during changing font some minutes before, and the brightness of pre-boot image was high, I plugged it during that image. Rest is in 2nd reason why I think it could have happened.
2. I put it on charger, forgot it and slept. Later after about 4 hours or so, I did unplug it but it is not working since then. However, this has happened a couple of times with me.
I hope you can help.
Problem: Sorry for not stating the problem first, but I am putting in sequence of time.
Whenever I start it, I can do just 4 things:-
1.See the pre-boot image
2.See the boot animation(the reason I can not show it, as it shows that my phone was rooted. Other reason is that the 1 year warranty is over)
3.Go to the recovery mode
4.See the 'Android is upgrading....' screen
After the 'Android is upgrading....' screen, it goes back to boot animation, then back to the 'Android is upgrading....' screen, and finally after some time screen gets off and I can not turn it on, although I can turn on light of the buttons by power button. Screen gets on for battery notification, and I can see the 'Android is upgrading....' screen. I can always take it to recovery mode, but can not switch it off once it is on so I have to wait for battery to finish. So it may not be bootloop, because that happens just 1 time when it goes back to boot animation. It is also not bricked, as it can do the 4 things.
Solutions already tried:
1. I have hard reset the phone at first.
2. I tried adb and fastboot but they do not recognize my device, maybe due to resetting of USB debugging option after the reset
3. No ROM or CWM is available on my phone, after searching and even using Goo manager
4. I tried removing the SD card after reset, but condition is same
About the phone:-
Name: Swipe Legend
Model: Alps hexxing77_ics2
Android: v4.0.4
Memory: 4GB ROM+32GB SD+512MB RAM
Processor: 2x1.5GHz Dual core(But I think it to be 1GHz dual core due to analysis by apps like Pi)
Screen: 7 inch
Pixels: 800*480
Status: Originally rooted, but maybe root is lost after reset
Already experienced reset: Yes, but it was not rooted by that time
USB Debugging: Was on last time, but maybe offed after factory reset
More details: I can not get the links but it can be searched on amazon or a site like naaptol.com.(I'm from India so don't know any shopping sites of other countries)
If any detail is missing, you may ask.
Please help if you can
Dump your recovery image
Go to builder.clockworkmod.com
Upload the image there
Get cwm for your phone
Press thanks :good: I'd helped :highfive:
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
And yes
Take a backup of rom if are able to boot
Press thanks :good: I'd helped :highfive:
arnabbiswasalsodeep said:
Dump your recovery image
Go to builder.clockworkmod.com
Upload the image there
Get cwm for your phone
Press thanks :good: I'd helped :highfive:
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
And yes
Take a backup of rom if are able to boot
Press thanks :good: I'd helped :highfive:
Click to expand...
Click to collapse
This seems good, but I don't have anything like recovery image. I once took a backup of user data but even that's corrupted. Is there any way to get the recovery image for my phone or it needs to be compiled by myself? Actually, I don't know much about recoveries and such things.
Use the command
dd if=/dev/recoverypartition of=/sdcard/recovery.img
Only you need to know the recoverypartition
It may be something like mmblck0p1
Only the numbers vary
Has your phone booted?
Press thanks :good: I'd helped :highfive:
arnabbiswasalsodeep said:
Use the command
dd if=/dev/recoverypartition of=/sdcard/recovery.img
Only you need to know the recoverypartition
It may be something like mmblck0p1
Only the numbers vary
Has your phone booted?
Press thanks :good: I'd helped :highfive:
Click to expand...
Click to collapse
Thats the only problem.
I can not enter any sort of command line.
Terminal: Not possible unless phone boots properly
ADB: Does not detect my phone
Another problem is my internet connection, due to it I can not access internet anytime.
[Q&A] [ROM][5.1.1][LDZ22D] Mysterious Magic v1.0 - 7/5/2015 - Let the magic begin!
Q&A for [ROM][5.1.1][LDZ22D] Mysterious Magic v1.0 - 7/5/2015 - Let the magic begin!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1][LDZ22D] Mysterious Magic v1.0 - 7/5/2015 - Let the magic begin!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I have had a couple of restarts and lags since I started use this ROM. Sometimes my watch don't want to turn on from ambient mode, I must wait and it's really annoying.
I think the wibration is too loud. But good thing is that my watch is faster.
Perhaps a factory reset would fix the issues you are having. The script clears both userdata and cache, but something weird may have happened.
No issues on my end, using the Windows script to install the ROM.
Sent from my SM-G925P using XDA Free mobile app
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
The first boot also takes a few mins to settle in. After that everything should be smooth sailing.
Sent from my SM-G925P using XDA Free mobile app
Pretty sure this has just bricked my watch. It couldn't find the firmware files after wiping the watch and then restarted it. Now it's just sitting on the LG unlocked bootloader screen and not responding to anything I can do, nor is it detected in device manager.
*Update*
Managed to recover using download mode.
I have stucked at logo LG for an hours after installing the rom, i dont know what i have to do, please help me!!! ((((
---------- Post added at 10:51 AM ---------- Previous post was at 09:59 AM ----------
I stucked at LG logo, then i entered download mode, but i dont know how to restore my watch to stock, help me, please!!! (
Help
Whenever I install(manually and auto) my watch wont reboot, it doesn't ever get past the LG logo. I found out boot wouldn't format, so instead of formatting before I flash the image I erased. I don't know if that's somehow the problem but I need help. I currently reinstalled stock boot and system and it's working fine.
Now the watch's touchscreen won't work. I think I installed the system.img but not the boot. Now it boots but the screen doesn't work and I cant get into fastboot
Gururek said:
Pretty sure this has just bricked my watch. It couldn't find the firmware files after wiping the watch and then restarted it. Now it's just sitting on the LG unlocked bootloader screen and not responding to anything I can do, nor is it detected in device manager.
*Update*
Managed to recover using download mode.
Click to expand...
Click to collapse
balaxitamon said:
I have stucked at logo LG for an hours after installing the rom, i dont know what i have to do, please help me!!! ((((
---------- Post added at 10:51 AM ---------- Previous post was at 09:59 AM ----------
I stucked at LG logo, then i entered download mode, but i dont know how to restore my watch to stock, help me, please!!! (
Click to expand...
Click to collapse
xander135 said:
Whenever I install(manually and auto) my watch wont reboot, it doesn't ever get past the LG logo. I found out boot wouldn't format, so instead of formatting before I flash the image I erased. I don't know if that's somehow the problem but I need help. I currently reinstalled stock boot and system and it's working fine.
Now the watch's touchscreen won't work. I think I installed the system.img but not the boot. Now it boots but the screen doesn't work and I cant get into fastboot
Click to expand...
Click to collapse
When your watch reboots after flashing everything, remove it from the cradle, then it will boot
GtrCraft said:
When your watch reboots after flashing everything, remove it from the cradle, then it will boot
Click to expand...
Click to collapse
Well now i cannot do anything. My watch is unresponsive to touch even for fastboot, i cant get into fastboot.
xander135 said:
Well now i cannot do anything. My watch is unresponsive to touch even for fastboot, i cant get into fastboot.
Click to expand...
Click to collapse
Have you tried holding the Tiny reset button on the back for 10 sec.
enigma2446 said:
Have you tried holding the Tiny reset button on the back for 10 sec.
Click to expand...
Click to collapse
How and when do I press it? While it's on?
When it's on it doesn't do anything. Or Im not pressing it right
undervolting
Hi! I like u rom on my watch with ondemand governor. What about undervolting of cpu?
Hello!
Im new to this forum, and to be honest, only registered to get help to this
New update came to phone. It was small and not a big deal so i installed it. That was my biggest mistake.
Now my huawei honor 7 is stuck on that "Your device has been unlocked and cant be trusted" thing, and only thing it does is "Your device is booting now"
I cant do or press volume buttons because it goes immetiadely to "Your device is booting now" state. It never boots by the way.
So what can i do? Nothing? Is there still hope. I never rooted my phone, but i "unlocked" it. This is very annoying and stressful
No help needed! I was so dumb that i forgot erecovery Just needed to boot into that while cable connected to pc. But i keep using this site still. Kind of weird welcome but whatever
jeisye said:
No help needed! I was so dumb that i forgot erecovery Just needed to boot into that while cable connected to pc. But i keep using this site still. Kind of weird welcome but whatever
Click to expand...
Click to collapse
So did you fix your issue?
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
If you solved that issue add a solved tag.