yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] uoY_redruM:
Everyone who helped, I greatly appreciate your time. I apologize for my inexperience, but I figured it out. It had just been so long since I used fastboot, I didn't even remember what it was. After about an hour of playing around, I remembered how to use it and I everything went flawlessly. New partition is on the phone, new ROM is on the phone, and everything appears fine.

Initial boot wouldn't allow me to install apps from the market, kept saying there was no room, but after reboot it was fine.

286MB of internal storage :)

EDIT

Yeah, 5MB is giving me issues. After every app installed, I have to reboot in order to download another app...keeps telling me there is no room on the device.

I'll switch it up to 50MB as suggested above.
[Nexus One Android Development] avgjoemomma:
Absolutely brilliant! *subscribed* :D
[Nexus One Android Development] samarium:
Which ROM are you using? CM7.1 works fine for me with 5MB.
[Nexus One Android Development] DeTool:
Miui needs more. With 5mb you can only dl apps less than 5mb from market.
[Nexus One Android Development] uoY_redruM:
Yeah, I'm using an Miui rom.

What do you recommend for a cache size, detool?
[Nexus One Android Development] DeTool:
I have mine set to 51 atm. Is working fine.
[Nexus One Android Development] samarium:
The market requirement for download space is not unique to Miui, market needs space in /cache/download in any ROM. CM7.1 just redirects this space onto /data when /cache is too small. Redirection described in this thread post, http://xdaforums.com/showpost.php?p=18344949&postcount=196 , which redirects /cache/download onto /data/local/download. Note that you make need to mkdir /data/local/download once prior.

Maybe Miui needs something similar?

The utility of reducing cache and increasing data is not just in the migration of space, it is in increasing the efficiency of using this space by reducing wasted space in the underutilized partition, and in not having to resize the partitions all the time when space requirements change.
[Nexus One Android Development] cyberon:
Biggest app on Market ATM is Angry Birds Seasons with 22Mb, so my cache is set to 30Mb.

Using MIUI by the way.
[Nexus One Android Development] uoY_redruM:
I tried at 5mb and had issues,so I tried at 50mb and had different issues,but still issue installing apps so I went back to default.

These were all on fresh installs as recommended in the op.

I may try again at 51mb.
[Nexus One Android Development] cyberon:
Strange, no issues here!
[Nexus One Android Development] vincom2:
Planning to upgrade my phone from CM6.1 to CM7.1 soon (yes, I am terribly out of date, I know, lol). It's irritating running out of space, so I'm also going to do the custom partitions thing. I have a few things I need to clear up:

1) Do I have to go from 0.35.0017 to 7.35.5017 (stock blackrose), and then stock blackrose to custom partition blackrose, or can I just hexedit 7.35.5117 with my custom partition setup and use fastboot to flash that immediately?

2) I should fully wipe my phone before flashing the new SPL, and then use fastboot to flash a new recovery (preferably CWM 5?), and then use the new recovery to flash CM7, right?

3) For CM7.1, about 145MB for /system and 5MB for /cache should be enough, right? That should bump my /data to about 300MB :)

4) If I want to revert to the stock partition sizes, do I just use fastboot to flash stock blackrose back onto the phone, and then do the necessary ROM reflashing?
[Nexus One Android Development] samarium:
I wouldn't bother before. Once you set the new partitioning you will need to reformat the partitions anyway, unless you want to try and upgrade from 6.1 to 7.1 and keep your settings, which may not work anyway. You could adapt my process in #217, although I don't know if the the /system/etc/init.d/06mountdl and /system/build.prop dalvik-cache hacks are in 6.1. I'm sticking with CWM 2.5.1.4, CWM5 I found to be unreliable for restores. You will probably need to format system anyway coming from 6.1. Remember to save any system apps that you want to keep like Quickoffice that aren't part of gapps.

That is what I did.

