yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] frankyyy02:
Stuck

Posted in the ICS forum previously by mistake:

Hi all,

I'm a little stuck, would be great is someone could help.

Have a rooted but locked bootloader N1 and just flashed Blackrose successfully. I then flashed the update partitions from the first post.

Now rebooting i am stuck on the N1 X boot logo. Have restarted after about 10mins, still the same. Cannot access recovery... just stuck on the N1 X.

Please help ?

Any advice please ???
[Nexus One Android Development] Pr0fess0rX:
What will I lose if I installed "BLACKROSE HBOOT"?

Am I going to lose the stock HBOOT for ever?
[Nexus One Android Development] :
fastboot oem unlock

---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------

No you can flash back with splhexeditor

Read thru thread it is all there
[Nexus One Android Development] jbbandos:
Hi, I tried to update blackrose to 111217_2 on linux, and the upgrade went well. However, I am now unable to flash a custom hboot, it always gives me "FAILED (remote: signature verify fail)". I created the custom hboot with BREdit, and I wanted to increase system to 220MB and reduce cache to 5MB. I've also tried with 15MB cache, but I always get this error.

In the end, I tried running fastboot myself ("other/fastboot-l flash hboot binary/hboot_brcust.nb0") but also had a signature verify fail.

Can anyone help?
[Nexus One Android Development] dla5244:
Did you set password?

if you changed partition layout, full wipe is needed

Check your hboot version(7.35.5017) and security status(S-OFF)
[Nexus One Android Development] MarkM83:
Heeelp.

Installed BR

Made 145-2-rest

Went to recovery, wiped data, dalvik, all i could find, and flashed cm253 nightly..

Now stuck at X ?????
[Nexus One Android Development] :
pull battery

what recovery you using

did you confirm your changes took by rebooting and verifying br version

you should wipe system and all 3x, maybe format sd with sdformatter

but, why change cache to 2--i run nightlies all the time and have no issues with stock boot sizes--using dt
[Nexus One Android Development] MarkM83:
Forgot step 3 and 4 :S

Ups, forgot step 3 and 4...

I saw it in the video OP.. he went 145 and 2, so i thought it might be good ?
[Nexus One Android Development] :
did you get it sorted then
[Nexus One Android Development] MarkM83:
Yeah:-)
[Nexus One Android Development] frankyyy02:
I did try that and it said 'no need to unlock', however, i'm not already unlocked and have never seen a padlock while booting. While flashing BR i selected that i am not unlocked. Is it blackrose that is returning 'no need to unlock'?

Thanks.
[Nexus One Android Development] efrant:
If you have Black rose flashed, yes there is no need to unlock, as Blackrose enables booting and flashing images via fastboot (which is essentially what you are getting when you unlock).
[Nexus One Android Development] frankyyy02:
Thanks for that - that explains it.

I just managed to fix the issue. I reflashed the recovery img again for AmonRa.

Once that completed i managed to boot into recovery successfully and proceeded to wipe and flash the img again.

Many thanks.
[Nexus One Android Development] :
confused franky

are you still stuck, i could not get to recovery one time and copied the stock hboot to my tools folder and fastbbooted it, then reboooted bootloader. i had thought i lost recovery, even tried to fastboot a new one to no effect. eventually i got it back.

br can't unlock you, i think you need to get back to stock hboot, restore a good rom, then use the regular command window to unlock. then do br again.

hope someone else has a better idea if you can't get it going
[Nexus One Android Development] frankyyy02:
Hi,

No i did manage to get it going. I tried the oem unlock only because of previous advice. But as BR is flashed it did nothing.

Flashing recovery img again fixed the issue.

Then flashed custom rom.

Thanks for the help.
[Nexus One Android Development] :
so you are up and running with no br and still locked
[Nexus One Android Development] frankyyy02:
No BR is installed, but since oem unlock did nothing i am still locked as well. Bootloader shows BR is installed with black line up top.
[Nexus One Android Development] :
i didn't think you could install br with a locked bootloader

helped one guy who couldn't install it till he fastboot oem unlock, then all went well

guess i was wrong
[Nexus One Android Development] frankyyy02:
Yep, when you run the Blackrose.exe and you select install, it asks if you are locked or unlocked. You select unlocked, then it asks you to select from 2 r.secure values. Follow that and it installs correctly.

Didn't have an issue installing BR, it was just that once i did that couldnt get past the X.

