Related
Hello there. I am not so lucky to have a Dream (well I do have other sorts ) but my colleague wanted to have a go at backups and flashing and did something stupid.
He performed a cat /dev/zero on mtd3 which is the system dir and afterwards ofcourse was not able to flash his system.img back because flash_image was on that same system partition.
NOW. How do we get this puppy back up from that Android blinking cursor screen?
ADB is there. Root is still there. Fastboot is in an waiting forever modus.
you might have better luck if you ask in the right section
please either re-ask in QnA or wait for the mods to move it
just wondering....why the hell did he do that? lol
put a recovery image on the sdcard and do
adb flash_image recovery /sdcard/(filename)
if that works, boot in to recovery and try flash an image
i doubt it will work but its worth a go
ok, my eye skipped over the failed flash thing
search around...there is a way to apply roms via adb...
i think there are even instructions on the adp1 page on the htc website
Thx. Had the exact same question. I will look it up.
If ADB works, why don't you just transfer flash_image back, apply the proper permissions, and go?
The entire MTD3 is gone. Maybe you could give us some pointers on how to do it? Every command you give in the shell points back in the error - exec '/system/bin/sh' failed: No such file or directory (2) - simply because nothing is there.
So how to begin putting flash_image back in a system dir that's not there?
Boot into the recovery image & then use adb flash_image should work. Otherwise you can just fastboot a system image from another Magic (search in the Magic forums & ask for one if you cant find it). Or just flash a ROM from recovery
Ooh I missed a vital detail. Appearantly the keys are none responsive so he isn't able to go into recovery or bootloader mode.
When trying the ol' fastboot boot recovery he gets cannot load 'recovery' while fastboot boot recovery.img spits out
creating boot image...
creating boot image - blahblahblah bytes
< waiting for device >
and well the ol' adb shell reboot bootloader gives him that saucy
- exec '/system/bin/sh' failed: No such file or directory (2) -
any takers?
So you can't get into the spl by holding the camera key while turning the phone on?
If you could, then once it's up, press the back button so it'll go into fastboot mode. Fastboot won't work unless you do this.
If you can't get it that far then you have bigger problems, i'd say.
Once you get that far though, just use "fastboot flash" the same way you would use "flash_image". If you get errors flashing system from a system.img, do a "fastboot flash erase system" first. I did something similar before and that solved it for me.
TemporalShadows said:
So you can't get into the spl by holding the camera key while turning the phone on?
If you could, then once it's up, press the back button so it'll go into fastboot mode. Fastboot won't work unless you do this.
If you can't get it that far then you have bigger problems, i'd say.
Once you get that far though, just use "fastboot flash" the same way you would use "flash_image". If you get errors flashing system from a system.img, do a "fastboot flash erase system" first. I did something similar before and that solved it for me.
Click to expand...
Click to collapse
if this doesnt work, just flash the RC29 recovery image (DREAIMG.nbh) and reroot
links can be found in many root guides
Let
s just give up on this one then. I even tried dnw.exe but that didn't help much either.
well i happened to have some problems with a theme i was using that made the icons appear themed even in cyanogens roms , and i was told that i needed to flash the htc adp image to fix that
the problem comes here i flashed the htc adp image but i forgot to read what cyanogen said that i had to flash his rom before rebooting
so i just found that cyanogen gives us something to follow just in case it happens what happened to me here http://wiki.cyanogenmod.com/index.php/RE-recovery-img
i went to ''if you currently have an engineering or a Hard SPL'' and followed all the procedures until i got to number 4 where it asks me to Change directory to where you have saved your recovery image..i've tried lots of paths but none seems to work...ADB NOOB HERE so please help
when you didnt follow the process, you lost root.
you have to start from scratch.
.............................................................................
i typed
cd C:\recovery-RA-dream-v1.5.2.img
and it tells me the directory name is invalid what am i doing wrong?
recovery image is not a directory, it'a file. What are you trying to do?
borodin1 said:
recovery image is not a directory, it'a file. What are you trying to do?
Click to expand...
Click to collapse
im trying to flash amon ra recovery via fastboot
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
borodin1 said:
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
Click to expand...
Click to collapse
i would do this..but i cant since i messed up when flashing the htc adp image im following cyanogens tutorial http://wiki.cyanogenmod.com/index.php/RE-recovery-img and it says that i have to flash the new recovery through fastboot , and the part im stuck at is step 4 where he says that i need to Change directory to where you have saved your recovery image
if you can get into the main phone operating system via a boot up then use linda file manager to move them
when i type this
fastboot recovery recovery-RA-dream-v1.5.2.img
i get this message "error: cannot load 'recovery-RA-dream-v1.5.2.img
then i changed the directory to where the recovery image was and when i tried to flash i got this message
'fastboot' is not recognized as an internal or external command, operable program or batch file
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
borodin1 said:
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
Click to expand...
Click to collapse
im going to tell you step by step what i do
turn the phone off
hold power and back
i see the androids on skateboards and it says fastboot in red letters
i connect my phone via usb then the name changes to fastboot usb
run the cmd
once there i type where adb is located which is cd C:\android-sdk-windows\tools
then when i type fastboot devices
i see the serial number of my phone
now when i type cd desktop i get this message "the system cannot find the path specified"
and if i ignore that and try to flash
fastboot flash recovery rec.img (yes i did rename the recovery image)
it says that it cant load 'rec.img'
Got it! Put your image file into the "tools' folder and once you see your device in the fastboot just flash it from there
Code:
cmd
cd C:\android-sdk-windows\tools
fastboot devices
fastboot flash recovery rec.img
fastboot reboot
Sorry about all this complication... the main idea is that your recovery needs to be in the same directory as you're when you're flashing. So if earlier you went to tools folder then your file needs to be there as well.
Try it out.
it worked...it said sending 'recovery' <4456 KB>... okay
writting 'recovery'...okay
fastboot reboot
then when i go to the system recovery..its the same htc adp one
i tried to flash amon ra's recovery and cyanogens
oh nevermind..instead of rebooting the phone i just unpluged the device and wnet directly into the system recovery and YES i have cyanogens recovery thank you so much borodin1
hmmmm that's weird because you got confirmation....
1. Did you download right recovery? You had to becaue you tried 2 of them and you can only make the same mistake once lol
2. AmonRA's recovery has the same image in the background as HTCs, are you sure that it's still HTC's recovery?
Other then that... I'm clueless
Can you get su in the adb shell? Try flashing it from adb....
You got me stomped on this.... Anyone else wants to take a shot at this????
i dont know what happened but when i flashed the recovery image on fastboot and then rebooted the phone...then turn off the phone and went to the system recovery and the htc adp recovery appeared...blue letters and the scrolling options..but when i did not reboot the phone after flashing the image and went directly to the system recovery i had the recovery i flashed...then i applyed the updateand everything is good now
weird uh?
will that new recovery stick?... I'm starting to remember something but it's vague... give me few minutes Reboot couple of times into recovery and back for now and see what happens...
it did stick..i just rebooted into recovery and i have the new recovery..haha
Great! Happy modding!
I wrote this Noob manual to help others achieve the same goal: Root the Nexus One. Thanks goes out to the XDA forums for such fantastic community support. In my quest to root, was overwhelmed and confused with the various ways to do it. Should you root by unlocking the bootloader or not, should you downgrade, then upgrade, which recovery image to use, how to flash a recovery image, everything shows "superboot" bla bla bla. We all have the same questions, but this can be a pain-staking process to find the answers. Here's a short guide that may help you root the phone.
Overview of the process: A) Unlock Bootloader B) Flash Recovery Image C) Install Rom through Recovery. D) Phone now unlocked and rooted.
1) Setup adb and confirm it's working by reading your serial number.
http://forum.xda-developers.com/showthread.php?t=613217
2) Unlock bootloader (voids warranty but htc may still repair). Turn on USB debugging (may need to toggle usb debugging off to move files to sd card, then back on for adb). Reboot phone into fastboot:
Power off device and hold down trackball while powering back on. The fastboot screen is the one with the Androids on skateboards.
Open a command prompt and navigate to your Android SDK tools folder.
Type ‘fastboot devices‘ to make sure your phone is recognized.
Type ‘fastboot oem unlock‘ to unlock the bootloader.
Use volume keys to navigate to yes and press the power button to confirm.
3) Flash Aman RA Recovery in fastboot (immediately following flash, go into recovery console before rebooting or the recovery image may not show up). The stock rom will re-flash recovery during boot because of scripts. Recovery rom should be placed in adb folder. To reboot into recovery from adb type 'reboot recovery'. Copy the recovery file to your Android SDK tools folder. Open a command prompt and navigate to your Android SDK tools folder. Type ‘fastboot flash recovery recovery.img‘ (or whatever the recovery file name is).
http://forum.xda-developers.com/showthread.php?t=611829
4) While in fastboot, select "Recovery" and new Recovery screen shows up. FRF91 signed image or custom rom should be on the sd card.
Download signed FRF91 signed image for rooting (only after adb is working, the bootloader has been unlocked and recovery image successfully flashed.
5) Flash Froyo 2.2 rooted & signed update file.
(update-nexusone-FRF91-root-signed.zip)
Get it here:
www.multiupload.com/L69XPNYDWP
www.megaupload.com/?d=XD8MYCSN
If this was done correctly, your phone is now rooted.
thx for your work
but also we have a this http://forum.xda-developers.com/showthread.php?t=636795
will this method wipe my data? and is the superboot method any easier?
Thanks!
Worked like a champ! Oh and yes it will wipe all your data... I thought maybe it wouldn't since you didn't say, but it did... oh well it's all backed up in my gmail, so it'll be ok.
I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?
If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?
How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.
ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks
Did you fix this yet?
Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!
Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!
Hello Folks,
I'm still stuck with my nexus one since I don't care that much about phones.
I've seen that jelly bean roms have made a significant progress. Thus I decided to give it a shot.
I started with installing adb and fastboot. :good: After that I rooted the nexus one :good: I've used this how to:
c2med blog, can't post links...
Next, I ran blackrose. :good: I saved the rom on the micro sd. Having done all the preperations I wanted to flash the JB rom.
I started the phone in bootloader mode but - unfortunately - couldn't access the recovery mode (ext4). I only get the Android figure and an exclamation mark.
In the how-to it sais i should use fastboot to flash the recovery made by ext 4.
Problem # 1: Ext4 generated a .zip, not a .img file
Problem # 2: I connect the device in fastboot mode, navigate to the adb/fastboot folder and use ./fastboot devices. The phone is recognized and I see the serial number. Next I try "flash recovery...." but I only get "command not found". Now, I basically have no idea what to do.
Which recovery should I flash? And how?
I'm so looking forward to your answers.
Androdicct said:
Hello Folks,
I only get the Android figure and an exclamation mark.
Which recovery should I flash? And how?
Click to expand...
Click to collapse
What you get is the stock recovery.
Flash 4Ext recovery or Amon RA recovery ( fastboot flash recovery recovery-RA-passion-v2.2.1.img)
Among the several guides to install JB, I suggest you to look at the following post:
http://forum.xda-developers.com/showthread.php?t=1804571
I just finished this morning the following process:
install RA recovery,
install Blackrose and resize partition,
install from SD card Evervolv-Perdo-3.2.0-Nightly-2013.01.13-passion.zip
install from SD card gapps-ev-jb-20120816.zip
I spent a lot of times reading and trying. I had an issue after installing Evervolv-perdo-3.1.0final-passion zip. That's why I switched to the Nightly (JB 4.2).
Once you are set install a2sd from within the terminal emulator on your N1.
In my opinion this is so far the best ROM I ever have had on my Nexus 1.:good:
I am impressed to the extend that I offer to my wife to do the same on her N1. She said no. No to unlock, no to root and of course no to custom ROM.
Good luck
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"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."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Androdicct said:
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"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."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Click to expand...
Click to collapse
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
gunner1937 said:
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
Click to expand...
Click to collapse
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=611829 : read posts #15 and #16.
In other words open your folder android-sdk-windows installed on the root of your C: hd. Click on the folder platform-tools and download Amon RA recovery in this folder. Left click anywhere on a blank area of this folder then press the key Shift (keyboard) and right click your mouse. In the drop down menu select Open command window. In the CMD, to be sure that the N1 is recognized by the pc (meaning the right drivers are installed) type ADB devices and press enter. You should see a string of numbers like HT9C......
Type adb reboot bootloader and press enter. You are in the fastboot mode ( and mood if I may say so) and the phone shows that it is in the bootloader. You can check again that N1 is recognized by the pc by typing fastboot devices. Same string appears.
Type fastboot flash recovery recovery-RA-passion-v2.2.1.img.
After the installation is completed boot in recovery, select Flash zip from sdcard, select the ROM you have dropped on the card. When the installation is completed go back to Flash zip from sdcard ( you are still in recovery mode) and select the gapps you have dropped on the sdcard.
Go back to Reboot system now. You are then out of the recovery and it takes some times for the N1 to boot to this beautiful JB
Edit:
http://forum.xda-developers.com/showthread.php?t=1804571 this is for posts #15 & #16
Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
As c2med posted in his guide, sometimes, people lose their recovery when they repartition using Black Rose. Hence, its always best to have Amon-RA or 4EXT flashable .img file in your PC so that incase you lose recovery, you can always flash it back.
Once you are in bootloader ( also called FASTBOOT mode) you can flash your recovery.
Then reboot into recovery from FASTBOOT (Shutdown and then restart using the recovery combination)
Once you are in recovery, follow the steps in c2med's guide (wipe cache/dalvik/etc - except sd-card ofcourse) and flash your ROM from sd card.
Then reboot into JayBee
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
jolinnard said:
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
Click to expand...
Click to collapse
Thank You! That's what I figuered out last night. Of course I also tried "fastboot flash" but forgot the "./". That was the key. Now the JB ROM works like a charm.
New Problem:
I can't install google apps. In fact I don't really need them. I only use a few apps and found the .apk files with google. Unfortunately the "official" Google apps like chrome don't work.
Plus, I wanted to install the camera (laggy in the evervolv - rom) and keyboard from here.
http://forum.xda-developers.com/showthread.php?t=1965290&page=38
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Androdicct said:
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Click to expand...
Click to collapse
When you're in recovery, select "Flash zip from SD card" and then select "Toggle signature verification" to disable signature verification, and then "Choose zip from SD card" and navigate to the zip file that you want to flash.