Database Develop

[Q] Phone unusable

PROBLEM IS NOW FIXED USING THIS METHOD: LINK
Hi, i'm new on xda (have been reading stuff here for a while though)
I have flashed DarkyROM 10.2 Extreme, DarkyROM 10.2 Resurrection and CyanogenMod 7.1 before, but tonight disaster struck
I have searched here, googled my problem but so far, nothing worked so lets try it here.
Ok so i have a few problems:
1. When i power up my phone it boots normal, i get the darkyrom bootscreen and then it goes into the setup screen, just pressing next is suddenly says: "proces com.sec.android.app.phonesetupwizard has stopped" (or something like that), afther that it just restarts the setupscreen. edit: Problem has changed, it is now stuck at the bootscreen (the screen you see the first when you press the powerbutton)
2. When i connect my phone to my pc (in this case my laptop) is doesnt recognise it, and wont install the drivers. I Reinstalled KIES, i reinstalled the drivers manually, nothing helped.
edit: tried installing drivers manually different times, different drivers not working so far
3. I can boot into download and into recovery (in my case CWM) but i cant install zip from sd card, because i cant connect my phone to my laptop (as said above). I have tried putting it on my external sd card, and then try to install it from there trough CWM (install zip from sdcard > choose zip from sdcard > external_sd/) but it just says: "no files found"
4. Found out a minute ago (9:20 AM) that i can't power off my phone either, when i do it just reboots itself. i have to pull out the battery for it to stop (duh..), when i put it back in, it just continues until it gets stuck on problem nr 1. again
so right now, i have an phone that won't boot or connect and that i can't flash because it wont connect
narrowed it down to just the USB problem, it wont recognise any drivers
i hope this is still repairable
(sorry for some mistakes in english if there are any )

Get into download and flash a stock rom from there with pit, pda, modem, csc.
Then reflash cwm and your custom rom.

Mordo_ said:
Get into download and flash a stock rom from there with pit, pda, modem, csc.
Then reflash cwm and your custom rom.
Click to expand...
Click to collapse
thanks for your reply, but i can't flash a stock rom as my phone wont connect to my pc, so i can't put anything on the sdcard to flash.
already have Odin + stock files waiting, but i can't do anything yet

Did you try a different usb-port and/or cable?

yes i tried all usb-ports on my laptop, haven't tried another cable though as i do not have one that fits, i am now trying to connect my phone to my desktop pc to see if it is recognised there (laptop has win7, pc has win xp)

As long as you can get to download, the consensus around here seems to be that it's fixable. Just a matter of finding the tools;-) but you may have to get another cable.

Tweexx said:
yes i tried all usb-ports on my laptop, haven't tried another cable though as i do not have one that fits, i am now trying to connect my phone to my desktop pc to see if it is recognised there (laptop has win7, pc has win xp)
Click to expand...
Click to collapse
it didn't work on my desktop pc either (desktop had win7 not xp) so could that mean the cable is just broken, as it seems to me its a driver problem
edit: alright its not the cable, my brother has the same phone and it works for him, installed the drivers (exept one called galaxy s >.<) and i could see his phone at "my computer" so its not a cable problem
edit 2: some extra info (dont think it matters): my brother has CyanogenMod 7.1 at the moment

Ok, too bad that would have been real easy;-)
Have a look at the last post, seems a similar situation.
http://forum.xda-developers.com/showthread.php?t=1442684&highlight=odin+usb

Mordo_ said:
Ok, too bad that would have been real easy;-)
Have a look at the last post, seems a similar situation.
http://forum.xda-developers.com/showthread.php?t=1442684&highlight=odin+usb
Click to expand...
Click to collapse
thanks for your reply, i tried to do the steps from the last post
- put the phone into download mode and plugged the cable into the back of the pc
Click to expand...
Click to collapse
give's me an error saying it doesn't recognise usb
1. I downloaded and used the 1click unbricker
Click to expand...
Click to collapse
didnt work, wont intall drivers correctly, also phone will show up as "unknown device" in zadig.exe
also using heimdall is impossble as it doens't recognises my phone
edit: tried it on a friend's laptop, same error, not recognising usb

