Database Develop

Droid and Milestone Differences

Obviously a radio difference, but what else prevents roms being easily ported to Milestone from Droid? Im not sure on the internals differences, but could we start porting.
NB do we even have root !?

we have root on both devices i think the exploit may be the same? forgive me if i am wrong.
(root guide for 2.1) the latest update at time of this post.
http://android.modaco.com/content/m...m/308422/milestone-2-1-update-and-root-guide/
the problem on the milestone as anyone will tell you, the LOCKED BOOT LOADER this isnt a problem for the Droid users, they got this for free. Hopefully with the power of the XDA super Dev team, we will have a solution for this, and start pumping out custom roms!
all of the accessories fit for each other, which maes it handy if you want some cheap bits from china, there isnt any carrier in the uk that has the milestone, what i am saying... carrier.. i mean mobile phone network!
i got my milestone from here. buymobilephones.net on a contract, but you can also get them from expansys, as far as i have researched, they are all unlocked. So you shouldnt even need to post about unlocking the sim.
there is another differnce i remember, if you are loading busybox on your device, this will not load if you use droid root helper from the market, you will need to manually do this via ADB and the loaction on the partition is different.

carphone warehouse sell the milestone on t-mobile and you can install busybox with droid root helper.

The kexec modules are nearly working. So there will be a 2nd bootloader in near future.
http://and-developers.com/motorola_milestone

I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.

iamdarren said:
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
Click to expand...
Click to collapse
Titanium installs busybox in its own data directory so that only it can access it.

Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet

Main difference is the locked bootloader , there is a signature verification at boot time that prevents us from running custom Kernel .
Its unlikely that the bootloader signature will ever be cracked , other workaround like Kexec will most likely help achieve further mods to our device eventho it seem to be right around the corner there is still much work to be done

iamdarren said:
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Click to expand...
Click to collapse
Download Busybox and use this to install it:
Code:
ADB push busybox /sdcard/busybox
ADB shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
# cat /sdcard/busybox > /system/bin/busybox && chmod 700 /system/bin/busybox
# sync
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system

Its better to push it to xbin and not to bin, as the most apps search there for the busybox

After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?

cmstlist said:
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
Click to expand...
Click to collapse
your good ..

Block future updates?

So, anyone come up with a way to block the NC from receiving its firmware updates from B&N? I can see Barnes releasing a update and it just installs itself and wipes out the root we have. I'm sure they cant be happy about all the stuff we are now doing on the nook, but I'm sure they are especially not happy about us being able to install the Kindle app! In my mind, its the best of both worlds, but I'm sure B&N wouldnt see it that way. They could (for all practical purposes), put out a 1.0.1 update that blocked that app and kills our root.

The "default way" of disabling OTA updates on Android might work (make sure your device is not currently updating or something):
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
cd /etc/security
mv otacerts.zip otacerts.zip_DISABLED_OTA_UPDATES
Although the key contained in that ZIP file does not look like it's really used (its name is testkey.x509.pem).

Edit: Please disregard my mindless ramblings below (I feel like the noob I am, now). I took a closer look at the code once my mind had emerged from whatever haze had been blocking my deeper thought processes and realized what needed to be done to get it to work (I learned a little more about ADB, which helps). And what's more, I think I did it the right way. *grin* Now, if we knew for sure this would block updates, we'd be set. I suppose we'll find out soon enough.
Thanks for posting the code, Weichel.
weichel said:
The "default way" of disabling OTA updates on Android might work (make sure your device is not currently updating or something):
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
cd /etc/security
mv otacerts.zip otacerts.zip_DISABLED_OTA_UPDATES
Although the key contained in that ZIP file does not look like it's really used (its name is testkey.x509.pem).
Click to expand...
Click to collapse
Just to make sure I'm on the right track (noob here), I'd want to do an "adb shell" then run the script above? Also, read-write access for the NC system partition is probably necessary, yes? I haven't enabled rw access yet, didn't want to take any chances of accidentally bricking my NC.
I tried the code above (without going through to proceedure to enable read-write access to the system partition), but it didn't return any messages confirming success or failure.

just looked in that /etc folder and I see install-recovery.sh I wonder what that does.

xboxexpert said:
just looked in that /etc folder and I see install-recovery.sh I wonder what that does.
Click to expand...
Click to collapse
Overwrites corrupted/custom recovery with stock one on boot. At least, that's what it did on the OG Droid.

disregard. wrong post

