FORUMS
Remove All Ads from XDA

[how-to] Install CM6 on Nexus One (SLCD version) with HBOOT 0.35.0017

16 posts
Thanks Meter: 0
 
By cestbibi, Junior Member on 17th September 2010, 10:55 PM
Post Reply Email Thread
Ok so I decided to put this up together because it took me two days of forum searching to gather the different bits and to understand what was happening.

Update: see the complete wiki here : http://forum.xda-developers.com/wiki...ecovery_Images

This applies to some latest N1 stock models as such:
MODEL: Nexus One (SLCD version)
HBOOT: 0.35.0017
RADIO: 32.41.00.32U_5.08.00.04
BUILD: FRF91

WHAT YOU WILL GET :
- Root without unlocking your bootloader
- Successfully Install Recovery
- Successfully Install CM6

WARNING: This method worked for me, It should work for you in the same conditions. If you intend to install a moded rom over your stock N1 , you are supposed to know what you 're doing. I can't be held responsable if you brick (not likely) your phone, break-up with your lover or witness a nuclear explosion.

----- Since I'm a new subscriber, ALL links in the guide don't work , just paste them in your browser -------
A- Root your phone
Get latest Universal Androot from (blog.23corner.com/tag/universalandroot/) install the app and follow the instructions.
This has the benefit of rooting your device without unlocking your bootloader and thus NOT voiding your warranty.
B- Install Recovery.
Since you got an S-LCD device you can't use the default Clockwork Recovery (for example if you install Rom Manager). If you do you'll end up with a black screen when rebooting into recovery and will not be able to go on to proceed to flashing the Rom.

You need to get Amon_RA Recovery v1.8.0.1 (I think v1.8.0.0 also works)
you can get it here : (alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img)

Since you didn't unlock the bootloader I believe you can't use the fastboot commands to flash the recovery, so it's a bit tricky but you have to install it with another method :

First you need to have Adb installed in your computer.
follow this guide: (forum.xda-developers.com/showthread.php?t=690362)

First save the file flash_image (get it here benocharm.lensworks.org/flash_image) to the root of you SD card

1) also put the recovery-RA-nexus-v1.8.0.1-aw.img to the root of your SD:

- next unmount the SD put keep your phone connected to the USB

2) Open a terminal prompt (if you do Windows type "CMD") and navigate to your adb "Tools" folder, type "adb shell" and hit Enter (don't write the quotes "" from now on)

3) On the terminal write "su" and hit enter
- Caution: At this point your phone should ask you permission to use the SuperUser app (if it does not you have to allow it specifically)
- Now on your terminal window the "$" symbol should change to a "#"

4) Still on the terminal, write "mount -o rw,remount /dev/block/mtdblock4 /system" and hit Enter

5) on the terminal, write "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter

6) on the terminal, write "chmod 775 /system/bin/flash_image" and hit Enter

7) on the terminal, write "flash_image recovery /sdcard/recovery-RA-nexus-v1.8.0.1-aw.img" and hit Enter

8) on the terminal, write "rm /system/etc/install-recovery.sh" and hit Enter

9) on the terminal, write "rm /system/recovery-from-boot.p" and hit Enter

10) Next: type exit + Enter till you get out of Terminal

You'll find that maybe steps 8 and 9 give you an error because the files don't exist, so don't worry anyways.

Now you should be set,
next, reboot the phone holding the Power button on + volume down and go into
recovery to see if anything went OK.
C- install CM6
Get yourself the latest Cyanogen ROM.

Since your phone has got HBOOT 0.35.0017, if you try to flash CM6 from recovery, it will give you an error and fail.

This is because the update script of CM6 checks for HBOOT 0.33.0012 and fails.

Some people have got a way around this by reverting phone to HBOOT 0.33, (just do a search in this forum if you need this) but personally I prefer a less "destructive" and simplier method.

What you need to do is to get winrar, or another zip/compress tool and unzip the rom.
Navigate to folder "META-INF\com\google\android\updater-script" and open "updater-script" with your favorite text editor.

What you need to do is to comment 3 lines of it:
Almost in the beginning of the script look for this part :

Code:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
assert(getprop("ro.bootloader") == "0.33.2012" ||
getprop("ro.bootloader") == "0.33.0012");
ui_print(" ");
ui_print(" ");
ui_print(" ");

You need to change it so that it goes like this.

