yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] slow88lx:
In a few short days this will support ROM flashing. Just be patient.
[Motorola Droid 3] gravenimage:
Oh snap, its chevy! Your D1 kernals made my life wonderful! Can't wait to see what you've got for us!

sent from my ROOTED DROID3 from the XDA app
[Motorola Droid 3] gravenimage:
You sir, are my hero. Can't wait to flash your rom when its ready.

sent from my ROOTED DROID3 from the XDA app
[Motorola Droid 3] GoogleAndroid:
Awesome. Steel Droid was one of my favorite D1 roms.

But for overclocking, what about modular overclocking? The Droid 2, D2G, and DX all have modular overclocking available, and even got up to 2 ghz. I know it isn't the same as a custom kernel, but running at 1.3ghz would be pretty nice.
[Motorola Droid 3] kshen1:
Yep and I also have a rom for both 959 and 890 users to go. I think chevys only supports 959, at least that's what he posted over at droidforums
[Motorola Droid 3] chevycam94:
Wrong chevy. Lol. You meant ChevyNo1. Im a dev also, and made many roms for the D1, but no kernels yet. I haven't heard if ChevyNo1 will support the D3 or not. I hope he does. He does amazing work!
[Motorola Droid 3] kshen1:
Nah, your the steel droid guy right? You posted last night on dforums that u said ur rom only supports 959. Mine supports 959 and 890
[Motorola Droid 3] ultima86:
lmao lol lol lol lol lmao...i was like "am i crazy? nah has to be a mix up" lol
[Motorola Droid 3] kingharrison:
How come no ROM yet? The recovery needs an update or the ROMs arent done yet?
[Motorola Droid 3] Yonnor:
Be patient, ROM Flashing support will be up soon.

Keep in mind the Dev's have real lives too, they don't get paid to do this stuff.
[Motorola Droid 3] kingharrison:
Sorry for the tone, i think it misled what i was asking. I didnt know which was the bottleneck.
[Motorola Droid 3] erismaster:
Ability to flash anything with recovery is disabled at the moment, that's the bottleneck. It'll be added soon, and supposedly a few devs have already got something cooked up.
[Motorola Droid 3] GoogleAndroid:
I'm not confusing you with ChevyNo1, I mean this ROM: http://www.droidforums.net/forum/st...-steel-droid-8-0-gingerbread-7-30-2011-a.html

Which was made by you. It's one of the last ROMs I used before getting the Fascinate, and I remember using it for awhile.
[Motorola Droid 3] somemadcaaant:
chevycam94 said he didnt do any kernels specifically mate, his roms may have come with custom kernels tho from other people.

-smc
[Motorola Droid 3] chevycam94:
I have been doing quite a bit of work, but Im unable to test to see if any of my D3 ROM tests work, because we dont have a way to flash ROMs yet. I probably WONT be the first dev out with a ROM, in fact, Im almost POSITIVE. BUT, on the other hand, waiting has advantages. I have time to completely test the ROM, work out bugs, get things updated, and tweak it more than just stock steetings. I have big plans, but for the major part, I need to be able to pull apart the boot.img (now 8MB for the D3), modify some values, and repack it successfully.

Other than that, its going to be a while before I have something concrete to distribute. Donations do help. lol I have NOTHING protecting my D3. No hard shell cases, screen protectors, or anything. Even just enough to get a case would be awesome. I just dont want to destroy this phone within a week of getting it. lol
[Motorola Droid 3] DoubleYouPee:
So...does this work on XT860? Anyone?
[Motorola Droid 3] erismaster:
Not 100% sure, but I think so.
[Motorola Droid 3] Androidsims:
Did you read the blog post? It says what devices it works on there.
[Motorola Droid 3] cellzealot:
Dont plan on being able to modify the boot.img at all on a locked bootloader.

The 2nd init ROMs utilize the stock kernel and ramdisk and run a modified system on top of it.

That is the best that can be hoped for without a factory oem unlock getting leaked, if that is at all possible on an OMAP chipset.
[Motorola Droid 3] DoubleYouPee:
Link? I can't find it on rootzwiki
[Motorola Droid 3] ultima86:
u have a name yet? just curious...
[Motorola Droid 3] chevycam94:
Nope. I didn't figure on anything creative. Lol. Thought I would keep my Steel Droid title, so its recognized by everyone as being the same ROM. Just change the phone its built for.
[Motorola Droid 3] ultima86:
shoulda cleared that quote up, i meant kshen1...i knew urs was Steel Droid lol
[Motorola Droid 3] kayelemenohpee:
Im confussed, ive never done anything to my phone till i got the D3 on the 14th of sept.