big.t_03 said:
Edit: Please disregard my mindless ramblings below (I feel like the noob I am, now). I took a closer look at the code once my mind had emerged from whatever haze had been blocking my deeper thought processes and realized what needed to be done to get it to work (I learned a little more about ADB, which helps). And what's more, I think I did it the right way. *grin* Now, if we knew for sure this would block updates, we'd be set. I suppose we'll find out soon enough.
Thanks for posting the code, Weichel.
Just to make sure I'm on the right track (noob here), I'd want to do an "adb shell" then run the script above? Also, read-write access for the NC system partition is probably necessary, yes? I haven't enabled rw access yet, didn't want to take any chances of accidentally bricking my NC.
I tried the code above (without going through to proceedure to enable read-write access to the system partition), but it didn't return any messages confirming success or failure.
Click to expand...
Click to collapse
I don't understand the confusion here. You have a rooted Color Nook. Install Root Explorer and go to /system/etc and click the Mount R/W button and then long press the ocacerts.zip file and rename it. It's that easy.

[Nook Noob] i can't get my adb to find my nook

ive used adb for a while now i use i to push apps to my evo and other mods but i cant seem to get adb to find my nook and it's very annoying because i cant do the "Permenant BN-OTA Update Block" session

http://forum.xda-developers.com/showthread.php?t=871996

madfatter said:
http://forum.xda-developers.com/showthread.php?t=871996
Click to expand...
Click to collapse
ive been searching for over 2 hours -.- i wouldnt post if i actually found it

Check the Nook Color Portal at Nookdevs, look under adb. You have to add the NC id. Also if you did the 1.1 update you may have to into Nooktools/developer and check debuging.

PhyscoAssassinx said:
ive used adb for a while now i use i to push apps to my evo and other mods but i cant seem to get adb to find my nook and it's very annoying because i cant do the "Permenant BN-OTA Update Block" session
Click to expand...
Click to collapse
-Get ADB wireless app from the market. works great and you dont need drivers.
-Then put this info into adb. I found it here in another thread.
Disabling OTA Updates
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell mv /etc/security/otacerts.zip /etc/security/otacerts.zip_DISABLED_OTA_UPDATES

techboydino said:
-Get ADB wireless app from the market. works great and you dont need drivers.
-Then put this info into adb. I found it here in another thread.
Disabling OTA Updates
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell mv /etc/security/otacerts.zip /etc/security/otacerts.zip_DISABLED_OTA_UPDATES
Click to expand...
Click to collapse
Adb wireless is nice but what if you get stuck in a boot loop or can't boot at all or stuck in recovery? Adb wireless is nice to not have to deal with wires but you really should have adb over usb working just because you never know what might happen.
To the op what operating system are you using? http://nookdevs.com/NookColor_USB_ADB that should get you going. If adb works with you evo you probably just need to update the driver (if your running windows) for your nook

Novarider said:
Adb wireless is nice but what if you get stuck in a boot loop or can't boot at all or stuck in recovery? Adb wireless is nice to not have to deal with wires but you really should have adb over usb working just because you never know what might happen.
To the op what operating system are you using? http://nookdevs.com/NookColor_USB_ADB that should get you going. If adb works with you evo you probably just need to update the driver (if your running windows) for your nook
Click to expand...
Click to collapse
I agree, but the OP was needing help disabling the updates as he stated. Some of the batch files work ok, but have found often dont work out for me with 64 bit system. Hopefully he can at least disable the updates, then worry about proper adb.

techboydino said:
-Get ADB wireless app from the market. works great and you dont need drivers.
-Then put this info into adb. I found it here in another thread.
Disabling OTA Updates
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell mv /etc/security/otacerts.zip /etc/security/otacerts.zip_DISABLED_OTA_UPDATES
Click to expand...
Click to collapse
thanks my issue was and still is drivers but adb wireless works like a charm, if i get into a bootloop trouble i have Clockwork burned onto a 2 gig SD with the repartition nook 1.0.1 retore Zip

[Q] Google Music apk sideloading?

Hi all, I'm trying to sideload the new Google Music apk onto my CM7 Nook Color. As i reside outside the US, I don't have it available through the market. I did sign-up for the invite through a proxy network though and got the invite a few days back. Now don't ask me how, but after receiving the invite, somehow the new google music app appeared as a manual update on my Nexus One(2.3.4) and it works like an absolute charm on it. I 'adb pulled' this Music app off my Nexus One and tried to install it on my Nook Color through adb. Here's the steps I followed:
- Connected through adb wireless first.
- Tried 'adb install' first. That didn't work.
$ ./adb install MusicGoogle.apk
493 KB/s (375498 bytes in 0.742s)
pkg: /data/local/tmp/MusicGoogle.apk
Failure [INSTALL_FAILED_DEXOPT]
- Then tried transferring the apk to /system/app
$ adb push MusicGoogle.apk /data/local/tmp/
$ adb shell
# su
# mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
# chmod 777 /system/app
# cp /data/local/tmp/MusicGoogle.apk /system/app/
# chmod 755 /system/app
# mount -o ro,remount -t ext4 /dev/block/mmcblk0p5 /system
This didn't work either. The icon failed to show up in the app-drawer.
Where am I going wrong here? Is it becuase I took the apk from my N1?..I hardly think that should be a problem. Could someone from the US post their apk which they installed on their NC, from the Android Market?
Thanks.

