hi,
so I keep getting updates and then my watch reboots, i think it installs something through TWRP and then i have to manually reboot it with TWRP. but I think the update fails. (it's going fast but I think A red line says "installation failed" and then it just goes to the TWRP homescreen)
somebody? I want to reflash a rom or restore but my lg g watch says my device is offline.....
what tool do you use?
grts
similar problem
liobeir said:
hi,
so I keep getting updates and then my watch reboots, i think it installs something through TWRP and then i have to manually reboot it with TWRP. but I think the update fails. (it's going fast but I think A red line says "installation failed" and then it just goes to the TWRP homescreen)
somebody? I want to reflash a rom or restore but my lg g watch says my device is offline.....
what tool do you use?
grts
Click to expand...
Click to collapse
i hope someone can help as well. i recently installed a custom rom and kernel. much better battery life. anyway, shortly after
i received a system update notification on the watch which cant be dismissed. i have to swipe left to install. click ok. then it
reboots to recovery. i dont know what to do at that point in TWRP i just reboot to system. then a couple hors later the
install update appears and i do it all over again. anyone have a solution? please and thanks.
jyesucevitz said:
i hope someone can help as well. i recently installed a custom rom and kernel. much better battery life. anyway, shortly after
i received a system update notification on the watch which cant be dismissed. i have to swipe left to install. click ok. then it
reboots to recovery. i dont know what to do at that point in TWRP i just reboot to system. then a couple hors later the
install update appears and i do it all over again. anyone have a solution? please and thanks.
Click to expand...
Click to collapse
What is happening is the 4.4W.2 update was released OTA and you're on a custom rom. The update won't take unless you restore to default or from a nandroid backup prior to flashing a custom rom. I was on Gohma and I went through the same problem. Restore to default and then the update will take. If not the annoying pop-up will drive you insane. Hope this helps.
m4tchb0x87 said:
What is happening is the 4.4W.2 update was released OTA and you're on a custom rom. The update won't take unless you restore to default or from a nandroid backup prior to flashing a custom rom. I was on Gohma and I went through the same problem. Restore to default and then the update will take. If not the annoying pop-up will drive you insane. Hope this helps.
Click to expand...
Click to collapse
ALTERNATIVELY, download (or find out where on the watch it has been downloaded) the update itself, put in /sdcard on watch and flash like normal rom with TWRP.
TjPhysicist said:
ALTERNATIVELY, download (or find out where on the watch it has been downloaded) the update itself, put in /sdcard on watch and flash like normal rom with TWRP.
Click to expand...
Click to collapse
I wasn't aware of this method. In doing this will the OTA flash over a custom rom? Do you need to wipe system/cache/dalvik before doing so?
m4tchb0x87 said:
I wasn't aware of this method. In doing this will the OTA flash over a custom rom? Do you need to wipe system/cache/dalvik before doing so?
Click to expand...
Click to collapse
OTAs will never flash over custom Rom, you need to flash back to stock. I didn't wipe, it was fine. This method is just if you don't want to wait for the popup (there IS a way to modv the ota zip so it will ignore inconsistencies in what it was expecting to see, but idk how and it didn't sound too stable)
TjPhysicist said:
OTAs will never flash over custom Rom, you need to flash back to stock. I didn't wipe, it was fine. This method is just if you don't want to wait for the popup (there IS a way to modv the ota zip so it will ignore inconsistencies in what it was expecting to see, but idk how and it didn't sound too stable)
Click to expand...
Click to collapse
That's what I assumed. I restored to my nandroid bak and then flashed 4.4W.2. I didn't wipe and then flashed Gohma 1.2. I had to install TWRP and root again. It's running smooth with great battery usage.
g watch
m4tchb0x87 said:
That's what I assumed. I restored to my nandroid bak and then flashed 4.4W.2. I didn't wipe and then flashed Gohma 1.2. I had to install TWRP and root again. It's running smooth with great battery usage.
Click to expand...
Click to collapse
continuously looping the boot animation. is the watch done?
imwatcinu a said:
continuously looping the boot animation. is the watch done?
Click to expand...
Click to collapse
What did you do before it went into a bootloop?
---------- Post added at 12:19 PM ---------- Previous post was at 12:11 PM ----------
imwatcinu a said:
continuously looping the boot animation. is the watch done?
Click to expand...
Click to collapse
You can try to reset the device (LG G watch) by the pinhole button on the back. If that doesn't work. Install this tool and follow the tutorial provided.
http://rootjunkysdl.com/?device=LG G Watch&folder=G Watch Script Tool
Related
Hi Folks,
I have just installed CWM recovery V 6.0.4.6 using ROM Manager app in my Galaxy S3 I9300 running on stock android 4.3 . I rebooted the device to check it and it was successfully installed. While I tried to reboot device through an option in the recovery, it showed up two messages as follows,
Message 1:
ROM may flash stock recovery on boot. Fix? THIS CAN'T BE UNDONE
1.No
2.Yes - Disable recovery flash
Message 2:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. No
2. Yes - Fix root (/system/xbin/su)
I selected option "2.Yes - Disable recovery flash" from Message 1 and again option "2. YES fix root (/system/xbin/su)" from Message 2.
Why these messages are getting displayed? Is there any problem now?
Also please let me know whether it will revert to Stock Android Recovery by selecting Option "1.No" from Message 1. If so again I have to flash CWM recovery?
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks. So shall I revert back to stock recovery by selecting 1.No from message 1 and then flash cwm using odin?. Will it be fine?
I have also read that many folks facing same kinda issue even they flashed CWM recovery using odin.
Please advice that will there be any issues if I flash Cynogenmod 10.2 now?.
Any help on this? Please.
mpadhu said:
Any help on this? Please.
Click to expand...
Click to collapse
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
boomboomer said:
Don't use rom manager on the s3.
Click to expand...
Click to collapse
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
Click to expand...
Click to collapse
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
dxppxd said:
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
Click to expand...
Click to collapse
Hence the statement:
"As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. "
dxppxd said:
It's better to install cwm recovery through means other than rom manager to avoid problems.
Click to expand...
Click to collapse
My point is that of the two, Rom Manager is the one that works. I have never had issues using Rom Manager to install recoveries. Although, I always install the first time using fastboot... So my anecdotal impressions may not apply here.
Care to explain your statement? (Which is the intent of my original message. Why the Koushik XDA witchhunt?)
I would search, but XDA search is borderline unusable.
Thanks!
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
None of the stock roms I've used have ever tried to restore stock recovery, it's just left there from other devices that do it.
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
Click to expand...
Click to collapse
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
When asked those i always select "no" to both. Never had an issue.
mpadhu said:
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
Click to expand...
Click to collapse
Looks like a successful backup to me.
t1n0m3n said:
Looks like a successful backup to me.
Click to expand...
Click to collapse
Thank you. I have successfully flashed Cynogenmod 10.2.
I can see my old android files still present in the internal memory. I did wipe data/factory reset, wipe cache partition and wipe dalvik cache but still the files are present. Will it cause any problem if I remove those files? If No will a factory reset work to remove those files?
I just received a Android update in my notification menu. I am rooted and running a custom recovery (twrp). I know I cannot accept the update but I can't swipe it away. Anyone know how I can get the update removed from my notification menu?
Have you tried long pressing on the notification and disabling notifications?
I froze system update in ti backup I didn't have a pending update but I would try that
Is that file under. Com in tb?
jreink01 said:
Is that file under. Com in tb?
Click to expand...
Click to collapse
Here you go
kennwoodkenn said:
Here you go
Click to expand...
Click to collapse
Thanks for the thumbnail. I did find it in TB and froze it but I'm still getting the update notification in my notification pull down.
Did you restart the phone after
that may work
Don't know if this will work or not, but on the Galaxy S3 the way to stop getting nagged about an OTA was to edit build.prop and replace all references to the old ROM with the new one. So you could try making a backup of build.prop, then edit all references to ZV4 and change them to ZV6. Save the file, make sure permissions are set to rw-, r--, r-- (0644), and reboot.
I would strongly suggest making a nandroid backup first.
Here's how I have been doing it:
1. Download Autorun Manager
2. In settings under advanced enable view services
3. Go to Google Services Framework and disable update...see below.
At your own risk if you decide to try it, of course.
Sent from my LGLS990 using XDA Free mobile app
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
If the update has already downloaded. Disabling the OTA still wont get rid the the notification. Easy way to get rid of it is long press it and go to app info. This will take you to Google Play Services. Simply uncheck show notifications and the system update in the pull down notifications will go away.
Just a temporary fix to get it out of the way. I reccommend just downloading a ZV6 rooted rom.
engine95 said:
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
Click to expand...
Click to collapse
guys I mistakenly installed this update and now my phone is stuck in twrp where can I go to delete it or am I s.o.l please help
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
im0rtalz said:
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
Click to expand...
Click to collapse
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Try this first before doing the LG Flash
[Fix] Stuck in Custom Recovery
Thanks to acparker posts
randyrampage609 said:
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Click to expand...
Click to collapse
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
FractalSphere said:
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
Click to expand...
Click to collapse
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------
randyrampage609 said:
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2916085
Without having to use a computer and lg flash tool
Sent from my LGLS990 using Tapatalk
Lucky you. Good find. Glad you got it sorted. Now you can relax.
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
jreink01 said:
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
Click to expand...
Click to collapse
Don't take OTA. Root it and TWRP it. Then flash STOCK ROM ZV6 Deodexed or Odexed, then you'll be up to date and keep root with TWRP.
So my watch recently downloaded the latest 6.0.1 update.zip and I'm more than happy to report: WE CAN FLASH IT VIA TWRP!
This update.zip was grabbed from /cache, however seems to be completely identical with the one you can download from here: https://android.googleapis.com/pack...3ec3e78cb2a7d3.signed-platina-ota-2576000.zip
Exciting news, means we don't have to reset our watch back to stock for it to flash
Here are the download links:
Dropbox
Google Drive
OneDrive
Happy flashing!
loving the new update. its so smooth.
eraycetin said:
loving the new update. its so smooth.
Click to expand...
Click to collapse
That indeed Once the watch was updated it lagged for about 10 minutes still, probably due to it doing stuff in the background after the upgrade. But once that was done it's now working great, smooth and awesomely well!
thanks.
i still wiped out everything to have a more clean experience. and faster.
Yeah I would say the only reason we don't have to go back to stock is that the ota contains completely brand new system image and boot and recovery of course so it thosen't even verify system files as they all get replaced anyway
Can we flash this new stock and then flash a custom kernel? Idk anything sorry, this will be my one annoying question for the day
For 6.0.1 there is no kernel at the moment.
MihaiSG said:
For 6.0.1 there is no kernel at the moment.
Click to expand...
Click to collapse
No kernel for 6.0.1?? Really??
Go here :
http://forum.xda-developers.com/showthread.php?t=3082669
I haven't checked the topic today. Good that it was updated, can't wait to test it. Thanks for the heads up
Gohma Custom Rom
Hey guys,
My watch is currently running Gohma ROM. can i sideload the update and install right on top, or should i return it back to full stock before installing it?
it does have TWRP installed...
livinstyle said:
Hey guys,
My watch is currently running Gohma ROM. can i sideload the update and install right on top, or should i return it back to full stock before installing it?
it does have TWRP installed...
Click to expand...
Click to collapse
you might be able to but doubt it just flash the system image and boot from here
Is it compatible with invisiblek's kernel 6.1?
Edit: this rom is the same as before, MEC23G, theoretically, it should be compatible...
Edit1: It is compatible.
Jhon998 said:
Is it compatible with invisiblek's kernel 6.1?
Edit: this rom is the same as before, MEC23G, theoretically, it should be compatible...
Edit1: It is compatible.
Click to expand...
Click to collapse
Um dude what are you on about there haven't been any updates since. Invisibleks kernel was made for that build anyway you can also try the non stock 6 version on his builds it has smartmax eps instead of on demand
Xmaster24 said:
Um dude what are you on about there haven't been any updates since. Invisibleks kernel was made for that build anyway you can also try the non stock 6 version on his builds it has smartmax eps instead of on demand
Click to expand...
Click to collapse
Lol I was lost I thought that the update was released yesterday, because the xda page of g watch listed this post as 22nd april as for the last activity not the actual post date...
hi guy's.I have a problem with this version.
when I put my phone on silent mode,my watch goes to"don't disturb mode" and when I turn off the "don't disturb mode" in watch,my phone go back to ring mode.I don't like this.
I want put my phone on silent mode and watch doesn't go to don't disturb mode.do you have this problem? Any idea for this?
is there any way to update my lg g watch without using "system update" and without using "stock recovery" ? i have problems with both of them, looking for a third method...
Help
I Download ROM + I Install TWRP On My Watch But I Don't Know to How install with twrp PLEASE Help Me
help
helppp me pls
MehranAB said:
I Download ROM + I Install TWRP On My Watch But I Don't Know to How install with twrp PLEASE Help Me
Click to expand...
Click to collapse
Do you know how to use TWRP? Copy update zip to watch using adb, reboot to recovery then flash zip. As it's a smartwatch you have to touch and swipe screen in a certain way to activate recovery, please search the forum for more info.
lfom said:
Do you know how to use TWRP? Copy update zip to watch using adb, reboot to recovery then flash zip. As it's a smartwatch you have to touch and swipe screen in a certain way to activate recovery, please search the forum for more info.
Click to expand...
Click to collapse
Thank You! But What is the exact command to copy the update file.zip to LG G watch via ADB?
Regards
Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch
So i had a hardricked phone(i thought) but than it worked again. So i flashed pacrom and it went in a hardbrick like state again (using twrp btw)I flashed it with nano gaps and the b330 package so you could get the fingerprint scanner. Than after an hour or so it worked again. Than i started running my battery low on purpose so i knew if it was just stuck or if it was something else. When my phone dies it will reboot again and work. And then i flashed rr with the nano gapps and the b330 package and it did this again, I thought it might have something to do with the b330 package so i flashed it without and it still did this. Then i thought it might have something to do with my twrp because i was still running on version 3.0.0 so i flashed the newer version through fastboot and it did this again!!
I dont know what is going on but my phone is acting really strange.
Does someone know of this problem or has ever heard of it or is my phone just strange?
jimandroidnerd said:
So i had a hardricked phone(i thought) but than it worked again. So i flashed pacrom and it went in a hardbrick like state again (using twrp btw)I flashed it with nano gaps and the b330 package so you could get the fingerprint scanner. Than after an hour or so it worked again. Than i started running my battery low on purpose so i knew if it was just stuck or if it was something else. When my phone dies it will reboot again and work. And then i flashed rr with the nano gapps and the b330 package and it did this again, I thought it might have something to do with the b330 package so i flashed it without and it still did this. Then i thought it might have something to do with my twrp because i was still running on version 3.0.0 so i flashed the newer version through fastboot and it did this again!!
I dont know what is going on but my phone is acting really strange.
Does someone know of this problem or has ever heard of it or is my phone just strange?
Click to expand...
Click to collapse
I have no idea why you keep flashing the firmware b330 it only needs done one time
clsA said:
I have no idea why you keep flashing the firmware b330 it only needs done one time
Click to expand...
Click to collapse
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
jimandroidnerd said:
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
Click to expand...
Click to collapse
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
jimandroidnerd said:
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
Click to expand...
Click to collapse
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
clsA said:
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
Click to expand...
Click to collapse
Demian3112 said:
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
Click to expand...
Click to collapse
I will do that. thanks for the help everyone
clsA said:
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
Click to expand...
Click to collapse
Demian3112 said:
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
Click to expand...
Click to collapse
Ok so i have gone back to stock, everything is working again as far as i can tell. Just done it 10 minutes ago. I will test for a week to see if erverything is working properly. Is it safe to flash custom roms / recovery after i have confirmed everything is working properly? Thank you guys so much for the help btw, i really appreciate it!:good:
jimandroidnerd said:
Ok so i have gone back to stock, everything is working again as far as i can tell. Just done it 10 minutes ago. I will test for a week to see if erverything is working properly. Is it safe to flash custom roms / recovery after i have confirmed everything is working properly? Thank you guys so much for the help btw, i really appreciate it!:good:
Click to expand...
Click to collapse
did you take all the updates to b330 ? if so you can pretty safely go to CM13 + gapps nano without any worries.
use one of the newest versions of TWRP
Do a factory reset and flash only CM13 and gapps
reboot let it fully load .. reboot to recovery / backup your fresh install to ext-sd
boot back to the OS and setup your new device.