Maybe it was an issue with the fact that i am still locked that caused it.

P.S. Not sure if it makes a difference but i am rooted, though not unlocked.
[Nexus One Android Development] :
ok since i am wrong on needing to be unlocked on installing br better give up advice:)

are you going to unlock--and have you tried to fastboot a custom br

---------- Post added at 04:43 AM ---------- Previous post was at 04:42 AM ----------

ok, i guess since i am unlocked, or installed an older br it never asked me those things
[Nexus One Android Development] frankyyy02:
I won't unlock unless i need to and now i actually don't see the need with BR.

I am currently running the custom partition from texasice http://xdaforums.com/showthread.php?t=1366897

Actually thinking back, it may have been after installing this custom partition that my N1 went belly up and i had to fastboot the recovery img.
[Nexus One Android Development] :
well glad you got it working

i don't remember the exact details of my recovery issue, just that i stumbled thru fixing it--:)
[Nexus One Android Development] frankyyy02:
Hehe make that two of us :)
[Nexus One Android Development] jbbandos:
Thanks, for some stupid reason I had set it S-ON some time ago and forgot it.
[Nexus One Android Development] ctfrommn:
Did you ever run into device not running when you tried installing this? I cannot seem to get this installed and that seems to be the issue.
[Nexus One Android Development] :
ctfrommn,

no issue installing after efrant and musashiken set me straight on how to do it. i am running ics and that may have played into the recovery issue

i know you are more versed on fastboot and adb then i am, so as long as you can use them in a command window and your device is seen--it should not be an issue--not talking about blackrose command window, just the regular one

i think you did this if i remember your posts, but i--

downloaded blackrose installer to my download folder

extracted it to the Downloads\blackrose_11217 folder path

that was the default path that came up

opened that folder and then clicked on to open the BlackRose.exe icon, the one with the picture to the left of it, not the white icon

up came the blackrose command window and selected install and followed prompts

reboot to bootloader to see changes

i don't use the br installer to flash the custom hboots, i fastboot them by extracting the zip and resizing with splhexeditor, saving and putting in my tools folder. if you use the installer to install a custom hboot, need to extract, resize and copy to the binary folder inside the extracted blackrose_111217 folder, name it hboot_brcust.nb0, then the br installer will see it

assume you also have an unlocked bootloader, although i guess that isn't critical, thought it was--:confused:

don't know if all this helps, maybe it will help someone else if not
[Nexus One Android Development] ctfrommn:
You definitely know more about adb and fasboot than me as I have never used either. I rooted my phone using superoneclick and my bootloader is still locked. I did everything you stated but I am getting a device not responding error. Because my bootloader is still locked, which option should I select when it asks 0 or 1 for ro secure value?
[Nexus One Android Development] :
that is a couple posts back by the individual who installed br being locked, franky

post 561 area, not sure which value myself

see post 554 also by efrant
[Nexus One Android Development] ctfrommn:
So I found my ro.secure value, but when I try to install BR it is saying error:device not found. Everyone makes this sound like a simple process but it has been anything but for me. Any advice from anyone would be appreciated.
[Nexus One Android Development] szihs:
$adb devices

In fastboot mode BR executable displays "Device not found",

Solution: Boot into recovery OR (re) boot your device and then retry.

(as soon device shows up in adb devices, you're ready to go )

Also i think you can either do via fastboot manually. (2nd post in this thread talks abt it i guess)
[Nexus One Android Development] ctfrommn:
When I try to type adb devices in command prompt, it says adb is not a recognized command. I will try to boot in recovery and give that a go.

Thanks
[Nexus One Android Development] :
i have no more ideas, sorry

are you s-on atm

maybe the way you rooted has something to do with it

do you have ALL these requirements met from OP page

REQUIRE

Windows PC or Linux PC

USB Debugging(ADB) ON

Connect USB before install

HBOOT 0.35.0017

ADB and Fastboot USB Driver - Windows

http://www.mediafire.com/?bhxmn903d6cz9eg

HBOOT 0.35.0017 Package(flashable zip)

http://android.clients.google.com/pa...-0.35.0017.zip

---------- Post added at 08:33 PM ---------- Previous post was at 08:03 PM ----------

Also i think you can either do via fastboot manually. (2nd post in this thread talks abt it i guess)

that's for a custom rom, not the installer

ctfrommn, also, although i don't think you do--blackrose installer adb doesn't work on Sense roms--need htc sync
[Nexus One Android Development] efrant:
Seems to me that you likely have one or both of these issues (both NOT Blackrose related):

1) You do not have the drivers for your device set up correctly (there are 2: one for fastboot mode and one for ADB).