Sorry if this is a dumb question, but is there any reason you don't just use Market Enabler?

MickMcGeough said:
Sorry if this is a dumb question, but is there any reason you don't just use Market Enabler?
Click to expand...
Click to collapse
I could always do that, but is there a reason why the above method shouldn't work? I've followed the above method many times to install apps on my rooted N1.

hungryTux said:
I could always do that, but is there a reason why the above method shouldn't work? I've followed the above method many times to install apps on my rooted N1.
Click to expand...
Click to collapse
I don't know if there's any reason that wouldn't work. I'm using Google Music Beta in Canada for a week or so now and I spent less time setting it up on my NC than I've spent replying in this thread

I'm not sure if the apk coming from your nexus one is being the reason the apk is not installing but sideloading is vary easy. all you have to do is place the apk on the root of your sd card and navigate from a file manager app like astro to the apk and press on it. the app manager will appear and ask if you'll like to install it, say yes. there, you're all done.
cm7 n111 6/18 OC kernel 300/600/800/1100/1200 conservative

[Q] Official update January 2014

Hi everybody!
I noticed there is another update...it should not be so strong, just minor fixes...
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/97885/p/30,6720,8302/action/auth
I haven't done it yet, but after 12 hours I have always the notice about it.
I'm using Droid 4 in Europe, so I'm not so interested.
Anyway, do you know if I will lose the root permission?
Thanks!

I currently have 98.72.18.XT894.Verizon.en.US and 4.1.2, so I'm curious as to what the new updates are for the xxxxxx.188 and xxxxx.189. I would suggest something like VooDoo OTA to attempt to save your root but there is no guarantee that it will protect it if Motorola has figured out how to patch the exploit.
From Motorola, new software is .....
98.72.188.XT894.Verizon.en.US or 98.72.189.XT894.Verizon.en.US

Voodooo worked for me on latest O.T.A
karlsdroids said:
I currently have 98.72.18.XT894.Verizon.en.US and 4.1.2, so I'm curious as to what the new updates are for the xxxxxx.188 and xxxxx.189. I would suggest something like VooDoo OTA to attempt to save your root but there is no guarantee that it will protect it if Motorola has figured out how to patch the exploit.
From Motorola, new software is .....
98.72.188.XT894.Verizon.en.US or 98.72.189.XT894.Verizon.en.US
Click to expand...
Click to collapse
I used Voodoo root keeper for the latest ota update. Worked for me. Just needed to reinstall SU

mercermtn said:
I used Voodoo root keeper for the latest ota update. Worked for me. Just needed to reinstall SU
Click to expand...
Click to collapse
ok! thank you for your answer...
except for what mentioned by Motorola, the update changes something else? I mean speed or other aspects?

Same with voodoo here, didn't uninstall the SU app though
Sent from my XT894 using Tapatalk

Using voodoo to temp unroot and install the update did not work for me. I've decided to pass on the update and instead I'll just do a different rom. I found what the update consisted of and basically it's "bug fixes and security updates"- no real benefit there for me.

woodoo didn't work for me...can I use the same procedure to root again?
Sent from my DROID4 using xda app-developers app

For those who failed with voodoo, you could try Saferoot, it harmless to try...
Just root my RAZR HD although it designed for VZW Galaxy S4...
http://forum.xda-developers.com/showthread.php?t=2565758