I'm rooted with Pzouza4's one click root

I deleted **** off my first one and i had to return it (slider turns off screen) so used the tool to restore the system apps and unroot.

is this the same thing as restoring with the one click tools system recovery,

or is this just if my phone is bricked and I can't run the one click?

I hear things about No flash recovery cause there is a locked bootloader, is this the way around that?

and what is nandroid? i found nothing in my serch of these forums about it.
[Motorola Droid 3] Androidsims:
NAND is a type of Flash memory. Creating a NANDroid backup is the term for backing up your phone. Creating Nandroids will allow you to flash back to the way your phone was at it's current state. How you back it up is how it will be when you restore it, apps, wallpapers, text messages, etc.
[Motorola Droid 3] kayelemenohpee:
Im rooted and Ive ran the script manager to change certain .apk files to .bak

im suppose to put the back to .apk before I make a recovery file right?

I have a folder that says clockwork recovery i have no idea what to do with it,

I just installed droid 3 bootstrap, says recovery state not installed

do i just put the files back to norm and then what???

I dont want to install a recovery cause I dont really need to recover anything

but Id like to make a recover file because Im thinking that this bootstrap is what i use if my phone is bricked and i can only enter it with powering on while holding "M"

what i want to do is... i guess make a NANDroid??? is that right? (which i couldnt use untill flash booting is supported right?)
[Motorola Droid 3] erismaster:
Alright.

first thing. installing just the app does not install a recovery. click install recovery in the app. then the checkmark next to recovery active should be checked. this needs to be checked for the recovery to work. once you get that done i would restore all the apps you renamed and then enter recovery. to enter recovery look at the op. it should be clear. once you get into recovery navigate to backup and restore and make a backup(volume buttons are up and down, power button selects). this will create an exact copy of the current state of your phone. it saves it into the clockworkmod folder on either your sd card or the internal memory, you get the option of which you want to back up to when you create the backup. after you make the backup you can feel free to rename whatever you want to .bak. rom flashing does NOT need to be enabled to restore a nandroid. to restore a nandroid go to backup and restore in recovery and then restore and then a backup you made.

i hope this helps.
[Motorola Droid 3] kshen1:
You should update the OP with this post ^^. :P
[Motorola Droid 3] kayelemenohpee:
so i just made my first back up, a NANDroid. now i can go and skrew up my **** as much as i want, like delete system apps right?

run bloat removing script, freeze kindle, delete crap apps and bloat apps i dont plan on defrosting?

now i need to learn what FLASHING A ROM is

is that like putting a different OS on my droid 3?
[Motorola Droid 3] erismaster:
Yeah as long as you don't do anything hardcore to the point where the phone won't boot past like line 152 or something you can still enter recovery. But apps should be fine to delete, if it messes up you can go to restore, advanced, and restore just /system(if its from deleting apps or metamorph themes). And flashing a rom is basically putting a different os on your phone. Some are more different from stock than others, but they all will be android. They're more like different flavors.
[Motorola Droid 3] thingonaspring:
There seems to be a lot of confusion around this recovery, so I thought I'd do my bit by adding to it ;-)

On this thread's first post, the list of unsupported features shows "Rom flashing", as does the equivalent thread on Droidforums (don't want to ruin my karma by linking to another forum here).

The odd thing is - I can't find any instance of Hashcode himself saying that applying an update.zip is not supported in this recovery. If you look at his blog it says :-

"you can make backups, perform restores and apply .zip files (though you better know that the update.zip is safe for the Droid 3)."

Rootzwiki has the following weird statement :-

"HOWEVER, ROM booting is not supported on this version as of yet."

God alone knows what that means - perhaps booting an OS from SDCard directly (as opposed to internal storage)?

So can we flash update.zips, with the usual warnings about flashing the wrong thing?