That is what I would do, ensuring I formatted each partition before restoration although I'm not sure that it is required.
[Nexus One Android Development] vincom2:
Thanks! I discovered my SPL was actually still 0.33.0012, so my process went flash 0.35.0017->flash blackrose stock (I did it following this because my blackrose.exe wouldn't work for some reason) -> edit cache partition to 5MB -> flash custom blackrose. Now sitting in recovery, where df -h shows a 5MB /cache. Going to install CM7.1! :D
[Nexus One Android Development] sabiwa:
Ok I altered the .nb0 but now I am really not understanding the thing I have to do.

2.fastboot flash hboot <custom partition blackrose path>

does <custom partition blackrose path> mean the nb0 file created by SPLHexeditor ?
[Nexus One Android Development] vincom2:
Yes. Just drag the file into your command prompt window if you're unsure of what to type.
[Nexus One Android Development] ebautista:
Help!

C:\Modified HBOOT>fastboot flash hboot NAND_HBOOT.nb0

sending 'hboot' (512 KB)...

OKAY [ 0.125s]

writing 'hboot'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 0.266s

I cannot even install blackrose coz in adb, my device is not listed. Im running runnymedemod007.
[Nexus One Android Development] musashiken:
Woohoo, finally got around to installing Blackrose. Now I got a larger system partition, no more worries with flashing large CM7 roms with extra scripts.

---------- Post added at 05:32 AM ---------- Previous post was at 05:23 AM ----------

You need to make sure you are on 0.35.0017 Hboot and unlock it before you do anything.

Make sure you installed android sdk and your phone can connect to windows in adb using command prompt. USB debugging has to be enabled on your phone settings.

Next when you run blackrose.exe from windows, it will ask you first if your device is listed there. If it's properly detected it should be listed there.

Then just follow instructions and the program will automatically reboot your phone to fastboot mode and install blackrose on it.

It also helps if you can type adb or fastboot from any directory in command prompt. Check here on how to configure this in windows if you haven't.
[Nexus One Android Development] taney:
Your ROM (runnymedemod) is irrelevant. Go download and install the Android SDK, it will have all the drivers for ADB.

It looks like it's failing because of something else. Make sure all your files are downloaded properly with an MD5 checker and make sure you have the proper hboot prerequisite.

---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------

Sorry, I didn't even see your post. LOL!
[Nexus One Android Development] meechto:
XDA rocks!!!!

Thanks a ton dla5244 for this wonderful hack :D I now have a cute splash of my 5 month old instead of having to put up with the boring X ;)

Thanks IR for the SPLHexEditor :)
[Nexus One Android Development] meechto:
Wondering if we can get rid of the haptic feedback (vibration) which occurs at boot? I somehow find it pretty annoying!
[Nexus One Android Development] :
Well, I am going to flash blackrose stock over .17 and if successful maybe try the partitioning--

Like some others, more use to terminal as opposed to fastboot/adb stuff. Haven't used it since I rooted 19 months ago. Don't want to assume and screw it up.

1. First, I guess no need to wipe if just flashing stock hboot, didn't do that when going to .17.

2. I can run any roms with it?

3. Unzip it and put blackrose.exe in my android tools folder.

4. Disregard the Trojan notice when opening the unpacked file. As in OP.

5. Get to fastboot devices and see phone. Or do I need to be in adb shell?

6. After I type fastboot devices, goto my tools folder and execute blackrose:

C:\android\android-sdk-windows\tools\blackrose.exe

7. Follow instructions from there--

Hope I am not way off base on--
[Nexus One Android Development] musashiken:
1. Nope, no need to wipe. Just make sure you already have .17 Hboot and unlocked it.

2. Yes any rom can work unless it has certain requirements for partition sizes.

3. Actually blackrose.exe can be opened from anywhere in the comp. As long you unzip the whole blackrose.zip into its own folder.

4. My comp antivirus did not treat it as a trojan though. Using Microsoft Essentials.

5. Well as long you know your android sdk is properly installed and your phone has usb debugging enabled, it should be ok. No need to go into fastboot. Just plug your phone into your computer with usb debugging on and execute blackrose.exe on your computer. You don't need to go into recovery or anything on your phone. Blackrose will automatically reboot it into fastboot for you.

6. See above. But I don't know if blackrose has to be in the same folder as your android tools folders. I edited my windows command prompt to be able to execute fastboot and adb from anywhere in command prompt.

7. Yes follow instructions once Blackrose has your device listed the first time.

Edit: If you are unsure, just run blackrose.exe once and it will tell you if your device is connected. If you see it listed, carry on. If not, then you can simply exit the program and reinstall android sdk etc.
[Nexus One Android Development] :
Thanks musashiken,

