Database Develop

amon ra 1.2.3 helpppppppp

hey i cant wipe ext and a few other option does not work from the recovery menu....??? it gives me error like
wipe from console???please help.....
when i click repair ext it says to do it from consol when i click wipe cach it says do it basically from via console.....please help....

so do it from console? thats the simplest method to fix that...
try flashing recovery again.

okay....
well is there a site with the commands i might need.....i tried to wipe the ext with this
# mount -o rw /dev/block/mmcblk0p2 /system/sd
but does not work??

if im not mistaken, that code just remounts/mounts the ext.... what you need is found by searching "console" + "reformat". And second result later...Here.....
Try searching the forums first. good luck

okay this is what im going to do?
im going to flash my g1 to 1.6 then add on cyanogen rom 4.1.9999 okay then what is the best way to reflash my recovery imgae.....i think i might have dl the h not the g version....how can i relfash my image without messing it up please help.....

xghostyxjokerx said:
im going to flash my g1 to 1.6 then add on cyanogen rom 4.1.9999 okay then what is the best way to reflash my recovery imgae.....i think i might have dl the h not the g version....how can i relfash my image without messing it up please help.....
Click to expand...
Click to collapse
If u doing this on G1 u got a wrong recovery image there is only 2 versions 1.2.2 and 1.2.3 there is no G or H. Link is in my signature. Why would u flash if u recovery image works half add u might as well **** ur **** up, flash proper recovery image. AND READ FFS IT'S ESSENTIAL.

Ghosty you need to put your phone down and start reading for a few hours, yes hours.
Your obviously jumping into that phone knowing little to nothing about what your doing.
So unless you have the funds to buy a replacement phone, start reading.

Custom ROM, rooted with unrEVOked "one-click"

OK, I rooted my stock Sprint 2.1 Hero using the "one-click" unrevoked web method, primarily to install wireless tethering, and now I'd like to flash Darchdroid 2.7 on to the phone to speed things up a bit and maybe fix some of the glaring issues I have with the phone.
So do I need to "re-root" with another method to install ROMs? Or can I just push a recovery ROM over and proceed from that step forward? Sorry for the newb, questions, but I'm a bit confused about what I should be doing at this point.
Thanks!

mrgreen4242 said:
OK, I rooted my stock Sprint 2.1 Hero using the "one-click" unrevoked web method, primarily to install wireless tethering, and now I'd like to flash Darchdroid 2.7 on to the phone to speed things up a bit and maybe fix some of the glaring issues I have with the phone.
So do I need to "re-root" with another method to install ROMs? Or can I just push a recovery ROM over and proceed from that step forward? Sorry for the newb, questions, but I'm a bit confused about what I should be doing at this point.
Thanks!
Click to expand...
Click to collapse
you just need to flash a recovery image download android sdk put it where ever you want. then download a recovery image name it ra or that wat i name it you can name it what ever you want then hit the windows symbol and r then in the little text box type cmd then you will see teminal like window so type
cd c:\path of your android sdks tools folder
make sure your phones pluged in and usb debugging is selected and its on charge only then type also make sure you put the recovery image on the root of your sd card
adb shell
you should see this #
then type
su
then
flash_image recovery /sdcard/name-of-recovery.img
than it should flash the reboot your phone holding the home button then pressing power and you should have a working recovery image to flash roms make backups ect.

i would recommend the darch droid one found on this page
http://forum.xda-developers.com/showthread.php?t=728491&page=3
just scroll til u see the link

[Solved][Q] Nexus one SLCD - custom rom

Solved!
Hi,
I have SLCD Nexus one(2.2) and I want to install custom rom.
But it shows black screen because it's not OLED.
Solved!! - Most custom roms having new kernels work, if it doesn't have new kernel installing new kernel works!

I've got the same problem. I even tried brute force, because I got everything working but got stuck on a black screen recovery, which I tried to get working for hours. I thought it might be the new rom or the new hboot, so I flashed a new image via fastboot. Now I'm stuck at a black screen os (thank god fastboot still works) - but I'd need a stock slcd rom to get back to where I started.
Could someone be so kind and upload an slcd rom? Or even better some slcd custom recovery+slcd+new hboot compliant custom rom?
I think, that a lot of people will get in this trap, because there are no warnings, that even the newest cm/ra_recovery won't work on a new nexus one.
Thanks in advance.
Update: Solved on my own. Now I'm just waiting for some slcd recovery + mod. ;-)

This is Amon Ra's Nexus One SLCD recovery dl.dropbox.com/u/4481275/recovery-RA-nexus-v1.8.0.1-aw.img

Well, at least be glad that fixing a dark Nexus One is probably much easier than fixing a dark HTC Desire!
I suggest this sequence if you have an SLCD N1:
1) Root first, then load ROM Manager
2) Install custom recovery but keep your ROM for now. Boot into recovery. If it's dark, wrong recovery - try again.
3) ONLY once you have a working recovery should you even think about trying other ROMs. And don't forget to take a full nandroid backup first. You should be able to restore that backup safely from recovery.

Zorr0theOne said:
This is Amon Ra's Nexus One SLCD recovery dl.dropbox.com/u/4481275/recovery-RA-nexus-v1.8.0.1-aw.img
Click to expand...
Click to collapse
Thanks, but I'm asking for custom rom, not recovery.
Anyway, thank you very much.
cmstlist said:
Well, at least be glad that fixing a dark Nexus One is probably much easier than fixing a dark HTC Desire!
I suggest this sequence if you have an SLCD N1:
1) Root first, then load ROM Manager
2) Install custom recovery but keep your ROM for now. Boot into recovery. If it's dark, wrong recovery - try again.
3) ONLY once you have a working recovery should you even think about trying other ROMs. And don't forget to take a full nandroid backup first. You should be able to restore that backup safely from recovery.
Click to expand...
Click to collapse
Thanks, but I'm asking for custom rom, not fix. (I already fixed it)
Anyway, thank you very much.

i have same problem as wisechild but u said u have fixed it and just waiting for custom rom if so how did u fix it. i no the recovery works in the background, when the screen is dark cause if u do a backup in rom manager and let it run despite dark screen it shows up when u go back to rom manager. the trouble is i have the hboot 0017 instead of 0012 so can't install cm roms. is there a rom that works with that hboot.
found solution, the latest Kang-o-rama rom work with the korean hboot 0.35.0017 . Installed it using rom manager install from sdcard option. despite not being able to see the recovery screen just let it run for like 5 mins then it reboots and u got a custom rom.

aljnbaptiste said:
found solution, the latest Kang-o-rama rom work with the korean hboot 0.35.0017 . Installed it using rom manager install from sdcard option. despite not being able to see the recovery screen just let it run for like 5 mins then it reboots and u got a custom rom.
Click to expand...
Click to collapse
Thanks, but I'll wait for custom rom supporting FM(ie NXSense).
Anyway thank you very much.

If you'd like a specific ROM to support SLCD, best to request this directly on the thread for that ROM.
I wonder if there is a component which can be swapped in easily to provide SLCD support?

wisechild said:
Solved!
Solved!! - Most custom roms having new kernels work, if it doesn't have new kernel installing new kernel works!
Click to expand...
Click to collapse
Can you verify with a ROM like CM6 or Evil Sense.

Please, do tell us how you implemented a fix .