Or have I missed something important?
[Motorola Droid 3] kayelemenohpee:
What are update.zips? Are those the upates to gingerbread that you need the sys apps to receive?
[Motorola Droid 3] SnowDeath:
It simply means only flash ROMs that have taken the Droid 3 bootstrap into account lest ye be ready for SBF flashing. He hasn't put in place a way for the bootstrap files (hijack, etc) to protect themselves from being wiped out. If they are deleted by mistake, your phone is bricked.
[Motorola Droid 3] Phibernaut:
I installed and ran a backup without issue but was never greeted by the friendly skateboarding Android animation. Anyone else missing that bit?
[Motorola Droid 3] thingonaspring:
So in fact there's nothing stopping us flashing any old thing to /system, as long as we have a backup available on SD card, and whatever system we flashed gets past line 104 of init.rc - right?

If some restrictions were lifted in the CWR, we could also modify the /preinstall partition - it's only off limits to prevent damage to CWR itself.

Even if the init.rc craps out, or the /preinstall partition is broken, we can still use the 5.6.890 update and RSDLite to get back to stock 5.6.890, accepting that we'd have to reinstall root and clockwork recovery afterwards.

So what we now have is a nice consequence-free-ish environment to develop our own roms - albeit with some restrictions, some of which could be easily removed as long as we're careful.

It seems weird to me that we've been granted all this freedom by Hashcode, and we're all sat here saying "can't flash", and not getting on with rom hacking. If all the semi-assumptions above are true - then I'm getting stuck in to start making my own modded ROM - but not before I've tested those assumptions of course.
[Motorola Droid 3] tcrews:
That's part of CyanogenMod ROM (their bootanimation) not recovery.
[Motorola Droid 3] driftinaway:
frozen motorola logo

followed instructions exactly, but when i select BP mode the phone reboots and freezes on the motorola logo. im rooted with psouza's tool, so not sure whats going wrong. Anyone else experiencing this? Ill retry and just let it go for a half hour and see if it just takes unusually long or something...

edit: I also installed the 890 ota leak prior to this, if thats of any needed info.
[Motorola Droid 3] slow88lx:
I can say with absolute certainty that as of now in v0.87 you cannot flash ROMs. Hashcode is working(in his spare time mind you) to bring us ROM zip support or maybe a superior technique for loading ROMs ;)

Just to be clear flashable zips != ROM zips.

It only takes 10 seconds for me. To be clear are you selecting "BP Tools"?

Also to be sure is the box in the app checked for "Recovery Active" and does it say "Recovery state: Installed " at the top?
[Motorola Droid 3] kayelemenohpee:
i have to deleted them myself to be skrewd right? they won't just be wiped out during booting will they, cause ive heard of people not getting the recovering to stick and having to do it over and over

and as long as i go to boottools, advance, and recover system, can i still recieve OTA updates? or is that why everyone is trying to flash the update.zip?
[Motorola Droid 3] driftinaway:
Yep, selecting BP tools. And correct, it does say "Recovery State: Installed" and the box for "Recovery Active" is checked. Tried 3 times now, the last time giving it 30 mins. No results...just freezes. I thought perhaps maybe it was because im rooted with the 890 update, but id assume other devs that have done this probably have 890 already anyway. So not sure whats wrong..perhaps ill re-download the apk and re-install it and give it another go...but i dont feel like thats the problem.

edit: i also did the script for removing 50+ bloatware thats popular on this forum...not sure if that conflicted with anything or not...
[Motorola Droid 3] Code3VW:
This didn't work for me either...

I didn't do the one-click root as I rooted it before the 1 click was out...

I also ran the bloatware removal script.

I installed the D3 Bootstrap apk no problem. I granted SU permission. I hit "Install Recovery" and it prepares, unpacks, checks busybox, runs script, and cleans up and then says INSTALLATION COMPLETE however it still says Recovery State: Not Installed, and when I powered off, and then powered on while holding M and chose BP Tools it just reboot into the OS...no clockwork...

EDIT 1: I just ran the restore script for the apps and that didn't help. I'm going to try re-rooting using psouza's root script...

EDIT 2: Alright, I got it working. I installed psouza's root script and ran it. Then, I ran the D3 Bootstrap apk again and it worked. Rebooted and went into clockwork mod and am backing it up now.

So for those that rooted before psouza made his script, you need to use his script (I assume because of busybox).
[Motorola Droid 3] Code3VW:
See my previous post.
[Motorola Droid 3] kshen1:
Did you run as root?
[Motorola Droid 3] kayelemenohpee:
If you ran bloat removal you have to run bloat restorer before you make a backup or your just backing up stuff that isn't there.

I think that's right. That's what I do anyways.
[Motorola Droid 3] Hashcode:
Hi Guys,