Actually it showed as Trojan Cryptic. Using Emisoft On-Line Armor.

Maybe someone can comment on that.

I think as far as any rom, Hypersense has them, which is why I want to do this. Otherwise, no issues with CM7 and MIUI atm.

Ken
[Nexus One Android Development] blunden:
It is probably the case that they mark compressed executables (using something like UPX) as some generic trojan since it's common for trojan creators to use compression of the executable as a means of obfuscation. You will notice that it's always a very generic name.
[Nexus One Android Development] avgjoemomma:
+1 He's right :)
[Nexus One Android Development] dla5244:
Yes we can!!!

It's so easy to me.

Your idea will be applied to next blackrose.

I will release new blackrose NOV.11(due to exam)

I tell everyone.

"Any idea?"
[Nexus One Android Development] dr1337:
Any way of getting Blackrose to boot Windows Phone 7?
[Nexus One Android Development] dla5244:
Right.

I packed blackrose installer.

Some scanner misjudge blaclrose.exe as virus/troy.

Blackrose installer has not any evil routine.

Trust me.
[Nexus One Android Development] avgjoemomma:
I like the haptic feedback on boot. Can you leave this as the default and provide an option to disable it for those that don't like it?

Is there any way you can enable use of the trackball for using the menu instead of the volume and power button? I think this would be really useful for those with a broken power button :)
[Nexus One Android Development] dla5244:
Oh it's too complicated.

We must execute WINCE kernel and rebuild nand area(except radio area) and so on.

Maybe we have to make new bootloader.

But I don't have much time :(
[Nexus One Android Development] dla5244:
1.OK, I will

2.hmm your opinion is right.

I will analyse hboot more :)
[Nexus One Android Development] samarium:
I also like the haptic feedback. If something is wrong, the more information the better.
[Nexus One Android Development] :
Thanks guys, kinda knew it wasn't, just surprised.

Will flash tonite, after getting musashiken's reply:

"Make sure you installed android sdk and your phone can connect to windows in adb using command prompt. USB debugging has to be enabled on your phone settings."

Will try above method--need adb practice

I'll type adb devices and after getting phone info run a command line with path to blackrose.exe a I described before. It will be in tools.

Ken
[Nexus One Android Development] meechto:
Thank you, dla5244! :) Will look forward to this update ;) But as suggested by someone here please keep it configurable so that people who would like to keep the haptic feedback at boot can do so. Thanks again for this wonderful hack :D
[Nexus One Android Development] intersectRaven:
If it's a simple edit, I can integrate the haptic feedback enabling in SPLHexEditor. (just an idea) :)
[Nexus One Android Development] :
Installin now--I chose the install choice, not update

says please wait.....

how long does it take

i put phone into bootloader then recovery thru usb

then got to type adb devices after typing my tools path, although did not get br to tools. Then saw phone. Br was still on computer.

opened br and followed prompt

it should reboot to fastboot and install, right?

Since nothing has happened on phone, still on recovery screen--maybe pull usb and redo with no command window opened and phone just connected in bootloader mode.
[Nexus One Android Development] efrant:
Not sure what you are doing, but I don't think you are doing it correctly. Do not boot your phone into the bootloader. Just turn on your phone normally and plug it in to your computer. Then run blackrose. That's it.
[Nexus One Android Development] :
ok since phone screen is still in recovery, I am going to kill server and disconnect

then just do as you said
[Nexus One Android Development] efrant:
Not sure why your phone would boot into recovery...
[Nexus One Android Development] :
thanks everyone, gotta run to Columbus and will redo tonite

if it is that easy-wow, i just got confused on all the adb/fastboot stuff that i need to get better at and also posts talking about basic br and partition br/eng br

---------- Post added at 05:18 PM ---------- Previous post was at 05:13 PM ----------

Oops--I put it there to be able to type adb devices in command window. Could not get it to adb devices and show my phone any other way. Didn't type fstboot devices either. OK flashing roms and getting out of touble. Suck at adb/fastboot--:(
[Nexus One Android Development] efrant:
I think you have a mental block... :) There is nothing special or difficult about fastboot or ADB.

