IT IS NO LONGER POSSIBLE TO CHANGE THE BOOT LOGO ON ROMS RELEASED FROM APRIL AND ONWARDS.
PLEASE READ THIS 1ST POST FULLY AND UNDERSTAND IT BEFORE REQUESTING A BOOT LOGO.
THINGS LIKE "CAN YOU DO THIS ONE" IS ABOUT AS MUCH USE AS A HANDBRAKE ON A HORSE.
I NEED TO KNOW WHETHER IT IS RK3066 or RK3188, THE DATE THE ROM WAS RELEASED AND THE RESOLUTION (800x480 or 1024x600)
Malaysk has been very kind to allow me to offer the service of changing the 1st boot logo and Recovery Mode logo to anyone using his great rom.
If you are using a different I can still do it, I will just need a link to download the rom.
If you want to have the 1st boot logo changed just give me a link to the image you want to use or add it to a zip file and add it as an attachment to your post.
I will also need to know the exact Malaysk rom version you are using (RK***, Resolution, Date of Rom)
The only down side to offering this service is it will mean you have to completely re-install the rom but you won't have to do a wipe so you won't lose any installed apps or settings.
I have tested extensively on my head unit with no problems but with any rom or mod you install at your own risk.
NOTE: If you find that you don't have root, just go to Factory Settings and enter code *#hct#root#
If you also want ADB enabled as well go back to Factory settings and enter code adbon
NOTE 2: The 1st Boot Logo and Recovery Mode Logo ARE NOT ANIMATED
Attached are some examples
Full list of completed boot logos
RK3066
alfa_800X480_RK3066_37_MAL_17_03_2016.rar
bmw_800X480_RK3066_37_MAL_17_03_2016.rar
bmw_800X480_RK3066_38_MAL_23_04_2016.rar
corolla_800X480_RK3066_37_MAL_17_03_2016.rar
ford_800X480_RK3066_37_MAL_17_03_2016.rar
ford_800X480_RK3066_38_MAL_23_04_2016.rar
hyundai_800X480_RK3066_37_MAL_17_03_2016.rar
toyota_moving_forward_800X480_RK3066_37_MAL_17_03_2016.rar
toyota_moving_forward_1024X600_18_RK3066_MAL_17_03_2016.rar
venza_1024X600_19_RK3066_MAL_19_04_2016.rar
vw_800X480_RK3066_37_MAL_17_03_2016.rar
RK3188
audi_800X480_RK3188_14_MAL_17_03_2016.rar
audi_mmi_800X480_RK3188_15_MAL_23_04_2016.rar
bmw_boo_RK3188_1024x600_2016-03-12_v1.0.0.rar booroondook Rom
chevrolet_800X480_RK3188_14_MAL_17_03_2016.rar
corvette_1024X600_RK3188_16_MAL_17_03_2016.rar
ford_1024X600_RK3188_15_MAL_09_03_2016.rar
ford_1024X600_RK3188_16_MAL_17_03_2016.rar
ford_1024X600_RK3188_17_MAL_23_04_2016.rar (with Ford boot animation (bootanimation_dancing_droids.zip))
hyundai_800X480_RK3188_14_MAL_17_03_2016.rar
hyundai_bluelink_1024X600_RK3188_16_MAL_17_03_2016.rar
hyundai_bluelink_boo_2016-0-3-12_v1.0.0.rar
mazda2_1024X600_RK3188_16_MAL_17_03_2016.rar
opel_800X480_RK3188_14_MAL_17_03_2016.rar
suzuki_800X480_RK3188_14_MAL_17_03_2016.rar
toyota_moving_forward_800X480_RK3188_14_MAL_17_03_2016.rar
Toyota_Moving_Forward_1024X600_RK3188_14_MAL_12_02_2016.rar
VW_1024X600_RK3188_15_MAL_09_03_2016.rar
vw_1024X600_RK3188_16_MAL_17_03_2016.rar
vw_1024X600_RK3188_17_MAL_23_04_2016.rar
vw_JY_rk3188_h(20160222).rar Joying Stock Rom
Cheers,
Goose
Toyota - Moving Forward
Dear @Goose247, thank you in advance for your efforts.
Here I'm attaching the "Toyota - Moving Forward" logo, which would look very nice when booting in the 2008 Toyota Yaris. (that was Toyota's slogan between 2004-2012, when this car was made).
It's simple and aesthetic, and looks very professional, in my opinion. No super-fancy stuff needed during that first couple of seconds.
I attached both JPG and PNG, PNG is better quality, use whichever you can.
I'm using Malaysk's 4_4_4_800X480_RK3066 image.
robertut said:
Dear @Goose247, thank you in advance for your efforts.
Here I'm attaching the "Toyota - Moving Forward" logo, which would look very nice when booting in the 2008 Toyota Yaris. (that was Toyota's slogan between 2004-2012, when this car was made).
It's simple and aesthetic, and looks very professional, in my opinion. No super-fancy stuff needed during that first couple of seconds.
I attached both JPG and PNG, PNG is better quality, use whichever you can.
I'm using Malaysk's 4_4_4_800X480_RK3066 image.
Click to expand...
Click to collapse
What date rom are you using?
Now I'm using update_4_4_4_800X480_RK3066_31_MAL_09_12_2015, but I plan to re-flash my unit later to update_4_4_4_FUSE_800X480_RK3066_35_MAL_13_02_2016.
robertut said:
Now I'm using update_4_4_4_800X480_RK3066_31_MAL_09_12_2015, but I plan to re-flash my unit later to update_4_4_4_FUSE_800X480_RK3066_35_MAL_13_02_2016.
Click to expand...
Click to collapse
Ok, to make things simple I will add the new boot logo to the latest rom for you so when you flash it, just flash it as per Malaysk's instructions for that version.
Boot logo has been done, just uploading to server. Will let you know when it is available for download :good:
Here is the link for Toyota Moving Forward Toyota_Moving_Forward_800X480_RK3066_35_MAL_13_02_2016.rar
I use 2 different methods to re-build the rom, 1 of them for some reason loses root and I have no idea why but if you find that you don't have root, just go to Factory Settings and enter code *#hct#root#
If you also want ADB enabled as well go back to Factory settings and enter code adbon
I have also used the same image for going into recovery but added "Recovery Mode" at the bottom of the logo.
I really need to figure out which method doesn't lose root for future reference
Take a photo and upload once you are up and running.
Can you share only .img file you modified? Which one is it?
- boot.img
- misc.img
- oem.img
- system.img
- kernel.img
- recovery.img
- RK30xxLoader(L)_V2.19.bin
???
Can you add this Chevy symbol please to update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016? Thanks.
http://www.car-brand-names.com/wp-content/uploads/2015/08/Chevrolet-logo-3.jpg
robertut said:
Can you share only .img file you modified? Which one is it?
- boot.img
- misc.img
- oem.img
- system.img
- kernel.img
- recovery.img
- RK30xxLoader(L)_V2.19.bin
???
Click to expand...
Click to collapse
Yeah sure. I will upload them. They are kernel and recovery.
Here is the link to just the kernel and recovery. Toyota_Moving_Forward_800X480_Boot_Logo.rar
MayfairDROID said:
Can you add this Chevy symbol please to update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016? Thanks.
http://www.car-brand-names.com/wp-content/uploads/2015/08/Chevrolet-logo-3.jpg
Click to expand...
Click to collapse
Just uploading now. Will be available soon :good:
MayfairDROID said:
Can you add this Chevy symbol please to update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016? Thanks.
http://www.car-brand-names.com/wp-content/uploads/2015/08/Chevrolet-logo-3.jpg
Click to expand...
Click to collapse
Chevy done. Chevrolet_800X480_RK3188_12_MAL_13_02_2016.rar
Its probably safe to say that all the major car makes would enjoy one.
Do you want a Honda one done? If so I need to know the exact firmware you are using.
Cheers,
Tam
You are the man when i get paid im sending coffee and donuts ur way lol...im using the latest malaysk feb 13th firmware and i have a res of 800x480 much appreciated brother below is the link ...gonna look dope
http://2.bp.blogspot.com/-Pwlujsk6DTU/USdHnu2j7fI/AAAAAAAAB7I/O_EeHyNDBaM/s1600/Hyundai-Logo.jpg
Goose247 said:
Here is the link for Toyota Moving Forward Toyota_Moving_Forward_800X480_RK3066_35_MAL_13_02_2016.rar
I use 2 different methods to re-build the rom, 1 of them for some reason loses root and I have no idea why but if you find that you don't have root, just go to Factory Settings and enter code *#hct#root#
If you also want ADB enabled as well go back to Factory settings and enter code adbon
I have also used the same image for going into recovery but added "Recovery Mode" at the bottom of the logo.
I really need to figure out which method doesn't lose root for future reference
Take a photo and upload once you are up and running.
Click to expand...
Click to collapse
I installed it, looks great! Thanks.
It indeed looses root, but entering root codes as you suggested restores root functionality properly. I'll post a photo later.
robertut said:
I installed it, looks great! Thanks.
It indeed looses root, but entering root codes as you suggested restores root functionality properly. I'll post a photo later.
Click to expand...
Click to collapse
Yeah I must have used the other method of 2 for re-building the rom and the best of it is I can't even remember what method I used to re-pack your now lol.
wcbray said:
You are the man when i get paid im sending coffee and donuts ur way lol...im using the latest malaysk feb 13th firmware and i have a res of 800x480 much appreciated brother below is the link ...gonna look dope
http://2.bp.blogspot.com/-Pwlujsk6DTU/USdHnu2j7fI/AAAAAAAAB7I/O_EeHyNDBaM/s1600/Hyundai-Logo.jpg
Click to expand...
Click to collapse
3066 or 3188? Was just about to upload it then realised that I had done it for 3188
3188 is corrent my man thank abunch broski
Im excited for the link
wcbray said:
3188 is corrent my man thank abunch broski
Im excited for the link
Click to expand...
Click to collapse
How is that for timing. Upload just finished.
Hyundai_800X480_RK3188_12_MAL_13_02_2016.rar
Install as a normal update, don't wipe anything. Once it has rebooted can you check to see if you still have root? I think I used the correct method this time.
If not follow the instructions on the 1st post.
Goose247 said:
How is that for timing. Upload just finished.
Hyundai_800X480_RK3188_12_MAL_13_02_2016.rar
Install as a normal update, don't wipe anything. Once it has rebooted can you check to see if you still have root? I think I used the correct method this time.
If not follow the instructions on the 1st post.
Click to expand...
Click to collapse
You did a fantastic job and i did not lose root at all it was flawless keep up the good work my man i will be keeping this rom a quite some time now because you u
---------- Post added at 07:42 PM ---------- Previous post was at 07:07 PM ----------
Hey goose you don't know how to rezise widgets or launchers do you?
Related
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.
Help! I made the foolish decision to try and mess around in my G3's build.prop without really knowing what I was doing. My phone is currently stuck in a bootloop, not getting past the verizon splash screen. I have attempted booting into recovery mode and factory resetting, but for one reason or another, the phone won't do it and it ends up loading the splash screen over and over again. I have also researched flashing the stock rom onto the device with the LG flash tool. But, when I try to do this, the tool gives me an error saying that the "Device Model is different" because according to the build.prop, it is a Nexus 5.
Does anyone know of a method that can help me get this stupid thing working again?
I have seen build.prop files cut in half because it was a bad file editor. I hope u saved a copy. Posible reboot to fast boot and replace? Rom toolbox has nice interface for editing build.prop.
Sent from my VS985 4G
Thanks for your reply! I do have a copy. How would I go about booting into fast boot?
n8bgr8 said:
Thanks for your reply! I do have a copy. How would I go about booting into fast boot?
Click to expand...
Click to collapse
what do you have in the recovery partion, stock or or bumped twrp?
Well, I fixed it somehow. I got the stock Rom to flash, but I don't really,understand what,made it work this time. Whatever, I've learned my lesson. Thank you for your attempt to help!
n8bgr8 said:
Well, I fixed it somehow. I got the stock Rom to flash, but I don't really,understand what,made it work this time. Whatever, I've learned my lesson. Thank you for your attempt to help!
Click to expand...
Click to collapse
Cool. I was going to mention that their may be a force or overide in the lg flashing software. Manual was one of the was to flash. any input you can add on how you did it would be great as I have read people have run into this before. their is no need to change the phone type to download apps from the market that are not compatible with your phone. The following link allows you to download any app and then you can sideload it (for future reference)
http://apps.evozi.com/apk-downloader/?id=ca.halsafar.genesisdroid
usage. go to the link. replace [ca.halsafar.genesisdroid] in your browser with the app you looking to download from the play store using the ending link in the play store address. then click the blue generate button on the page. a new green button to download the file will appear.
glad it worked out for ya. And check out rom tool boxs build.prop editor. very nice.
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
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
## I TAKE NO RESPONSIBILITY IF YOU BRICK YOU DEVICE##
So Im sharing some custom BOOTLOGO.BIN that I have made to remove the unlock boot-loader warring
for the Moto X4 with the latest logo.bin file form the latest update
i have tested them on my owen device
the zip file has a flash.bat included for a/b only logo.bin files for Havoc (will make more/custom if asked)
or
you cant flash manually via fastboot if your (UNLOCKEDBL)with stock recovery
reboot in to boot-loader mode
extra zip file
fastboot flash logo (logo you pick).bin
fastboot reboot
and to set manually swap from AorB slot
fastboot set_active other
I hope you like and enjoy
new test update has a new logo in bootloader mode
let me know what you think keep in mind this is a test changes will be made
new full logo mod (flashlogo.bat file in zip)
**new full logo mod**
custom logo bin
custom bootloader logo
and tab,arrows keys new look
NOW WE ARE MAKING BOO ANIMATIONS WITH IN SOME OF THE LOGO'S
ALL TWRP FLASH-ABLE
PLEASE LOOK HERE
One's that i made for far
Also check out
A fellow devs work havoc A is all thanks to him
https://photos.app.goo.gl/tkikcftmRdapXrjX7
AWESOME UPDATE WE NOW HAVE A TWRP FLASH-ABLE ZIP
THANK TO (ander38122) WITH OUT HIS HELP THIS WOULDN'T BE POSSIBLE
its under payton.zip
i have new update i have made a twrp zip that now flashes 2 different logo on each slot so you can tell them apart
PLEASE IF YOU WANT OR NEED HELP WITH A CUSTOM TWRP LOGO FILE PLEASE CONTACT!
Also join in on the NEW GROUP channel
share you own Custom Logo's/Wallpaper's,Get help, tips, an updates
NEW FILES/UPDATE BIN ZIP WILL BE HERE
[]
great job...
munchy_cool said:
great job...
Click to expand...
Click to collapse
Thanks
I've seen this talked about but I didn't really get it.
Is this twrp flsshable? Or do like normal? Your OG post says "can't" in fastboot so that's where I'm getting lost
stovo06 said:
I've seen this talked about but I didn't really get it.
Is this twrp flsshable? Or do like normal? Your OG post says "can't" in fastboot so that's where I'm getting lost
Click to expand...
Click to collapse
At this point there fastboot flashable only
I'm currently work out the bugs with twrp flashable zip
But I'll keep make up dates
and post them as soon as i get the bugs out
FizzyAps said:
At this point there fastboot flashable only
I'm currently work out the bugs with twrp flashable zip
But I'll keep make up dates
and post them as soon as i get the bugs out
Click to expand...
Click to collapse
Got any instructions? Been following a bit in telegram. I'm sure there be a twrp soon and I'm sure it isn't that hard, but a few details can go a long way.
stovo06 said:
Got any instructions? Been following a bit in telegram. I'm sure there be a twrp soon and I'm sure it isn't that hard, but a few details can go a long way.
Click to expand...
Click to collapse
Extract anyone of the zip flash manually via bootloader mode by running the commands
fast food flash logo (the one you pick).bin
The new full mod contains a flashlogo.bat already
Simply boot into bootloader and run bat file and enjoy
Same for the A/B havoc logo.bin have made a simple bat file for them as well
Now for the twrp side of thing I keep running in to error(6)
No matter how I reconfigure
Reaching out to another Dev that might be able to help me reconfigure
Cool Brother, this Havoc Bootlogo was me I created, you just grabbed from my album https://photos.app.goo.gl/tkikcftmRdapXrjX7
ander38122 said:
Cool Brother, this Havoc Bootlogo was me I created, you just grabbed from my album https://photos.app.goo.gl/tkikcftmRdapXrjX7
Click to expand...
Click to collapse
I linked it to you album and I also tweaked it little
FizzyAps said:
I linked it to you album and I also tweaked it little
Click to expand...
Click to collapse
OK, Leaves the album of Wallpapers linked to your post, anything calls me on the telegram
https://t.me/ander38122, I Can send the files soon. bin that I created also
ander38122 said:
OK, Leaves the album of Wallpapers linked to your post, anything calls me on the telegram
:good:, I Can send the files soon. bin that I created also
Click to expand...
Click to collapse
you might want to remove this so ppl dont blow you up
Twrp is a go already? Dam you on it. Which file and is it OK to flash over my bin logo I already have?
stovo06 said:
Twrp is a go already? Dam you on it. Which file and is it OK to flash over my bin logo I already have?
Click to expand...
Click to collapse
there a link to one that are twrp flashable and yes
you can flash with no wipe
FizzyAps said:
there a link to one that are twrp flashable and yes
you can flash with no wipe
Click to expand...
Click to collapse
Worked! There's a black screen for a few seconds but other than that, perfect!
Love to make my own. Hint hint ?
---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------
BTW, One issue I've had since I fastboot the first time (a bin file, can't say it was from a zip file), TWRP has not been able to do a backup. Fails everytime at system image.
At one point it wouldn't reboot to the rom. Kept going back to TWRP. Eventually I just flashed a new ROM (which I was about to anyway thus the reason for the backup).
Edit; haven't tried since I flashed this new one.
stovo06 said:
Worked! There's a black screen for a few seconds but other than that, perfect!
Love to make my own. Hint hint
---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------
BTW, One issue I've had since I fastboot the first time (a bin file, can't say it was from a zip file), TWRP has not been able to do a backup. Fails everytime at system image.
At one point it wouldn't reboot to the rom. Kept going back to TWRP. Eventually I just flashed a new ROM (which I was about to anyway thus the reason for the backup).
Edit; haven't tried since I flashed this new one.
me and the other dev will look into this issue
and as for the black screen issue we are working on it please try this attached file via twrp and let me know
Click to expand...
Click to collapse
FizzyAps said:
me and the other dev will look into this issue
and as for the black screen issue we are working on it please try this attached file via twrp and let me know
Click to expand...
Click to collapse
Same as previous. About a 2-3 second black screen.
Don't know if it matters but someone on telegram (didn't get an opportunity to read into it at the time) mentioned a bat file (but I think that may have been about TWRP).
And just outta curiosity, this stuff has progressed faster than myself. Is it necessary to remove security settings anytime I flash something? Have been just in case but I don't thing I do, just wanted confirmation if you have time
stovo06 said:
Same as previous. About a 2-3 second black screen.
Don't know if it matters but someone on telegram (didn't get an opportunity to read into it at the time) mentioned a bat file (but I think that may have been about TWRP).
And just outta curiosity, this stuff has progressed faster than myself. Is it necessary to remove security settings anytime I flash something? Have been just in case but I don't thing I do, just wanted confirmation if you have time
Click to expand...
Click to collapse
ok was it as bad??
and which group was this in please link me in to it
aslso no you shouldnt have to be but i do for testing
but it you want fast reply's,update,help,request,or anything like that please share and join the new grup on telegram