if only there was a way to flash trough external usb, that would probably work right? as i can put files on my external sd, but not via usb cable to internal sd

i had a similar issue once, nothing was recognized when connected via USB.
the problem was gone after i had powered off the phone and taken out the battery for some time (half an hour or so).

sennator said:
i had a similar issue once, nothing was recognized when connected via USB.
the problem was gone after i had powered off the phone and taken out the battery for some time (half an hour or so).
Click to expand...
Click to collapse
tried that already, went to school (about 3 hours ago) and left my phone at home, now i am back home, but the problem is still there

hmmkay..
Tweexx said:
if only there was a way to flash trough external usb, that would probably work right? as i can put files on my external sd, but not via usb cable to internal sd
Click to expand...
Click to collapse
i guess CWM shows the content of my external SD when i select "choose zip from internal SD" (confusing!). did you try that?

sennator said:
hmmkay..
i guess CWM shows the content of my external SD when i select "choose zip from internal SD". did you try that?
Click to expand...
Click to collapse
when i go into CWM and do this:
install zip from sdcard > choose zip from sdcard
i get these 2 options:
voodoo/
clockworkmod/

Does your phone "react" if you plug in the charger?

Mordo_ said:
Does your phone "react" if you plug in the charger?
Click to expand...
Click to collapse
how do you mean exactly?
i can't turn of the phone without removing the battery, and when i put the battery back in it boots automaticly and then hangs on the bootscreen.
in recovery i don't get any "reaction", in download mode i also get no "reaction"
so i guess i get no reaction if i plug in the charger

have u tried to put all the files u need to flash the phone on the external sdcard? use a card reader connected to your pc, copy them to the card, put the card back in your phone, boot cwm and select
install zip from sdcard > choose zip from sdcard and select the external one. I always flash from my external sdcard.
hope this helps

that is exactly what i did, but the only 2 options i get are voodoo/ and clockworkmod/ there is no option to select the external sd, i think it isn't mounting it correctly or something

Tweexx said:
when i go into CWM and do this:
install zip from sdcard > choose zip from sdcard
Click to expand...
Click to collapse
ok, so you don't have an additional option called "choose zip from internal sdcard"? i think that depends on your CMW version (i'm running v5.x).
unfortunately, no more ideas so far...

sennator said:
ok, so you don't have an additional option called "choose zip from internal sdcard"? i think that depends on your CMW version (i'm running v5.x).
unfortunately, no more ideas so far...
Click to expand...
Click to collapse
no i dont have any additional option.
my CWM version is: CwM Dark Core Recovery v.3.0.2.8x (dont know if it helps :S)
thanks anyway for trying

How to wipe internal storage and install rom via ADB sideload using TWRP

Recently i wanted to a full wipe including internal storage on my nexus 5 and since nexus 5 does not have external storage i found it a bit tricky to flash a rom again...
so,here im going to explain the easiest and simplest way to install a rom via adb sideload on nexus 5 using TWRP after a complete wipe
I am not responsible for bricked devices.
Please do some research if you have any concerns about adb sideload
BACKUP YOUR DATA FIRST
1.Download the file and place it on desktop View attachment Nexus5.zip
2.boot your device into recovery, wipe everything and connect it to pc and make sure drivers are installed. if not do as follows:
open device manager in control panel and if drivers are already installed, it shows something like ANDROID ADB INTERFACE,
if not,it shows some name with yellow symbol..
right click on it and select update drivers and select browse my computer and select let me pick..
click next > have disk>browse> and select the usb_drivers in downloaded file> open > open > ok
now it shows as ANDROID ADB INTERFACE..
3.In TWRP, select advanced and choose sideload option.
4.open command prompt and change the directory to where you downloaded the file ( easy if on desktop )
to open command prompt: win+r>cmd
for changing directory: cd desktop > cd nexus5
5.Now type adb devices in command prompt and it should show list of devices with your device code name and mode as sideload mode.
if not install drivers again.
6.copy your ROM zip file to the folder 'Nexus5' which you downloaded.
7.type adb sideload romzipname
8.now it starts copying and wait till it shows 100%. after copying it automatically starts installing.
when the installing is finished,it shows reboot system. reboot and njoy :highfive:
Note: If stuck while flashing rom, hold power and volume down until it reboots to fastboot then go to recovery and repeat the same procedure.
Please hit the 'thanks' if this helped you.

