Develop Bugs

Help!! Need Red Market Theme

Can anyone color the green parts of this icon red for me?

10 characters

Which icon do I need to replace if I want to use one of these, and where is it located? Thanks much.

Much Thanks
jonnybueno said:
10 characters
Click to expand...
Click to collapse
Thanks a bunch Johnny. Im way past due in sending some baby formula your way!!!

Icon Replacement
nyonya said:
Which icon do I need to replace if I want to use one of these, and where is it located? Thanks much.
Click to expand...
Click to collapse
Its in System/App/vending.apk
ic_launcher_androidmarket.png
ic_market_bag_normal.png
Remember you will need to push these back thru adb shell after your done.
PS. The files need to be renamed also to the ones listed above.

craigmack said:
Its in System/App/vending.apk
ic_launcher_androidmarket.png
ic_market_bag_normal.png
Remember you will need to push these back thru adb shell after your done.
PS. The files need to be renamed also to the ones listed above.
Click to expand...
Click to collapse
I tried replacing the first file (I can't even figure out where ic_market_bag_normal appears, so I decided to leave it alone for now) and pushing back the apk, no go, my market icon is the same as before. Just to be sure, I replaced the icon in both the drawable-hdpi and drawable-mdpi folders. What am I doing wrong?
Thanks.

Instructions
nyonya said:
I tried replacing the first file (I can't even figure out where ic_market_bag_normal appears, so I decided to leave it alone for now) and pushing back the apk, no go, my market icon is the same as before. Just to be sure, I replaced the icon in both the drawable-hdpi and drawable-mdpi folders. What am I doing wrong?
Thanks.
Click to expand...
Click to collapse
This is what I did.
1. adb pull /system/app/Vending.apk
2. Used the same icon for both files.
3. Named one ic_launcher_androidmarket.png and the other ic_market_bag_normal.png
4. I copied these two files to the following spots:
C:\sdk\tools\Vending.apk\ (This is the location as soon as you open up the Vending.apk file)
C:\sdk\tools\Vending.apk\res\drawable-hdpi\
5. Placed the the new Vending.apk file on my sd card
6. Reboot into recovery
7. Mount System and SDCARD
8. adb shell
9. su
10. /system/bin/cat /sdcard/Vending.apk > /system/app/Vending.apk
11. /system/bin/chmod 4777 /system/app/Vending.apk
12. exit
13. adb reboot
Make sure the "V" in Vending is capatilized. I had this problem at first.

craigmack said:
This is what I did.
1. adb pull /system/app/Vending.apk
2. Used the same icon for both files.
3. Named one ic_launcher_androidmarket.png and the other ic_market_bag_normal.png
4. I copied these two files to the following spots:
C:\sdk\tools\Vending.apk\ (This is the location as soon as you open up the Vending.apk file)
C:\sdk\tools\Vending.apk\res\drawable-hdpi\
5. Placed the the new Vending.apk file on my sd card
6. Reboot into recovery
7. Mount System and SDCARD
8. adb shell
9. su
10. /system/bin/cat /sdcard/Vending.apk > /system/app/Vending.apk
11. /system/bin/chmod 4777 /system/app/Vending.apk
12. exit
13. adb reboot
Make sure the "V" in Vending is capatilized. I had this problem at first.
Click to expand...
Click to collapse
Thanks for the instructions. I did exactly that, but my icon still has not changed. Is there temporary files I need to delete somewhere, or something like that?
Thanks.

im not sure yet if this has changed with 2.2 , but with 2.1 you cannot theme the market app...and make it stick. There is an update that market automatically installs, this can be found in /data/apps/ but ive tried theming that aswell to find it only FCs... Even after resigning! So hope that 2.2 doesnt have an updated version pushing the system version aside.

[Q] Access system folder on PC?

What do you guys use to access the system folder on your PC?
Basically, I want to have a play with a few of the files etc, but how do I get them (eg. Rosie.apk) onto the PC?
Is there software to do this, or do I have to use command line?
Many Thanks

You can pull the files from the phone by using the "adb pull [FILE]" command from the command line.
You'll have to have HTC Sync drivers and ADB on your system before that.

Is this the only way/easiest way? I'm asumming to send back I would use "adb push"?

Ease is a relative term so I cant judge on that basis.. Personally I find using the command line rather easy and fun.
Another possible way would be to use an app like Root Explorer on the phone to copy the system files on to the sdcard and then access the card via PC. (More cumbersome I think)
And you're right.. "adb push [FILE] [PATH]" is the command to send the file back to the phone. Try typing just "adb" and hit enter to see a list of commands and their usages.

Stuck at the first hurdle....
I've got the ADB on C:\ root
I open command prompt, type cd c:\adb
This puts me into the abd directory OK.
I type adb, and it adb is not a recognised command???

You sure you've got adb.exe and the dlls in that same directory?
I've attached a zip for you. Extract it and double-click on StartHere.bat, you'll get a command window and you can start using adb right away.

Cheers, I must have had a missing .dll

download Samba app: http://forum.xda-developers.com/showpost.php?p=8239139&postcount=128
this gives you access to the sdcard only, so to get access to system follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?p=18722729#post18722729
it works a treat! and is very easy! just be careful what you play with, using adb pull and push is safer

I agree that command line is the best way, but if you really want a GUI, then QtADB is pretty good:
http://qtadb.wordpress.com/
http://forum.xda-developers.com/showthread.php?t=683223
It's really just a graphical front end to adb.exe, but makes it easy to push or pull files to or from the phone. The only thing I haven't spotted is how to adjust permissions on files on the phone.

preacher65 said:
I agree that command line is the best way, but if you really want a GUI, then QtADB is pretty good:
http://qtadb.wordpress.com/
http://forum.xda-developers.com/showthread.php?t=683223
It's really just a graphical front end to adb.exe, but makes it easy to push or pull files to or from the phone. The only thing I haven't spotted is how to adjust permissions on files on the phone.
Click to expand...
Click to collapse
I didn't know about that.. I'll try that too. (Although I still think I'll end up to command line usage again)
Btw, APK Manager is quite useful if you're planning to mod some apk files like framework-res etc.. I use to make minor image changes to my ROMs..

if4ct0r said:
I didn't know about that.. I'll try that too. (Although I still think I'll end up to command line usage again)
Btw, APK Manager is quite useful if you're planning to mod some apk files like framework-res etc.. I use to make minor image changes to my ROMs..
Click to expand...
Click to collapse
Yep, I use the command line for 95% of stuff too - but then I'm old school and like the level of control command line gives.
But QtADB is useful if you want to move lots of files about, and as a bonus it has good logcat functions. Plus the support in the thread is pretty good as well. The guy really cares about his app, so I like to let people know about it.
APK Manager is awesome as well, though lately I've been going hardcore and doing everything apktool related from the command line as well!

I need some help accesing the system folder
Hey guys I am pretty new to android, I had been dealing with WebOS devices, I recently gotten a irulu a20 (all winner device) android 4.2.2 and wanted to improve the gaming performance and followed this instructions http://forum.xda-developers.com/showthread.php?t=2329080 and now my tablet does not stop popping a message saying "unfortunately System UI has stopped" and does not let me do anything or select anything. One of my friends did a wipe data/hard reset on it and still giving me the same issue with the same message, and what is worst I don't see the root browser icon (I guess due to the hard reset) so I don't know if my tablet still rooted or it is bricked. Please help and thank you to those who reply

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]

[CWMR ZIP] ICS Keyboard backlight fix

First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE

Awesome!

does not work for me...

Worked perfect here, that fixes my only serious issue with the ICS rom.

I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.

does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing

The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.

Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.

Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was

Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium

Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!

Can anyone help me with this via step by step?

I could use a little help as well
Sent from my SGH-I927 using xda app-developers app

Yea, i could use some help too, after re-writing over the existing file didn't work

OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.

Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch

ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man

LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?

Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister

Hummm is their gonna b a flashable zip for this ?

How To Guide How to set up adb and fastboot on a Mac

Hi guys,
This is a tutorial meant to show you how to set up adb and fastboot to be used on a Mac running Catalina or newer OS.
Requirements:
platform-tools from Google.
a Mac (duh) running Catalina or newer OS. Mac not included with this tutorial.
Sublime Text.
There are other ways to achieve the same thing (using Terminal commands), I just like this better cause it's more user friendly, and this way you also get a pretty awesome text editor which you can use in the future. If you already know how to do it from Terminal, you can skip this step and the coresponding steps below.
How to:
Press "Shift + CMD + ." to toggle on/off hidden files. To hide them again, just press the same key combination again.
The "." symbol is important. It's not punctuation. Not that punctuation isn't important, but this is part of the key combination to show hidden files, not part of grammar. So make sure you do it right.
Create a folder called /Developer in your Home folder (under ~/Users/[your username]).
This is optional. It's just to keep things more organised. You can skip it if you either already have a in mind, or you want to place this folder somewhere else.
Download and install Sublime Text.
Go to File > New File and paste this inside:
if [ -d "$HOME/Developer/platform-tools" ]; then
export PATH="$HOME/Developer/platform-tools:$PATH"
fi
NOTE: this assumes that your Developer folder is under your Home folder, and the platform-tools folder that you downloaded from Google is inside it. If that's not the case, adjust accordingly.
save the file and name it ".zshrc".
Yes, the "." is part of the deal, so make sure you include it, too. Also, don't add any extensions to the filename. So NO .rtf, .txt, .omg etc. If you've done it right, the file's icon should show as semi-transparent. That means the file is generally hidden, but it's shown to you now so you can work with it.
move the .zshrc file to your Home folder (~/User/[your username])
unzip and extract the platform-tools folder (you should have adb and fastboot inside it, among other things)
copy-paste it under ~/Users/[your username]/Developer/ (in the end, it should look like this: ~/Users/[your username]/Developer/platform-tools)
done
Now, connect your phone via USB and test adb and fastboot with the following commands:
adb devices
For this command to work, USB Debugging under Developer Options needs to be enabled.
If everything ok, it should show your device's serial number.
After that, you can do:
adb reboot bootloader to go into fastboto mode, and then:
fastboot devices
to check if your device is properly recognised.
If all goes well, congratulations, you've successfully managed to brick your device. Oups, sorry, I meant set up adb and fastboot on your Mac! Now you can start bricking your device.
I'm joking, of course! That would be bad. But on a more serious note, you should now be able to start developing, flashing custom ROMs, fixing your device if it's already broken etc.
N-joy!