Related
I have a T-Mo G1 that had CM 4.1.11.1 on it and I was looking to upgrade to the newest stable, 4.2.1, using CM recovery 1.4. Something went wrong while upgrading so I decided to unroot the phone. I've read many guides on rooting and unrooting, but something just doesnt seem right to me.
1. When I return to rC29 should Telnet be downloading automatically? Does this mean I still have stored info somewhere in there?
2. When performing tasks in CM 1.4, such as flashing, it prompts me to reboot so I do it. Should I be returned to the recovery screen again after boot every time? I don't remember this happening before...
3. Which update.zip do I use when unrooting, the 177kb (droids on skateboards) or 205kb (red, green, blue, white) file?
4. Can someone give me a guide to unroot and fully wipe with CM 1.4?
Any help is appreciated, thanks alot.
I'll give you the steps to unroot which should answer your questions
1) Flash the stock SPL (the tri colour one). If you have 1.33.2005 (AKA Danger) SPL and you do downgrade to 1.1/RCx YOU WILL BRICK.
2) Flash the RC29 DREAIMG.nbh from the SPL - boot in to it by holding power and camera (it should be tricolour). Telnet should not magically be there, even if it was, doesn't matter
3) Put a recovery image of your choice on the root of the sdcard as 'recovery.img'
4) Flash the recovery image
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
After that you can flash the 26I radio then a 1.5/1.6 ROM.
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
*Double post fail*
mrnv45 said:
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
He wants to re-root I believe, so not point updating.
RC29 and RC7 aren't root enabled ROMs, they just have security flaws which can be exploited to flash root enabled ROMs. Updating doesn't matter...
Thanks for your help, I'll be able to try this in about a half hour, will report back. As you said after step 4, I will need to flash a "26I" radio?
Had to install Telnet manually. Good to see a sign of normalcy here.
Flashing 26I Radio, HTC Recovery 1.6, and CM 4.2.1. Flash Radio, reboot, HTC, no reboot, CM 4.2.1, reboot. Right?
Tried the above, also tried with a reboot in between the HTC flash and CM 4.2.1 flash, stuck at G1 screen.
I'm still stuck at the G1 screen.
Probably be me next.
Finding myself having to do the same thing, somehow doing the CM 4.2.1.? whatever the last one was. I managed to lose root, be really nice to have a second card right now having to move 8 gigs off and repartition it to make it see the R29 image so i get to do literally everything all over again.
As someone once said, Ah Linux! Its Free! assuming your time is worth nothing. So true, lol. well ill be even better once it all works, if i can figure out what it takes to make it all work ill come back and try to help you out. Looks like mine wont see the image cause of my multi-partitioned microSD card. Not sure if yours is like that too or not, something to think about.
virtually painless
Kind of like virtual reality i guess?
Only gotcha i found in going back and reinstalling the RC29 image back on to be able to reclaim root was that my SD card having being partitioned. would cause it to fail. I would hit the tri-color screen, see a real quick gray flash and a message that vanished as quick as it popped up and then i would be stuck back on the colored screen.
So, i backed up the whole card, followed by
removing all data from the card. then running fdisk /dev/sdg. deleting the 3 partitions, writing a filesystem to the root of the disk via mkfs.vfat /dev/sdg , copying the 5 required files over and proceeding to get root and then recreating the paritions and copying data back over.
Back up and running.
mrnv45 said:
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
Thanks XDA - have to do a TMo warranty exchange and this helps greatly.
Hello!
I followed this guide and read the comments of everyone, and it's a reliable guide to rooting and installing a new ROM. The rooting went perfect, so I decided to go further and load cyanogen's latest ROM.
Power off your phone.
Boot into recovery mode. (Press and hold the Home key, then hit the power button).
Before you flash a rom file, perform a wipe. Press Alt+W to wipe the data and cache folders. You must wipe when going form different builds of Android.
Wait for the wipe to finish and the recovery image to display again, then select “apply any zip from sd”. Flash the zip file of your choice.
After flashing any zip you should be able to reboot your system and watch it load to the home screen.
After changing Android builds, it came take several minutes for the first boot. If you phone hangs on the animated Android logo, this is because you did not perform a wipe. If you are stuck in a boot loop, return to the recovery image and make sure you wipe.
Click to expand...
Click to collapse
-Taken from the guide
At the first time I rebooted it took me back to recovery, so using logic I rebooted again and now it is stuck at the T-Mobile G1 screen (the one before it normally shows the android)...
I know it's supposed to take several minutes.. but 30minutes is ridiculous -.-"
Can somebody please help me out before I do something stupid and remove the battery? Thanks so much..
You need to read a bit more then, because you would have learned that you have to install the 1.6ADP fro Htc before installing a cyanogen rom, that is one of the things you would know if you followed the guide in his thread...
-Best Regards
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
tk112190 said:
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
Click to expand...
Click to collapse
You have to listen to cyanogen plus that might be a different rom like enom or something.Cyanogen has a different maybe tricky install method.
You need to goto his thread.
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-XXXX
-put them both on your SD card
-Boot up into Amon_RA recovery by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
-Then update any zip usig CyanogenMod (update-cm-xxxx-signed.zip)
-Then reboot the phone
Thanks a lot man.
I found the 1.6 ADP file and I have it downloaded onto my computer. Is there anyway I can put this on my SD card? It won't let me.. :/ If I could somehow get this on there, run it.. and THEN run the cyanogenrom.zip I think it could work again?
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
Thanks a lot for the help, I really appreciate it.
I took your advice and did those steps and it rebooted me into recovery like you commanded. I plugged it via USB into my computer hoping that the computer would recognize it and let me put the file on the SD card - but to no avail.
What is the next step I can take?
http://code.google.com/p/sapphire-port-dream/
I loaded the radio first...
and then I loaded the SPL...
and then I loaded the ROM...
I didn't go out of order. Was the problem that I didn't have the 1.6 ADP on my SD?
@Ace42: If I get a card reader and add the 1.6 ADP (signed-dream_devphone_userdebug-ota-14721.zip) to my sd card.... and load it. Can you tell me what to do from there?
Do I load that zip and then reload the ROM?
You may want to try Dwang1.13 rom. I don't think his rom requires the extra step to get the google apps.
Ok, so I have read through all of the posts I can and still cannot revert to stock.
I was playing with some different APKs and accidentally rewrote the AccountandSyncSetting apk with one from another device. At that point my NC rebooted and went into a boot loop. I eventually was able to get to recovery to restore factory settings, but after that completed it continued to boot loop. I have installed Nookie Froyo on an SD card which boots, however I get an SD card error, you may have to reformat. (nookie froyo is still usable, just no SDCard to mount) I have the stock files that I need to fix the device, however I cannot figure out how to do it from Nookie Froyo. Will someone please walk me through this.
thank you
I did this and I am still in a boot loop... please help
http://forum.xda-developers.com/showthread.php?p=10599116#post10599116
There are two different resets. Power+n (hold around 30 secs to boot) (data) and 8 failed boots (system). Do those two and your set.
Sent from my HTC Desire using XDA App
samuelhalff said:
There are two different resets. Power+n (hold around 30 secs to boot) (data) and 8 failed boots (system). Do those two and your set.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How do I get it to 8 failed boots... just turn it off each time it starts looping?
Yes. Once the Nook tries to boot up unsuccessfully 8 times, It reinstalls the factory settings during the 9th time.
Solution:
All that you need to do is create a bootable clockwork mod sd card:
http://forum.xda-developers.com/showthread.php?t=922870
Then download the system and boot images from here:
http://forum.xda-developers.com/showthread.php?t=919353
Install ADB:
http://forum.xda-developers.com/showthread.php?t=910008
- ADB is a command line interface to your Nook.
Mount your Partitions (except sd) using ClockWork Mod (easy to find in the Nook ClockWork menu)
Get that system.img/boot.img file to your internal partitions:
Open your comand prompt. Browse to the folder with adb.exe using the cd command. (If you're on Vista or Higher you can shift+right click on the adb folder's background to get the option "open command window here".)
Type adb push "path to system.img file" / (eg.adb push "C:\Users\Name\Desktop\system.img" /). The last slash tells adb where to push your system img to. Also, this takes a few minutes 5-10.
Type adb shell, or adb.exe shell if the first doesn't work.
You'll just get a # symbol after that.
Type dd if=system.img of=/dev/block/mmcblk0p5 (dd - writes image to a location, if=input file, of=output file.
You can do the same with the boot.img just make the of=/dev/mmcblk0p1 for your dd command.
Also go ahead and format all of the partitions (except for sd anything) using clockwork mod before you use dd to write your img files to your partitons.
I think that should work to restore your system partiton.
If you have trouble getting it to boot, what works for me is holding all of the buttons for 10 seconds...3 times. And that usually makes it boot off of the microSD. That's probably the same as n+power, but idk.
dfellars77 said:
How do I get it to 8 failed boots... just turn it off each time it starts looping?
Click to expand...
Click to collapse
Actually, if you wait for the looping logo to start, you've waited too long. you want to hit the power button, then hold it down to start the restart as soon as you see the "n" logo to power it off. it will only trigger the auto reset after eight consecutive reboots that dont make it past that first "n" logo.
You could also do the reflash methods mentioned in this thread or in the dev threads, if you're up for something more intense. just be sure to take out the SD card when you're done flashing, or else you will boot back into whatever recovery you are using.
Thanks everyone. CWM is up and running and once I have a solid charge I will take another go at it. I have been having a heck of a time getting ADB to work properly on my machine (although it works fine on my Galaxy S). I think I just need to uninstall the Mass Storage Driver each time I connect and manually install the NOOK ADB driver. I will try some of the Dev tools recommended above and report back.
Thank you for the help (and at the very least nookie froyo works and has a better linpack score than my rooted stock!)
SUCCESS!!!! I can finally close all of the tabs I have open. In the end I had to run the dd commands through ADB while Nookie Froyo was running, but it all seems to have worked!
Thank you for all of the help.
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
douglaspott said:
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
Click to expand...
Click to collapse
How long did it just sit there? Starting up a new ROM the first time sometimes takes a few minutes or more. It it's not rebooting itself, let it sit and load.
maybe
douglaspott said:
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
Click to expand...
Click to collapse
more info is needed to help you. What steps did you take EXACTLY? get long winded. Like what root method, what recovery, what wipe process, what flash process, etc.
Okay...I used Z4Mod and went with a permanent root (seemed to be successful)...I grabbed the free version of ROM manager from the mkt place...I then flashed Clockwork Recovery in ROM Mgr...Finally, I selected "Install ROM from SD Card." A prompt showed up and I selected "Backup Existing ROM" and "Wipe Data and Cache." After checking OK, it rebooted and froze on the HTC screen for 15+ minutes two times. I have two zip files on my sd card: "update-cm-6.1.0-RC1-Heroc-signed.zip" and "gapps-mdpi-20101213-signed.zip" This is as far as I could get...thanks!
Well when you chose to backup existing rom that was good. When you chose to wipe data that was bad. Now your phone can't boot into anything because you wiped all of your data. But you were smart and made a backup. A general rule of thumb at least IMO
Is only wipe data if your flashing a new rom or having trouble with an exiting one. With that being said. Just boot into recovery by
Holding home and power until you see your recovery
Then look for an option that says install update zip from sd or update from sd. I don't use clockwork mod but I'm sure its something to that effect. Then choose install from sd or what ever the option was. Then you should see your two rom zips on your sd choose which one to install,let it finish and reboot. Being a fresh install it might take a minute. Or if you want to go back to your factory rom just look for an option that says restore and choose your backup you made when you used rom manger. Hope this helps good luck.
Yea its me Again With the
Modified Hero-
douglaspott said:
Okay...I used Z4Mod and went with a permanent root (seemed to be successful)...I grabbed the free version of ROM manager from the mkt place...I then flashed Clockwork Recovery in ROM Mgr...Finally, I selected "Install ROM from SD Card." A prompt showed up and I selected "Backup Existing ROM" and "Wipe Data and Cache." After checking OK, it rebooted and froze on the HTC screen for 15+ minutes two times. I have two zip files on my sd card: "update-cm-6.1.0-RC1-Heroc-signed.zip" and "gapps-mdpi-20101213-signed.zip" This is as far as I could get...thanks!
Click to expand...
Click to collapse
Instead of installing from ROM Manager, select the option to Reboot Into Recovery.
From there, select Wipe Data/Factory Reset, then select Wipe Cache Partition, then go into Advanced and select Wipe Dalvich Cache.
Once those steps are complete, go back to the main menu and select Install zip from SD Card, then select Choose zip from SD Card. Find the CM zip and select it.
Once it completes, select Install zip from SD card again, find the gapps zip and select it.
Go back to the main menu again, and select Reboot now.
That's an old build of 6.1 anyway, grab the "stable" release instead.
Thanks for all of your assistance. Where can I find a current, stable 6.1 download file? I will replace it on my sd card before going forward.
Also, how do I get to the boot/recovery screen? When I choose recovery, it freezes with the HTC screen...I have success getting the phone back to original when I select fastUSBboot, or something similar to that...
Trying powering off, then press and hold the Home button while you press and release (don't hold) the Power button.
If that doesn't work, try pressing the volume up button while pressing the Power button.
Turn off the phone and hold volume down and power. A white screen will appear from there press the home button. It will take a good 15 to 20 seconds to get into recovery. Are you waiting long enough???
Or power off phone and hold power and home untill it boots into your recovery remember it takes a few seconds 10 to 15 seconds
Yea its me Again With the
Modified Hero-
I selected the home key to get into recovery...after 10+ minutes of showing the HTC screen, I think there is something wrong. This goes back to the same issue when I originally attempted to install the CM ROM - it was supposed to reboot into recovery but instead restarted into a frozen HTC screen. What ele can I do? Can I just go back to original and try all over again? I had to take the battery out and reset the device...
After Fastbooting, I lost network access and can't get into the marketplace...When I go into ROM manager to restore the backup, it just sits and looks like it is working on it...How long should this take? Is 10 min too long?
So your able to boot into your rom right.??? So just go to rom manger and choose flash alternate recovery. Place a different recovery on your sd and flash it. Or just flash the clockwork recovery. Basically I think you need to get into recovery first.
Yea its me Again With the
Modified Hero-
I think you're right as far as getting into recovery being the key...Since my network is down, I had to try "Flash Alternative Recovery," but it showed "An error occurred while flashing your recovery" ...Is there another alternative to getting a new recovery installed?
My network connection just started working...I had to uncheck and recheck the connect to network...Clockwork recovery finally worked and I was able to install 6.0 and the Google apps...Thanks for all of your help! I do have one additional question - How do I set up my apps to store on the sd card instead of the internal memory? Thanks again
I'm having a similar issue as OP.
This is my first time trying to load CM7 on my Hero CDMA. I rooted my phone successfully and then installed Amon_Ra's Recovery (v1.6.2) and wiped the data/Dalvik-cache and then flashed CM7 and Google Apps. Everything seemed to install without problem.
However, when I reboot the device it doesn't get past the initial "HTC" screen.
I then attempted to use adb to look at the logs but when I boot into recovery mode and enable USB mode, the computer doesn't recognize an HTC device/serial:
c:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
000000000000 recovery
and trying to access the logs or run shell commands through adb fails.
It's been stuck on the "HTC" logo for 10 minutes; I'm not sure if I just need to wait it out or if something has gone awry. Did I just brick my phone or can this be salvaged?
I managed to flash whatever I had backed up from nandroid, but it's incredibly unstable. Took several resets and almost an hour stuck on the "HTC" splash screen before booting. I have missed calls and can make them, which is a good sign, but I'm repeatedly hit with an error "The application Setup Wizard (process com.android.setupwizard) has stopped unexpectedly. Please try again.".
I can't post pastebin links since I'm new, but I have dumps of logcat and /proc/last_kmsg.
At this point I'd be happy to either get CM working OR revert back to a stable stock ROM.
How did you root ???
Also what's your baseband/ radio ??
Also what hboot are you currently on ??
Root-Hack_Mod*Always\
I needed to have a phone so I took it back to Sprint and they were able to do a factory reset. So while I'm glad it's not bricked, I'd prefer to have a better ROM on here.
I rooted using the following set of commands:
adb push asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
Firmware version 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d [email protected]
Build number: 1.56.651.2 CL85027 release-keys
Software version: 1.56.651.2
Hardware version: 0002
I'm not sure how to find out the hboot version.
When you first rooted or before did you make a backup/nandroid ?? Also after you rooted did you flash a recovery ??
Root-Hack_Mod*Always\
Hi all, I wrote a long-winded Tutorial to put Evervolv KitKat on a stock N1. I don't have a stock N1 (I stumbled all the way through this process and got done yesterday, was so excited I wrote this tutorial) and don't know how to get it back to stock, so I'm wondering if anyone who has one and has experience putting new ROMs on other devices would like to test this out and let me know if anything doesn't work as written. Please go ahead if you like and reply your updates! Once it's dialed I'll make it a thread in the N1 ROMs forum.
Here's the text:
How to put KitKat on a Nexus One (And have computing power & space to spare):
Things you'll need:
1. A Windows/Linux computer with internet connection, USB port, and terminal
2. A USB Cable
3. A Nexus One with the most recent stock gingerbread rom (Settings->about, look for Android 2.3.6 or GRK39F, else apply/google updates to get to that version)
Before you begin, note that you're playing with a generally safe form of fire, but when playing with fire, you may brick your phone. The maker of this guide and any sites you visit during the process assume no responsibility, the user assumes full responsibility for lost work and damaged or ruined phones. Your warranty will be voided about six times over. Save all your stuff somewhere, save apps with Titanium Backup (Google it) or something, and do a full Nandroid backup (Goog that too) before you begin. You will be fully wiping your phone and SD card multiple times. Make sure at every step of the process that your battery is at least half full. Running out of battery during an update can cause bricks. In this guide, “Boot” means standard boot, the way it normally turns on. Not hboot or fastboot or recovery.
I did part of this from a Windows7 computer on Cygwin and part on Ubuntu 12.04, each presented some annoyance but by far the greatest was due to my Linux ineptitude with PATH and Root. If you're trying the same, I've made an appendix for that.
It may help to have a brief conceptual overview of what you'll be doing in case you run into snags and have to step out of the walkthrough. Your N1 has a few basic parts: Internal memory that is chopped into 3 partitions: One for the system files (System) , one for the files that they will need to make during the first bootup and use in order to operate, along with your apps and their created files (Data) and one for temporary files that your OS and apps can regenerate (Cache). Somewhere in there it also has space for a Radio (that also includes some critical power functions, flashing a new radio is the easiest way to brick an N1 but we won't), as well as a Recovery partition and an Hboot&Fastboot partition. We will be messing with Recovery and Hboot. The virtual machine that turns all the friendly pseudo-english computer code into 1s and 0s for the processor to deal with is called Dalvik, named after a town in Iceland where some old dev's family is from. It has its own Cache (the VM, not the town, as there are no longer any fish in Iceland ). It's SOP to wipe Cache & Dalvik before and after applying any updates, and wipe Data (Factory reset) before applying most updates. Sometimes when my phone bogs I reboot to recovery and wipe caches just for funsies. This makes it take longer to boot the phone and to use each app just the first time after that, while the files are created fresh. The phone also should have an SD-Card. You should have or buy an 8+MB, Class 10 SD card. The class relates to read/write speed, anything less than 10 will noticeably slow your Nexus One's operation. Why?
Because we're going to put some of your operating system on the SD card. We're going to use a special recovery system (aka recovery ROM) called “4ext” to partition your SD card. Mine is 16GB, partitioned to 14GB for storage and 2GB to use as fake internal memory, where my system's Data and Cache live. The KitKat System files that normally live on internal memory's System partition are too big for a normal N1, so we'll use a special Hboot called BlackRose to repartition your internal memory so you can fit KitKat, and then after you first boot it up we'll use an app called Mounts2SD to install a startup script so that every other time you boot it up after that, it will know to find Data and Cache on the SD card. In order to install BlackRose, you'll need to be running CyanogenMod Rom as your main OS, and in order to do that you'll need ClockWorkMod Recovery ROM. So the installation order will be: ClockworkMod recovery->Cyanogen7OS (Gingerbread based)->4ext recovery to partition SD card->BlackRoseHboot to repartition internal memory->Evervolv KitKat-based N1 ROM-> run Mounts2sd for startup scripts ->reboot to your new life among the anatomically modern cyborgs (and then you're on your own for getting all your apps and music and contacts and stuff back on the phone from wherever you saved it).
Ready? Here we go!
1. Install the Android SDK on your computer.
1. Get the appropriate version here: http://developer.android.com/sdk/index.html
2. Unzip it.
3. Run the setup.exe (if using windows)
4. When asked which packages to install, choose “Android SDK Tools”, “SDK Platform Android 2.1″, and “Usb Driver package” (If you use eclipse, check that last link for instructions on using the ADT plugin (Not the same ADT that cuts your paycheck, much less inept))
5. Make sure the USB drivers installed properly (windows).
1. Go to printers and devices in the control panel, or device manager
2. If you see an android device with no warnings, you're golden. If it has warnings, right click it and go properties->update driver (driver can be found in your android sdk directory where you unzipped the sdk bundle, in \usb_driver).
6. Boot up your N1 and plug it in to the computer. If the computer recognizes it and they play nice, you're set with the sdk. To extra check, open terminal and cd to the sdk's platform-tools folder that should contain the adb utility. Type #adb devices and see if it comes up with a message telling you that it's running a daemon on a port like 5037, and then lists something like HT9CPP800063 device. This is your phone, it's telling you you're beyond connected. You've got the sdk working. Else have your friend Google help you get the SDK properly installed.
2. Root the phone so it will let you dig in.
1. Put your N1 in USB debugging mode (Settings > Applications > Development > USB Debugging)
2. In the terminal, in the platform-tools folder, type #adb reboot bootloader. (((My phone has a power hardware issue and will not reboot while plugged in ever to any mode ever at all ever, if yours does too you can unplug (first type #adb kill-server to make it ok to unplug) the usb cable, power down, wait five seconds, and hold the trackball and power button to power back up into the bootloader, then plug in again. There was a lot of unplugging, waiting fifteen seconds, booting while holding buttons, plugging in, adb devices -ing that I will omit henceforth due to low likelihood that you have the same problem.)))
3. Using the onscreen directions on the phone and the hard buttons, navigate to fastboot mode. It may be unresponsive and throw some not-found messages for five seconds before it lets you do anything.
4. In the terminal on your computer, in the platform-tools folder, type #fastboot devices to see if your devices is connected (it should come up with the same HT#XXX###### number).
5. This step will gain Root access, unlock the bootloader, and WIPE ALL YOUR ****. Now type #fastboot oem-unlock . You may have to accept the warranty voiding. If for whatever reason it doesn't work, use this method http://code.google.com/p/bexboot/, and unzip the files to the platform-tools folder.
6. Using the phone buttons, reboot. Your little lock logo during the bootup should be unlocked now.
7. Power down and boot again for good measure. Re-enable usb debugging in the phone app dev settings.
3. Get ClockworkMod Recovery.
1. Download koush's ClockworkMod Recovery from : recovery-clockwork-5.0.2.0-passion.img and put it in the platform-tools folder.
2. To make sure the file is not corrupted and will not brick your goods, check the md5sum. This is the result of a complicated equation that easily reveals even a single flipped bit in the file by vastly changing the output. Google how to do this, in windows you'll need to download a tool like winmd5free. The output for this particular file should be: md5: 45716c8d51ed2375873f01f0b14b2184 If it's anything else don't use it.
3. Reboot to the bootloader again, either by #adb reboot bootloader or by powering up while holding the trackball, and navigate to fastboot.
4. Verify that you're connected with #fastboot devices
5. Flash ClockworkMod Recovery by typing #fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img
6. It should give a success message. Reboot to recovery from the fastboot menu. It should be a sweet new blue and white ClockWorkMod recovery. Power down and reboot to recovery by holding volume up as you power up, just for good measure.
4. Get CyanogenMod7 ROM.
1. On your computer, go to http://download.cyanogenmod.org/?device=passion&type=stable and download the latest stable CM7 zip. Put it in the platform-tools folder.
2. Check its md5 as you did in part 3.
3. Do #adb-devices, which should give you that serial again, and the word recovery.
4. Place the zip file on the root of your SD card by doing #adb push cm-7.2.0-passion.zip /sdcard/
5. If that last step failed, try running #adb shell mount /sdcard or #adb kill-server then #adb devices then #adb shell mount /sdcard, then try the push again. Or mount the sdcard through the recovery menu before running that push command. Or use your computer's file system to drag and drop the .zip to the root (lowest) folder of the sd card.
6. Using the recovery menu, in backup and restore options, backup your current ROM.
7. In the format menu, do a wipe data/factory reset. Wipe the cache and dalvik cache while you're at it.
8. Back in the main recovery menu, do install zip → choose zip from sd card.
9. Select that CM7 zip file.
10. Return to the main menu and reboot the system. It should come up with a totally different looking leaner meaner version of Gingerbread, that gives you more control and speed and saves battery. But even with this system, given modern app sizes, you'll soon run out of room on the internal memory if you stop now. And besides, you're having too much fun.
5. Get 4EXT recovery
1. Go to 4ext.net and download the free .apk file: http://www.4ext.net/get.php?apk Congratulations if you're about to install your first not market app (apps are now .apk, not just something you get from the store's GUI.). Save it in platform-tools. Or, to be really nice to Max, you can just buy the app in the play store and skip the next two steps.
2. Enable USB debugging, plug in and #adb-devices.
3. # adb install 4EXTRecoveryUpdater.apk. You should get back a success message in a fistful of seconds.
4. At this point you may need to back out to regular settings, turn on wifi, and hook up to your wifi router.
5. Open the 4ext recovery updater app. Go to settings. Allow superuser permissions and everything else. It should detect Nexus One, connect to the internet, and boot you back to the main menu.
6. Go to online install. They're all release candidates and no stable versions, so just go with the newest one. Select install.
7. Wait for it to finish and then reboot to recovery, either by # adb reboot recovery or manually. You should have a beautiful new touchscreen recovery.
6. Partition your SD Card
1. In recovery, go to tools->partition sd card->remove all partitions and start from scratch.
2. For the first Ext partition, where you'll be keeping a good chunk of your OS, The consensus online is not to go above either 1.5GB or 2GB. I'm working fine with 2GB aka 2048MB.
3. You can skip the 2nd Ext partition.
4. The internet says Swap size should be 0.
5. Internet says File system should be ext4. This should do the partitioning, the rest of your SD card will still be great for storage as before.
7. Repartition internal memory using BlackRose:
1. I have never used BlackRose on Windows, but here goes: go here : http://forum.xda-developers.com/showthread.php?t=1270589 and download this zip archive: http://forum.xda-developers.com/attachment.php?attachmentid=1016437&d=1334971685; It has windows and linux files. The site also has a manual in case this walkthrough lets you down.
2. Unzip it into a folder in your platform-tools. Execute it with a ./ in linux or a .exe in win. It should say waiting for devices.
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
4. Blackrose is rumored to have an interactive guide to partitioning, but it didn't work for me and at least some other genius on the internet, but being an industrious Austrian, he figured out the fix: Run Blackrose in Editor mode. Type resize as prompted.
5. The post here http://forum.xda-developers.com/showthread.php?t=2540366 on Evervolv KitKat implies that 250MB for System works with enough space for Gapps (Google does not allow their standard apps like Play Store to be included with Mod roms anymore, so you will need to install them from recovery too, but they distribute them bundled so it's not hard.), and some commenter said 260MB, but that didn't work for me long enough to run startup scripts and move some of it off. So I had to redo it and I went with 265MB for System and 10MB for Cache, which is working fine. Give it a name, I went with Kat.
6. BlackRose will shut down, but it will leave a golden turd in the form of a file called hboot_brcust.nb0 probably in the folder called “other.” That's what you want.
7. Put that file in the same folder as the Blackrose utilities fastboot-l and fastboot-w if it's not already there. Then boot your phone into fastboot again, via adb or manually. I think. Maybe try this from being standard booted up if the next part doesn't work.
8. Run # fastboot-l flash hboot hboot_brcust.nb0 . Windozers should use fastboot-w instead. Blackroot will wait for the device again.
9. Reboot your phone into the bootloader manually, by holding the trackball while powering up. The image should install on this boot, resizing your phone's internal memory partitions.
10. Run # fastboot -w. Your Bootloader should be loaded up, with the 1st line saying something about BlackRose and the 2nd line saying 265/10/161. This is how you know it worked. That 265 is where it's at for KitKat. Your main OS had been destroyed, but your Recovery ROM should still work.
8. Install Evervolv KitKat.
1. Go here http://evervolv.com/devices/passion and download the latest stable release. At press time that's the 4.0.0p4.2 version. Save it to platform-tools.
2. Reboot to Recovery from the menu in the BlackRose bootloader.
3. Do # adb devices. Then do # adb push ev_passion-4.0.0p4.2-perdo-squished.zip /sdcard/ . If it doesn't work, try using the touch recovery menu to toggle mount USB, then push, then unmount. Or mount USB, use the computer's file system to move the file to the root of the sd card, then unmount USB. Or try as root if you're using linux.
4. From the main recovery menu, select install zip from SD card → choose zip → select the ev_passion-4... zip. Wait up, it could take a while.
5. Success!! Right? Right. #adb kill-server, you can unplug now and won't need to plug back in! Reboot the phone, you're getting perilously close! This boot could take five plus minutes, or just one, but be patient.
9. Install Gapps.
1. You are such a lucky dog. Gapps bundled updates are available through the Evervolv toolbox. So you can get Play Store and everything else will come easy. Go to settings → wifi, turn it on, hook it up to your wifi router.
2. Back up to settings, and go Evervolv Toolbox → Updates and swipe over to the Gapps section. Tapp the most recent Gapps-kk zip. Tap the down arrow to download.
3. Reboot manually to recovery.
4. From the main recovery menu, select install zip from SD card → choose zip → select the gapps-kk... zip. This could also take a sec.
5. Reboot again! You're almost done! When it's all loaded up, Play Store should now be installed, as well as various google options that you can enable through the Evervolv settings.
10. Install Mounts2sd.
1. Go to the Play Store and get Mounts2sd.
2. Hit the top right corner for application settings. You'll need to install a startup script. Agree, give it permanent superuser status.
3. Reboot.
4. Go back into Mounts2sd, and go to the Tool menu (Wrench). Note that boxes aren't checked unless they're green-checked.
5. Enable the Cache to move cache partition to data or sd-ext. Storage threshold is up to you. Make sureApplications, Libraries, Data, and Media are all checked. Dalvik should stay unchecked, System apps can too.
6. Reboot again.
11. You're done!!! Or at least we're done. You still have to restore your apps and put all that music back on and figure out how to resync your contacts and... Good Luck.
12. If you want to get extra tricky, it's believed to be possible to leave app data on the real internal memory by default, and use Titanium Backup to move the data of most of your apps to the SD-ext, thereby leaving the data of your favorite apps on real internal memory. Use at your own risk.
ENJOY!!
Appendix 1:
Linux PATH env: I put all my android stuff in a file called androidy, so my path to my platform-tools was /androidy/adt/sdk/platform-tools, and my blackrose was in there too. So to set my PATH, I used: $ export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sean/androidy/adt/sdk/platform-tools:/home/sean/androidy/adt/sdk/platform-tools/blackrose_120421/binary"
In order to make sure that while using it as root (as was necessary for some fastbot operations), I referenced the same PATH instead of the messed up root PATH, I used sudo env PATH = $PATH a few times.
Appendix 2:
The only actual bug I've noticed in a few days with this ROM is that my Chrome bookmarks don't add shortcuts to the homescreen when I tell them to from within Chrome. The widget-adder (longpress homescreen) has a bookmark option though, so if you bookmark it you can put it on the homescreen from there.
Huge Thanks to everyone involved with ClockworkMod, Cyanogen, 4Ext, BlackRose, and Evervolv!
Sources:
http://wiki.cyanogenmod.org/w/Install_CM_for_passion
http://nexusonehacks.net/nexus-one-...n-how-to-unlock-bootloader-on-your-nexus-one/
http://marian.schedenig.name/2012/07/22/installing-android-4-ics-on-the-google-nexus-one/
http://forum.xda-developers.com/showthread.php?t=2540366&page=24
Wooooh, Amazing book ! Everything is soo.... deep. In my opinion, tutorials should be only few lines.
Some mistakes :
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
In my mind, big steps should be :
1) Backup SD, and SMS and Apps
2) Root
3) Install recovery (TWRP is advised by evervolv, but CWMRecovery is OK)
4) Partition SD
5) Install Blackrose (using 260mB system)
6) Flash ROM
7) Flash GAPS
8) A2SD Y N Y
Notes :
About SD-Ext size, i recommend reading this post from his creator : http://forum.xda-developers.com/showthread.php?t=1716124
A2SD is an old version of INT2EXT+
Using terminal is not friendly for beginners. Avoid it at maximum.
Provide a link for a MD5 sum checker.
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
ldFxl said:
In my opinion, tutorials should be only few lines.
Click to expand...
Click to collapse
This tutorial doesn't need to exist at all. All the information is available elsewhere on the internet, I did nothing original. Its only value is that it puts all the information in full detail in one place so you don't have to look in the forums for elaboration on each line of a more concise tutorial. Hopefully with info this detailed, someone with more chops than me could script it.
ldFxl said:
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Click to expand...
Click to collapse
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
ldFxl said:
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
Click to expand...
Click to collapse
4EXT is also touch, CWM cannot repartition SD. If you can go stock to TWRP this might be the best option. Or if not, stock to 4ext.
ldFxl said:
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
Click to expand...
Click to collapse
Yes! Thanks.
ldFxl said:
Using terminal is not friendly for beginners. Avoid it at maximum.
Click to expand...
Click to collapse
Don't you have to use terminal to use the built in A2SD? At any rate, it didn't work for me (I'm kind of a beginner), Mounts2SD's GUI seemed a little more beginner friendly. Also I certainly wouldn't have been able to make BlackRose work
ldFxl said:
Provide a link for a MD5 sum checker.
Click to expand...
Click to collapse
Good idea
ldFxl said:
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
Click to expand...
Click to collapse
I once used SuperOneClick on another phone, it looked like it struggled and finally worked with a DDoS style attack, it seemed simpler to just do it the way the manufacturer intended (if that's even a thing). But I suppose if it works with one click it really is simpler as seen by the user. Anyone have a report on whether it worked from stock N1?
Fituate said:
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
Click to expand...
Click to collapse
On my first flash, i was pretty beginner, so i followed a tutorial ; ) . And they used CWM. But flashing a recovery procedure from .img file doesn't differ with the recovery. TWRP allows you to partition SDCard. I did it last week (on HTC wildfire S, TWRP 2.6 as for N1).
Flashing step is the same -> just replace img file name. You can get it Here (From official TWRP Website)
Procedure from TWRP Website said:
Download the above file. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fasboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
6. Partition your SD Card
1. In recovery, Tap Advanced
2. Tap Partition SD Card
3. Set 2048 (MB max) on EXT Size and 0 on Swap Size
4. Tap EXT4 then swipe to start partitioning
Fituate said:
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
Click to expand...
Click to collapse
Backrose is a custom Bootloader-> it replaces your HBoot/Fastboot
You don't need to reboot your phone to install blackrose. You just need your phone in ADB over USB, then the win setup will install blackrose.
Once done, run setup again, your phone will automaticaly go to HBoot, then choose 1, and 1 again.
Then enter "resize", "260" and "8".
In case that the installer don't work correctly, you can get flashable HBOOT from [Provide a nb0 (texasice recommend 260/8/168) AND MD5 Checksum]
While googling to find some infos (I don't remember me unlocking my bootloader) I found this guide : http://forum.xda-developers.com/wiki/HTC_Nexus_One/Flashing_Guide
Apperently SuperOneClick does not even need unlocked bootloader on 2.3.3 or previous ...
Isn't what we are trying to write down ?
There are many links pointing to this forum aswell.