jaj473 said:
Recently i wanted to a full wipe including internal storage on my nexus 5 and since nexus 5 does not have external storage i found it a bit tricky to flash a rom again...
so,here im going to explain the easiest and simplest way to install a rom via adb sideload on nexus 5 using TWRP after a complete wipe
I am not responsible for bricked devices.
Please do some research if you have any concerns about adb sideload
BACKUP YOUR DATA FIRST
1.Download the file and place it on desktop View attachment 2461684
2.boot your device into recovery, wipe everything and connect it to pc and make sure drivers are installed. if not do as follows:
open device manager in control panel and if drivers are already installed, it shows something like ANDROID ADB INTERFACE,
if not,it shows some name with yellow symbol..
right click on it and select update drivers and select browse my computer and select let me pick..
click next > have disk>browse> and select the usb_drivers in downloaded file> open > open > ok
now it shows as ANDROID ADB INTERFACE..
3.In TWRP, select advanced and choose sideload option.
4.open command prompt and change the directory to where you downloaded the file ( easy if on desktop )
to open command prompt: win+r>cmd
for changing directory: cd desktop > cd nexus5
5.Now type adb devices in command prompt and it should show list of devices with your device code name and mode as sideload mode.
if not install drivers again.
6.copy your ROM zip file to the folder 'Nexus5' which you downloaded.
7.type adb sideload romzipname
8.now it starts copying and wait till it shows 100%. after copying it automatically starts installing.
when the installing is finished,it shows reboot system. reboot and njoy :highfive:
Note: If stuck while flashing rom, hold power and volume down until it reboots to fastboot then go to recovery and repeat the same procedure.
Please hit the 'thanks' if this helped you.
Click to expand...
Click to collapse
in the cmd prompt it keeps telling me it cannot read my rom file. any helpm please?

b_rangel29 said:
in the cmd prompt it keeps telling me it cannot read my rom file. any helpm please?
Click to expand...
Click to collapse
Did you copy the rom file to Nexus5 folder?

Why not use WugFresh's tool.... that thing does everything.
Sent from my Nexus 5 using Tapatalk

We try to discourage the use of toolkits as they remove the "ability" element or the "learning" aspect.
Doing things manually teaches the skills to get out of trouble later on.
Sent from my Nexus 5 using Tapatalk

try to update usb driver. browse the file inside dowloaded file but it came result windows was unable to instal your nexus 5
i'm using windows 7
any sugestions?

Help
So, I have/had a N5 on stock 4.4.4 rom, rooted & Xposed installed with TWRP & a lollipop preview on MultiRom.
Was installing the new Lollipop .zip. In an act of hurried stupidity, I wiped my phone, including the internal storage.
Which for some reason also wiped my NANDROID backup. I thought that is not supposed to be wiped even when doing an internal storage wipe, BUT it did.
Now, all i have is TWRP on my phone with no rom installed.
I tried connecting my phone to the pc to see if i can just transfer the rom file onto the internal memory, but nothing shows up when i connect my phone to PC.
after some searching, I ended up in this thread.
The problem is, when i connect my phone to the PC, the phone doesn't show up in the device manager.
So i cannot install the drivers & android SDK itself.
So, How do i Install a rom onto it?
I have a PC & a MAC, so i can use either of the machines. But i don't have much technical knowledge about stuff, I did all the above modifications with the help of tutorials & guids. so ELI5 please.
Please help!
Thank you.

Jugal.PM said:
So, I have/had a N5 on stock 4.4.4 rom, rooted & Xposed installed with TWRP & a lollipop preview on MultiRom.
Was installing the new Lollipop .zip. In an act of hurried stupidity, I wiped my phone, including the internal storage.
Which for some reason also wiped my NANDROID backup. I thought that is not supposed to be wiped even when doing an internal storage wipe, BUT it did.
Now, all i have is TWRP on my phone with no rom installed.
I tried connecting my phone to the pc to see if i can just transfer the rom file onto the internal memory, but nothing shows up when i connect my phone to PC.
after some searching, I ended up in this thread.
The problem is, when i connect my phone to the PC, the phone doesn't show up in the device manager.
So i cannot install the drivers & android SDK itself.
So, How do i Install a rom onto it?
I have a PC & a MAC, so i can use either of the machines. But i don't have much technical knowledge about stuff, I did all the above modifications with the help of tutorials & guids. so ELI5 please.
Please help!
Thank you.
Click to expand...
Click to collapse
Read here - http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my Android 5.0 Nexus 5

accidently wiped internal memory in lenovo p1m
i accidently wiped internal memory using twrp. so now can i flash a custom rom for my lenovo p1m

[Q] Full tutorial to put KitKat on N1. Who wants to test?

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.

[Q] I accidentally wiped my OS - how to restore?

I had to use a factory reset to decrypt my phone. TWRP was asking a password (a known bug, nothing works) and I did a factory reset using TWRP. Now I get the message "No OS Installed! Are you sure you wish to reboot?".
What is the easiest way to install OS? I want to use CyanogenMod and I have the latest build zip file. M7 doesn't support SD cards but I have OTG USB stick and I've copied cm-11-20141112-SNAPSHOT-M12-m7.zip there. I don't know if TWRP can recognize the drive. Windows doesn't currently recognize my device.
I don't have a recovery backup because decrypting my memory (stock encryption) apparently wiped that out.
Please help me, I have to get my phone up and running again!
TWRP 2.8.6.0

I found the folder "usb-otg" but TWRP doesn't recognize CyanogenMod zip file. I'm on the install menu.
Is it safe to turn off my phone now? Maybe I just turn off the screen and connect the phone to charger.

Musicbee said:
I found the folder "usb-otg" but TWRP doesn't recognize CyanogenMod zip file. I'm on the install menu.
Is it safe to turn off my phone now? Maybe I just turn off the screen and connect the phone to charger.
Click to expand...
Click to collapse
The file you have is 18 months old
look in the developer forums for something newer
you doing it right just copy the zip to the OTG and plug it into your phone and install it

clsA said:
The file you have is 18 months old
look in the developer forums for something newer
you doing it right just copy the zip to the OTG and plug it into your phone and install it
Click to expand...
Click to collapse
Yeah, I just noticed that (does it matter?). Can you recommend me a relatively stable build?
What is usually the name for USB OTG device folder in file explorer? "Usb-otg" folder exists even when no device is connected to my phone. I don't think that TWRP recognizes the drive.
EDIT: I found my USB device!

Musicbee said:
Yeah, I just noticed that (does it matter?). Can you recommend me a relatively stable build?
What is usually the name for USB OTG device folder in file explorer? "Usb-otg" folder exists even when no device is connected to my phone. I don't think that TWRP recognizes the drive.
Click to expand...
Click to collapse
when the drive is plugged in just click storage and choose usb-otg
If you want a simple non sense rom I would use this
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927

Please tell me if it's safe to reboot my device now?

CM is now working fine, haven't noticed any issues. I still need Google apps.

Question | how to extract an android backup that i made before updating

hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!

doesitburn said:
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
Click to expand...
Click to collapse
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works

mrmazak said:
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
Click to expand...
Click to collapse
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s

doesitburn said:
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
Click to expand...
Click to collapse
I know you said you have data currently on phone you dont want to loose. But it seems it might be easier to make twrp backup of phone now. then put factory recovery on and restore that back up you have from before , save off it what you wanted, then put twrp back and restore the twrp backup.

where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh

doesitburn said:
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
Click to expand...
Click to collapse
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then

mrmazak said:
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
Click to expand...
Click to collapse
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery

doesitburn said:
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
Click to expand...
Click to collapse
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.

mrmazak said:
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
Click to expand...
Click to collapse
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)

doesitburn said:
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
Click to expand...
Click to collapse
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"

mrmazak said:
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
Click to expand...
Click to collapse
ok so for that matter
fastboot boot c:\downloads\recovery.img
that it ? sweet thanks alot.
learning something new every day