[APP] Motorola Boot Logo Maker (source code included) (Version 2.2) - G 2014 Themes and Apps

Here is my full gui tool for creating boot logo files, for a number of Motorola Devices.
You get a preview of the picture, exactly how it would look on your device.
Features
Open Existing Logo.bin files
Open Existing Flashable zip files
Create logo.bin files
Create Flashable zip files
Export images from Logo.bin / Flashable zips.
Instructions
To use, you just double click on the treeview entries, select your picture, and repeat that process for all of the files that would be in logo.bin You then go to File / Save, and then save either as a .bin file, for flashing using fastboot, or as a Flashable zip file, for flashing using TWRP or CWM. In general, boot_logo is used on a factory locked device, and as a result, you probably should clear that one, as you would be wasting your space. logo_battery is your 0-3% indicator when the battery is run dry, and you plug it in to charge. logo_unlock is the actual boot screen logo you see on unlocked devices.
You can also open existing logo.bin files, wither from zip files, or directly, in order to modify them. Custom mode is for the advanced users, or for cases where a new Motorola device is released, where its logo.bin contains files that are not known. This tool auto-detects whether the file is the pre-kitkit format or not, and pictures that are larger than screen resolution, or in the case of pre-kitkat format, 540x540 is automatically scaled down. Upscaling options are provided, but centering the image is the default selection.
Bugs
None that I am aware of. If any are found, report them.
Limitations
The tool will not create any logo.bin files that are greater than 4MiB. This is a device limitation, specifically the logo flash partition is exactly 4MiB in size on all the known devices that I specifically support with this tool. As such, you may have to downscale or reduce the bpp formats of your images, to get them all to fit within the 4MiB.
Version History
Version 2.2 - Released Set 15, 2014
[new] Metadata added to created logo.bin files - The following data is present.
Version of this program that created the bin file. (was present since Version 2.0)
Motorola Device Selected
Motorola Device Resolution
User Comment
Full source code available at https://github.com/CaitSith2/MotoBootLogoMaker
Credit: @caitsith2

Great work! I did not think such a thing would be around so soon! Thanks alot for this!

Aileach XDA said:
Great work! I did not think such a thing would be around so soon! Thanks alot for this!
Click to expand...
Click to collapse
:good:

Thanks man for sharing your work:highfive:

Actually my work, as noted by the direct link to the source code itself. This is just a cross-posted copy. I specifically added support for quite a few devices from the get go, and as devices became known about, I added them in as well. grabbing firmware dumps, to determine what logo_* things were supported by the device.

caitsith2 said:
Actually my work, as noted by the direct link to the source code itself. This is just a cross-posted copy. I specifically added support for quite a few devices from the get go, and as devices became known about, I added them in as well. grabbing firmware dumps, to determine what logo_* things were supported by the device.
Click to expand...
Click to collapse
All credit goes to u. thats y i taged u :victory:

archies20 said:
All credit goes to u. thats y i taged u :victory:
Click to expand...
Click to collapse
Might want to link to the original post as well, since that is what I will be updating when a newer version comes out.

caitsith2 said:
Actually my work, as noted by the direct link to the source code itself. This is just a cross-posted copy. I specifically added support for quite a few devices from the get go, and as devices became known about, I added them in as well. grabbing firmware dumps, to determine what logo_* things were supported by the device.
Click to expand...
Click to collapse
haha Thanks to man too,didnt did my research lol,bt ok now Keep up the good work:good:

@archies20 - Version 2.2 of this utility is online. Quote the latest version of http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/ And in the credits, put
Code:
Credit: @caitsith2 - Original post quoted from http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/

caitsith2 said:
@archies20 - Version 2.2 of this utility is online. Quote the latest version of http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/ And in the credits, put
Code:
Credit: @caitsith2 - Original post quoted from http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/
Click to expand...
Click to collapse
:good:

Made a little oldschool screen with this wonderful tool :b

Awesome work sir.... But can i change the Motorola Logo using source code

smart_roy said:
Awesome work sir.... But can i change the Motorola Logo using source code
Click to expand...
Click to collapse
Hii friend, I donno about source code but you can change only the boot logo with adb fastboot method
steps...
Note : USB Debugging Enabled
1. Go to bootloader mode
2. Then attach USB cable
3. Open command window in directory where your logo.bin file is placed (to open cmd window -> press+hold shift and press right click, select open command window here.)
4. Once in cmd, type fastboot devices, if it shows some device id then type fastboot flash logo logo.bin
That's it.

Nice tool, thank you for sharing

Anyone create a dark battery screen?

Related

Places to host toolsets and boot/recovery roms?

