Database Develop

trying to root cdma hero with 2.1 on a mac, help please.

i just got my refurb phone in the mail, and to my surprise it has the 2.1 update on it. D:
im having a real hard time rooting, could anybody help.
i haven't gotten any progress.

my mac interpretation of this is below thissssss
regaw_leinad said:
If you do not see the Superuser Permissions app in the app tray after running the exploit, on your phone, go to
Settings > About Phone > Software information
If it says 2.27.651.6 under "Build Number" (notice the bolded, underlined, italic 6), you need to run the RUU in the second post of this thread to revert to .5 first. Doing this WILL erase all of your data on your phone, so be sure to back up anything if you need to first.
It's been a long search for root, but it has finally been achieved!
The Hero 2.1 exploit is based on the EVO rooting method.
The EVO rooting could not have been possible without the combined efforts of:
Matt Mastracci
ozzeh
Joshua Wise
They are all AMAZING and should be thanked for all they have done.
Thank you to Amon_RA for the recovery.img (1.5.2) and Jus10o for packing up a boot.img for me last night when I needed it quick.
Over the past week, Matt and I worked hard applying this exploit to gain permanent root on the Hero.
I now have permanent root access on 2.1 down to a few simple steps that are detailed in this guide.
Also, I'd like to thank everyone that worked really hard on trying to find root here in the Hero community, and specifically all of those who contacted me and worked together with me trying to gain root:
abcdfv
imleon
thatguythatdid
navalynt
nfinitefx45
lifetrip718
rejectedkid
nebenezer (for being cool)
These guys worked incredibly hard with me and had extremely innovative ideas. They deserve a ton of credit for sticking with it as well trying to find . They were all in this for all the Hero users.
If I forgot your name, please let me know via pm so I can add you to the list.
As of right now, this guide is for windows only. Soon to come, OSX & Linux.
HOW TO ROOT SPRINT'S 2.27.651.5 RELEASE FOR THE CDMA HERO (Stock Android 2.1)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here
Run the installer, and reboot your computer when it is finished. Move on to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Go to Settings > Applications > Development > and make sure it is checked.
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter.
It is also found under Start Menu > All Programs > Accessories > Command Prompt
Step 9: You will now enter the commands that I have put in code boxes followed by pressing ENTER, one code at a time.
You may also copy/paste these commands in to the Command Prompt, pressing ENTER after each, one at a time.
Comments will be outside of the code boxes (do NOT type these into the Command Prompt as they just are to help describe the root process)1:
Code:
cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands:3:
Code:
adb push unrevoked /sdcard
4:
Code:
adb push recovery.img /sdcard
5:
Code:
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.6.
Code:
adb shell
7.
Code:
sh /sdcard/unrevoked
You should now see output that says this:
Code:
# sh /sdcard/unrevoked
sh /sdcard/unrevoked
Unpacking, please wait...
88 88 88b 88 88""Yb 888888 88 dP dP"Yb 88 dP 888888 8888b.
88 88 88Yb88 88__dP 88__ 88dP dP Yb 88odP 88__ 8I Yb
Y8 8P 88 Y88 88"Yb 88"" 8dP Yb dP 88"Yb 88"" 8I dY
`YbodP' 88 Y8 88 Yb 888888 YP YbodP 88 Yb 888888 8888Y
==================================================================
unrEVOked: root for HTC evo and hero (http://unrevoked.com)
$
-----------------
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it.
Open the Superuser Permissions app. You will see a blank screen.
-----------------
In the Command Prompt on your computer, type:8.
Code:
su
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
Code:
$ su
su
#
Now type:9.
Code:
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type10.
Code:
reboot recovery
Your phone will now boot to the custom recovery image you just flashed.
If that doesn't work, (ie you get errors or it stays at the white/green HTC screen) try using this recovery image, put it on your sdcard, and try code #9 again.
In the Recovery Menu on your phone, choose the option:
Code:
Flash zip from sdcard
Then select
Code:
boot-patched.zip
and press the Home button to apply.
Once Recovery says "Install from sdcard complete", you need to make a nandroid backup!
In the main menu or the Recovery Screen, you will see an option that says
Code:
Backup/Restore
Choose that option, and then choose the option
Code:
Nand backup
This can take up to 5 minutes, so be patient while you see the
Code:
............
Once done, a nandroid backup of your phone will be created and saved to your sdcard in the folder directory:
Code:
/sdcard/nandroid/(your serial number)/
When it is complete, hit the back button to return to the Main menu, and hit "Reboot system now" from the menu to reboot normally!
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
You now have full root access on 2.1!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
step 2, where he moves the android sdk just move it to where ever you want,
step 3, don't worry about step 3,
step 4, do it as he says
step 5, move the files to the tools file in the android sdk folder you extracted to your preferred location,
step 6, do as he says
step 7, do as he says
step 8, go to your applications folder, open utilities, open terminal
BTW DO NOT TYPE THE QUOTES INTO THE TERMINAL
step 9, go to where you put the android sdk folder and right click on the tools folder and you should see the whole location for it, something like this /blah/blah/androidsdk/.......... so now in your terminal you are going to write "cd (now type the location from the tools folder path)and add /tools" to the end. what you are doing is moving your terminal into that tools folder where the root files are.
9-2, instead of adb devices it is "./adb devices"
9-3, instead of adb push unrevoked /sdcard it is "./adb push unrevoked /sdcard"
9-4, instead of what he has it is "./adb push recovery.img /sdcard"
9-5, instead of what he has it is "./adb push boot-patched.zip /sdcard"
9-6, type "./adb shell"
9-7, type what he has
9-8, type su
9-9, type what he has
9-10, type what he has
continue doing what he says,
if you want the disabling the ota part translated just ask me

eagles16 said:
my mac interpretation of this is below thissssss
step 2, where he moves the android sdk just move it to where ever you want,
step 3, don't worry about step 3,
step 4, do it as he says
step 5, move the files to the tools file in the android sdk folder you extracted to your preferred location,
step 6, do as he says
step 7, do as he says
step 8, go to your applications folder, open utilities, open terminal
BTW DO NOT TYPE THE QUOTES INTO THE TERMINAL
step 9, go to where you put the android sdk folder and right click on the tools folder and you should see the whole location for it, something like this /blah/blah/androidsdk/.......... so now in your terminal you are going to write "cd (now type the location from the tools folder path)and add /tools" to the end. what you are doing is moving your terminal into that tools folder where the root files are.
9-2, instead of adb devices it is "./adb devices"
9-3, instead of adb push unrevoked /sdcard it is "./adb push unrevoked /sdcard"
9-4, instead of what he has it is "./adb push recovery.img /sdcard"
9-5, instead of what he has it is "./adb push boot-patched.zip /sdcard"
9-6, type "./adb shell"
9-7, type what he has
9-8, type su
9-9, type what he has
9-10, type what he has
continue doing what he says,
if you want the disabling the ota part translated just ask me
Click to expand...
Click to collapse
i really appreciate your help, it workded. the ota translation would be lovely, if its really needed. idk if its needed after flashing a custom ROM, if so, your help would be nice.

glad to know it worked out for you , ill do the ota one right now
plug you phone in, set to charge only, make sure usb debugging is on,
step 1, open up terminal from the utilities folder again, and remember the step where we did " cd /blahh/blahh/androidsdk/tools", yeah well do it again fa sho.
step 2, type "./adb devices"
step 3, type "./adb remount"
step 4, type "./adb shell"
step 5, type "mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak"
and you should be good to go

eagles16 said:
my mac interpretation of this is below thissssss
step 2, where he moves the android sdk just move it to where ever you want,
step 3, don't worry about step 3,
step 4, do it as he says
step 5, move the files to the tools file in the android sdk folder you extracted to your preferred location,
step 6, do as he says
step 7, do as he says
step 8, go to your applications folder, open utilities, open terminal
BTW DO NOT TYPE THE QUOTES INTO THE TERMINAL
step 9, go to where you put the android sdk folder and right click on the tools folder and you should see the whole location for it, something like this /blah/blah/androidsdk/.......... so now in your terminal you are going to write "cd (now type the location from the tools folder path)and add /tools" to the end. what you are doing is moving your terminal into that tools folder where the root files are.
9-2, instead of adb devices it is "./adb devices"
9-3, instead of adb push unrevoked /sdcard it is "./adb push unrevoked /sdcard"
9-4, instead of what he has it is "./adb push recovery.img /sdcard"
9-5, instead of what he has it is "./adb push boot-patched.zip /sdcard"
9-6, type "./adb shell"
9-7, type what he has
9-8, type su
9-9, type what he has
9-10, type what he has
continue doing what he says,
if you want the disabling the ota part translated just ask me
Click to expand...
Click to collapse
im stuck on step 9... can you make video or something

hotboyray said:
im stuck on step 9... can you make video or something
Click to expand...
Click to collapse
I'm not a mac user so this might be wrong but if you have the latest updated version of the sdk files they for some reason took out the adb file. So google search for the adb files, download them into the android sdk tools file and then try step 9 again. This should work.

One click root APK in the themes forum if you can't get it. It's worked everytime for me. Super fast

This doesn't work for me
Sent from my HERO200 using XDA App

Bootscreens/Bootanimations by Synaptyc

I have made bunches of Bootanimations & Bootscreens in the past.
I will list them here.
Note: some are good ... some are bad.
But you can find anything I make in this thread.
What is the difference between bootscreen and bootanimation? (Both produce an animation upon boot.)
BOOTANIMATION
resides in the "/data/local/" or /system/media/" folder on your phone
is made up of individual picture files and strung together upon boot to make an animation
does not read any audio file therefore doesn't have sound upon boot
BOOTSCREEN
resides in the "/system/media/bootscreen/" folder on your phone
is made up of a animated GIF file and played as an animation upon boot.
plays an mp3 file to add audio to the animation (but only works on certain ROM's. I use them with xtrROM & xtrSENSE ROM's and have no issues. other ROM's may not support them)
NOTE: both should not be on your device at the same time, or it will only play the bootanimation and never the bootscreen
Helpful links
********************************************
Custom Boot Animation Gallery {No root Needed}
[HOW-TO]--Stock Bootscreen w/ Sound
Animations
********************************************
CLICK A PICTURE AND GO TO THAT ANIMATIONS POST
DroidX
Andy Colors
xtrROM & xtrSENSE
Andy Does
Sylock
Droid Eye
3D Plasma
Plasma RGB
Wait Circle
Unstable Core
Andy Colors V2
Loading System Check: Blue
Loading System Check: xtrROM & xtrSENSE
Andy Power Black and Colors
Loading Semicircles
B&W
portrait_________landscape
Red
...coming soon
Green
...coming soon
Blue
Pink
R2-D2 with sound!
Preview Bootanimation on phone while in Android!
1) Install GScript Lite from the app market
2) Create a script called "Bootanimation"
3) Make sure "Needs SU?" is checked
4) In the bottom field type:
Code:
TIMEOUT=20
( bootanimation & sleep $TIMEOUT; kill $! 2>/dev/null )
The TIMEOUT is in seconds and can be changed as you like.
*** this code was contributed by Arabia ***
5) Save the script
6) Click on the Bootanimation script you just created. Let the animation run all the way through until the script ends returning you to the GScript app.
7) Show off your bootanimation whenever you want =)
Helpful files
********************************************
Here are a few BATCH files I use to swap BootAnimations and BootScreens.
(you are responsible for backing up any animations you want to keep before running any of these batch files)
Just make a TEXT file and save it as "whatever.bat"
RemoveAnimations.bat
Code:
:: this batch file will remove ANY bootscreen or bootanimation on the device
:: ***make sure you backup any that you want to keep***
@echo on
path=C:\android-sdk-windows\tools
adb remount
adb shell rm /system/media/bootscreen/*.*
adb shell rm /system/media/bootanimation.zip
adb shell rm /data/local/bootanimation.zip
Preview.bat
Code:
:: connect your phone to your PC and select Charge Only or HTC Sync
:: This batch file will demo the bootscreen/bootanimation on your phone
@echo on
path=C:\Android-SDK-windows\tools
adb shell bootanimation
ADBWireless.bat
Code:
:: Sets the PATH for ADB and enables ADB Wireless. Launch the APK on the phone first.
@echo off
path=c:\android-sdk-windows\tools
adb connect 192.168.1.5:5555
BootanimationRemovePushPreview.bat
Code:
:: connect your phone to your PC and select Charge Only or HTC Sync or install "ADB Wireless".
@echo on
:: Sets the PATH for ADB.
path=C:\android-sdk-windows\tools
:: Enables "adbWireless". Launch the app on your phone first.
adb connect 192.168.1.5:5555
:: Remove ANY bootscreen or bootanimation on the device.
:: ***make sure you backup any that you want to keep***
adb remount
adb shell rm /system/media/bootscreen/*.*
adb shell rm /system/media/bootanimation.zip
adb shell rm /data/local/bootanimation.zip
:: Install the bootanimation on your phone and preview it.
adb push bootanimation.zip /data/local/
adb shell bootanimation
BootscreenRemovePushPreview.bat
Code:
:: connect your phone to your PC and select Charge Only or HTC Sync or install "ADB Wireless".
@echo on
:: Sets the PATH for ADB.
path=C:\android-sdk-windows\tools
:: Enables "adbWireless". Launch the app on your phone first.
adb connect 192.168.1.5:5555
:: Remove ANY bootscreen or bootanimation on the device.
:: ***make sure you backup any that you want to keep***
adb remount
adb shell rm /system/media/bootscreen/*.*
adb shell rm /system/media/bootanimation.zip
adb shell rm /data/local/bootanimation.zip
:: Copies the 5 bootscreen files to your phone and previews the bootscreen.
adb push .DS_Store /system/media/bootscreen
adb push boot1.gif /system/media/bootscreen
adb push boot2.gif /system/media/bootscreen
adb push droid.mp3 /system/media/bootscreen
adb push boot_animation.xml /system/media/bootscreen
adb shell bootanimation

Droid X Bootanimation
Resized to 320x480
Original
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original Inverted
Retro
Retro Inverted
OldPhoto
OldPhoto Inverted

Andy Colors
Andy Colors
bootanimation & bootscreen

Bootscreen/Bootanimation for xtrROM & xtrSENSE
This is an animation I made for the xtrROM & xtrSENSE roms
I made 2 versions of this one.
A BootAnimation and a BootScreen (with sound)
As always, the actual animation is sized for the Eris and much better quality and frame rate.

whoa.. these are nice ima try some

Andy Does
Andy Does
BootAnimation & BootScreen with the "Oh Yeah" sound from Ferris Bueller's Day Off

Sylock animations
Sylock bootanimations
The speed and graphics quality of the animated GIF's is very low compared to the animation on your phone.
They are much faster and prettier.
Sylock Red
Sylock Blue
I may add the DROID intro and sound to these.

Droid Eye
I saw this commercial for the Droid X and decided to rip it to a bootanimation.
Sized for our Droid Eris @ 480x320.
View this one in landscape.
Main ______________________________Loop

3D Plasma
*** 3D Plasma ***
Yep... break out your red and blue 3D glasses for this round
(again, the frame rate and quality are much better than these GIF's)
Blue on Red
Main_______________________Loop
Red on Blue
Main_______________________Loop

Plasma RGB
Plasma RGB
with or without sound

Wait Circle animation
Wait Circle animation
Very simple and small.
The default 'desc.txt' file is:
Code:
320 480 12
p 1 0 main
p 0 0 loop
These look great at half size also (like this):
Code:
160 240 12
p 1 0 main
p 0 0 loop
The frame rate looks best at 8, 12, or 16.
*** I also ported this to a BOOTSCREEN (all 3 versions are in one zip file) ***

New Animation
I came across this animation but it was for the Droid. Can you get it to work for the eris? also, can you format it to run vertically so that it takes up the whole screen? the file is included. thanks for the time.

Unstable Core
DroidEris1981 said:
I came across this animation but it was for the Droid. Can you get it to work for the eris? also, can you format it to run vertically so that it takes up the whole screen? the file is included. thanks for the time.
Click to expand...
Click to collapse
Here ya go!
Resized to 320x480
turned to landscape view
added "DROID" sound
(frame rate and image quality are much better)

Andy Colors V2
Andy Colors V2
bootanimation & bootscreen w/sound

how about this one?
http://www.youtube.com/watch?v=ZBuhqzseFN4&feature=related

Funnyface19 said:
how about this one?
http://www.youtube.com/watch?v=ZBuhqzseFN4&feature=related
Click to expand...
Click to collapse
LOVE IT!
I will convert this one later tonight or tomorrow morning for sure. Check back then.

Noob Q alert
Do we just flash in recovery?

TheDoctor1177 said:
Do we just flash in recovery?
Click to expand...
Click to collapse
no. all of mine are meant to be pushed VIA adb. Check the "helpful links" the first post in this thread for more education about bootanimations and bootscreens.

Thanks man! These boot screens are awesome!!

REALLY close to being done with the "LOADING SCREEN" bootanimation.
I have to take a break to pickup my daughter from school =)
Be back in a bit and I will upload the finished product.
Check back in a couple hours.

[GUIDE][MOD]Enable SMS/MMS Delivery/Read Reports[GUIDE][MOD]

For those of you who want delivery/read reports in SMS/MMS here is a simple CSC edit to enable them.
NOTE: If you are running KoolKit Roms you must edit /system/csc/koolkit.xml
connect your device to your PC, make sure you have adb tools installed and usb drivers installed
adb pull /system/csc/feature.xml
Make the following changes to your /system/csc/feature.xml
Search for the following lines:
Code:
<CscFeature_Message_DisableMenuRequestMmsReadReport>[COLOR="Red"]true[/COLOR]</CscFeature_Message_DisableMenuRequestMmsReadReport>
<CscFeature_Message_DisableMenuSmsDeliveryReports>[COLOR="Red"]true[/COLOR]</CscFeature_Message_DisableMenuSmsDeliveryReports>
<CscFeature_Message_DisableMenuRequestMmsDeliveryReport>[COLOR="Red"]true[/COLOR]</CscFeature_Message_DisableMenuRequestMmsDeliveryReport>
<CscFeature_Message_EnableMenuSendMmsDeliveryReport>[COLOR="Red"]false[/COLOR]</CscFeature_Message_EnableMenuSendMmsDeliveryReport>
Change the values highlighted in Red to the Values highlighted in Blue as seen below:
Code:
<CscFeature_Message_DisableMenuRequestMmsReadReport>[COLOR="Blue"]false[/COLOR]</CscFeature_Message_DisableMenuRequestMmsReadReport>
<CscFeature_Message_DisableMenuSmsDeliveryReports>[COLOR="Blue"]false[/COLOR]</CscFeature_Message_DisableMenuSmsDeliveryReports>
<CscFeature_Message_DisableMenuRequestMmsDeliveryReport>[COLOR="Blue"]false[/COLOR]</CscFeature_Message_DisableMenuRequestMmsDeliveryReport>
<CscFeature_Message_EnableMenuSendMmsDeliveryReport>[COLOR="Blue"]true[/COLOR]</CscFeature_Message_EnableMenuSendMmsDeliveryReport>
reboot to SafeStrap recovery and mount system read/write
adb push feature.xml /system/csc/feature.xml
adb shell
cd /system/csc
chmod 0644 feature.xml
Reboot, and enjoy delivery reports for SMS and read reports for MMS
DEVs, Feel free to include this in any rom or mod you build all i ask is proper mention in your thread

@cstayton
Another Great work Craig.[emoji41][emoji106]

any way to do this on stock lolipop (not rooted)?

puddi said:
any way to do this on stock lolipop (not rooted)?
Click to expand...
Click to collapse
Pull file edit. Then push file back set permission.

[THEMEING]with[GUIDES]and[MIRRORS] for TizenMod (updated 16/04/22)

ANYTHING YOU FLASH FROM HERE YOUR DOING SO AT YOUR OWN RISK
AND DOING SO VOIDS YOUR WARRANTY
I WILL TAKE NO RESPONSIBILITY FOR ANY ERRORS YOU MAY HAVE
SEE GUIDES POST BELOW FOR INFO ON FLASHING ANYTHING HERE
<<<< ALL DOWNLOADS AND ROM MIRRORS >>>>
<<<< NOW IN ONE PLACE,AT THE BOTTOM OF THIS POST >>>>
<<<< BROWSE INSIDE EACH LINK TO FIND WHAT YOU WANT >>>>
THEMEING
Icon Packs
icon packs (complete stock icons-for now)
TIZEN LOVE ICONS
Thanks to KASHORTIEXDA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GALAXY S5 ICONS
ROUNDED S5 ICONS
Thanks to KASHORTIEXDA
CYANOGENMOD ICONS
BLUE
THIN BLUE BLACK BG
BLUE TRANSPARENT BG
BLUE BLACK BG
THIN BLUE TRANSPARENT BG
]BLUE THIN BORDER
RED
THIN RED BLACK BG
RED BLACK BG
RED TRANSPARENT BG
THIN RED TRANSPARENT BG
RED EXPLOSION
RED THIN BORDER
GREYSCALE
IOS ICONS
thanks to ANDROID_2013
COLOUR
IOS ICONS
thanks to ANDROID_2013
SEE ATTACHMENTS BELOW FOR ICON PACKS
......................................................................................................................................
wallpapers
also available - individually or as wallpaper packs
CYAN converted wallpapers coming soon
more to come soon.......
tell me what you want and il make it happen.........
......................................................................................................................................
BOOT/SHUTDOWN ANIMATIONS
stock samsung
The Simpsons Intro
R2D2 boot
R2D2 shutdown
tizen mod android popping
android with tizen chest spinning
more coming soon
......................................................................................................................................
RINGTONES, NOTIFICATIONS,ALARMS, OTHER SOUNDS
GOOGLE EDITION SOUNDS
CM10.2 SOUNDS
IOS7 SOUNDS
HTC SENSE SOUNDS
......................................................................................................................................
FONTS
TIZEN SANS FONTS
22,385 .TTF FONTS
individually or zipped
......................................................................................................................................
DOWNLOADS AND MIRRORS
HERES THE LINK TO ALL AVAILABLE ROMS, SOUNDS, WALLPAPERS, FONTS BOOT AND SHUTDOWN ANIMATIONS AND ICON PACKS
be sure with roms you pick the correct rom, for the correct gear
downloads
gdrive
dropbox
IF YOU WANT YOUR WORK FEATURED HERE PM ME
.....................................................................................................................................​
WITH THANKS TO
GOOGLE
SAMSUNG
APPLE
HTC
THE CYANOGEN MOD TEAM
ANDROID_2013
SKIN1980
KASHORTIEXDA

GUIDES
FLASHING BOOT ANIMATIONS
first download your custom boot animation
place it on the root of your gears internal memory
then open sdb.exe , and run the following code
Code:
sdb root on
sdb shell mount -o remount rw /
sdb shell install-bootanimation.sh
sdb shell install-shutdownanimation.sh
sdb shell reboot watch
thats it done
FLASHING THEMES
To install these theme packs,open a command propmt naviagtated to sbd.exe, then in windows explorer copy all icons [unzipped, just the .png files] into the theme folder on your gear 2 internal disk, if you dont see it, the script "setup-folder.sh" below, will create it for you
run command
Code:
sdb root on
then
Code:
sdb shell
then if you havent already
Code:
setup-folder.sh
then,
Code:
install-theme.sh
then to complete type
Code:
reboot
CUSTOM SOUNDS
to install custom sounds follow these steps exactly
FIRST YOU MUST COPY CHOSEN SOUND FILES TO THE ROOT FOLDER WHERE YOUR COMMAND PROMPTING SDB.EXE
RINGTONES
Code:
sdb root on
Code:
sdb push (name_of_tone).ogg /opt/share/settings/Ringtones/
IF YOUR TONE NAME HAS SPACES USE "_" SEE BELOW
FOR EXAMPLE ;- sdb push Vega_tone.ogg /opt/share/settings/Ringtones
MUST USE CAPITALS WHERE THEY ARE
Code:
sdb shell reboot watch
DO NOT EXCEED 80MB
MAKE SURE IT LOOKS LIKE THIS
NOTIFICATIONS
FIRST YOU MUST COPY CHOSEN SOUND FILES TO THE ROOT FOLDER WHERE YOUR COMMAND PROMPTING SDB.EXE
Code:
sdb root on
Code:
sdb push "(name_of_tone).ogg" /opt/share/settings/Alerts/
IF YOUR TONE NAME HAS SPACES USE "_" SEE BELOW
FOR EXAMPLE ;- sdb push "Vega_tone.ogg" /opt/share/settings/Alerts/
MUST USE CAPITALS AND QUOTATION MARKS WHERE THEY ARE
Code:
sdb shell reboot watch
DO NOT EXCEED 80MB
MAKE SURE IT LOOKS LIKE THIS
thats it done
CUSTOM FONTS
FIRST YOU MUST COPY CHOSEN FONT FILES TO THE ROOT FOLDER WHERE YOUR COMMAND PROMPTING SDB.EXE
Code:
sdb root on
Code:
sdb push (name_of_font).ttf /usr/share/fonts/
IF YOUR FONT NAME HAS SPACES USE "_" SEE BELOW
FOR EXAMPLE ;- sdb push my_font.ttf /usr/share/fonts/
MUST USE CAPITALS WHERE THEY ARE
Code:
sdb shell reboot watch
MAKE SURE IT LOOKS LIKE THIS
then select chosen font on your gear 2 in display settings
CUSTOM ALARMS
To install custom alarms. First thing you must do is find your chosen sound and make it .ogg
Then make a copy of it in and convert to .wav format (do that fast and free here)
Then rename them both too
Ticktac.ogg
and
Ticktac.wav
Then you will need to turn on root and mount the system rw
With these commands
Code:
sdb shell root on
Code:
sdb shell "mount -o remount rw /"
Then either in tizen in sdk or sdb
remove the Ticktac.ogg and Ticktac.wav files from
opt/usr/share/settings/Alarms folder "with right click, remove"
Or
In sdb.exe using the pull commands
Code:
sdb pull /opt/share/settings/Alarms/Ticktac.ogg
Code:
sdb pull /opt/share/settings/Alarms/Ticktac.wav
Then reboot your watch with commands
Code:
sdb shell reboot watch
then copy Ticktac.ogg and Ticktac.wav to the gears internal disk folder "alarms"
then run sdb.exe again
Code:
sdb root on
Code:
sdb shell "mount -o remount rw /"
Code:
sdb shell install-alarms.sh
Code:
sdb shell reboot watch
disconnect your gear from your computer
and your done
MAKE SURE IT LOOKS LIKE THIS
CUSTOM BLUETOOTH DISCONNECT TONE
copy your desired tone, to the folder your sdb.exe is located
then rename it to "bt_disconnect.ogg"
then push it to "/usr/share/feedback/sound/operation/bt_disconnect.ogg"
like so
Code:
sdb push "C:\Users\Gav\Downloads\tizen\sdb\bt_disconnect.ogg" /usr/share/feedback/sound/operation/bt_disconnect.ogg
you will need to right click the file holding the shift key, and selecting copy as path for its location which i will highlight in bold below
sdb push "C:\Users\Gav\Downloads\tizen\sdb\bt_disconnect.ogg" /usr/share/feedback/sound/operation/bt_disconnect.ogg
(it should look like this)
then run code
Code:
sdb shell reboot watch
and its done
the same can be done for reconnect tone, by renaming the file "bt_connect.ogg"​

new wall papers added

Galaxy s5 icons added

more icon packs added

sq s5 icons fixed

Hi you
gav83collins said:
sq s5 icons fixed
Click to expand...
Click to collapse
Theme of you very nice, If I want to back theme my gear as before set up your theme, how can I do?, please show me?

theaminh81 said:
Theme of you very nice, If I want to back theme my gear as before set up your theme, how can I do?, please show me?
Click to expand...
Click to collapse
simply re flash the rom via odin

sdb link and other links updated

so I followed directions to the T and the theming wporked perfectly. As for the notification sounds not so much. Now when i go to settings, sounds, and click on notifications it just takes me back to the home screen.... any ideas sir @gav83collins

ragzz03 said:
so I followed directions to the T and the theming wporked perfectly. As for the notification sounds not so much. Now when i go to settings, sounds, and click on notifications it just takes me back to the home screen.... any ideas sir @gav83collins
Click to expand...
Click to collapse
oh, errrrr ??? thats a new one, i dont know, all i can suggest is re flashing the rom and trying again

gav83collins said:
oh, errrrr ??? thats a new one, i dont know, all i can suggest is re flashing the rom and trying again
Click to expand...
Click to collapse
OK... Is there a way to batch install the sounds. It took forever to push each one...

ragzz03 said:
OK... Is there a way to batch install the sounds. It took forever to push each one...
Click to expand...
Click to collapse
im afraid not, you will find the process quicker this time though, with experience comes speed
the fastest way, is to write the text in to a text editor like notepad, save it, then copy it all into sdb and press enter and it will do it all in 1 go, for example look at my next post

gav83collins said:
im afraid not, you will find the process quicker this time though, with experience comes speed
the fastest way, is to write the text in to a text editor like notepad, save it, then copy it all into sdb and press enter and it will do it all in 1 go, for example look at my next post
Click to expand...
Click to collapse
sdb.exe
sdb root on
sdb shell mount -o remount rw /
sdb push (name_of_tone).ogg /opt/share/settings/Ringtones/
sdb push "(name_of_tone).ogg" /opt/share/settings/Alerts/
sdb shell reboot watch
you could even do fonts and themes
sdb.exe
sdb root on
sdb shell mount -o remount rw /
sdb push (name_of_tone).ogg /opt/share/settings/Ringtones/
sdb push "(name_of_tone).ogg" /opt/share/settings/Alerts/
sdb push (name_of_font).ttf /usr/share/fonts/
sdb shell install-theme.sh
sdb shell reboot watch

gav83collins said:
im afraid not, you will find the process quicker this time though, with experience comes speed
Click to expand...
Click to collapse
You are wise kemosabe..

ragzz03 said:
You are wise kemosabe..
Click to expand...
Click to collapse
lol, dont forget to save the text file in notepad, and update it whenever you add things, then if you need to reflash the rom, its just a couple of clicks to do it all at once

gav83collins said:
lol, dont forget to save the text file in notepad, and update it whenever you add things, then if you need to reflash the rom, its just a couple of clicks to do it all at once
Click to expand...
Click to collapse
Sounds good to me.. I need to be faster as I do all my fiddling at work lol.. Thanks for everything

Custom bluetooth disconnect tone guide added

ragzz03 said:
Sounds good to me.. I need to be faster as I do all my fiddling at work lol.. Thanks for everything
Click to expand...
Click to collapse
http://forum.xda-developers.com/gea...io-guide-installing-mods-to-tizenmod-t2884142
there you go this will make it faster

Is there a way to go back to the stock icon theme after applying one?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Navibar 3 -5 -7 buttons mod - android 5.0 air3g, air 2

Like in description
Navibar 3 -5 -7 buttons mod - android 5.0
air3g, air 2​
If you have my rom Lolipop ( mirek190 ) just plug USB and choose proper option.
On other rom make sure you have root and USB debugging on.
3 buttons navigation bar​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5 buttons navigation bar​
7 buttons navigation bar​
air 3g
https://drive.google.com/open?id=0B8BF9-TGlz-FY2tWZUVZa05FU00
air 2
https://drive.google.com/open?id=0B8BF9-TGlz-FTEhvUTl2clE3Z3M
Ps - NOT RUN IT AS ADMINISTRATOR !

Hi mirek.
Can you add systemui.apk with a clock in its original position with 3 buttons?

Nope - center clock stays in the center like buttons

delete

Great job Mirek!

Hi, can you do this for the Air III? Do you need the stock SystemUI.apk?
EDIT:
I found this post www[dot]tsochen[dot]com/blog/post/15 and nearly the same intructions works for Air III M5C5. But the status_bar_*xml fix as not needed. This is the diff of navigation_bar.xml for 3 buttons
gist[dot]github[dot]com/kazuoteramoto/c0730bb27d0fb8dc6332

The system cannot find the path specified
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?

Wow, thanks, teramoto--this is fantastic! I just modded the SystemUI.apk on my device based on the tsochen link you provided, and your diff. I didn't want the screenshot and volume +/- buttons, but I did want to keep the menu button. So I just modded as indicated, and left the @id/menu entries untouched. The result is a nicely centered, four button variant.
EDIT: Somebody requested that I post my modded SystemUI.apk for a 4-button nav bar for the Air 3/III 32GB (M5C5). At the link below, I have done this, but also included 3- and 5-button versions, as well as the original 7-button SystemUI.apk version from the M5C5 v1.04 stock rom. The various SystemUI.apk files are obviously named by an explicit filename extension as you'll see when you download the archive. Also, let me reiterate--these are specifically for an Air 3/III 32GB (M5C5) tablet. Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing. Finally, and most importantly, note that credit for this goes to teramoto and the tsochen blog posting he pointed out above, which I just followed to do this, and also to mirek190 for starting this thread, and for helping out so many X98 Air users. Here's the link:
https://mega.nz/#!Hw0jRKBJ!0omuxVQXFHjzdbMV1bg6yvBhtMT570-gBhnkKxw2A4o

irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Facing the same problem...

irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Have you installed drivers ?

It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work

irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
I did the same as you for whole day....thanks anyway.

irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
Thanks for a clue - 1st post updated .

verbage said:
Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing.
Click to expand...
Click to collapse
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!

verbage said:
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
Click to expand...
Click to collapse
Hi. first let me thank you for your effort.
I tried your solution but I'm still without the buttons and notification bar.
Code:
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb shell
[email protected]_m5c5:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_m5c5:/ # cd /system/priv-app/SystemUI
cd /system/priv-app/SystemUI
[email protected]_m5c5:/system/priv-app/SystemUI # ls
ls
SystemUI.apk
x86
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI # chown root.root SystemUI.apk && chmod 644 SystemUI.apk
chown root.root SystemUI.apk && chmod 644 SystemUI.apk
<
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI #
Am I doing something wrong? Any other idea? Or can I put the original file back?
Thanks for any help with this
EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?

wepecko said:
I tried your solution but I'm still without the buttons and notification bar...Am I doing something wrong? Any other idea? Or can I put the original file back?...EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
Click to expand...
Click to collapse
Hmmm, from your ls -l command, it appears that the file ownership and permission were already set correctly, and so there was no need to give the chown/chmod commands again, but doing so didn't hurt, and only confirmed things.
My M5C5 is also on sikke1's rom--I started with mirek190's v6.1 slim version for the Air 2/II even though I have an Air 3/III, and it worked pretty good except for some hiccups. And so that is why I ended up on sikke1's debloated M5C5 rom, too.
Have you rebooted? You may be nervous to do so, understandably, but adb is enabled by default in the sikke1 rom so even if the graphical UI does not pop up, you can still do manual triage via adb.
---------- Post added at 07:19 PM ---------- Previous post was at 06:53 PM ----------
One thought for the future--if you are going to do this manually, you should stage it appropriately to hopefully avoid issues. For example, copy the original to a backup with the -p option to preserve file properties while still leaving the in-use original completely intact (i.e. "cp -p SystemUI.apk SystemUI.apk.ORIGINAL)". Then copy your modded apk file(s) into the same directory, and make sure file ownership/permissions are set as per above. Then do another cp -p to replace the in-use original with the modded apk.
Here's my listing for the directory to show you what I mean. I have the original apk plus the 3-, 4-, and 5-button modded apks all in the same directory with the correct ownership/permissions set. I can quickly change to any config, for example, the 3-button config, with a single cp -p command, i.e. "cp -p SystemUI.apk.MODDED-3-BUTTON SystemUI.apk". And there is no downtime/hiccup because one file is immediately replaced by the other, and the ownership/permissions are already correctly set.
Code:
[email protected]_m5c5:/system/priv-app/SystemUI # ls -la
ls -la
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-03 16:43 SystemUI.apk.MODDED-3-BUTTON
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk.MODDED-4-BUTTON
-rw-r--r-- root root 3572764 2016-01-03 16:43 SystemUI.apk.MODDED-5-BUTTON
-rw-r--r-- root root 3604448 2015-12-31 00:21 SystemUI.apk.ORIGINAL
drwxr-xr-x root root 2015-08-26 23:06 x86
[email protected]_m5c5:/system/priv-app/SystemUI #
Again, since you have confirmed everything, I would suggest rebooting if you have not done that. As I said, even if the graphical UI does not come up, you can still get into adb for repairs. At the very worst, you might have to reflash the rom.
I'm not sure why you have had hiccups, but these modded apks are directly from the stock SystemUI.apk of a v1.04 M5C5 rom. I have the modded navigation_bar.xml files, and I can send those or just diffs vs. the original so you can see the few lines that I changed. But you'll see they are just like described by teramoto and the tsochen blog he pointed out.

Thanks verbage. I understand your backup procedure and admit it was a mistake to rewrite the file directly.
However im still trying to find solution to this. I did restart ofcourse, several times, but it didnt help at all. It was late yesterday so i didn't have much time to try different scenarios. Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck.
One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?
Sent from my XT890 using Tapatalk

wepecko said:
Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck... One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Hmmm, sorry to hear you are still having a problem. The 3-, 4-, and 5-button versions all work perfectly on my Air 3/III using sikke1's debloated M5C5 rom, and since you have the same device, any of the versions should also work for you.
Certainly, the 7-button stock original should work, too, and that is also included in the archive I posted.
Whether there may be a conflict with the xposed framework you have installed, I don't know as I do not have xposed installed on my Air 3/III.
Anyway, good luck with fix, and we'll wait to hear more.

I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:

wepecko said:
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
Click to expand...
Click to collapse
Great, glad to hear you have it working!