Fastboot commands can only be issued to your device if it is booted in fastboot mode (i.e., booted into the bootloader). They allow you, among other things, to flash entire partitions, i.e., fastboot flash recovery <NameOfRecoveryImage.img> will flash the recovery partition with whatever recovery you chose. Fastboot flash system <NameOfSystemImage.img> will flash a new ROM (well the system partition of that ROM). As well, you have to have the fastboot drivers for your device installed properly on your computer.

ADB commands can only be issued to your device if it is booted normally (i.e., booted into your ROM) or booted in recovery. As well you need to have USB debugging enabled on your device, and the ADB drivers for your device installed properly on your computer.
[Nexus One Android Development] :
thanks efrant-there is lots of info on this that I can research and play with to get better--have just been lazy

I was playing around and can get to fastboot devices and phone recognized

but when I type adb devices as I usually did and how you stated--no device found

I think i lost my adb usb driver according to prompts coming up

it was there when i booted to bootloader/recovery and ran adb devices from command prompt before flashing BR hboot and it just said please wait---

i can redo BR as you said by just plugging phone and running BR, but would like to resolve this first

don't know if I should just update sdk revision thru android sdk on pc or find and install driver

searches have not found me corrrect driver yet and when windows wants to do it, it can't find one

so i am on hold for BR

EDIT: got the driver installed and adb devices sees phone--away we go :)
[Nexus One Android Development] musashiken:
Remember, you don't have to get into recovery for adb to work. Just turn on your phone, enable usb debugging in settings>applications>development and plug into your computer.

Only when you need to type in fastboot commands, then you have to go into bootloader and choose fastboot mode.

And I said before you don't have to go into recovery for blackrose.exe to work.
[Nexus One Android Development] :
Thanks musashiken

I am now ready to run BR

But, to understand on adb

If I just plugin phone and open command window the type my sdk path, I can type adb devices and go from there?

I haven't had much problems running commands just was confused on getting into these two modes with little if no practice. Always used terminal emulator since I first usd sdk to unlock and root.
[Nexus One Android Development] musashiken:
Actually you don't have to type adb devices. Just run blackrose.exe. It will automatically execute adb devices to check if your phone is connected.

So just plug in your phone. And run blackrose.exe. Blackrose will open up it's own command prompt window, it will auto run adb device to list your device if it is detected.

But yes, if you want to try adb in normal situations, just go to the sdk tool folder and type adb devices to check if your phone is detected by your computer.
[Nexus One Android Development] :
Sorry,

I didn't pose my question correctly. I understood that and am now S-Off--:D

I was asking if my steps just above are correct for getting into adb for other purposes as efrant mentioned--

I will practice more and start installing and removing things from command window to get better

Doing the partition hboot is another story and will require a lot more reading before I attempt :eek:

Thanks for all the help--:)
[Nexus One Android Development] musashiken:
Ah yes I just realized you have not really used adb and fastboot commands before.

Ok, to use adb commands in windows command prompt, just turn on your phone, enable usb debugging, plug it into your computer and that's it. You don't have to be in recovery to do it, just leave your phone at its homescreen or whatever.

Then you can just adb anything to your phone, like push and pull and list apks in your phone. Usually, in command prompt, you "cd" into your android tools folder and then you type adb commands.

As for fastboot, you need to reboot to bootloader and choose fastboot. Then you will see the word "fastboot" in red and your phone is in fastboot mode. Then you can type in fastboot commands. Of course your phone has to be connected to the pc.
[Nexus One Android Development] :
Thanks again I will practice--:)

Will probably ask again on being correct in the steps to do partition hboot when ready--:)
[Nexus One Android Development] :
Well, got adb/fastboot figured out better. Part of my problem was not having a good path to android sdk/tools.

I can now easily get to either adb or fastboot.

So, I ran spl and partitioned brcust and saved as hboot.nb0 and put in tools folder

Will run following commands in fastboot--from tools--then flash fresh Nightly

1.fastboot flash hboot hboot.nb0

2.fastboot reboot-bootloader

3.fastboot erase cache

4.go to hboot and recovery

5.full wipe

5.update rom

6.reboot

Question is after erase cache, do I kill-server to disconnect from phone. Then go into bootloader (hboot) then recovery on phone, then wipe, flash etc?

BTW: I did 155/51/rest data Any problem there?

Appreciate all the help, if this works on CM7, I will run HyperSense 2.0 per OP page which requires Blackrose,

Ken
[Nexus One Android Development] avgjoemomma:
If you're flashing the latest CM 7.1 nightly then you just need 2MBs for the cache partition. Enjoy!
[Nexus One Android Development] musashiken:
Yes once you erase the cache, you are done. Just do the power button + volume button to reboot straight into bootloader and go into recovery. Just full wipe and flash rom as per normal.

Do note that if you want to flash Hypersense 2.0, you need to repartition again using the nb0 file that the hypersense developer has. It will change your system to 330mb to fit in the whole rom.
[Nexus One Android Development] rjmohit:
Need help

I had a small query actually. Will your method of flashing hboot work on other devices if I just replace the hboot files with the ones of the target device.

For example, if I wish to flash an unsigned hboot file on an S-ON or S-OFF Desire S, can I just replace the files in your package with the unsigned hboot files of the device and rename it to hboot_blackrose.nb0, etc as given in your package?

Pls guide me with this. I wish to downgrade my hboot by flashing an unsigned (even signed will do for now) hboot file on my other HTC devices (My Desire S and my friend's Flyer).

Thank you. :)
[Nexus One Android Development] :
Thanks again musashiken,

I do understand the new partition sizes on HS 2.0. I'll just have to reflash mine when going back to CM7/MIUI.

I just thought to disconnect from fastboot/adb you had to adb kill-server, then proceed.

This is getting pretty easy after everyone's help--:)

---------- Post added at 03:48 PM ---------- Previous post was at 03:47 PM ----------

Thanks

I use MIUI also, have to re-read posts--thought that needed more cache

Ken
[Nexus One Android Development] musashiken:
Actually I never bother with adb kill-server. I just close the command prompt window and plug out my phone after I'm done with any adb stuff. I believe you only kill-server when adb commands do not respond and need a way to reset adb.
[Nexus One Android Development] :
You are probably right,

I think one time when I was done , I did not get ok to disconnect on pc. So, researched and found the kill-server. But, closing the command prompt may be like closing my window that comes up when displayng sdcard content on pc thru usb. I'll try that next time.

@dla5244

BTW: Thanks for allowing me to get a little off-topic too figure this out. Great hack and as soon as I get thru it all--will buy you some coffee. Besides if I get to Eng hboot and splash screens, may need more help :)

Thanks to IR also :D

Ken
[Nexus One Android Development] dla5244:
No. :(

Only works on N1 hboot 0.35.0017

DesireS is not compatible.

To works on DS, it needs to make 'new door' :)
[Nexus One Android Development] rjmohit:
Okay, thanks! :)

Can you tell me how to make that door? Pls guide me.
[Nexus One Android Development] samarium:
My guess is the first step is to extract and disassemble the existing hboot and understand the functions you will need to hack. This is nothing simple like repartitioning or installing a new recovery or ROM.

If you are asking the question you are asking then you don't understand the scope of the problem, and you need to do much more reading and experimenting with your own hboot before you can ask good questions.
[Nexus One Android Development] :
I have now flashed the HyperSense rom with HS Modified BR Hboot--very smooth and trouble free so far. This was the reason I wanted BR. So, thanks again dla5244 and everyone else who helped me figure out fastboot/adb.

One question: I saved my custom partition hboot from here to tools folder, but saved it as nbo and not nb0. Realized that when I couldn't flash the HS hboot using nbo--:o

When I went to rename it said if I change name now it may not work--true/false?

Ken
[Nexus One Android Development] meechto:
That's probably the Windows warning. You get it no matter you try changing the extension of any file. I think renaming it to nb0 should work ;)
[Nexus One Android Development] :
Thanks, didn't think about it being ext. Don't normally change them, just bu names on sdcard--:)
[Nexus One Android Development] jbbandos:
Depends on which MIUI - on mine you can get along with 2MB cache, as I've added the same script as CM has to move the cache if the internal partition is too small.
[Nexus One Android Development] :
Thanks,

I run the latest MIUI-Dev or Nightly. But haven't had any partition/memory issues with MIUI or CM.

Just wanted this hboot to run HyperSense. And has worked great, no reboots/fc's/touchscreen issues at all.

ken
[Nexus One Android Development] dla5244:
If you are using MIUI with 2MB CACHE Partition,

It need to change download folder

su

rm /cache/download

ln -s /data/local/download /cache/download