I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
If you're against the typical file hosts and the files aren't too big you could try using dropbox or sugarsync and sharing the links.
Can I ask you a question? I have a Kyocera ZIO M6000 and have the openzio clockworkmod 2.5.1.1 port that only works with "fastboot boot openzio-recovery" and we have tried flashing to our recovery partition with no success. What will it take to break the tether and reboot recovery locally without fastboot?
Sent from my Zio using XDA App
merwin said:
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
Click to expand...
Click to collapse
I would also suggest dropbox or even id host them off my computer via ftp
Can your method work with Garminasus A10?
Merwin you still working on this?
Yeah, I am working on it still. I am still looking for a better place than dropbox or hosting off of someone's home PC...
As for the A10, if you can get me a dump of the boot and recovery images I can make one for that too... you will want to preferably use the dump_image utility to get the image and the flash_image utility to flash it.
I can probably attach those to a post with dump instructions. They're tiny.
Basically, you root your phone, copy the files to a certain location, type a couple commands to fix permissions on the executables, then run a command to dump the image.
Flashing back requires clearing the boot or recovery partition with a command and then using the flash_image command to flash it.
My method tests the new boot image first by flashing it to recovery first and rebooting into recovery to make sure the new image works. Then flash the modified recovery image to the recovery and make sure it is rooted (so you can get things up again if something does go wrong). Then you flash the new tested boot image to boot. If, for some reason, that fails, it should reboot automatically into recovery after a few boot failures. Never had to test that, since I pre-test all images I make.
hi merwin, we are a fans group of GA a10 and we trust a lot in your work! if you need any kind of help contact me! probably you are the first in the world who can flash a GA phone
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
afoster1003 said:
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Click to expand...
Click to collapse
You forget one widely used protocol. Good old http on a standard web server.
Those other sites annoy me greatly, between the amount of ads, having to wait to download and daily limits, and the fact that they are temporary unless I pay. I am against them on principle.
I figure if there is enough interest, someone will step up to host them, otherwise I will just provide scripts, instructions, and technical info for people to do it themselves.
slumpz said:
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
Click to expand...
Click to collapse
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
merwin said:
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
Click to expand...
Click to collapse
I have, magically I might add. I downloaded the source for v.5.0.70 and managed to get it compiled. The resulting files can be found on on my blog, the one Slumpz posted(I can't post links yet, lol.)
The only problem is, I don't have much experience with anything linux. But, If you have any questions Merwin, email me, [email protected].
Here's a little how to, just check my blog, or google: How To: Build Garmin-Asus Kernel from Source.
am willing to giv a subdomain/storage ftp access on this domain for the good of the community if it helps any
Domain darkjester.net
Disk Usage 5.4 / 1500.0 MB
Bandwidth 100000 MB (100GB)
Home Root /home/a2931495
Apache ver. 2.2.13 (Unix)
PHP version 5.2.*
MySQL ver. 5.0.81-community
Activated On 2011-05-15 14:42
Status Active
Hello guys, are you still working on this.
I found out that A10 has a new firmware posted, which is versioned 5.2.7 instead of 5.0.x like the others. I wonder if there's any method to test this firmware on foreign A10 (non Chinese firmware)?
So, got an HTC Sensation 4G... meaning not much more work on the Garminfone for me.
Still trying to find time to compile everything that I have done into some semi-coherent document with the unlocked boot and recovery images. I still have the Garmin, so if someone manages a huge breakthrough then I may pick it up again. Really didn't want to get rid of the phone but there just isn't enough community development going on to make it worthwhile.
By the way, the Garminfone GPS blows every other phone away. The Sensation 4G is crap in comparison.

SHV-E160L Debricking Tool / Qualcomm Tool Pack V2-1

Note to NON SHV-E160L users
This software & this thread is aimed at developers Mainly, Please don't post 3 line request like "my device is bricked , please help" as you will be ignored, if you cant do the research required to provide the right details plus finding the correct files required then this thread is not for you and you should post in the device thread for your device, This program and it's associated files & thread is NOT being actively developed but the thread remains open for user to post more information, additional files, updates from the public etc.
It's not here for lazy people to scream fix my device, can those type of users please speak to your retailer, cell phone service shop.
I will reiterate again, THIS IS A DEVELOPMENT THREAD AND NOT A REQUEST PAGE FOR "fix my device"
PLEASE NOTE: This tool only comes pre-packed with files for the Korean SHV-E160L galaxy note. Usage on other devices requires that you understand the requirements, this includes but not limited to :-
1. Alteration of the scripts to use the files specific to your device
2. Correct HEX and SD-CARD loader also known as sdcard mbn
3. Correct partition information (knowing if it's MBR/GPT or hybrid)
4. Correct bootloaders for your device (SBL1/2/3/ABOOT)
I am not currently doing further development on this tool, it is here for anyone to expand on use how they seem fit so long as the authors involved are given the credit.
Users are welcome to build and post altered versions specific to their device but PLEASE post plenty of information as to what device/model it is for or the post may be deleted to protect other less educated users.
darkspr1te
Hi All,
I've updated my Debrick tool to Version 2.
Many Changes to the base code, inclusion of new tools, Almost a one click Linux solution for Qualcomm Development and debricking of Qualcomm devices.
As documented on this thread SHV-E160L home debrick thread I debricked a qualcomm based msm8660 device without using any special devices.
my first tools were internal development and had more bugs than a sewer, so after many hours of work i can now bring this new version to you.
Please do not pm with bugs, POST HERE Only.
This tool currently only supports the SHV-E160L , if users willing to provide the files from their devices I can expand the support of this tool.
in most cases linux is required for this, a ubuntu live cd/flash will work perfectly.
New Feature, Windows Based BACKUP of partitions and bootloaders, ROOT/Python27-windows is required and cannot function without this.
*nix backup coming soon,
Rules for posting backups
Post ONLY the link here, use www.sendspace.com to upload your backup zip (remember to change the .zip filename to reflect your device, example SHV-E160L-16GB.zip )
zip up only the backup folder, not the whole program, right click on backup folder, sent to compressed folder, rename.
this program does not backup personal or device specific data like IMEI number, it only backups the bootloaders, partition table and .pit file for samsung SHV based devices
When Posting links, please include your device details well, a example would be
SHV-E160L 16 GB, 9000lang rom,
The rom part is only so if we a tracing possible backup issues that may be rom specific.
Future backup features will include automatic detection of .mbn partitions based on qualcomm header.
Support for non SHV devices will be slow, but future versions will include other devices.
Well Enjoy,
EDIT: some users are reporting cookie not present error could be fixed by using a winxp/another qpst driver windows driver. this is unconfirmed bu i thought i should mention it. 04-12/2013
Changelog:- V2-2(dev version only - not a public release)
added command line device/folder parameter, you can now specify a unzip copy of posted bootloaders and it will restore them
added additional file to specify output sectors based on getpart data, testing option for building partition0.bin by hand based on known simalr devices
added dev switches for wiriting specified parts only
added skip aboot option (for now it is specified to skip writing of aboot.mbn, public release will be opposite, you will have to force writing aboot , sbl1/2/4/tz/rpm seems to come as one package, interchangeable as a package, aboot is totally device specific)
bugs:-
there is a known bug in the getpartbin.py python program, it cannot handle greater than 29 partitions.
Changelog:- V2-1
added windows backup.bat program to backup all bootloaders and partition0.bin
minor changes to code for changing device (current version support only changing of variable $DEVICE, feature will eventually be cmd line based)
tesing of backup files
bugs:-
there is a known bug in the getpartbin.py python program, it cannot handle greater than 29 partitions, and one will to help in python please let me know. I am not the author of the program
Changelog : V2
Improved error checking*
automated qdload detection*
automated qdload hex & .mbn upload
automated detection of device in sd-card mode*
user input*
colours
major code changes to start support for automatic parition information & collection allowing backup to be one command and upload to a website for distribution & recovery for all
development documentation
Code changes to allow expansion to other Qualcomm devices
Sendspace Links
BrixFix V2-1-Inc Python27-Inc cwm recoveries
http://www.androidfilehost.com/?fid=9390355257214632490 mirror tanks too Marduk191
Brixfix V2-1 No Python for windows, No cwm-recovery-Slim Version
Brixfix V2-1-Super-SlimNo drivers, bootloaders, python-win.
Media Fire Links
BrixFix V2-1-Inc Python27-Inc cwm recoveries
SHV-E160K 32GB Recovery files
SHV-E160L 32GB Recovery Files
SHV-E120L Recovery Files (posted on another page)
-------------------------
Here is the README
brixfix V2
=================================
By dakrspr1te ========Doc=V=1====
=================================
Thanks To :-
E:V:A, SLS, JCSullins(Rootz Wiki), Adam Outler, many more, sorry if i've missed you out.
Warning, Although i've tested this tool many times on my own devices, it always has the potential to damage both computer & cell phone device, YOU HAVE BEEN WARNED!!!!
This tool is designed to repair SHV-E160L Korean Galaxy Note 1 based on the MSM8660 & MDM9600 Qualcomm Chips
It Only works with devices that are stuck in QDLOAD mode or 05c6:9008 as the PID/VID
It uses Tool/info Written By Others as well as myself.
Namely :-
qdload - http://github.com/jcsullins/qdloader
getpartbin.py - http://blog.csdn.net/su_ky/article/details/7773273
hex2bin - hex2bin.sourceforge.net
Instructions
############
connect Qualcomm based device to usb port on linux PC, not tested under windows via USB redirection,
on command line run
sudo ./brickfix
Follow on screen instructions, tool will detect device in QDLOAD mode (05c6:9008) and switch to DMSS protocol, upload a hex (converted to bin for this purpose)
the hex is then executed and the device switches to Streaming Protocol, at this point we write a .mbn file to the internal emmc chip, at the end of the emmc write process the device then reboots
after the reboot re-running brixfix with detect the device in the second stage for repair , the device's emmc is accssable as a sd-card, we then write back the damaged parts of the bootchain,
at a minimum you must write a new partition table or the device will always boot in sd-card mode, WARNING, failure to write the rest of the boot chain could leave your device in a situation
which give only black-screen, no usb enumeration, dead. The only way around that is jtag, or finding the Boot resistor which switches the device back to QDLOAD mode, or emergency boot.
goto http://forum.xda-developers.com/showthread.php?t=1914359 for further details.
Come give me thanks on XDA if this tool helped you
Additional Tools (DEV Level)
===========================
getpartbin.py - A tool for backing up the primary partition & extended parition tables and combines them into a writable parition0.bin file (python)
qdload.pl - A tool for talking in the HDLC framed DMSS & Streaming Protocol's used by Qualcomm (Perl)
switchmode.sh - A executes qdload.pl for msm8660 device upload
get-part.sh - **DEV** unfinished tool by darkspr1te for creating partition tables in sfdisk format and .csv format (to be used in the future to create parition0.bin plus more automated collection)
tools/ - Folder containing armv5 (arm7 compatible) tools for parition manipulation and data collection
SHV-E160L-16GB/ - Folder contain SHV-E160L bootloaders & pit file
ADB/ - Folder containing adb programs
extras/ - Folder containing odin and clock work mode recovery installers for 160l devices
QUALCOMM/ - Windows drivers (For QPST, Not required in linux, included for backwards compatability with older guides)
hex2bin - convert your xxxxMPRG.hex file to bin for use with qdload
Tips
====
Additional
==========
I will accept brick qualcomm devices for developing further debricks. pm me via XDA Forums
Darkspr1te
Click to expand...
Click to collapse
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
Kudos to u.
Nicely done ..OP
I'll get this thread added into the note super thread .
An amazing resource to be sure ...
Many thanks ....g
Very nice!
< reserved >
Thank you!
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
I'll take a deeper look at it later.
You should note that qualcomm chipsets do not have support for USB 3.0. While the linux USB 3.0 driver is backwards compatible with the older standards, it is still buggy so it's best to only use USB 2 and lower ports.
Also, you should be using a 32bit Linux distro with a kernel from 2012 or later.
-SLS-
Will this work on SHV-E160S??
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
Probably. You'll need Linux. If you don't have linux, go grab the above mention ubuntu live cd (I suggest version 12.04 32bit)
As I'm not familiar with that device I don't know exactly what will need to be fixed.
-SLS-
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Sent from my A210 using Tapatalk 2
darkspr1te said:
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Sent from my A210 using Tapatalk 2
Click to expand...
Click to collapse
What files do you need from the ATT Note? I know what you have done, but don't understand it, but sure as hell would like to help !!!!!!!!!!
I have Ubuntu...(Yay !) ..... let me know the steps to dump files.
PS: Is there any chance of getting Tegrak kernel or ROMs for ATT Note. Maybe I should ask what is the status of the Tegrak kernel etc.? I see it on the app store, but I know its not for ATT Note. I remember Tegrak from when I used to use Voodoo Sound that Tegrak kernel supported. But I have never found anything comparable to voodoo sound for our more 'advanced' phones like the note.
PS: Does this make any sense to you ? Or am I rambling ?
Shv-e160s 32gb..
darkspr1te said:
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Click to expand...
Click to collapse
SHV-E160S 32GB, Thats all I know about this..
I'm downloading ubuntu right now. Then I'll try this tool on my device
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
This tool works only on the 16gb right now, as soon as I can get a 32gb partition and S about file I will extend it
Sent from my A210 using Tapatalk 2
darkspr1te said:
This tool works only on the 16gb right now, as soon as I can get a 32gb partition and S about file I will extend it
Sent from my A210 using Tapatalk 2
Click to expand...
Click to collapse
Oh.. No luck for me then..
Tool Updated, Please go my OP
SouL Shadow said:
Probably. You'll need Linux. If you don't have linux, go grab the above mention ubuntu live cd (I suggest version 12.04 32bit)
As I'm not familiar with that device I don't know exactly what will need to be fixed.
-SLS-
Click to expand...
Click to collapse
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
As soon as a user uploads a backup for the 160S (16 or 32GB depending on your device) I will include it in a repair file.
chappatti said:
What files do you need from the ATT Note? I know what you have done, but don't understand it, but sure as hell would like to help !!!!!!!!!!
I have Ubuntu...(Yay !) ..... let me know the steps to dump files.
PS: Is there any chance of getting Tegrak kernel or ROMs for ATT Note. Maybe I should ask what is the status of the Tegrak kernel etc.? I see it on the app store, but I know its not for ATT Note. I remember Tegrak from when I used to use Voodoo Sound that Tegrak kernel supported. But I have never found anything comparable to voodoo sound for our more 'advanced' phones like the note.
PS: Does this make any sense to you ? Or am I rambling ?
Click to expand...
Click to collapse
you can find all tegrak roms/kernels via my clean korean rom link in my signature,not sure on ATT but i've ported a few ATT kernels to the 160L so it's possible to convert back. *nix backup coming soon but for those that want to jump the gun, just run the same adb commands as in backup.bat and also the python command. please note they will download the files to the current directory so make a directory first, cd into it and refer back to the scripts. to run python partition0.bin script just use python ../getpartbin.py to create a partition0.bin file in current directory.
root is required for backup, python27 is required for windows backup (13mb file, included)
Thank
darkspr1te said:
As soon as a user uploads a backup for the 160S (16 or 32GB depending on your device) I will include it in a repair file.
Click to expand...
Click to collapse
I found some useful links (I hope) to the understanding of some mechanisms useful in debricking of devices using Qualcomm chipsets. I hope this may help generally, even to unbrick the i8150 (Ancora)!
http://blog.csdn.net/su_ky/article/details/7773273
http://www.anyclub.org/search/label/emmc boot
http://www.anyclub.org/2012/04/how-to-build-emmc-flash-programmer.html
Some stuff is in chinese, other in english but reading a bunch of articles I became convinced that the explanations available can be very useful!
Regards!
Just curious, why not post under original development? Love to see you there, you deserve it. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
shv-e160L 32GB
Any success on the SHV-e160L 32GB yet?

[TOOL][MAC]Splash Flasher for Mac OSX

This is a simple tool/script used to:
1. convert .jpg .png and .bmp files into the format used for the splash screen on your device.
2. Make a full backup/restore of your device.
3. Flash the new image to your device.
I have only tested this on the HTC Droid DNA, if anyone wants to test it for another device and post results that would be great.
This script is based on the work done by TrueBlue_Drew, but since I am on a Mac, I got tired of booting a virtual machine every time that I wanted to make a new splash screen. So I decided to "convert" his script to a bash script to make my life easier. After testing several boot screens and all of the functions myself to make sure they all work, I decided to share the script with everyone here on XDA. I have been using this site since I got my first Android phone just a few years ago (and it was a Motorola Citrus...one of the worst "smart" phones ever created!), and have learned a ton - I figured it is time that I start giving back to the community.
If you like my work, don't be afraid to click the "Thanks" button. If you see any way to improve the script or have suggestions for other functions, leave a comment. If you have a question about bash scripting or using adb, leave a comment (I may or may not be able to help, but I will try...and there are many others here that can help).
Thanks again to TrueBlue_Drew for writing a nice little batch file that got me started on the path to creating this tool for myself.
The flash/backup splash option should work for any HTC devices that use a 1080x1920 splash screen but has ONLY been confirmed working with the HTC Droid DNA (I will add others to the list if anyone else confirms they work. I am already thinking about a way to select an option for the boot screen size you want to convert in order for this to work on more devices. :fingers-crossed:
REQUIREMENTS
1. Written on Mac running OSX 10.9.1 (Mavericks), but should work on any OSX Mac
2. Rooted HTC device with S=OFF and Eng Hboot
3. 1080x1920 png, jpg or bmp image
INSTRUCTIONS
1. Download the attached zip and unzip it somewhere on your Mac.
2. Create or find the 1080x1920 image you want for your splash screen.
3. Go into the "Splash Flasher Mac" folder you unzipped and place your image
in the "place-image-here" folder.
4. Run the file "splash_flasher.sh" file in the terminal and follow the on screen instructions.
NOTE: At this time this does not support having more than one of the same image type in the "place-image-here" folder when converting and flashing. A fix for that is already being worked on, but didn't see it as a major issue right now since you can only flash one splash screen anyway.
NEW NOTE: I was finally able to get the multiple images in one folder working and have implemented it only for .png images (other file types coming with next version). So now you can dump multiple .png files in the folder and the program will create the boot images, name them using the original filename and move them to the "images" folder. The next part of this to figure out is how to select your screen size and create a boot image of that size. Stay tuned...not that it seems many people are tuned, but that's OK.
NOTE: VERSION 1.2 - Removed support for .jpg and .bmp files. Didn't see the need to support multiple file types. There is now a Photoshop template file included with the script. Just open in photoshop and add your image to the top layer (labeled as "Team Logo" because I am using that as my template for my sports teams splash screens). If your image is large and covers the HTC and Beats logos (and you want them in your splash screen), just move the layers around how you want them. The colors of the HTC letters can also be changed however you want.
RESERVED
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
drakemata said:
Has anyone used this to create their own custom boot screen? I am just trying to figure out if I should continue working on this or not. If you have made your own boot screens, feel free to share.
I am also working on a port of this script to Linux and improving on the original for Windows that TrueBlueDrew created and I based my script on. Would there be any interest in that?
Click to expand...
Click to collapse
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
I don't typically work with Windows, either...but I know there us still a large demand for making things easier for Windows users since a great majority of them are not as inclined to do stuff at the command line.
As long as there is one person interested, I will continue to work on this. Thanks for your reply.
Mav3rick40 said:
I have forgotten about this. I'm going to look at it today sometime. A Linux version would be AWESOME. Mac and Ubuntu is all I work on. I'm really surprised that more things aren't for the Linux os.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
drakemata said:
Mav3rick40, have you had a chance to check out the script on your Mac? Just wondering if you have any issues or recommendations for improvements. I have just completed a revision to the script to remove support for .jpg and .bmp images. I figured I would keep it simple with support for .png images since I feel they have the best quality of the three file types.
I am also hoping to finish the Linux version and post it tonight. If you would be willing to test, that would be great. I will probably start a new thread for that.
Click to expand...
Click to collapse
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Mav3rick40 said:
Not yet hopefully tonight. I got busy with school work.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
Ok cool. Yeah I'm going to school for programming.
Sent from my HTC6435LVW using Tapatalk
drakemata said:
I completely understand that. I hate when work/school gets in the way of my programming time. If you previously downloaded the script, please delete and use the new version attached to the OP.
Click to expand...
Click to collapse
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Mav3rick40 said:
is there anything special I need to do to make this run? every time I try to open splash_flasher.sh it opens up in Xcode.
Click to expand...
Click to collapse
You need to navigate to it from the terminal and do ./splash_flasher.sh
Sent from my Droid DNA using Tapatalk
I figured it out after playing around with it for a couple of hours.
Sent from my HTC6435LVW using Tapatalk
Glad to see you figured it out. I am trying to convert this over to an Applescript app as well as working on my Linux version and making new splash screens for all sports teams (which was a much bigger undertaking than I thought it would be).
If you have any suggestions for improving the script or for additional tools that should be added, I would appreciate the feedback.

[TOOL][LINUX]DNA Splash Flasher for Linux

This is a simple tool/script used to:
1. convert .png files into the format used for the splash screen on your device.
2. Make a full backup/restore of your device.
3. Flash the new image to your device.
I have only tested this on the HTC Droid DNA, if anyone wants to test it for another device and post results that would be great.
This script is based on the work done by TrueBlue_Drew, but since I am on a Mac, I got tired of booting a virtual machine every time that I wanted to make a new splash screen. So I decided to "convert" his script to a bash script to make my life easier. After testing several boot screens and all of the functions myself to make sure they all work, I decided to share the script with everyone here on XDA. I have been using this site since I got my first Android phone just a few years ago (and it was a Motorola Citrus...one of the worst "smart" phones ever created!), and have learned a ton - I figured it is time that I start giving back to the community.
Since the creation of my script for the Mac, I decided to port it to Linux as well since they both use the bash shell. The only difference was having to find the compiled adb, fastboot, and ffmpeg tools for Linux.
If you like my work, don't be afraid to click the "Thanks" button. If you see any way to improve the script or have suggestions for other functions, leave a comment. If you have a question about bash scripting or using adb, leave a comment (I may or may not be able to help, but I will try...and there are many others here that can help).
Thanks again to TrueBlue_Drew for writing a nice little batch file that got me started on the path to creating this tool for myself.
The flash/backup splash option should work for any HTC devices that use a 1080x1920 splash screen but has ONLY been confirmed working with the HTC Droid DNA (I will add others to the list if anyone else confirms they work. I am already thinking about a way to select an option for the boot screen size you want to convert in order for this to work on more devices. :fingers-crossed:
REQUIREMENTS
1. Written on Linux Mint 16, but should work on any version of Linux with a bash shell
2. Rooted HTC device with S=OFF and Eng Hboot
3. 1080x1920 png image
INSTRUCTIONS
1. Download the attached zip and unzip it somewhere on your computer.
2. Create or find the 1080x1920 image you want for your splash screen.
3. Go into the "Splash Flasher Mac" folder you unzipped and place your image
in the "place-image-here" folder.
4. Run the file "splash_flasher.sh" file in the terminal and follow the on screen instructions.
I am currently having trouble uploading the file, I will try again tomorrow. In the mean time, the script can be downloaded from my dropbox.
RESERVED
Do you by any chance know how to extract the splash screen from another device's firmware update?
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Do you by any chance know how to extract the splash screen from another device's firmware update?
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Not sure if this works with the DNA or not, but try the tools in CNexus' post. I am not on my Linux machine right now, so I can't test. If the tools work, I will see if I can incorporate them into my tool. I am also working on converting the script to use easybashgui to give a graphical interface.

[sparrow] AsteroidOS - Alpha 1.0

Asteroid OS Alpha 1.0​
Freedom & Privacy​
We believe that when it comes to wearable devices, users should have full control over their machines and data. AsteroidOS has been created from the ground-up with modularity and freedom in mind. For this reason, it is a free and open-source project.
Proven building blocks​
AsteroidOS is built upon a rock-solid base system. Qt 5.6 and QML are used for fast and easy app development. OpenEmbedded provides a full GNU/Linux distribution and libhybris allows easy porting to most Android and Android Wear watches.
Community-friendly​
Since its creation in 2015, AsteroidOS has been led by Florent Revest, but is open towards external contribution and collaboration. The project is still in active development and if you want to help, make sure to check the Get Involved page.
Click to expand...
Click to collapse
This is only for SPARROW, the larger ZenWatch 2.
The way AsteroidOS is implemented it is not meant to be flash to any partitions. It boots an isolated root file system from the sdcard partition using a custom fastboot image.
This is very powerful because it allows a person to switch between AsteroidOS and Android Wear with relative ease.
Status: The Asus Zenwatch 2 hasn’t been supported by AsteroidOS for very long and there is currently a bug with the touchscreen but overall it is good enough to test Asteroid.
The Bluetooth synchronization app for Android is named AsteroidOSSync and is available. Be careful that dory is the only port with Bluetooth capabilities and this app will be of no use with other watches yet.
Click to expand...
Click to collapse
Known Issues:
Touch Screen disabled after resuming from "sleep"
Bluetooth - needs to be implemented.
To Do:
How to get logs
Pictures
AsteroidOS documentation [url]https://asteroidos.org/wiki/documentation/[/URL]
Source:
meta-asteroid: [url]https://github.com/AsteroidOS/meta-asteroid[/URL]
meta-sparrow-hybris: [url]https://github.com/AsteroidOS/meta-sparrow-hybris[/URL]
AsteroidOSSync: [url]https://github.com/AsteroidOS/AsteroidOSSync[/URL]
My test repo: [url]https://gitlab.com/lrs/asteroidos-sparrow[/URL]
Build Changelog:
December 1, 2016:
/dev/.coldboot is created by systemd
btsync fixes
libaccounts fixes
mtp fixes
and much more
September 18, 2016:
Move msm-fb-refresher to meta-asteroid
machine.conf: Remove some MACHINE_FEATURES for more lightweight images
bcrm-patchram-plus: be less verbose
Make layers Machine specific to prevent conflicts with other meta-*-hybris
lipstick, sensorfs: move hybris dependencies to meta-*-hybris layers
lipstick, sensorfs: fix typo
Simplify patchram script
September 11, 2016:
sparrow.conf: provide proper SERIAL_CONSOLE for systemd
misc. meta-astroid patches
August 13, 2016:
sparrow.conf remove some useless config values
linux-sparrow: pack with mkboot
July 28, 2016: Initial Official Bring up
Sparrow Kernel Bring Up
Initialize Sparrow lollipop system
Configure Initd scripts to support Sparrow
Configure Sparrow device flags
Testing Changelogs:
September 10, 2016:
Provide proper serial console to prevent systemd timeouts
Old logs:
Nothing yet
Requirements:
Linux/OSX (Windows if drivers are available)
Unlocked Bootloader
ADB and Fastboot in path - recommended not required
Developer mode
ADB enabled
Not Needed:
DOES NOT NEED TWRP
A backup, though it is recommened
Before Installing (only if the bootloader is locked):
Install the Android developer tools: adb and fastboot, on your computer.
Enable ADB in the Android Wear settings under Developer options/Android Debugging. (Developer options appear after tapping the Build number in the About page several times)
Enter the following commands in a terminal:
adb reboot bootloader
fastboot oem unlock
Temporrary Install (Assumes your using Linux):
Go to the AsteroidOS website - link is below
Select Asus ZenWatch 2 (sparrow)
Download the official rootfs and zImage files
Download the AsteroidOSSync app from the bottom of the website
Install on your phone - Useless until bluetooth is implemented
Push the rootfs to the sdcard
adb push -p /home/user/Downloads/asteroid-image-sparrow.ext4 /sdcard/linux/asteroidos.ext4
Reboot to bootloader
adb reboot bootloader
fastboot boot the zImage
fastboot boot /home/user/Downloads/zImage-dtb-sparrow.fastboot
Download:
AsteroidOS Official Downloads
Archives/Mirrors:
To be updated
Old How To "Install":
Extract asteroidos-*-sparrow.tar.xz
cd to extracted files
adb push -p asteroid-image-sparrow.ext2 /sdcard/linux/rootfs.ext2
adb reboot bootloader
fastboot boot zImage-dtb-sparrow.fastboot
enjoy
Getting logs:
While there is no straight forward way to determine which log is needed because there are so many pieces that break regularly. Some common areas are debuging the launcher, and hw issues. I do not remember all the logging commands or what does what, so if you are obtaining logs you will need to run all the commands and capture the outputs.
adb access to Asteroid OS (windows, linux, mac)
adb shell
add strace - if needed
journalctl -u mce --no-pager (requires disabling 1000 user first) - used to debug launcher and other packages.
EGL_PLATFORM=hwcomposer strace lipstick --platform hwcomposer
EGL_PLATFORM=hwcomposer lipstick --platform hwcomposer
more to come
Q: Why doesn't x, y, z, feature work?
A: Probably, because it hasn't been implemented yet.
Q: I have x, y, z, issue.
A: Logs Please
Q: Can I use a custom kernel?
A: Only if you are willing to put forth the effort replace the kernel source in the build process yourself and make your own builds.
Q: I flashed *insert file here* and now it won't boot.
A: Sounds like a personal problem, since you didn't read the instructions properly. Seriously, you will probably need to restore some sort of backup.
Q: Will you port AsteroidOS to my watch?
A: No, but I can, somewhat, help you port it yourself. #asteroid on freenode or [url]https://asteroidos.org/irc-channel/[/URL] is a good place to get help.
Lrs121 said:
Q: Why do I need linux?
A: Because I don't know of any working Windows/OSX(macOS) fastboot drivers.
Q: Why doesn't x, y, z, feature work?
A: Probably, because it hasn't been implemented yet.
Q: Can I use a custom kernel?
A: Only if you are willing to put forth the effort replace the kernel source in the build process yourself and make your own builds.
Q: I flashed *insert file here* and now it won't boot.
A: Sounds like a personal problem, since you didn't read the instructions properly. Seriously, you will probably need to restore some sort of backup.
Q: Will you port AsteroidOS to my watch?
A: No, but I can, somewhat, help you port it yourself. #asteroid on freenode or https://asteroidos.org/irc-channel/ is a good place to get help.
Click to expand...
Click to collapse
after the bootanimation, the display is turning black and it seems to have a bootloop
---------- Post added at 12:09 ---------- Previous post was at 11:42 ----------
Lrs121 said:
Requirements:
Linux
p7zip
Unlocked Bootloader
ADB and Fastboot in path - recommended not required
Developer mode
ADB enabled
Not Needed:
DOES NOT NEED TWRP
A backup, though it is recommened
How To "Install":
Extract asteroidos-*-sparrow.7z
cd to extracted files
adb push -p asteroid-image-sparrow.ext2 /sdcard/linux/rootfs.ext2
adb reboot bootloader
fastboot boot zImage-dtb-sparrow.fastboot
enjoy
Download:
Google Drive Folder
Mirrors:
To come?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24694152805485105
Mirror for your file
matze19999 said:
after the bootanimation, the display is turning black and it seems to have a bootloop
---------- Post added at 12:09 ---------- Previous post was at 11:42 ----------
https://www.androidfilehost.com/?fid=24694152805485105
Mirror for your file
Click to expand...
Click to collapse
Thanks for the mirror.
Have you tried pressing the power button after the boot animation. I can't remember if it defaults to the sleep state after boot. There is no "ambient" mode, the screen is either on or off.
It is also possible that, because it is a dev preview, this particular build is broken and may be so for a while.
Lrs121 said:
Thanks for the mirror.
Have you tried pressing the power button after the boot animation. I can't remember if it defaults to the sleep state after boot. There is no "ambient" mode, the screen is either on or off.
It is also possible that, because it is a dev preview, this particular build is broken and may be so for a while.
Click to expand...
Click to collapse
Will try it, thanks
---------- Post added at 19:59 ---------- Previous post was at 19:55 ----------
matze19999 said:
Will try it, thanks
Click to expand...
Click to collapse
no, doesnt work. I can access the watch via adb shell, but display is black all time..
matze19999 said:
Will try it, thanks
---------- Post added at 19:59 ---------- Previous post was at 19:55 ----------
no, doesnt work. I can access the watch via adb shell, but display is black all time..
Click to expand...
Click to collapse
Ah that's useful. If adb can be access then that means is not the boot image nor is it boot looping. Which narrows it down to the root file system and probably just an unstable build.
I thought you are the developer of this build?
matze19999 said:
I thought you are the developer of this build?
Click to expand...
Click to collapse
I maintain the device tree, beyond that I'm clueless. So if there happens to be bad code or something related to the system I'm clueless. That or I had a bad download during the build process. Anything could be the issue.
If I can remember the some of the logging commands I can have people get me logs from their watches and I can get help decoding what the issue is from Florent Revest or someone on IRC.
Lrs121 said:
I maintain the device tree, beyond that I'm clueless. So if there happens to be bad code or something related to the system I'm clueless. That or I had a bad download during the build process. Anything could be the issue.
If I can remember the some of the logging commands I can have people get me logs from their watches and I can get help decoding what the issue is from Florent Revest or someone on IRC.
Click to expand...
Click to collapse
If you tell me how I can take a log file, I would send it to you...
Update:
There is now a directory for test changes. Use this if you are brave, though in general it should be safe.
It can be found under the Google Drive link. Please read the README file. It will include important information related to the test builds
Edit:
the sync app has been uploaded. it is not signed so any future updates will probably require uninstalling the old app and installing the new
I get parsing Error while installing the apk file.
Android 6.0
Snapdragon 820 64Bit
http://hastebin.com/onuyifedet.md
Code:
sh-4.3# lipstick --platform hwcomposer
EGLFS: Screen Info
- Physical size: QSizeF(29, 29)
- Screen size: QSize(320, 320)
- Screen depth: 32
Segmentation fault
matze19999 said:
http://hastebin.com/onuyifedet.md
Click to expand...
Click to collapse
Make sure you have the EGL_COMPOSER=hwcomposer pre-appended or else it will segfault. I forgot strace had to be built and added to /bin. Also I believe the journalctl command is used to debug the launcher
matze19999 said:
I get parsing Error while installing the apk file.
Android 6.0
Snapdragon 820 64Bit
Click to expand...
Click to collapse
I'll look into the app issue
Lrs121 said:
Q: Why do I need linux?
A: Because I don't know of any working Windows/OSX(macOS) fastboot drivers.
Q: Why doesn't x, y, z, feature work?
A: Probably, because it hasn't been implemented yet.
Q: I have x, y, z, issue.
A: Logs Please
Q: Can I use a custom kernel?
A: Only if you are willing to put forth the effort replace the kernel source in the build process yourself and make your own builds.
Q: I flashed *insert file here* and now it won't boot.
A: Sounds like a personal problem, since you didn't read the instructions properly. Seriously, you will probably need to restore some sort of backup.
Q: Will you port AsteroidOS to my watch?
A: No, but I can, somewhat, help you port it yourself. #asteroid on freenode or https://asteroidos.org/irc-channel/ is a good place to get help.
Click to expand...
Click to collapse
fastboot and adb is working flawlessly on Mac OSX 10.11.6
Update:
Major updates to meta-asteroid (core of the os) - should probably fix launcher issues
Minor update to sparrow device tree
Will be up soon
Major update:
meta-asteroid has had many changes and some rewrites
sparrow device tree has been updated to support changes to meta-asteroid
rootfs is smaller after removing some optional features
bootloader
I was wondering if after executing these two adb commands
will the bootloader remain unlocked even after reboot and
a power down? (my phone has the MM 6.01 updated)
adb reboot bootloader
fastboot oem unlock
Thanks, have a great day everyone!
Misterjunky said:
I was wondering if after executing these two adb commands
will the bootloader remain unlocked even after reboot and
a power down? (my phone has the MM 6.01 updated)
adb reboot bootloader
fastboot oem unlock
Thanks, have a great day everyone!
Click to expand...
Click to collapse
Adb reboot bootloader just reboots the watch into fastboot mode.
Fastboot OEM unlock is what unlocks the watch, this is "permanent" as in it will stay that way until you run the command fastboot oem lock

Categories

Resources