Let me explain what this version of the Recovery is and isn't.

First off, it's the first version I could possibly pump out that was fairly tested and acceptable for general consumption.

What it is:

- It's a fairly stock version of CWRecovery. You can backup/restore partitions and I believe the apply zip feature works, though, it's quite dangerous. I purposely disabled several partitions due to having a locked bootloader and the fact that our recovery is installed on the preinstall partition.

- It's a 2nd-init recovery. Which means it loads by hijacking the init process about 100 lines in. Even tho it's triggered by a boot-menu, it's still a hijack.

What it is not:

- It's not "protected" in any way. It's only a "recovery" if you keep the system intact enough to get into it.

- I can't say that it's an effective way to flash ROMs, because of the complexity of making and supporting them. Currently, every developer who wants to try and create a ROM for the D3 can handle the hijack in various ways. So there might be issues..

I am working on making this recovery more of what we NEED for developing ROMs.

The reality is we have a locked bootloader. That means any significant mistake to the /system and you're looking at a fastboot restore.

TO make this happen:

- We need to work in a "sandbox".

- If we can keep the primary system intact and hijack to a 2nd-system where we have more control and less danger, than the development of our ROMs will be fair easy. The individual developer doesn't need to worry about the hijack or how it works.

- The recovery that we use, needs to focus on the 2nd-system like it's the only /system that we have. For example when you apply zips, it applies them to the 2nd-system. Any changes to "system" would be the 2nd-system.

And that's exactly where I'm headed with the Droid 3 Bootstrap / Recovery.

TL;DR:

The recovery is a work in progress and it might just end up being like nothing we've seen before. A full featured and fully "safe" locked bootloader recovery.
[Motorola Droid 3] kshen1:
i <3 hashcode.
[Motorola Droid 3] wootizzle:
Idk what any of that meant. But my mind is blown.
[Motorola Droid 3] DoubleYouPee:
:D haha

(filler)
[Motorola Droid 3] thingonaspring:
@Hashcode

Thanks for clearing up a bunch of the confusion, it's very much appreciated.

Understood that we're in second init here, so we're relying on the stock init process up to ~100 lines of /init.rc, and beyond that we reject that init and substitute it with our own, still on process id 1, so the kernel doesn't panic that pid1 has died.

Your caution on denying access to dangerous partitions is probably for the best, I need to be saved from my own enthusiasm just as much as anyone.

2nd-system/"sandbox" - this makes a lot of sense. It would mean the only modifications made to the stock firmware would be rooting and CWR, limiting the dangers of further modification.

It would be great if we could nominate some directory or partition (remount/chroot?) of internal/external storage for this 2nd system.

With that layout, we could treat the "real" system as read-only and have the option to boot into to "real" mode if we've made a catastrophic error on the 2nd system. That would avoid the need to fastboot recover for all but the very biggest mistakes.
[Motorola Droid 3] sic4672:
ding ding ding!

Quote from Hashcode's blog:

"The recovery currently requires a "busybox" with the "which" applet."

Just so everyone knows: psouza's root script has the correct busybox, so definitely use it.

(sorry if I come off sounding like as ass, this isn't intended as a shot at you)
[Motorola Droid 3] lordgodgeneral:
My knowledge on this is limited but I'm wondering...

How does the bootstrap and 2nd init hijack work on the D2/DX or even the Bionic that they the alpha of CM7 running on compared with how we're doing it on the D3?

Can't it just be done in a similar fashion for what works for flashing on those devices? I'm assuming since they're using a 2nd init to get around their locked bootloaders as well that they would have ran into the same situation we're in.
[Motorola Droid 3] thingonaspring:
@lordgodgeneral

Yep the same approach that D2/DX use would work in theory, but those devices have one big fat advantage - a proper full SBF to flash back to when it all goes wrong.

We don't have that, so we need to be a great deal more careful.
[Motorola Droid 3] ultima86:
thx...i was wondering the same thing

Edit: bionic doesnt have full sbf either, unless i missed that news, so im still confused lol
[Motorola Droid 3] limaxray:
Is there any possibility of chain loading another kernel? ie high jack the kernel's execution to execute another kernel? I don't see why it wouldn't work, but its also not something that would ever cross my mind in any other circumstance so I really have no idea.

I do like the idea of using a separate system partition. Perhaps an image on internal storage. If you did the same thing with data and cache, you could have a boot menu to select any number of ROMs to boot to. This would make switching between ROMs quick and painless.
[Motorola Droid 3] Hashcode:
Re: limaxray:

Your "chain loading another kernel" idea is known as: kexec.

http://en.wikipedia.org/wiki/Kexec

It's being worked on in a variety of ways, but no working phone implementations that I know of.

For now, I'm testing /preinstall as my 2nd-system. it's actually larger than the stock /system partition by about 50M.

Note: We do have a proper full fastboot restore method, as does the Bionic.

Re: lordgodgeneral:

The hijack can be done the same way it's been done on D2, DX, Bionic, etc. But this means every developer has to do it. As users, we take a risk of knowing that if the ROM they are loading has a hijack flaw, then they're looking at a fastboot recovery.

2nd-system would take the locked-bootloader complexity out of ROM development.

As a user:

1. We get the solid stock-like recovery experience we expect of a non-locked phone.

For developers:

1. ROMs are easier to develop if you don't have to worry about the hijack.

2. Having the recovery be bulletproof is a huge timesaver. I personally have fastboot restored my /system partition no less than 15 times during the testing of the Recovery. Do I wish I was able to simply restore my /system to a backup and move on? You bet. Or even better, go into recovery and use ADB to fix booting issues on the fly.
[Motorola Droid 3] ultima86:
that cleared it up for me lol...i thought the fastboot files were full restore, but since its not named "sbf" & he said the others had "full sbfs" i got mixed up

hope all goes well w/ ur testing of 2nd system & preinstall...thx for all ur work
[Motorola Droid 3] eww245:
Actually kexec has been compiled for xdandroid by Howard Chu (highlandsun) . But I believe the kernel has to be pached in order to use it. Here is some info I found lists.xdandroid.com/pipermail/xdandroid-dev/2011-May/000327.html

Here's his git but I cant find the source https://gitorious.org/~hyc
[Motorola Droid 3] thingonaspring:
Kexec has been done on other motorola hardware, but as far as I know, it's always hit one big limitation - nobody has managed to get the radio ROM working with a kexec kernel. The result is no calls, no data, no sms, just wifi.
[Motorola Droid 3] Wolfhere:
Okay, I am still learning. But then again; if I wasn't, I would not be coming here. You dev's are awesome!

Anyway, I see renamed apk's need to be restored to the original name. How about frozen app's ? Do I need to defrost those to get my backup/restore (NANdroid) to work correctly?

Thanks in advance, please excuse my ignorance
[Motorola Droid 3] erismaster:
Yeah, personally I always like to make a completely stock(well, rooted) backup. All bloat. All unfrozen. After I do that ill rename it (using a file mananger go to the sdcard or sdcard-ext and then the clockwork folder then backups(something like that) and then you'll see a file with numbers, you can rename that, and then you can name it stock. then debloat, backup again, and name that debloated stock.) That's what I do, that way when I use metamorphs and can just restore the debloat backup and I'm good to go.

Hope this helps
[Motorola Droid 3] tacosrdelicioso:
Does fastboot restore uninstall cwm?
[Motorola Droid 3] Adam.h.ogle:
The technical problem is that the phone is split into two parts: the smart, and the phone. The smart side runs Android, the phone side is the radio, which is a separate OS. Communication between the two is handled by a serial (as in serial port). When you kexec, you drop the communications between the two, and it is believed that the radio says "the phone died, so we might as well turn off". Under normal conditions, this is fine, because usually the phone is being rebooted, so the hardware will re-init the radio and life is good. However, under kexec, without a graceful way to terminate the connection, followed by a way to restore the connection, you have a 4" tablet.
[Motorola Droid 3] anomaly256:
droid3 recovery bootstrap market price

Heyas,

Hope this is the right thread to ask.

I notice the 'official' droid3 clockwork recovery bootstrap app is $3 in the market.

Just wondering, does the clockwork dev donate some or all of this back to hashcode for doing the actual legwork? Just wondering if I should donate something back to hashcode to be fair or if this is taken care of when I purchase the market app..

Cheers
[Motorola Droid 3] btonetbone:
Those are two different variants from two different people, even though they are both based on Clockwork Mod. The one on the market was developed by Koush and the one on the thread (http://xdaforums.com/showthread.php?t=1265312) was developed by hashcode. So, if you are interested in donating, I would recommend either the creator of the version you are using or both if you are feeling generous to the dev community.