Related
UPDATED 5/16/2010
I followed these steps. Originaly for the milestone android phone but it worked.
It should work with any of the 2.1 roms based of the sprint leak. I have tested and confirmed it working on.
DC v2.05
DC v2.07
DC v2.07.2
Fresh Toast v1 - v1.1 - v2.0b
EDIT:This does not currently work with the newest 2.1.1(or what you call it) rom. Might be changed eventually, ill keep it updated.
Before enabling
*Change home laucher
*Delete htc lock screen
see below if you dont no how
Jit does not work with htc sense, it will give you many problems. I suggest using Helix launcher from market (free and its what i use daily with no issues). You can also try GDE and nexus launcher, or really anything other then sense.
To change launchers go to setting>applications>manage apps>htc sense And clear defaults. Press home and choose a different launcher.
OR download "Home Switcher" from market.. Its a free app that lets you change between launchers.
JIT does not like any HTC apps.. So delete your HtcLockScreen by doing this.
Code:
adb remount
adb shell rm /system/app/HtcLockScreen.apk
Here is the htc lock screen if you want it back
View attachment HtcLockScreen.apk
JIT is in no way perfect on our htc hero's so MAKE A BACKUP before trying.
And you could very well run into TONS of problems, its just something to test out.
Though if used right, you wont have any problems. I use this daily.
THIS IS FOR JIT
Download: *View attachment vmlibs.zip*
Then follow these steps:
•Create 2 folders on your sdcard: “jit” & “dalbk”
•Extract the vmlibs.zip to the “jit” folder on your sdcard
•Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad or similiar program.
•Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Save the changes
•Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit.
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
Now while in recovery, wipe dalvik cache, not everything, just dalvik. It will help from being stuck in a boot loop. After that you can reboot your phone and it will take awhile since dalvik is being rebuilt.
TO DISABLE:
This should disable JIT and return phone back to defualt
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
Post For help if the disabling gives you any problems.. If it does you can always do back up of your rom that you should of made.
Original site http://sholes.id.au/how-to/
Jus10o said:
I followed these steps. Originaly for the milestone android phone but it worked.
It will work on htc sense but it force closes alot, you cant swipe so you have to press home and change screens that way.
I am using it on the helix launcher with no problems and its running very smooth so far.
Download:View attachment 305272
Then follow these steps:
•Create 2 folders on your sdcard: “jit” & “dalbk”
•Extract the vmlibs.zip to the “jit” folder on your sdcard
•Using ADB pull your build.prop
ADB pull /system/build.prop C:\build.prop
•Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
•Save it & push it back to your “jit” folder on the sdcard
ADB push C:\build.prop /sdcard/jit/build.prop
ADB shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
# cp /system/build.prop /sdcard/dalbk/
# cp /system/bin/dalvikvm /sdcard/dalbk/
# cp /system/lib/libdvm.so /sdcard/dalbk/
# cp /system/lib/libnativehelper.so /sdcard/dalbk/
# cd /sdcard/jit/bin
# cp -f dalvikvm /system/bin/
# busybox chmod 755 /system/bin/dalvikvm
# cd /sdcard/jit
# cp -f libdvm.so /system/lib/
# cp -f libnativehelper.so /system/lib/
# cat build.prop >/system/build.prop
# chmod 644 /system/lib/libdvm.so
# chmod 644 /system/lib/libnativehelper.so
# chmod 666 /system/build.prop
# sync
# mount -o remount,ro /dev/mtd/mtdblock6 /system
# reboot
Original site http://sholes.id.au/how-to/
Click to expand...
Click to collapse
whats your linpack benchmark?
and how well does launcher work?
mrchu001 said:
whats your linpack benchmark?
and how well does launcher work?
Click to expand...
Click to collapse
Before jit: 2.4 mflops
Jit enabled: 3.45 mflops
And its running very smooth, havent had a single problem yet, but I it hasnt been on for that long. I post it so others can test it out.
ill post a screen shot in a sec.. posted them in main post
hmmm i might just have to try this..
let me know if you run into any problems.
mrchu001 said:
hmmm i might just have to try this..
let me know if you run into any problems.
Click to expand...
Click to collapse
The only one iv had so far is when unlocking the phone. It will do a small reboot of the phone and then it loads and goes back to working fine. When sense was my home screen it did it way more often. With the helix launcher it rarely does it.
Edit: Using the menu button to unlock the phone instead of sliding seems to not give me the issue. Or it hasnt so far that is.
hmmm.. alright.
how are apps running?
have you tried neocore?
mrchu001 said:
hmmm.. alright.
how are apps running?
have you tried neocore?
Click to expand...
Click to collapse
I just loaded almost every app i have with no problems and test a view like yellow pages(with google nav) and many others. They are all very snappy so far.
And i did benchmark pi, i posted in main post the scores.
Ill try to find neocore, i wasnt familiar with it.
If its not a problem, could you run the few benchmarks I have so I can compare them to the stock. Other then my stock scores.
hey sorry for taking so long..idk if your still on but here are my benchmarks
i'm running fresh 2.0d with darkstar theme, auto killer on strict.
Test 1: 1.858 MFLOPS
Test 2: 2.015 MFLOPS
Test 3: 1.999 MFLOPS
Test 4: 2.281 MFLOPS
Test 5: 2.07 MFLOPS
mrchu001 said:
hey sorry for taking so long..idk if your still on but here are my benchmarks
i'm running fresh 2.0d with darkstar theme, auto killer on strict.
Test 1: 1.858 MFLOPS
Test 2: 2.015 MFLOPS
Test 3: 1.999 MFLOPS
Test 4: 2.281 MFLOPS
Test 5: 2.07 MFLOPS
Click to expand...
Click to collapse
Im still on..
I got auto killer about 30mins ago and this is what im getting now..
Linpack:
1: 3.49 mflops
2: 3.45 mflops
3: 3.529 mflops
4: 3.571 mflops
5: 3.595 mflops
benchmark pi:
1. 9339
2. 9251
3. 9156
4. 9320
Jus10o said:
Im still on..
I got auto killer about 30mins ago and this is what im getting now..
Linpack:
1: 3.49 mflops
2: 3.45 mflops
3: 3.529 mflops
4: 3.571 mflops
5: 3.595 mflops
benchmark pi:
1. 9339
2. 9251
3. 9156
4. 9320
Click to expand...
Click to collapse
my neocore scores were
Test 1: 22.7 FPS
Test 2: 23.0 FPS
Test 3: 23.2 FPS
Average: 22.97
mrchu001 said:
my neocore scores were
Test 1: 22.7 FPS
Test 2: 23.0 FPS
Test 3: 23.2 FPS
Average: 22.97
Click to expand...
Click to collapse
Ok awesome..
My neoscores were anywhere from 23 to 27.5 averaged around 26 fps.
I was comparing it to flips benchmark test, but your scores make alot more sense.
anything else you want me to test before i attempt JIT?
Oh and I can also add, I figured out how to get it to run error free, with the way I personaly use my phone. Could change for others.
The lock screen is htc using Lock 2.0 I avoid htc and it runs perfectly fine.
Im going to run this rom with jit as my everyday rom and see what error i come across.
so if i use an app like lockbot pro instead of the htc lockscreen...it's pretty much error free?
mrchu001 said:
anything else you want me to test before i attempt JIT?
Click to expand...
Click to collapse
No, everything else i still have records of.
Try it, i want to see if it works as well for you.
I would try using helix (downloadable from market) or nexus launcher if you already have it. (idk if anyone got it working in v2.0)
And use the menu key to unlock phone.
The bootscreen might take awhile, but as long as it doenst freeze, its still working.
mrchu001 said:
so if i use an app like lockbot pro instead of the htc lockscreen...it's pretty much error free?
Click to expand...
Click to collapse
Yea, its the htclockscreen it doenst like. I have Lock 2.0 pro working good with it.
It will load your htc sense, but it might reboot it a couple times, from there press menu to unlock the phone then menu again to clear the default of htc sense.
well i'm running launcher as my default homescreen so i'll be okay right?
mrchu001 said:
well i'm running launcher as my default homescreen so i'll be okay right?
Click to expand...
Click to collapse
Yeah as long as its not the droid rosie launcher. All it is, is the htc sense with a different look.
The one i meant was the nexus launcher. Was common in dc 1.0
If your launcher doesnt have any htc things on it, like the clock, power control, so on then you are fine.
The helix launcher is a very clean simple home launcher and you can change the amount of screens to 7 and so on.
hey when i go to pull the build prop from /system it says its not there..
mrchu001 said:
hey when i go to pull the build prop from /system it says its not there..
Click to expand...
Click to collapse
Uh it should be, try typing
adb remount
adb pull /system/build.prop build.prop
it will put it into your c:/android/tools folder (Or your android folder path)
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Wreximus said:
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
i wish i knew how to do this, but if i can't figure it out, i'm sure others will soon.
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
abliss said:
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
Click to expand...
Click to collapse
Oh really? Cool. So far all I've used is one-click root for the Samsung Epic.... is this similar? I'll check it out, thanks!
Has anyone tried using SuperOneClick yet?? I will probably try in a bit and post back with my results..
Ok... well I didn't try SuperOneClick, but I did root it via the rageagainstthecage exploit...
Want to help me do the exploit on my SK4G to root it man ?
Give me instructions ?!
I got it working on mine too. The basic steps were
1) enable debug USB mode on your phone
2) install Samsung drivers for the phone - right now Samsung's site seems to not have a choice for the Sidekick 4G's model (SGH-T839), but I grabbed the drivers for the Vibrant (at www .samsung.com/us/support/downloads/SGH-T959ZKDTMB) and they worked.
3) get adb shell working on your PC (Google it)
4) download the rageagainstthecage-arm5.bin and Superuser packages from the links in this page: wiki.cyanogenmod.com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide (be sure to unzip the files into the directory where your adb.exe program is unless you've put it in your path)
5) reboot your phone and plug it in
6) adb push rageagainstthecage-arm5.bin /data/local/tmp
7) adb shell
8) cd /data/local/tmp
9) chmod 755 rageagainstthecage-arm5.bin
10) ./rageagainstthecage-arm5.bin
11) wait until you get booted back out to your DOS command prompt
12) adb kill-server
13) adb start-server
14) adb shell
15) you should now be at a # prompt. The first few times I tried, I wasn't - I was at $. Doing this from a fresh boot seemed to be the trick. Reboot your phone and try again if you're getting a $.
16) mount -o remount,rw /dev/block/stl9 /system
17) exit
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/stl9 /system
22) exit
23) reboot the phone then run an app that requests root, such as Root Explorer, to verify
(p.s. sorry for having to mangle the URL's above, XDA won't let me include links since I haven't posted 8 times yet)
josby said:
16) mount -o remount,rw /dev/block/st19 /system
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/st19 /system
Click to expand...
Click to collapse
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Also, after step 20, I had to run the following commands for the superuser application to grant root privledges to applications..
adb shell echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
adb shell echo "root::0:" > /etc/group
Awesome to see it being rooted so fast.
I'm really interesting in getting this phone but I'm not in the US. Does anyone know if the phone will work outside US?
brenix said:
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Click to expand...
Click to collapse
Dang, good catch, thanks. That's what I get for not copying and pasting from my terminal window...stupid, since I was just chastising two people at work for making the same mistake yesterday. I've edited the original post to prevent problems for people who might start before reading the entire thread.
Interesting about having to create a passwd and group file...I've only run a few root apps so far, but they've worked without me doing this. I wonder if it's app-specific.
Now to start removing some of the damn bloatware this thing comes with!
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
i'm so glad this thing got rooted. i used to be a scene kid with a kick. i dont have this phone, i doubt i'm going to get this phone considering the sensation is droppin soon.... but for nostalgia purposes, i'm glad it got rooted. now you can really hack it!!!
not like the old ones!!
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
fawkReviewz said:
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
Click to expand...
Click to collapse
Double-check your step 18...that's the step that copies the su file from your computer onto the phone. I forget the exact output format, but it shows you a Kb/second number of how fast the file transfer went when it finishes successfully.
droctii said:
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
Click to expand...
Click to collapse
I'm not brave enough to try putting the ClockworkMod for one of the Samsung devices on the list onto mine, for fear of bricking it. Don't know enough about that works as far as hardware differences go.
I have removed the APK's listed below from /system/app with no apparent ill-effects. Not that YOU should remove them necessarily - just that they're things I don't have a need for:
AccountAndSync.apk
AmazonMp3.apk
AppPack.apk
DriveSmart.apk
DriveSmartHelper.apk
install_flash_player.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Memo.apk
MiniDiary.apk
MobileBackup.apk
MyFiles.apk
PhoneSetupWizard.apk
Twitter-2.0.1-121.apk
vvm-signed.apk
Though there must be something I don't fully understand, because even after a reboot, Amazon MP3 and AppPack are still on my phone, and they still work.
FYI, don't remove Settings.apk - I got stuck in a loop where the launcher kept crashing then reloading itself (thank goodness I was able to put it back in place with adb).
Can anyone tell me if Setcpu works for them?
Ace42 said:
Can anyone tell me if Setcpu works for them?
Click to expand...
Click to collapse
Appears to work fine.. no crashes although the Max Hz is 1000. U can still raise the Min Hz.
Sent from my Nexus S using XDA App
Can someone post a full:
ls of / and /dev/block and /efs
Thanks
Will this phone get a proper sub-forum on xda?
Hey guys,
Changing my android font is one of the first things I do everytime I flash a new ROM. The plain arial font always seems so bland. Me being a huge linux fan and Ubuntu user I love the custom Ubuntu font that the distribution uses. Alot of effort and research went into the making of these fonts and they look beautiful on android. So I thought i'd write a small tutorial on how I do it. This can work for any font, but I have used it only for the Ubuntu font. Beware if you try using very funky fonts, you can get UI defects here and there. Also please be sure you understand whats going on here before trying because if they dont replace the old fonts properly youll be stuck at the boot animation screen and will have to reflash your ROM. So here goes.
Step 1: Download your required font
Your font needs to be in the .ttf format for it to work. Since Im using the ubuntu font I will give you the link for where to download that. You only need 2 versions of the font for use on android. Regular and Bold. Here is where you can download the ubuntu font set: http://font.ubuntu.com/download/ubuntu-font-family-0.71.2.zip
Step 2: Place font in your ADB folder
In the new version of the Android SDK ADB has been moved to platform tools. If you are using the older version then its probably in the tools folder. Place your two desired fonts in the ADB folder. The next step is renaming your fonts. Rename your fonts in the following way. You have to rename them exactly the same for it to work. Basically what you are doing is pushing your custom font over the old one and fooling android into using your font. Thats why you need to rename them exactly like they are in the default. E.g for the MIUI ROM, you need to use root explorer and see what the fonts are named because its different from the froyo builds. If you're using the the XT720 froyo builds you can rename them as follows.
Regular font: DroidSans.ttf
Bold Font: DroidSans-Bold.ttf
Step 3: Setting up and mounting your /system/fonts/ Folder
Okay now you basically need to mount your system folder and for that you have to use the ADB tool. Run the following 3 commands to mount your folder.
Code:
adb shell
su
mount
After you enter mount you will get output which will look something like this:
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
You need to see which dev/block your system folder is in. For all the froyo builds on the XT720 its usually dev/block/mtdblock7. See according to your own ROM.
Next we need to give the folder read write permissions.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system
Code:
chmod 777 /system/fonts
After this we can exit the adb shell by issuing the command twice.
Code:
exit
exit
Step 4: ADB pushing your desired font
All you have to do is change directory to your ADB directory. In my case its platform-tools. Do according to your own folder names.
Code:
cd ~/android/platform-tools
Then push both fonts with the following commands.
Code:
adb push DroidSans.ttf /system/fonts/DroidSans.ttf
Code:
adb push DroidSans-Bold.ttf /system/fonts/DroidSans-Bold.ttf
Reboot your phone and enjoy your new font.
Code:
adb shell
su
reboot
Attached are some images of how my Ubuntu font looks compared to the old one. Not much of a difference but I still like it. If you have a favourite font give it a try.
I recently upgraded my desktop to 11.04 and I've become smitten with this font. I haven't had time to put it on my phone, but I like its look in your screenshot. I will install it when things settle down again. Anyway, I just wanted to say thanks!
You're welcome
If you want to change the font for the lock screen clock, here is how (provided you aren't using widgetlocker already). No adb needed, just root explorer or the like.
1 Find a font (.ttf) you like and copy it to you sdcard.
2 Go into system/fonts and copy Clockopia.ttf. Don't forget to toggle r/w before. Put Clockopia.ttf into a safe place on your sdcard in case you ever want to go back.
3 Take your new font and copy it into system/font.
4 Rename you new font Clockopia.ttf exactly, ***this is case sensitive***.
5 Long click on the new Clockopia.ttf and go into permissions. Make sure the entire first column is checked on the top-center user is checked, no others.
Edit: they are user, group, other all read checked (first column), user write checked (second column). Only these 4 should be checked.
***If this isn't done you WILL bootloop. Trust me, I know this for sure bc I forgot once. Make sure you have system nandroid on case any problems***
6 Reboot and behold your new lockscreen clock.
Thanks for the tip, Woodrube. I wonder if you can do the root explorer thing for the main fonts too.
I use fontchanger.
sohrab.naushad said:
Thanks for the tip, Woodrube. I wonder if you can do the root explorer thing for the main fonts too.
Click to expand...
Click to collapse
Don't see why not. You are essentially fooling the system to think its font is one thing but really it is a whole other, just renamed.
One thing I do know it all are case sensitive and have rom be exactly named as the ones you are replacing. And the permissions gave to be correct as my above says.
Thanks! I love the Ubuntu-font! I'm a Ubuntu-user for a long time now!
But 1 question: can you change it back to the Droid-font somehow? Gonna try this anyway
Vistaus said:
Thanks! I love the Ubuntu-font! I'm a Ubuntu-user for a long time now!
But 1 question: can you change it back to the Droid-font somehow? Gonna try this anyway
Click to expand...
Click to collapse
If you use my way, just save the original ttfs to somewhere on your sdcard. Then if you don't like yours anymore, just replace yours with the originals.
Good free font source
http://www.1001freefonts.com/
Vistaus said:
Thanks! I love the Ubuntu-font! I'm a Ubuntu-user for a long time now!
But 1 question: can you change it back to the Droid-font somehow? Gonna try this anyway
Click to expand...
Click to collapse
Glad you liked it. Yes, use root explorer to copy DroidSans.ttf and DroidSans-Bold.ttf from /system/fonts somewhere on your SD card. Then later you can adb push it the same way if you dont like the font you've chosen.
Also like woodrube said, maybe you can do the whole process with root explorer. I haven't tried it yet though but it sounds much more easier than my ADB method.
Good luck!
sohrab.naushad said:
Glad you liked it. Yes, use root explorer to copy DroidSans.ttf and DroidSans-Bold.ttf from /system/fonts somewhere on your SD card. Then later you can adb push it the same way if you dont like the font you've chosen.
Also like woodrube said, maybe you can do the whole process with root explorer. I haven't tried it yet though but it sounds much more easier than my ADB method.
Good luck!
Click to expand...
Click to collapse
Just an fyi, you can do it all my way. I changed my DroidSans.ttf and the bold one too and it worked like a charm. Beware that it changes font across the board, from settings to time/date on status bar to keyboard.
Also I made a folder on my sdcard labeled Original Fonts and copied all the originals from system/font in there in case I want to revert back.
If you want an app-based procedure like the description above, I recommend TypeFresh-you can get it on xda.
I used it and it worked flawlessly - backing up the old Droid Sans family and installing e.g. Comfortaa, a font I often used.
- motorola milestone xt 720 | miui xt final 2.2.1 -
eSu.Matix said:
I use fontchanger.
Click to expand...
Click to collapse
Really simpel, tnx!
Thanks for the tip!
I just use TypeFresh and it's totally hassle-free.
I have found Font Installer app to be a better solution. The good thing is it automatically lists 200+ fonts for you to choose from, so no need of searching for fonts. Just tap, install and reboot. The new font will be decorating your phone -
How to change android font using font installer.
All credit goes to Tilbert at UnleashedPrepaids.com for finding how to root the Mercury, and Salas from CricketUsers.com for posting this information.
I thought this should be posted on this site, as it is the main site I go to for everything Android. The Mercury is the newest Android from Cricket and is worth talking about since it has a 1.4GHz Snapdragon CPU, FFC, 8MP camera with LED flash, HD video recording, and a 4" FWVGA capacitive touch-screen. I also think that there should be a forum created for this phone.
MAKE SURE YOU READ ALL THE STEPS BEFORE STARTING!! Additional setups may be required!!
I AM NOT RESPONSIBLE FOR YOU MESSING UP YOUR PHONE BY FOLLOWING THESE INSTRUCTIONS!!!
If your not comfortable with the procedure then don't do it!!!
I'm sure it won't be long before someone smarter than me figures out a one-click method for root.
1. First download su, busybox and Superuser.apk
mediafire.com/?or723znkep9s3o3
2. Use ADB to push these 3 files to /data/local/tmp
3. In ADB shell:
$ chmod 6755 /data/local/tmp/su
$ chmod 755 /data/local/tmp/busybox
$ chmod 644 /data/local/tmp/Superuser.apk
4. Shut down phone with the power button/menu.
5. Holding the Vol+ AND Vol- AND Power together when the phone is off will put the phone into a mode that gives you a BRIGHT purple screen....
this is good! Nothing should be happening, just a static purple screen.
6. THIS NEXT STEP HAS TO BE DONE FROM A LINUX DISTRO!
Plug the phone into the computer through USB and you will notice that you can access all of the partitions of the phone with full R/W.
Browse to /data/local/tmp and move su and busybox to /system/bin/
Move Superuser.apk to /system/app/
7. Unplug the phone from USB.
8. Pull the battery out, put it back in, boot the phone normally and ENJOY YOUR NEWLY ROOTED MERCURY!!!
Some notes:
Superuser.apk will need to be updated (found on market).
From inside the Superuser app: update the su binary's.
Download the BusyBox installer from the market and update busybox to the latest version.
thanks, I've tried that (just that I did a "su" in ubuntu and then used mv command instead of nautilus) but then it didn't work and I found out that I had no /system/bin folder and the su file was moved as file /system/bin (file not directory). I don't think I removed the folders...
Has anyone else missing the /system/bin and /system/app folders? the phone works fine otherwise. I created the folders and redid the steps but it still doesn't work
I hate to direct you to another forum but since there is almost no Merc activity here I guess it's okay
http://www.cricketusers.com/showthread.php?t=29050
Sent from my M886 using Tapatalk 2
Don't you need to change the permissions also before you reboot? Since Linux is very secure about permissions and all. Just a thought... I am gonna try it and post back. I just scored this phone for some work that I did. I gave it to my son, but I always root my devices, etc.
How to root Nook HD+ (and Nook HD too, I guess).
(Thanks for some useful ideas to sparkym3: http://forum.xda-developers.com/member.php?u=4411543 )
(tested only on 2.0.0 version (as comes out of the box), also works on 2.0.2
Get one of the attached files: root_win.zip if you are on windows, or root_unix.tgz if you are on Linux or Mac.
unpack the file to some dir and run "makeroot" on Windows or "sh makeroot.sh" on Mac/Linux
After a couple of reboots you should be able to do
adb shell and issue a "su" command in the shell and get the root prompt (#).
Thanks to someone0 for his prior investigations here.
Known bugs:
Superuser.apk does not really install because package manager could not be contacted.
Oh, and I think you'll find this interesting too:
Hai.
Kind of a two-fer, eh?
I noticed that people see their Nook HDs restoring to factory settings after 8 unsuccessful reboots next time you boot after rooting, so possibly there's some extra check somewhere.
Very sneaky on the B&N side, I'd say.
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
roustabout said:
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
Click to expand...
Click to collapse
Do the new HD & HD+ still allow you boot from the external sd card ?
roustabout said:
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
Click to expand...
Click to collapse
if you put your books into /system/media, it will back them up to the cloud
Is it possible to push a new recovery with adb after rooting? The 8 failed boot repair is only possible with the stock recovery. But then again you may end up in an endless bootloop without it there to finish it's task. But maybe you can find and delete the trigger flag that starts the process.
leapinlar said:
Is it possible to push a new recovery with adb after rooting? The 8 failed boot repair is only possible with the stock recovery. But then again you may end up in an endless bootloop without it there to finish it's task. But maybe you can find and delete the trigger flag that starts the process.
Click to expand...
Click to collapse
stuff is best to be not mentioned. /sarcasm.....
recovery is signed, so it's not super easy to replace it with anything that would run.
The unsigned bootloader trick at the moment requires a boot from sdcard.
shouldn't step 8 & 9 be outside the code block?
verygreen:
I just want to thank you for your all your work on the Nook series. I've been using your "size-agnostic method ..." tools and process to run from the SD card on my Nook Color since you created the method, and now I'm excited to use your work on my new Nook HD+ (just received yesterday) !
just got mine and got an update notification. turned off wifi so it didnt complete.any word if it breaks root ir bootloader?
CWM is now possible too.
Something is interesting, eventhough mine originally got automatically updated to 2.0.2, but after the factory reset, it went back to 2.0.0. But for some weird reason I can't get root.
Maybe this will help, the build number is 2.0.0.1031.lithium01.ovation.rldp.s68403 with the manufactured date 10/22/2012
please compare mine to your.
I also rewrote your code into a batch file. You can double check it I guess.
Code:
@echo off
cls
@echo .
@echo wait for it
@echo .
adb devices
@echo .
@echo if you do not see you device listed above hit ctrl+c and exit the script
@echo then check adb on your PC and device then try again.
@echo .
@echo reroute /data/local/tmp
adb wait-for-devices shell rm -r /data/local/tmp
adb shell ln -s /data/ /data/local/tmp
@echo .
@echo Now rebooting
@echo .
adb reboot
@echo .
@echo waiting for reboot to finish and making directory /data/su
adb wait-for-devices shell mkdir /data/su
@echo uploading su
adb push su /data/su/
@echo uploading busybox
adb push busybox /data/su/
@echo uploading boot_complete_hoot
adb push boot_complete_hook.txt /data/boot_complete_hook.sh
adb shell chmod 755 /data/boot_complete_hook.sh /data/su/*
@echo .
@echo Now rebooting again
@echo .
adb reboot
@echo .
@echo waiting for reboot to finish and getting shell
adb wait-for-devices shell
someone0 said:
Something is interesting, eventhough mine originally got automatically updated to 2.0.2, but after the factory reset, it went back to 2.0.0. But for some weird reason I can't get root.
Maybe this will help, the build number is 2.0.0.1031.lithium01.ovation.rldp.s68403 with the manufactured date 10/22/2012
please compare mine to your.
I also rewrote your code into a batch file. You can double check it I guess.
Click to expand...
Click to collapse
so, when you run this, after the final adb shell, what are the permissions on /system/xbin/su?
run su and you should get the root prompt.
I don't get root prompt, su never get copied to /system/xbin/su
here is the list of my finding.
Code:
/data/
-rwxr-xr-x shell shell 167 2012-11-10 05:52 boot_complete_hook.sh
/data/su
-rwxr-xr-x shell shell 586212 2012-11-10 06:07 busybox
-rwxr-xr-x shell shell 22364 2012-11-10 06:07 su
/data/local
lrwxrwxrwx shell shell 2012-11-10 06:20 tmp -> /data/
cat boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
everything is in place and correct, but no dice. either boot_complete_hook.sh didn't get executed or it did but never get launched with root permission.
someone0 said:
I don't get root prompt, su never get copied to /system/xbin/su
here is the list of my finding.
Code:
/data/
-rwxr-xr-x shell shell 167 2012-11-10 05:52 boot_complete_hook.sh
/data/su
-rwxr-xr-x shell shell 586212 2012-11-10 06:07 busybox
-rwxr-xr-x shell shell 22364 2012-11-10 06:07 su
/data/local
lrwxrwxrwx shell shell 2012-11-10 06:20 tmp -> /data/
cat boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
everything is in place and correct, but no dice.
Click to expand...
Click to collapse
well, there should be more stuff in the shell file, you miss the final chown line: chmod 06755 /system/xbin/su
It did, I just didn't copy and paste the output correctly. But regardless, since the foulder /system/xbin don't have the su file, this mean as I suspected earlier, either it wasn't executed or lauched w/ root permission.
someone0 said:
It did, I just didn't copy and paste the output correctly. But regardless, since the foulder /system/xbin don't have the su file, this mean as I suspected earlier, either it wasn't executed or lauched w/ root permission.
Click to expand...
Click to collapse
check if your /system/bin/clrbootcount.sh calls /data/boot_complete_hook.sh
verygreen said:
check if your /system/bin/clrbootcount.sh calls /data/boot_complete_hook.sh
Click to expand...
Click to collapse
This is interesting, it look as if it won't launch the /data/boot_complete_hook.sh
Code:
cat /data/boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
[B][email protected]:/data $ /data/boot_complete_hook.sh
/data/boot_complete_hook.sh
/system/bin/sh: /data/boot_complete_hook.sh: No such file or directory
1|[email protected]:/data $
[/B]
Yub it does
Code:
cat clrbootcount.sh
#!/system/bin/sh
################################################################################
##
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
[B]/data/boot_complete_hook.sh[/B]
# Zero the boot count
cat /system/etc/zerobootcnt > /bootdata/BootCnt