Hmm
Can anyone help please?
I previously flashed an old Amon Ra recovery onto my N1 SLCD & suffered the blank screen fate. Since rooted with universal androot and tried to copy over and flash using adb shell (for some reason fastboot flash recovery doesn't seem to work - i still get the blank screen). However, adb shell denies permission to become su even though following root i can become su using terminal emulator on the phone ... Anyone have any ideas?

rob_2010 said:
Can anyone help please?
I previously flashed an old Amon Ra recovery onto my N1 SLCD & suffered the blank screen fate. Since rooted with universal androot and tried to copy over and flash using adb shell (for some reason fastboot flash recovery doesn't seem to work - i still get the blank screen). However, adb shell denies permission to become su even though following root i can become su using terminal emulator on the phone ... Anyone have any ideas?
Click to expand...
Click to collapse
I think fastboot flash recovery requires an unlocked bootloader.
With adb shell you have to type su and then, on the phone, look for the permissions dialog to come up. After you accept, it will give you a root shell. If it's not asking you for the permissions, I'm not sure what else to do.
I think you could also conceivably run flash_image from the terminal emulator as root and flash the correct recovery that way.

shundi82 said:
I've got the same problem. I even tried brute force, because I got everything working but got stuck on a black screen recovery, which I tried to get working for hours. I thought it might be the new rom or the new hboot, so I flashed a new image via fastboot. Now I'm stuck at a black screen os (thank god fastboot still works) - but I'd need a stock slcd rom to get back to where I started.
Could someone be so kind and upload an slcd rom? Or even better some slcd custom recovery+slcd+new hboot compliant custom rom?
I think, that a lot of people will get in this trap, because there are no warnings, that even the newest cm/ra_recovery won't work on a new nexus one.
Thanks in advance.
Update: Solved on my own. Now I'm just waiting for some slcd recovery + mod. ;-)
Click to expand...
Click to collapse
how did you solve the problem, i'm stuck with a blank screen os also the keys light up and work but no screen

Flash AmonRa's 1.8.0.1 recovery that supports SLCD, and then flash any ROM you like - most of them support SLCD now, and if you see that the one you flashed doesn't - flash another.

Jack_R1 said:
Flash AmonRa's 1.8.0.1 recovery that supports SLCD, and then flash any ROM you like - most of them support SLCD now, and if you see that the one you flashed doesn't - flash another.
Click to expand...
Click to collapse
cant really troubleshoot now cause i'm at work but how would i be able to enable usb debugging if i cant see the screen?

You couldn't get stuck in ROM if you flashed a recovery that doesn't support SLCD, because you wouldn't be able to install ROM without it - and you couldn't get stuck without ROM if you only flashed a recovery that doesn't support SLCD. So one of them should be working for you, and enable to make the other work.
That is unless you used ROM manager, which flashed the recovery for you and did all the stuff - and it didn't show anything, because Clockwork recovery doesn't support SLCD (so you would get your ROM installed for you and not see it, and then you'd get stuck with a ROM that doesn't support SLCD).
If that's the case, run the recovery and try to connect ADB (recovery runs ADB interface).

Jack_R1 said:
You couldn't get stuck in ROM if you flashed a recovery that doesn't support SLCD, because you wouldn't be able to install ROM without it - and you couldn't get stuck without ROM if you only flashed a recovery that doesn't support SLCD. So one of them should be working for you, and enable to make the other work.
That is unless you used ROM manager, which flashed the recovery for you and did all the stuff - and it didn't show anything, because Clockwork recovery doesn't support SLCD (so you would get your ROM installed for you and not see it, and then you'd get stuck with a ROM that doesn't support SLCD).
If that's the case, run the recovery and try to connect ADB (recovery runs ADB interface).
Click to expand...
Click to collapse
that was the case. i'll try in a few hours when i get home. once i'm in adb i would try to flash amon ra's recovery and start over correct?

Indeed, correct.
Use recovery flashing guide from Wiki. If you're rooted without unlocking - follow the "flash_image method" guide. If you find out that you need to install busybox - download the APK and install using ADB, instead of downloading from the Market.

I wrote this how-to, I think it might help you.
h**p://forum.xda-developers.com/showthread.php?t=785581

cestbibi said:
I wrote this how-to, I think it might help you.
http://forum.xda-developers.com/showthread.php?t=785581
Click to expand...
Click to collapse
It's essentially the same guide as in Wiki, but executed through ADB - which is good. I'll add your guide to the Wiki for reference, with a link. I saw, it doesn't require Busybox (uses "cat >" instead of "cp").

[Q] Can't get into Recovery? ??

ok. i was running RA-Darchstar Recovery and was curious about Gingerbread so i decided to read up and i had seen that the CLockworkMod recovery was to be used.
so i put it on my sd card and did the adb shell way to install...
-Orginally, i've been using cm 6.1 stable-
(i am using firerats mtd mod so i'm betting this is why what happened, happened.) read on.....
so i flashed the new recovery and i got many mtd "re-read errors (out of memory)" and "Skipping Write Block at..."
when i rebooted to recovery, it got stuck at the htc screen. so i rebooted normally and tried to flash the original RA-darchstar recovery that i had and the same "out of memory" "no space left on device" errors.. have shown up in cmd.
so my question is How do i get back to a Recovery so i can reflash firerats recovery with a bigger mtd partition --or even nandroid for that matter??
should i delete some things through root explorer and if so, what folder should i delete them from?
there has to be a way to get my recovery back. thanks for any help thrown my way...
-cue
EDIT: when booting to Recovery from Bootloader.. it gets stuck at the HTC screen with a white bar just above the htc logo with FASTBOOT USB in red. ??
Am i gonna have to run a RUU? and if so... which RUU do i use? i've never RU'd before. .

Yeah at this point you should ruu. Download the ruu in regawleinads how to root the cdma hero thread. It's in development.

Asadullah said:
Yeah at this point you should ruu. Download the ruu in regawleinads how to root the cdma hero thread. It's in development.
Click to expand...
Click to collapse
ok. just a little confused as to which ruu to use... the .7 or .5?
EDIT: ok i have read a bit and i'm going with the .5 ruu. thanks a lot Asadullah for the confirmation on ruu. i wish there was an easier way to get a Recovery image back on this phone as i just got things set up correctly for me on this cm 6.1 rom.

[Q] rooting Nexus One

Hi,
I am just wondering, i am rooting my Nexus one 2.3.3 and in the instruction it says "Also download and copy the SU program to your SD card and name it sd.zip."
My question is where do i get this file from?
Thanks.

masantula said:
Hi,
I am just wondering, i am rooting my Nexus one 2.3.3 and in the instruction it says "Also download and copy the SU program to your SD card and name it sd.zip."
My question is where do i get this file from?
Thanks.
Click to expand...
Click to collapse
Go to the "rooted" link in my signature, and take the Eclair/Froyo version

Isnt the Su file in your signature for froyo? And isnt 2.3.3 gingerbread? or it works?
Thanks.

masantula said:
Isnt the Su file in your signature for froyo? And isnt 2.3.3 gingerbread? or it works?
Thanks.
Click to expand...
Click to collapse
The file in the thread that you want is: su-2.3.6.1-ef-signed.zip It works for Eclair, Froyo and Gingerbread.

efrant said:
The file in the thread that you want is: su-2.3.6.1-ef-signed.zip It works for Eclair, Froyo and Gingerbread.
Click to expand...
Click to collapse
Great, thanks alot for the help

im also rooting but grj22 build, what do i need to download to my sd before i unlock my boot loader?

To unlock your bootloader, you don't need anything on the sdcard. To continue with rooting, you would need to have a custom recovery on your computer and use fastboot to install it after you unlock it, then flash the zip that was mentioned above (which would need to be on the sdcard) to actually root your phone from the custom recovery.

bassmadrigal said:
To unlock your bootloader, you don't need anything on the sdcard. To continue with rooting, you would need to have a custom recovery on your computer and use fastboot to install it after you unlock it, then flash the zip that was mentioned above (which would need to be on the sdcard) to actually root your phone from the custom recovery.
Click to expand...
Click to collapse
can i use adb to put the file on the sd card i tried unsuccessfully and now my phone wont boot. but i still have bootloader and fastboot, also adb devices works? ugh , such a newb but it seems all is not lost, right?

Install recovery, boot into recovery, mount the SD from recovery, then move the file over to the SD using windows...

danger-rat said:
Install recovery, boot into recovery, mount the SD from recovery, then move the file over to the SD using windows...
Click to expand...
Click to collapse
ok col, now heres the kicker...i flashed recovery-RA-nexus-v2.1.1.img as my recovery , and im pretty sure i put cryogen 7 on the sd so i fudged it up pretty good.whats the best recovery to flash i, if had gingerbread 2.3.4 which came ota au natural? also im finding the su-2.3.6.1-ef-signed.zip file either, anyone have a proper link to it?

If you're going to flash cm7 or ANY pre-rooted rom you do not need to bother with the su.zip. Just flash the rom from custom recovery.

i keep getting the no img wrong img message in fastboot when i try to hboot?

Fastboot is used to flash the custom recovery. The recovery flashes the rom.
I can't understand your post in the first place so I dont know what is your actual issue.
But read the wiki.
Sent from my Xoom using Tapatalk

yes!!! it worked i knew i was close.
albundy2010 said:
Fastboot is used to flash the custom recovery. The recovery flashes the rom.
I can't understand your post in the first place so I dont know what is your actual issue.
But read the wiki.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
well i used my girls htc 3g slide and loaded a the file before mentioned to my sd and BLAM! im so happy i almost cried a lil bit! so excited thanks to albundy and everyone else who walked me through this and gave me helpfull tips will post photos of my success!

big al,so now i have tested a few roms didnt like cm7 to much nightly or stable but i found an 2.3.4 ota vanillia and i like it of course cause its what im used to stock basicly. Well now im having problems running my gallery or music player or camera? seems like im missing something again? is it cause im rooted> i think i rooted?hmmm uh help. thanks

nevermind got it worked out downloaded a root version and wipe wiped flashed and Blam! im back.