I used voodoo on my wife's phone. Saved the su binary, installed the ota, clicked restore root. Voodoo said root restored but the check box for root stayed empty and root apps didn't work (like titanium backup). Found a post that gave terminal commands to manually restore the su backup. Worked perfectly and I now have root back. I forgot the link but luckily I copied and pasted the steps. So If voodoo said it worked but didn't, give this a try...
(I'd give credit where credit is due but lost the link)
"My wife's Transformer Infinity exhibited basically the same behaviour after its last 2 updates (both 4.2.something, IIRC). Fortunately the backup copy of su was intact, as it likely is in your case, and I was able to restore it manually using a terminal emulater app... adb would presumably have worked as well, but my notebook wasn't available at the time. Here's what I did.
.
1. Launch the terminal emulater of your choice (I used Better Terminal Emulater Pro, but the specific app probably doesn't matter)
.
2. Go to the location of the backup copy.
===========================
cd /system/usr/we-need-root
===========================
.
3. Use the su backup to obtain a root shell. This should trigger the usual superuser popup/notification, assuming that it's configured to do so.
=================
./su-backup -
=================
.
4. Remount the /system partition in read/write mode.
============================
mount -o remount,rw /system
============================
.
5. Copy the su backup to the proper location, taking care to keep the permissions intact.
=============================
cp -p su-backup /system/xbin/su
=============================
.
6. Remount the /system partition in the normal, read-only mode.
=============================
mount -o remount,ro /system
=============================
.
7. Reboot the device (might not be strictly required), to ensure that any root-enabled background apps are able to startup cleanly.
.
The usual disclaimers apply, of course. Your device might not have the same configuration as mine, etc., so these commands may need some tweaking. Also, if it was a 4.3 upgrade which caused you to lose root then this procedure likely won't work... I believe that su needs to be running in daemon mode in order to grant privileges, which certainly won't be the case for the backup copy (even if it is a 4.3-compatible version).

squall90x said:
Hi everybody!
I'm using Droid 4 in Europe, so I'm not so interested.
Thanks!
Click to expand...
Click to collapse
I too use this in Europe, and made the mistake of accepting this OTA update, which bricked my data connectivity. More info in this post:
http://forum.xda-developers.com/showpost.php?p=49627296&postcount=23

mike-phone said:
I too use this in Europe, and made the mistake of accepting this OTA update, which bricked my data connectivity. More info in this post:
http://forum.xda-developers.com/showpost.php?p=49627296&postcount=23
Click to expand...
Click to collapse
My data connectivity works without problems...

squall90x said:
My data connectivity works without problems...
Click to expand...
Click to collapse
Your reply inspired me to dig a bit deeper. It looks like the OTA update just cleared the list of APNs. I re-added the APN, and it works fine. Thanks.

mike-phone said:
Your reply inspired me to dig a bit deeper. It looks like the OTA update just cleared the list of APNs. I re-added the APN, and it works fine. Thanks.
Click to expand...
Click to collapse
You're welcome!
Sorry I didn't tell you...it was the same also for me!!

androitri said:
For those who failed with voodoo, you could try Saferoot, it harmless to try...
Just root my RAZR HD although it designed for VZW Galaxy S4...
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Thank you so much for this link. I accepted this OTA update about a week ago and lost my root access, despite having run Voodoo OTA Rootkeeper (maybe I did something wrong?) I tried to re-root it using the Razr Blade tool (which is what I had used originally to get root access), but that didn't work. Apparently motorola/verizon plugged the smart action security hole. But this one (saferoot) got the job done. Back to wifi tethering; thanks!
Richard
edit: I have the Droid 4 XT894, and the OTA update which broke my root was 98.72.189.XT894.Verizon.en.US

squabeggz said:
I used voodoo on my wife's phone. Saved the su binary, installed the ota, clicked restore root. Voodoo said root restored but the check box for root stayed empty and root apps didn't work (like titanium backup). Found a post that gave terminal commands to manually restore the su backup. Worked perfectly and I now have root back. I forgot the link but luckily I copied and pasted the steps. So If voodoo said it worked but didn't, give this a try...
(I'd give credit where credit is due but lost the link)
"My wife's Transformer Infinity exhibited basically the same behaviour after its last 2 updates (both 4.2.something, IIRC). Fortunately the backup copy of su was intact, as it likely is in your case, and I was able to restore it manually using a terminal emulater app... adb would presumably have worked as well, but my notebook wasn't available at the time. Here's what I did.
.
1. Launch the terminal emulater of your choice (I used Better Terminal Emulater Pro, but the specific app probably doesn't matter)
.
2. Go to the location of the backup copy.
===========================
cd /system/usr/we-need-root
===========================
.
3. Use the su backup to obtain a root shell. This should trigger the usual superuser popup/notification, assuming that it's configured to do so.
=================
./su-backup -
=================
.
4. Remount the /system partition in read/write mode.
============================
mount -o remount,rw /system
============================
.
5. Copy the su backup to the proper location, taking care to keep the permissions intact.
=============================
cp -p su-backup /system/xbin/su
=============================
.
6. Remount the /system partition in the normal, read-only mode.
=============================
mount -o remount,ro /system
=============================
.
7. Reboot the device (might not be strictly required), to ensure that any root-enabled background apps are able to startup cleanly.
.
The usual disclaimers apply, of course. Your device might not have the same configuration as mine, etc., so these commands may need some tweaking. Also, if it was a 4.3 upgrade which caused you to lose root then this procedure likely won't work... I believe that su needs to be running in daemon mode in order to grant privileges, which certainly won't be the case for the backup copy (even if it is a 4.3-compatible version).
Click to expand...
Click to collapse
After some days I found time to try...
I put the same command and reboot and it worked!!
Thank you so much!!