2) You are not in the right directory when you open a command window and issue commands.
[Nexus One Android Development] :
efrant,

that was my thought since he said he never used fastboot or adb before

does that mean he needs to install android sdk and set it up or is there a way around that if only using br installer and editor--others probably interested also

with what lies ahead for the n1 I would do that and unlock--be easier in long run

with your previous help I am using fastboot and adb a lot more and it is getting easier, almost think it may be quicker to flash roms with fastboot than recovery

ken
[Nexus One Android Development] ctfrommn:
I have SDK tools installed, I am not sure if the drivers are set up correctly, but it does recognize my device as a N1 and not just generic usb storage. I am opening the main Blackrose.exe and following the directions given, but I suspect adb is the issue here as cmd prompt does not recognize that command.
[Nexus One Android Development] efrant:
Doesn't necessarily need to install the SDK, but he needs to install the drivers (which are part of the sdk, but are also in the file you linked to).

I agree with you though: unlock, and set up the sdk properly and you will most likely have less issues
[Nexus One Android Development] :
I don't know what path br looks for in using adb

for me I need the fastboot and adb exe in my tools folders along with the adbwin dlls all done when setting up sdk if done correctly. and the environmental path set in windows.

also recently and don't know how, my adb.exe got moved out of tools. found it in another android sdk subfolder and moved it back. that is one reason i had issues setting up br

the later sdk versions I think use platform-tools instead of tools

i think it will work after getting adb sorted
[Nexus One Android Development] ctfrommn:
Well, good news is I am getting closer with everyone's help, now I am getting hboot install errors instead of device not responding. Looks like various read/write errors. I will try to get further info. When/if I get this installed will I be able to use my current backups as long as I don't change the partition size?

Update.....success installing BR, now have to see if I can boot.

Update 2....Booted fine, thanks for all the input, what is next? If I re partition for ICS can I flash the stock partition back easily?
[Nexus One Android Development] dburg84:
Edit: It did not brick me following the resizing tutorial. However it did not resize.
[Nexus One Android Development] cyberon:
Where you able to do that without loosing data?
[Nexus One Android Development] boqonx:
Using the image on post #2?
[Nexus One Android Development] intersectRaven:
If the image on post #2 works, you should be able to retain the data by going to recovery BEFORE flashing the modified SPL, deleting cache partition, backup (CWM 5.0.2), flash modified SPL, then restore the backup. Since the recovery now sees the modified partition sizes, it should restore properly. (well at least with CWM 5.0.2) :p

*I haven't tested the SPL method. I'm just basing it on my own MTD command method since the concept is the same although if the modified SPL works, it would be simpler to do. :)
[Nexus One Android Development] dburg84:
Yes. I followed post 2 and the image. All system/userdata was there after restore.

EDIT: Hmmm... well it did not brick me but this is what df -h reports. Let me try it again.

# df -h

/dev/block/mtdblock3 145.0M 113.4M 31.6M 78% /system

/dev/block/mtdblock5 196.3M 155.1M 41.2M 79% /data

/dev/block/mtdblock4 95.0M 41.3M 53.7M 43% /cache
[Nexus One Android Development] cyberon:
Wich recovery you used?
[Nexus One Android Development] dburg84:
I am on cwm recovery. The latest rom manager installs.

Anyway I tried again without restoring system/data/cache. Basically just followed post 2 without backing up. I am getting the same result as posted by me above.

I will try a full wipe then flashing the hboot. Hopefully that will work. Maybe the recovery must be modified as well?

Edit: after full wipe I get the same result. doesn't appear to be resizing.
[Nexus One Android Development] boqonx:
I flashed #2 as well, it didn't get resized either..hboot re-partition solution is cleaner, since we don't need to fiddle with the kernel nor the recovery.
[Nexus One Android Development] dla5244:
thank you for testing

I am noticed that nothing changed.

I made mistake and tested new repartition blackrose

As a result, i succeed in repatition.

I will update soon.