Code:
# assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
# assert(getprop("ro.bootloader") == "0.33.2012" ||
# getprop("ro.bootloader") == "0.33.0012");
ui_print(" ");
ui_print(" ");
ui_print(" ");
That's it !
Now repack the rom (CAUTION: if you did unzip it don't zip the resulting folder, just zip ALL the files IN IT, otherwise it will give you an error later)

Next copy the Rom to the root of you phone SD card.

Now reboot into Recovery and flash your Rom.

Welcome to CM6 !!


I hope this will help someone.

Please keep in mind I'm by no means a specialist, and that there are maybe other (better) ways to achieve this (I didn't find them). Also my knowledge of Android is very limited so I won't probably be able to help you if you run into problems following this how-to. I repeat, I did it and worked ok for me.

I will be happy that some of you maybe correct or contribute to what I have exposed if you fell like it.

Cheers
 
 
18th September 2010, 07:06 AM |#2  
Senior Member
Thanks Meter: 49
 
More
Thank you for posting this.

Where did you get an SLCD nexus one from though?
18th September 2010, 09:06 AM |#3  
OP Junior Member
Barcelona
Thanks Meter: 0
 
More
They ship them now in Vodafone Spain
21st September 2010, 01:58 PM |#4  
Junior Member
Thanks Meter: 1
 
More
Has been fixed in the nightly builds.

github.com/CyanogenMod/android_device_htc_passion/commit/6d19e88c86f01b68a206fa27a49bf58567ff255e

I am not allowed to post links, normally just lurk here and post on the CyanogenMod forums.
21st September 2010, 03:55 PM |#5  
Senior Member
Flag Toronto
Thanks Meter: 517
 
More
I'm surprised that ROM Manager still hasn't been updated to include recovery images that support SLCD Nexus Ones.
21st September 2010, 07:27 PM |#6  
OP Junior Member
Barcelona
Thanks Meter: 0
 
More
Quote:
Originally Posted by kibje

Has been fixed in the nightly builds.

github.com/CyanogenMod/android_device_htc_passion/commit/6d19e88c86f01b68a206fa27a49bf58567ff255e

I am not allowed to post links, normally just lurk here and post on the CyanogenMod forums.

Thanks ! good to know

Quote:
Originally Posted by cmstlist

I'm surprised that ROM Manager still hasn't been updated to include recovery images that support SLCD Nexus Ones.

Yes indeed I am surprised too, but I think koush will be working on this sooner or later, tweeted asking for plans about this but no news so far.
21st September 2010, 07:55 PM |#7  
Senior Member
Flag Toronto
Thanks Meter: 517
 
More
I'd imagine it wouldn't be too big a change, seeing as versions now exist which support the SLCD Desire.

Sent from my Nexus One using XDA App
22nd September 2010, 09:50 PM |#8  
Junior Member
Thanks Meter: 1
 
More
Hi!

I'm stuck with a boot partition with bad blocks which prevents me from flashing other custom ROMs than CM6. I read somewhere that the new hboot 0.35.0017 changed the partition sizes so that might help me.
Could you do a
#cat /proc/mtd so I can see if the sizes differ from mine?
22nd September 2010, 10:02 PM |#9  
OP Junior Member
Barcelona
Thanks Meter: 0
 
More
Quote:
Originally Posted by ollegut

Hi!

I'm stuck with a boot partition with bad blocks which prevents me from flashing other custom ROMs than CM6. I read somewhere that the new hboot 0.35.0017 changed the partition sizes so that might help me.
Could you do a
#cat /proc/mtd so I can see if the sizes differ from mine?

Ok so that's what I get:
Code:
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 000e0000 00020000 "misc"
mtd1: 00400000 00020000 "recovery"
mtd2: 00380000 00020000 "boot"
mtd3: 09100000 00020000 "system"
mtd4: 05f00000 00020000 "cache"
mtd5: 0c440000 00020000 "userdata"
good luck !
22nd September 2010, 10:20 PM |#10  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by cestbibi

Ok so that's what I get:

Code:
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 000e0000 00020000 "misc"
mtd1: 00400000 00020000 "recovery"
mtd2: 00380000 00020000 "boot"
mtd3: 09100000 00020000 "system"
mtd4: 05f00000 00020000 "cache"
mtd5: 0c440000 00020000 "userdata"
good luck !

Great! It looks like they grew the boot partition

Guess I should try updating to a ROM with the new hboot that's rootable...

Thanks for the help!
22nd September 2010, 10:39 PM |#11  
OP Junior Member
Barcelona
Thanks Meter: 0
 
More
A very concise but complete Wiki has been updated on this matter courtesy of Jack_R1

h**p://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images

**damm I still can't embed links**
Post Reply Subscribe to Thread

Tags
hboot 0.35.0017, nexus one, slcd

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes