Related
I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
So far, this is going to be a guide for noobs. Please read through this, and ask any questions that you have. This has been compiled from different guides around XDA, and information has been stripped that does not relate to our phones. More will be put up here when I find it, and all credit will be provided. This will be from 'duh' to 'didn't know that'. The idea is to provide a beginning to end explanation: Stock Incredible to Rooted with custom Rom.
Topics so far - ADB, Rooting (reflash), Unrooting, Nandroid, Remove/Install Apps, roms, kernels...
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE DOING ANY OF THIS.... REGARDLESS OF WHY. Yadda, yadda, yadda...
**********At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done).**********
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Now, we get USB drivers to work. Some use HTC Sync for drivers, however HTC Sync does not like to play nice with the reflash tool (later on this), so we will use the generic google USB drivers.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.
============================================================
2) Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
============================================================
3) Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in:
cd C:\**your sdk name**\tools (Press Enter)
adb devices (Enter) You should see your device listed
adb shell (Enter) you should see $ in the next line
**After you obtain root**
su (Enter) you should see # in the next line if you are already rooted
**you may need to allow adb shell to run as root. Look at the phone and see if Superuser.apk is asking for your permission to allow adb root access. Click on "Remeber my selection" and select yes.
Now you are all set to run adb commands as root or as a regular user
**Note: for a list of commands that you can type using adb type "adb" in cmd
All Credit for Topics 1 - 3 go to user XDA member nephron. I mostly copied all of his guide, but updated some information on it to make sense for our phones. Also, removed some stuff I didn't see necessary. Please go to the original thread for the G1: http://forum.xda-developers.com/showthread.php?t=532719&highlight=nandroid+guide for a list of further Credits, and for information I've left out. If you like this thread, please donate to HIM
============================================================
4) Rooting your phone - READ THIS WHOLE SECTION BEFORE GOING TO ANY EXTERNAL LINKS PLEASE. At this point, running the UnrEVOked reflash3 tool will root your phone and install a custom recovery. To try to make it really easy to understand, recovery allows you to access your phone to make PERMANENT changes (something we can't do while booted yet), flash custom roms, and save your sorry little @$$ if you do something that you weren't supposed to
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it), and that you have the Google USB drivers installed (i.e. you read at least some of this post). The first thing we're going to do is:
1) Read this: http://forum.xda-developers.com/showpost.php?p=6875912&postcount=1
2) If you read #1, you already went here: http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
and downloaded the MODIFIED (i.e. changed, not the same, DON'T SKIP THIS STEP) driver and installed it
3) If you read #1, you already downloaded the reflash tool executable
4) If you read #1, you've already done #2, and 3, and this is just a worthless step of me explaining how important it is that you did #1
5) Lets do this. #1,2,3 and 4 were "get ready" steps. By now, you installed the modified driver, went to the webpage and downloaded the UnrEVOked3 reflash tool. HTC sync is also uninstalled. Plug in your phone (normally booted) to your pc and select "Charge Only" when asked how to connect to PC, and click on "remember my selection". Click Done.
6) Unplug Phone from PC.
6a) If you have double twist installed, at this time open the task manager on your pc, and kill doubletwist.devicehelpder....
7) Run the "reflash_package" executable that you just downloaded. Notice the path that it lists and click "install". This will unzip "reflash.exe" and a bunch of other stuff that is needed to the directory that you just noted. Go to this directory (usually the same one where the executable you just ran is) and run "reflash.exe"
8) Plug in your phone.
9) When the program is finished, you should see koush's clockworkmod recovery on your phone's screen and reflash will say that it's done. Congrats, you have root and a new recovery.
If something went wrong, and you're not on koush's recovery and reflash says it's done, don't worry, just re-run reflash. You can run it as many times as necessary. It will not hurt anything AT THIS TIME (this may change later)
10) Koush's recover works a little differently:
a) Vol+ and - scroll up / down
b) the Power button work as a "Back" button, and will turn off screen if you're at the root of the menu. If your screen goes blank, don't read, just hit Power again
c) To make a selection, click the optical trackpad
11) Reboot your phone by highlighting the selection and choosing it
For the most part, these instructions were written from memory, but all credit goes to UnrEVOked, Shadowmite, and anyone that they've given credit to in original links.
============================================================
5) Unrooting - I didn't want to re-invent the wheel, so I'm posting an external link:
http://androidforums.com/all-things...ideo-howto-unroot-incredible-downgrading.html
Just follow the instructions. Credit goes to the OP. If this link ever goes to a 404, pm me and I will find another link with instructions and update this. Also, if you don't understand something, just ask in this thread, someone will answer (maybe even me ).
============================================================
6) Whats is a Nandroid Backup?
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
Nandroid Backup is a tool allowing your Incredible that has koush ClokworkMod Recovery to create a full system backup and restore it, which, when flashing and testing different roms can be very useful.
A) Creating a Backup using Nandroid
Boot up your phone in recovery (Turn off, then turn on while holding Vol- and Power. Press Vol- once to highlight recovery, hit Power once to go into it)
You will now see your new koush recovery
Scroll down (Vol -) to "nandroid" and select it (press the optical button in)
"Backup" will be highlighted. select it
Let it work, it might take a while for a full system backup
Once its done, your backup is complete and is saved on your sdcard in the "clockworkmod" folder. Normally it's stored in the "nandroid" folder, however our Recovery does things a little differently.
B) Recovering to Your Nandroid Backup
Make sure u made a backup and its in the clockworkmod folder on your sdcard
Boot up your phone in recovery (Explained Above)
Go into "nandroid" in the recovery (also explained above)
Select "restore backup" and select from the backups you have (if you have multiple) that you want to restore; this will do a simple, "restore all" of your latest nandroid backup
:OR:
Select "Advanced Restore", choose from the backups that you have on your SD card, and then what you want to restore. You can individually restore "system", "data", "cache", etc....
In "Advanced Restore", i have not seen a way to restore multiple options (cashe AND system, etc...) Koush, am I missing something?
Let it work
Once its done, restore more options through the Advanced Restore menu, or reboot your phone and your selections will now be restored!
============================================================
7) Remove Apps
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Go into Clockworkmod Recovery (With phone turned off, Vol - + Power, then Vol - to select recovery, then hit Power)
2) Select "partitions" from menu, then select "mount sytem" You can also "mount sdcard" if you want to back apps up to sdcard
3) Connect Phone to PC
3a) Open a command prompt and navigate to your sdk\tools directory
3b) Type: adb remount (it shoud return successful)
4) Open Adb Shell on your pc (Type: adb shell)
It should automatically show #, otherwise type "su"
Type:
cd /system/app (enter)
5)Type ls (this will show you all of the stuff in the /system/app directory)
6) To "delete" apps, type the following:
/system/bin/mv Your_APP.apk Your_APP.apk.bak (i.e. CityID.apk CityID.apk.bak). If you want to clear up space on your internal storage for whatever reason, you can replace Your_APP.apk.bak with /sdcard/Your_APP.apk.bak (this will move the app to the root of your SD Card instead of just change it's name)
If you don't get errors, you're done.
*This does not delete apps, but changes their file type so they will not show up as an app, in case you want to get them back at any time later you still have them and don't have to frantically post threads on XDA asking for them.
============================================================
8) Install Apps to /system/app
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Place your app you want to install into the root of your sd card (this is easiest)
2) Go into Clockworkmod Recovery (Explained in 7)
3) Mount system and sdcard under partitions (Explained in 7)
4) Connect Phone to PC
4a) adb remount in command prompt (should sow successful) (again, in 7)
5) Open Adb Shell on your PC
6)
IF NOT at #, type "su" to go from $ to #.
Type:
/system/bin/mv /sdcard/Your_App_Name.apk /system/app/Your_App_Name.apk
7) If you don't get errors, you're done. You can unplug phone, and reboot
============================================================
9) Flashing Custom Roms
Download a ROM that you want to try. One of the roms from here are a good starting point: http://inc.sodpit.com/. They are mostly stable might get a few random reboots.
Steps:
1. Download Rom of your choice
1a. Right now, there might be two ROM types, a nandroid backup and an update.zip type file. For right now, I recommend sticking with the update.zip kind. These instructions are meant for it, but I just want you to make sure you know which type it is before you try to flash it.
2. Copy and Paste the downloaded file onto sdcard. Make sure it is not in any directory's of SD card, just on the sdcard (the "root" of it).
3. Verify it's there using Astro or some other File Manager just to be safe.
4. Download and Run Titanium Backup from the Market if you haven't already. (If you don't have it, get it, it's must have for root users.)
a. Select Menu, Batch, Backup user apps. (in Titanium Backup)
b. let it run, this will take some time.
5. When that's done open your command prompt, navigate to your sdk\tools directory, and type "adb reboot recovery" (Not within adb shell, but in command prompt in that directory. I'm not going to explain how to do this because it's already explained above. Also, if you're flashing roms then you're already familiar with it, or maybe you shouldn't be flashing roms ).
6. Do "Wipe data/factory reset" and "wipe cache partition" in Recovery **This WILL WIPE your phone**
7. Select "install zip from sdcard", then select "choose zip from sdcard", then select the name of the zip you want to install.
8. When that's done reboot your phone, once your done setting up all the settings, download titanium backup from the market again, and set that up.
9. In Titanium, Select Menu, Batch, Restore User apps.
After that's done you'll have all your apps that you had before, data included, with a fresh new rom to try out. Hope this helps!!
All credit for these instructions goes to tcbert2010, they were suggested to me, and I liked them. I modified them a BIT, so they make more sense to me and hopefully to you. See post #2 in Original Thread = http://forum.xda-developers.com/showthread.php?p=6953608#post6953608
============================================================
10) Installing custom kernels
I'm only mentioning Hydra's kernels. I'm running the Undervolted, NOT overclocked kernel with wireless N to preserve my battery to get more life out of it
**Taken from website's FAQ**
Q: So how do I install the kernel?
A: First step is to either download the kernel zip file straight to your phone, or download it onto your computer and put it on the sdcard of your phone. Next you turn the phone off hold volume down and power at the same time. When the phone is in HBOOT wait a few seconds for it to initialize then hit volume down once and then power to boot into Clockwork recovery. Once in clockwork recovery you want to select "Install zip from sdcard", then "Choose zip from sdcard". You will now see a listing of files on your sdcard select the kernel zip you downloaded, or if you downloaded strait to your phone go to the Downloads folder and select the kernel zip file. The kernel will now install to the phone and once it's done it will say install complete. Now you can hit the power button once to return to main menu and select "reboot system now" . Your phone will now reboot with the new kernel.
***
Go to: http://hydrakernel.net/ to download the kernels
Please read: http://hydrakernel.net/faq.htm to educate yourself. It's worth it.
Credit to EJHEART for the wonderful kernels! Where are my 2.2 kernels EJ ?
============================================================
Again, if you have suggestions, requests, or whatever please post or PM me.
PM Me if I missed giving someone credit. PLEASE!!!
reserved
reserved for future.
Reserved
reserved for future
Great thread topic... reserved for future use
Updated
Updated with Reflash instructions.
dreamersipaq said:
Help I'm stuck at waiting for system to settle
check these common issues:
- You switched your driver to the one from this post? It's NOT identical to the SDK one.
- You don't have any usb applications that might be taking focus while we are working with the phone right?
- Is the SD card present in the device?
- You did give su permenent access when you allowed it in superuser right?
More to come...
Click to expand...
Click to collapse
Good start, iPaq! I just want to plug Linux AGAIN. I had zero problems using reflash for linux and using Gparted in Ubuntu/Debian/Linux Mint mint means one can do all kinds of things that will become helpful very soon if not already (e.g., manipulate ext and swap partitions on the sdacard!). Aside from linux being Android's native file system, using a Linux distro just makes 110% good sense if you plan to do any developing for the DI/Android. Why poeple struggle so much with Windows when Linux is free is beyond me
2 cents deposited!
Additional items to add
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Great topic
Sent from my ADR6300 using XDA App
...
jdmba said:
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Click to expand...
Click to collapse
1) - Will update soon
2) - I BELIEVE that this works:
1) Go into Clockworkmod Recovery
2) Mount Internal Storage under partitions
3) Connect Phone to PC
4) Open Adb Shell on your pc
Type:
su (will change to #)
cd /system/app
mv CityID.apk CityID.apk.bak
you're done.
Not in front of my phone at this sec, but if mv does not work, try
busybox mv CityID.apk CityID.apk.bak or
/system/bin/mv CityID.apk CityID.apk.bak
*This does not delete it, but changes the file type so it will not show up as an add, in case you want to get it back at any time later.
If I'm wrong please correct me.
3) The easiest way to update recovery at this time is through Koush's Rom Manager. However, at this time I've read somewhere that it's not persistent. Let's give this a few days.
Updated
First Post Updated.
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
qwho said:
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
Click to expand...
Click to collapse
Take this opportunity to flash up to HBOOT 79, wipe, and re-root. Start fresh. Re-reflash w/unrevoked2. Alles in Ordnung! At least, that solved all of my problems. Start with the big headache to avoid later headaches. Once you have a nandroid of a "proper" root, you'll never have to do the annoying initial root again.
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
qwho said:
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
Click to expand...
Click to collapse
Exactly. Doing will wipe out all userdata, everything not stored online, on your card, or on internal disk. It's really the best way to go, to start fresh and remove all the little variable piecemeal rooting has placed in your path to date.
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
qwho said:
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
Click to expand...
Click to collapse
Just down this, run it in Windoze, and before it tries to flash (you don't need your DI connected!), go into your AppData/temp directory, find the ~142mb rom.zip file, rename it to PB31IMG.zip, put it on /sdcard root directory, boot into bootloader, let the card/file get picked up while holding down-volume, ok the flash, no need to ok the reboot, then boot into to recovery and proceed with adb shell/rooting process one
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
sanchagrins said:
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
Click to expand...
Click to collapse
Not sure what you mean. Go into Hboot, and select recovery. When Koush's recovery loads, use Vol- to highlight "nandroid". Click the optical button in, and you'll enter another menu. Select the first option, which should be highlighted by default, which should be "Create Backup" or "Backup Device" or something like that.
Let me know if that works.
When I go into recovery the only options I get are:
Reboot System now
Apply sdcard: update.zip
Wipe data/factory reset
Wipe Cache partition
----------------------------------
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
sanchagrins said:
When I go into recovery the only options I get are:
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
Click to expand...
Click to collapse
You can't install anything to recovery that will stick until you get root via procedure 1, then reflash with unrevoked 2. Sounds to me like you've gotten ahead of yourself
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
[Edit]
For those users who need the original "flash_image.zip" file, I have uploaded it and it is available here.
PS: As an added note: **** you Koush! From all of the DS7 community!
Just what was needed
sent from somewhere
thanks but if you would of search there was a thread made already but i am sure the more the marrier
mooch777 said:
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
PS: As an added note: **** you Koush! From all of the DS7 community!
Click to expand...
Click to collapse
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
jiwengang said:
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
Click to expand...
Click to collapse
No its not his fault.. people shouldn't have tried to install the ota update while having cwr installed.. instead should have waited for a zip of the update that hell posted on behalf of did steve. As I have said if you have cwr you really can't get ota updates and install them the normal way. If the update was an update.zip you could flash through cwr but dell uses pgk files not zip.. so the only way to update is to wait for a dev to release a flashable cwr zip fike
Sent from my HTC Glacier using XDA App
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
mooch777 said:
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
Click to expand...
Click to collapse
Did he retire completely?
graffixnyc said:
Did he retire completely?
Click to expand...
Click to collapse
Think so!
From my CM7 UrBan Glacier
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Any ideas.....?
Thanks
SkI
Error 1
Error 1 means that the file is not where it is supposed to be. In this case on the SD card. Check and make sure that you have the right file, with the right file name on the root of your SD card and try again!
Good Luck
What does
"Error scanning partitions" means?...
jiwengang said:
What does
"Error scanning partitions" means?...
Click to expand...
Click to collapse
nvm, it is solved. don't use your own flash_image. use the stock one.
dj_ski69 said:
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Click to expand...
Click to collapse
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
dfspot said:
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
Click to expand...
Click to collapse
when you adp push to sdcard, make sure you mounted it already.
after that , it always help to adb shell ls /sdcard to make sure all files are there.
then you go to adb shell,
use the stock flash_image to flash. remember point to the path to flash_image
eg. flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
my understanding, if you don't mount sdcard, you canot see your sdcard FROM the tablet's perspective.
I mean, for table's flash_image to work, it has to be able to access its drive, in this case, is sdcard 's content.
so did you try leave sdcard mount and do the command above?
Hey Team...
can someone help me find the stock flash_image plz.....
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
What command did you do.
Sent from my HTC Glacier using XDA App
chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
do I need to push flash_image to my tablet?
If I remember correctly it needs to be in the nvflash folder
Sent from my Dell Streak 7 using XDA Premium App
I initially looked for a complete update guide on here and eventually found all the information I needed, but it was in multiple places and sometimes hard to find. After getting everything installed on my N1 I thought I would write a guide for other noobs like me that want to try out ICS or JB but would like a step-by-step guide. I hope that it is helpful. SpazeDog ROMs (both ICS and JB) are working wonderfully on my N1 - its a very nice update from CM7 with only minor issues so far.
Note: this was initially written specifically for SpazeDog roms, but as they have not been updated in a while I have provided links to other popular roms as well. If you would like to try a different ICS or JB rom this guide should work, just substitute with the appropriate rom and depending on the one you choose, you may also need to install Google apps.
If you looking at this guide and don't know the basics yet, check out the Newbie Friendly thread first.
Links to popular roms that will work using this guide:
Evervolv JB 4.2
Evervolv JB 4.1
CM 10, JB 4.1.2 by vijendrahs
CM 10, JB 4.2.1 by vijendrahs
Spazedog ICS/JB
Disclaimer: This guide involves making changes to your phone that potentially could brick your phone leaving it unusable. I am not liable for any changes you make or problems you may have with your phone. You should at least be familiar with entering commands using command prompt. This procedure will erase ALL the data on your phone. Make sure you have a backup of everything. A nandroid backup is highly recommended. Proceed at your own risk.
Before we get started make sure you have the following: a rooted Nexus One, a USB cable to attach your phone to a computer, and the Android SDK. If you are just now installing the Android SDK, open the SDK manager and make sure to install the "Tools" and in "Extras" the "Google USB Driver" are checked off and download them. Alternatively, you just download ADB and Fastboot (search this forum or google). If you have a Mac see this thread to get started with ADB and Fastboot.
If you Nexus One is NOT already rooted, then follow this guide from Cyanogenmod to root your phone. If you plan to use the adb commands below (they are optional) make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Step 1 - Download everything you will need:
4EXTRecovery Updater - the first link will download the .apk to your computer or phone.
BlackRose - go down to bottom of the first post to "Attached Files" and download the latest BlackRose zip file. If you don't want to do it yourself, check out this thread to flash a pre-made partition scheme. Often the developers (Evervolv) will also have a partition schemes that you can flash via Fastboot from your PC as well.
Your rom of choice - go to the downloads section and choose which rom you would like to try. Download the zip installation file.
Since you will be decreasing the size of your partition that apps can be stored on consider something like Mounts2SD or AD2SDX to move apps to your SD card.
Step 2 - Install and use 4EXTRecovery Updater on your phone:
The easiest thing to do is go to the 4ext link above, download and install it, directly from your nexus one. You can also install it by copying the APK file to your SD card, then using a file manager to find it and install it or you can use command prompt by opening command prompt, cd to the location of the Android SDK tools, and then type in the following command (replacing "path" with the path to where the APK is located on your computer):
Code:
adb install /path/4EXTRecoveryUpdater.apk
After you have installed 4ext open the 4EXT Recovery Updater. Tap "Settings" → "Allow" superuser request → "Yes" to connect to 4ext to get new data. Now select "Online install/upgrade" → "Yes" assuming it detects your nexus one correctly → select and install the latest 4ext recovery (at the top of the list).
After 4ext has installed, it will have placed a recovery image on your SD card - find it (its called recover.img) and it should be located in SD/Download/4EXT_Recovery_Touch/ folder. Copy this to your computer in case something goes wrong later and you need to re-flash the recovery image!
After installation of the 4ext recovery turn off your phone and boot into recovery by turning off your phone, turning it on again while holding the trackball down. This will boot into the bootloader, then press the power button once, use Volume Down to select "recovery" and press the trackball to select. Alternatively you can use the command prompt:
Code:
adb reboot recovery
Your phone should now boot into the 4ext recovery menu. Before moving on make sure you have any important stuff backed up because you are about to erase your entire SD card! Select "tools" →“partition sd card” → “remove all partitions and start from scratch.” Then for the 1st partition select “1024″ for a 1GB partition (this will be where ICS will be able to put your applications & data). Select "skip" for the 2nd partition and for the swap partition. Finally select the system “ext4″.
Step 3 - Copy the Evervolv, SpazeDog, or whatever zip installation file you have chosen to your phone's SD card
Download the ICS or JB zip file above and copy it to the root of your newly formatted SD card.
Step 4 - Installing and using BlackRose to resize the system partition:
Download the BlackRose application and install it on your computer. (Alternatively people have made flash-able partition schemes that you can just flash from your PC - usually links and instructions are provided in the installation rom's thread, Evervolv's here. If you do have access to a computer you can check out this thread).
Make sure your nexus one is attached via USB to your computer.
Open the BlackRose application - it will install and reboot your phone. Then follow along as shown in this video to resize your partitions for a JB ROM.
If you plan to install the ICS rom then use the video above as a guide but use the numbers (sizes) for the different partitions as indicated below.
After BlackRose has installed you will need to restart the application. After it has started up and recognized your device select "apply stock/custom blackrose" by typing in 1 and enter.
Then select "custom blackrose" by typing in 2.
Then type "resize" when prompted.
Now you will need to change the sizes of the system partition to 220 for ICS or 260 for JB.
Change the cache size to 8.
Finally name the new system partition, either "ICS" or "JB" depending on what you plan to install.
Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip.
Step 5 - Install JB or ICS:
Now turn your phone off and boot into recovery as you did in step 2.
4ext will load. Select "wipe/format" → "format all partitions (except sdcard)" and then also "wipe data/factory reset."
Now go back and select "install from sdcard" → "choose zip from sdcard" → and then select the ICS or JB zip you copied to the SD card in step 3.
Now either the ICS/JB installer will load or it will just install in one step. Just follow the prompts to install and enjoy.
Depending on the ROM you chose you may need to install Google apps (see the specific ROM thread for details) and will also likely want to flash an apps-to-SD script as mentioned above so you do not run out of space.
This method worked perfectly for me, hopefully it will work well for you as well. Enjoy.
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
diegolm said:
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
Click to expand...
Click to collapse
I am sorry to hear that. Can you boot into recovery or is that broken as well? If you can boot into ext recovery try selecting "wipe/restore" → "wipe data/factory reset" and then try to install BCM again. I probably should have added that above, I will do that now.
If your recovery is broken but you can get into the bootloader (holding down trackball while starting up), you should be ok. You will probably need to flash Amon_Ra's Recovery using Hboot as was described in the guide from cyanogenmod link above. If there is a way to directly hboot flash 4ext recovery I don't know how to do it. Then you can try installing BCM again from the Amon_Ra's recovery and re-install 4ext after you get everything working.
I tried the Texasice ROM and it worked, but I didn't like it! Later I tried again BCM and It worked! I dont know, maybe I did something wrong... Anyway thanks again for the guide!!
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I am not sure which part you are referring to, but, yes, a few of the above instructions could be replaced with fastboot commands.
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
intel415 said:
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I used the adb commands above because you can use adb to reboot directly into recovery (fastboot you can only reboot normally or into the bootloader) and you can also use adb to directly install apk files - fastboot cannot do those two things - it is more for flashing images (recovery, roms, etc). In order for adb to work make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Note that adb commands are not required - you can reboot into recovery and install the 4ext manually.
It won't let me post a link right now, but just google "adb commands" to find a list of all the commands you can use.
Hope that helps.
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
intel415 said:
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, its not bad - glad you got it working! ICS has been smoother than cm 7.2 for me as well.
Blackrose didn't ask me about userdata - it just assumed that automatically after putting in 220 system and 16 cache... I'll make note of that in the guide so its clearer. Thanks.
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Look for "recovery.img"
bobbyphoenix said:
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Click to expand...
Click to collapse
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
c2med said:
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
Click to expand...
Click to collapse
OK I'm stuck on what the path name is suppose to be. I tried it every way I can think of. Can you take a look at my screen shot, and tell me where I'm going wrong? The recovery image is on my desktop, so I'm not sure what exactly I should be replacing "path" with. I tried it from the link, and how you have it in your note. You don't have the "/to/" after path as in the CM link.
Well I tried a couple more times, and I can get it to seemingly do it, but it just hangs on this: (see screen shot) I get no error, and if I try to enter recovery on the phone I still get the reboot to the android and triangle with the ! in it.
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
n1newbie said:
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
tommert38 said:
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
Click to expand...
Click to collapse
WOW Thank you both. I spent literally hours yesterday trying to get it to work. Tried your suggestions, and in five minutes it was up and running!
---------- Post added at 12:31 PM ---------- Previous post was at 11:33 AM ----------
I may have spoke too soon. I followed the instructions to the end. Installed the ROM, and rebooted, but now after the X I get the Spazdog splash screen with the big Z in the middle and green dots moving, but it stays there forever. I waited 20 minutes one time. Tried reflashing, but I get the same thing.
---------- Post added at 01:17 PM ---------- Previous post was at 12:31 PM ----------
Just giving an update on progress (in case someone else is in my boat too) Flashed back to stock GB. Reinstalled recovery, and reflashed Spaz. Got past the X, and the splash screen, but now it's stuck on the Android logo that looks like the night rider beam that goes across the word. Been there now for about 10 minutes.
You do have Blackrose, right?
Yep. Installed everything according to OP. I think it may be the partition sizes as I think flashing back to GB messed with them. It says 220 and 10, but after checking some threads, it looks like there is one missing (userdata). I tried flashing a custom GB from here http://forum.xda-developers.com/showthread.php?t=1214543&page=98 and I was able to install everything. Got it up and running, so I'm going to start over for ICS, or do you think I can flash one of these for ICS http://forum.xda-developers.com/showthread.php?t=1637166 , and then just flash the ROM after?
220/10 means that you have 220MB for system and 10MB for cache, everything that's left will be userdata, so it doesn't ask (total is ~436MB, so userdata will be ~206MB in that case).
In HBOOT you can check how large your partitions are, or you could use the FreeSpace app for example. Always make sure your system partition is large enough before flashing a ROM.
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.