ps.you can repartition without modify kernel command line and use fastboot flash,erase command(compared with intersectRaven's custom MTD)
[Nexus One Android Development] dla5244:
I posted how to repartition
[Nexus One Android Development] rjmohit:
How about we just resize the cache partition to its 1/4th size and give the extra to /data w/o touching the system partition in the stock layout. I heard some apps (like games) require a minimum of 20MB of cache to function properly. Also everything we download thru market is downloaded in the cache partition. If this is re-sized to a very low value (~5MB), downloading big apps will be a problem.

So I would suggest the following layout:

145/25/266
[Nexus One Android Development] kaiser_tytnii:
looking forward to repartitioning! thanks a lot!

---------- Post added at 11:36 AM ---------- Previous post was at 11:35 AM ----------

Cache to SD-EXT will solve it no?
[Nexus One Android Development] rjmohit:
We dont have cache to sd-ext, its dalvik cache to ext, which is a different thing altogether.

The problem of files being downloaded to cache can be solved by changing some values in the ROM, but then it becomes ROM specific and we are looking for a general solution here. :)
[Nexus One Android Development] cyberon:
That being true, i agree, currently my MIUI uses 128/2/170 so i purpose:

145/30/261

Thanks
[Nexus One Android Development] daveid:
CyanogenMod uses the cache partition for the systems dalvik cache, currently on my device that is 50M, there needs to be sufficient space for that or major problems will occur.
[Nexus One Android Development] kaiser_tytnii:
Maybe I was not getting this right but my Desire has been using CM7 Partition for a long time, as layout on Alpharev (130/5/302), maybe we need MTD version of CM7 for Nexus 1 specifically?

I don't think that's the case since there is only 1 version of CM7 for Desire (Brovo) for Stock Partition and CM7 Partition
[Nexus One Android Development] AdamOutler:
Disregard.. I read wrong..
[Nexus One Android Development] dla5244:
I would upload custom partition blackrose

but I don't have much times.

so i posted how to repartition.

sorry.
[Nexus One Android Development] PhaseBurn:
I assume you've seen http://n0rp.chemlab.org/android/nexus/hboot-0.33.2012.img (0.33.2012) that I dumped already, but I will post 0.33.2017 when I get home on Tuesday (BBQ time this weekend) as requested after I dump it from my Nexus One
[Nexus One Android Development] uoY_redruM:
Man, if you could create something that repartitions for us, instead of us doing the steps ourselves, that would be phenomenal!
[Nexus One Android Development] :
Great News

I don't use the br editor as mentioned, but think that is how you now resize back to stock

otherwise the stock hboot is in the binary folder within the extracted br installer folder

I still think if you use br to flash back to stock or another hboot you may have modified with splhexeditor on OP page the hboot must be in binary and renamed hboot_brcust.nb0

i do all mine with hexeditor and fastboot thru sdk
[Nexus One Android Development] ctfrommn:
So any Android I currently have will not work with new partition? Or do I just need them to fit in the correct size partitions?
[Nexus One Android Development] :
you won't be able to restore a nandroid created with different sizes than this one

you will need to resize to its layout with br editor or fastboot

OP has a video on resizing--but, like I mentioned I prefer splhexeditor and fatsboot

so haven't used the editor

but, again--the resized custom hboot you want to install needs to be in the binary folder named hboot_brcust.nb0--unless something has changed
[Nexus One Android Development] ctfrommn:
I am wondering why anyone would flash a custom partition when you can create one via the editor in a matter of moments. Seems like that is a lot easier. So if I do a fresh install of a non ICS rom on the new partition size then the created backup will be able to be restored? I think I will go that route if true. I am very curious to try the A2EXT on the new version.
[Nexus One Android Development] efrant:
As long as they fit, you should be OK.

Are you sure? I think you can, as long as the backed-up partitions fit in your current partitions.
[Nexus One Android Development] dla5244:
You can install blackrose with no issue even you have locked bootloader.

Also I recommand BREditor than SPLHexEditor because BREditor can change title label while SPLHexEditor can change partition size only.

As far as i test, all function is worked well.

If you face any problem with blackrose, let me to know :)

Edit: about restore backup image

142 -> 220 O

194 -> 150 X(if backup image size not exceed 'want size ', you can restore)
[Nexus One Android Development] ctfrommn:
That makes much more sense, as I have all my apps on sd, I should never have a space issue with ICS partitioned nand. Thanks for clarifying.
[Nexus One Android Development] :
I was thinking of HyperSense were you have a very large System and only 50 data, some folks had some problems in the past.

Also, some devs made special hboots for there roms again like HyperSense and I didn't know if they had anything else special in them.

ctfrommn--when some of the special ones were made we didn't have br editor--devs just made them for the users

Also, I just realized after some research the adb and fastboot exe's are in the binary under the Other folder which eliminates sdk--just need the drivers

Hope this is all correct--just my take--
[Nexus One Android Development] ctfrommn:
Gotcha, editor seems like the better option, looking forward to trying this.
[Nexus One Android Development] :
did you watch the video on op page

after watching it again may try it myself

just promised myself I would improve on fastboot and adb
[Nexus One Android Development] pseudoheld:
i tried installing blackrose 6 times via BlackRose.exe, but i keep ending up with the standard hboot and not the custom 7.something blackrose hboot.

any ideas?`

everything is setup correctly as far as i can tell.

im on the right hboot, blackrose recognizes my phone straight away, i have the usb drivers installed. it just doesn't seem to flash the custom hboot.
[Nexus One Android Development] nealed:
Hey pseudo - I had the same - when I entered the command fastboot reboot-bootloader I got back to standard hboot - on second attempt it installed the custom hboot - so don't know if that helps or not...

Oh and if you're running vista / win 7 - make sure you run blackrose as administrator
[Nexus One Android Development] happyassshit:
noob question

How can I check the size of my system partition.

Not sure if the procedure was successful...
[Nexus One Android Development] taney:
# df

df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 207508 32 207476 0% /dev

tmpfs 207508 0 207508 0% /mnt/asec

tmpfs 207508 0 207508 0% /mnt/obb

/dev/block/mtdblock3 225280 142564 82716 63% /system

/dev/block/mtdblock5 205056 2848 202208 1% /data

/dev/block/mtdblock4 16384 1176 15208 7% /cache

/dev/block/mmcblk0p2 984248 459488 524760 47% /sd-ext

/dev/block/mmcblk0p2 984248 459488 524760 47% /data/app

/dev/block/mmcblk0p2 984248 459488 524760 47% /data/app-private

/dev/block/mmcblk0p2 984248 459488 524760 47% /data/data

/dev/block/mmcblk0p2 984248 459488 524760 47% /data/dalvik-cache

/dev/block/mmcblk0p2 984248 459488 524760 47% /cache/download

/dev/block/vold/179:1

14263384 4712440 9550944 33% /mnt/sdcard

/dev/block/vold/179:1

14263384 4712440 9550944 33% /mnt/secure/asec

#
[Nexus One Android Development] pseudoheld:
win7 - check

run as admin - check

still aint working

i'm using the BlackRose.exe did you do it via adb?

might be my only chance left then....
[Nexus One Android Development] dla5244:
Check your adb and fastboot driver

If you fail to install with unlocked method, try to install with locked method
[Nexus One Android Development] Franc38:
I'm trying to install and all I ever get is a message saying windows cannot access to the device, path or file and that maybe I don't have the corresponding autorisations...

Drivers are OK, I see my phone when I run adb devices,

I've tried runing blackrose as administrator...

I've got no clues what to do now... Another way of installing? Using adb? I'm not too used to this, having mostly done stuff directly from the phone terminal...

my bootloader is "apparently locked" (doesn't show the open lock) since I've used (I don't remember the name) method for getting root in the first place...
[Nexus One Android Development] pseudoheld:
tried with the locked method and it worked fine...but now i have s-off...would have been nice to know that this would make me s-off and not leave me at rooted s-on :( :( :(
[Nexus One Android Development] efrant:
How else do you think you'd be able to flash an unsigned bootloader to your device? :confused: If you don't like it, you could always flash back the stock bootloader.
[Nexus One Android Development] earth08:
How to get back to original (stock) hboot

Pls guide
[Nexus One Android Development] pseudoheld:
well it aint quite like that now is it...

the bootloader wasn't locked. i had full root and recovery. i just unlocked it by a method that shows the bootloader as "s-on" which is nice to have for warranty. i still had full access to everything.

if i now flash back to stock im pretty sure i will still be "s-off" thus having voided my warranty.

im not complaining about blackrose doing this im just saying it would have been nice to have a warning somewhere saying "if you do this you will be "s-off" do you wish to continue?!" thats all. as it is there was no way to know that this would happen...