Related
I already went through the process of rooting my phone, and am currently running JF 1.5
So to try out the Cyanogen Rom, from my understanding all I have to do is download the zip, rename it "update.zip" and boot it like I did JF?
Is this correct?
Thanks,
Mike
yes that is correct, if it will not get past the android screen or gets pasts it, but goes to black screen then you will need to wipe and reflash the rom, but i wouldn't wipe unless it doesn't work without wiping.
nopotential said:
I already went through the process of rooting my phone, and am currently running JF 1.5
So to try out the Cyanogen Rom, from my understanding all I have to do is download the zip, rename it "update.zip" and boot it like I did JF?
Is this correct?
Thanks,
Mike
Click to expand...
Click to collapse
Taken from the FAQ on the release thread:
1. Do I have to wipe?
You shouldn't have to wipe if coming from a JF ADP-based ROM, otherwise, probably. If weird things are happening, try wiping. You can also try the permission fixer script linked above. If you are coming from an HTC-based ROM like Hero or Sapphire, you are going to have to wipe.
Click to expand...
Click to collapse
So yeah, flash as update.zip, if you have issues, wipe and reflash.
haha beat you to the punch by a few seconds adriank
david1171 said:
haha beat you to the punch by a few seconds adriank
Click to expand...
Click to collapse
Damn you!! *shakes fist*
I would actually flash the Radio first if you haven't (look at my sig for teh latest version). Then flash the Cyanogen ROM.
Do I have to flash the recovery too?
Do I have to flash the recovery img too?
nopotential said:
Do I have to flash the recovery img too?
Click to expand...
Click to collapse
Nope. But with the CM 1.4 Recovery, you can update using the "any zip" feature...so no more renaming to update.zip etc.....
Makes keeping track of things alot ezier
I second wilnotdie, using the CM 1.4 Recovery will make life a lot easier in the long run. Worth flashing it.
Hey, so i have a g1 and was using youtube to jailbreak it and was doing ok, and even installed cupcake fine version 1.51 by jesus freak. i didnt really notice much differnce from the stock g1 so i tried to install cyanogenmod's latest rom so i put it on the memorycard as update.zip and i also put JFv1.51 ADP.zip on the card and tried to do a reset. i pressed alt W to wipe and alt S to install the new ROM but i noticed it still says JFv1.42 on the recovery utility and when i ry to boot after the update it just hangs on the tmobile g1 screen. I cant figure out what to do and need help. thanx!
Get amon_ra 1.5.2 recovery img,
then to flash cyan's rom you need th 1.4 ota dev zip then cyans roms
do a wipe
then flash the ota, it will say reboot but dont,
press back the go to flash any zip and flash cyans rom then reboot, it will take you back to Recovery menu and wait till your able to move around then reboot phone again
Or use cyans Wiki guide to rooting and upgrading to use his rom
ANYONE? Ive read as long as i can get back to the recovery screen im ok, but weather i wipe it and just reboot or wipe and try to install the update it gives me the t mobile g1 screen. what can i do?
ilostchild said:
Get amon_ra 1.5.2 recovery img,
then to flash cyan's rom you need th 1.4 ota dev zip then cyans roms
do a wipe
then flash the ota, it will say reboot but dont,
press back the go to flash any zip and flash cyans rom then reboot, it will take you back to Recovery menu and wait till your able to move around then reboot phone again
Or use cyans Wiki guide to rooting and upgrading to use his rom
Click to expand...
Click to collapse
Hey, so even if i get the amon_ra 1.5.2 recovery img how do i get it onto the phone?
and what is the 1.4 ota dev zip? im a real noob with all this so any walk thru steps would be greatly appreciated!
takashikastl said:
ANYONE? Ive read as long as i can get back to the recovery screen im ok, but weather i wipe it and just reboot or wipe and try to install the update it gives me the t mobile g1 screen. what can i do?
Click to expand...
Click to collapse
Use Super-D or wesgarner and enom those are faster than cyan.Just wipe then reflash any of the above
sorry my fault its 1.6 ota dev zip.. my fault...
well do these steps
Copy recovery-RA-dream-v1.5.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
Click to expand...
Click to collapse
or you can do it thru terminal
Copy recovery-RA-dream-v1.5.2.img to the root of your sdcard
start the terminal app
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
Click to expand...
Click to collapse
once you get that flashed you can use
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
jus read to get an idea on how.. but mainly wanna follow tese instructions
You will now install the actual OS of the phone. First you will install the legal Google apps, and then you will install CyanogenMod on top of those apps.
1. Turn your phone off.
2. Hold the Home button and "End" (power) button to boot to Recovery mode.
3. If you wish to have an option to return to your factory settings, select nandroid backup now. If not, continue.
4. Press Alt-W (or select "wipe data/factory reset")Press home to confirm
5. Press Alt-A (or select "apply any zip from sd")
* DRC83_base_defanged.zip or signed-dream-devphone...
6. Press home to confirm and let installation complete --Note that no "I have finished my job" message will appear after it finishes. Attempt to move the trackball once you see "Formatting CACHE:;" if you can see the highlight moving on the menu, it has completed the installation.
7. STOP - DO NOT REBOOT YOUR PHONE
8. Once again, press Alt-A (or select "apply any zip from sd")
* Select update-cm-4.2.x-signed.zip
9. Press home to confirm and let installation complete --Note that no "I have finished my job" message will appear after it finishes. Attempt to move the trackball once you see "Formatting CACHE:;" if you can see the highlight moving on the menu, it has completed the installation.
* If you used the Defanged DRC83, you need to manually install the ota-radio-2... just like the first two updates.
10. When this is complete, reboot your phone by pressing Home & Back.
11. Wait, your phone will display a [box] -> [phone] and say writing radio image and then reboot. This will take a couple of minutes. Be patient!
12. If the phone enters Recovery mode after rebooting, press Home & Back again to reboot it once more. You should see the blue CyanogenMod Android logo this time.
If that's all you wanted to do, you're done! You should now have a fully functional phone.
Click to expand...
Click to collapse
ilostchild said:
sorry my fault its 1.6 ota dev zip.. my fault...
well do these steps
or you can do it thru terminal
once you get that flashed you can use
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
jus read to get an idea on how.. but mainly wanna follow tese instructions
Click to expand...
Click to collapse
OK this looks like somrthing i can definatly do but how am i suppose to get something from my computer to the sd card if the phone is stuck. i dont have a card reader on my comp. only thing i have is the cable to connect the computer to the phone!
That indeed is a problem dont have a card reader at all? you can mount the sd card thro console form recovery.. but im not sure if you need adb shell or not.. also if you want a good rom you should go with dwangs rom or superD 1.2(doesnt require dangerSPL) on eve WES new y2.6 build doesnt require it either
http://www.androidspin.com/downloads.php?dir=benbuchacher/ROM/ click on SUPERD 1.2(most stable) what i am on now
http://forum.xda-developers.com/showthread.php?t=592466 Wes Garners Rom
ilostchild said:
That indeed is a problem dont have a card reader at all? you can mount the sd card thro console form recovery.. but im not sure if you need adb shell or not.. also if you want a good rom you should go with dwangs rom or superD 1.2(doesnt require dangerSPL) on eve WES new y2.6 build doesnt require it either
http://www.androidspin.com/downloads.php?dir=benbuchacher/ROM/ click on SUPERD 1.2(most stable) what i am on now
http://forum.xda-developers.com/showthread.php?t=592466 Wes Garners Rom
Click to expand...
Click to collapse
HOW DO I MOUNT IT FROM RECOVERY? i think this would solve my problem.
im on recovery JFv1.42 still.
takashikastl said:
HOW DO I MOUNT IT FROM RECOVERY? i think this would solve my problem.
im on recovery JFv1.42 still.
Click to expand...
Click to collapse
What spl do you have. If you have the Eng. or Haykuro spl, there is a way to help, if not...
on the card currently is cyan rom which even tho it says it installed doents work and i have a new recovery on it which is jfv1.51 adp.zip anyway i can get the new recovery working thru console and there by helping me restore my phone?
JAguirre1231 said:
What spl do you have. If you have the Eng. or Haykuro spl, there is a way to help, if not...
Click to expand...
Click to collapse
HOw do i find out what spl i have? i have a g1 stock that i rooted with rc29 i think, then i went up to rc 33 and then i went to cupcake 1.51 i also did a radio update for cupcake
OK so i pressed on button with camera and found it says
drea100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO 2.22.19.261
OCT 20 2008
takashikastl said:
HOw do i find out what spl i have? i have a g1 stock that i rooted with rc29 i think, then i went up to rc 33 and then i went to cupcake 1.51 i also did a radio update for cupcake
Click to expand...
Click to collapse
So you never once flashed the hard spl? Would you boot with power+camera and tell us what you see there?
JAguirre1231 said:
So you never once flashed the hard spl? Would you boot with power+camera and tell us what you see there?
Click to expand...
Click to collapse
OK so i pressed on button with camera and found it says
drea100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO 2.22.19.261
OCT 20 2008
You have the HardSPL, you can do it the other way as JAguirre1231 said but i do not know how to do this so would go with his route
here is how to get sdcard (mass storage mounted)
http://forum.xda-developers.com/showpost.php?p=4041756&postcount=1
but go other way be much simpler
takashikastl said:
OK so i pressed on button with camera and found it says
drea100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO 2.22.19.261
OCT 20 2008
Click to expand...
Click to collapse
You have the hard spl. Well it looks like your going to need a new sdcard reader...
ilostchild said:
You have the HardSPL, you can do it the other way as JAguirre1231 said but i do not know how to do this so would go with his route
here is how to get sdcard (mass storage mounted)
http://forum.xda-developers.com/showpost.php?p=4041756&postcount=1
but go other way be much simpler
Click to expand...
Click to collapse
Wrong information on my part, edited out my previous text
JAguirre1231 said:
My way won't work, he does not have a fastboot enabled spl...
Click to expand...
Click to collapse
WOW AWSOME!!! NOw im connected to my SD card. So since your the ****ING MAN with the answers what should i download and install to get the best rom out there.
takashikastl said:
WOW AWSOME!!! NOw im connected to my SD card. So since your the ****ING MAN with the answers what should i download and install to get the best rom out there.
Click to expand...
Click to collapse
Just use cyan or wesgarners or superd or dwang. Any donut should be fine (I'm using wesgarner's).
BTW, I read that with sarcasm (as I read all posts with) and I totally took that as an insult.
JAguirre1231 said:
My way won't work, he does not have a fastboot enabled spl...
Click to expand...
Click to collapse
HARDSPL is fastboot enabled
http://forum.xda-developers.com/showpost.php?p=3007992&postcount=1
its the same as engineer just with this its region free
only Stock SPL doesnt have FASTBOOT capabilities
@takashikastl
That did sounded kinda bad, But if really are jus follow instructions from the wiki and the new recovery dirctions
I don't want to jump on IRC and I don't know where else to post this, but I have a small request, if possible. Can you fine folks make the recovery flasher so that you can add your own updated recovery images? Currently, the flasher only only installs clockwork 2.0.1.0 and there is a version 2.0.1.3 available, but no way to make it stick.
Install ROM Manager from Koush on the android market, and update your recovery that way.
It does not stick. Please read my post. Its easy enough for you to check yourself. I have Rom Manager already. It cannot work any magic. Once you reboot, you are back to the original version that the recovery flasher puts on there.
really? mine works great....
Boot into clockwork and look at the version number. No, it does not.
Rom Manager thinks its flashing an updated version, but thats not the case.
Look... I am not a liar, and don't appreciate being called a liar. I am just trying to help you. In my ROM Manager it says current and latest is 2.0.1.3. In my Clockwork Recovery it says version 2.0.1.3. I have restarted it three times into recovery, and it says the same number. So, sir, please refrain from being a jerk, and sorry if I came off that way.
And I just confirmed with another friend that his works great also.
Post an image please.
Nobody called you a liar, and if you think I am being a jerk, you are way too sensitive.
I have this same problem. Mine is at 2.0.1.0. I believe koush was in the irc channel last night saying something about it.
Thanks for the update.
fennellchrid said:
Look... I am not a liar, and don't appreciate being called a liar. I am just trying to help you. In my ROM Manager it says current and latest is 2.0.1.3. In my Clockwork Recovery it says version 2.0.1.3. I have restarted it three times into recovery, and it says the same number. So, sir, please refrain from being a jerk, and sorry if I came off that way.
And I just confirmed with another friend that his works great also.
Click to expand...
Click to collapse
Apparently if you reboot into recovery using rom manager it will show you are in the updated version, but if you boot into recovery manually from a completely shut down phone you will see that you are actually in the old version and you were never updated at all. The thought is that if you reboot into recovery from rom manager it loads their recovery image but if you manually boot into recovery it doesn't. The reason is that the nand is still locked, so rom manager can't actually reflash the recovery image without being in recovery at the time.
I am currently at work... If I had a camera I would. Ask some other people to do it, and I promise they will tell you the same thing. If you read in the Recovery Reflash Tool forum, you will see others talking about this very same thing.
I see just as many from the other side of the fence. What do you think of that?
sdorn77 said:
Apparently if you reboot into recovery using rom manager it will show you are in the updated version, but if you boot into recovery manually from a completely shut down phone you will see that you are actually in the old version and you were never updated at all. The thought is that if you reboot into recovery from rom manager it loads their recovery image but if you manually boot into recovery it doesn't. The reason is that the nand is still locked, so rom manager can't actually reflash the recovery image without being in recovery at the time.
Click to expand...
Click to collapse
This makes sense. This is how I rebooted into recovery. Thanks!
Update - Sorry, you were right. What he said is true. Mine is still 2.0.0.7, just shows up at 2.0.1.3 when you reboot via the ROM Manager. Again, I apologize.
that's correct, koush's rom manager uses a fake flash to upgrade the recovery versions. It does not stick if you boot normally into recovery without rom manager. If we weren't pursuing other things you will like even more we would make a way to flash custom recoveries. But we will instead work to eventually give you true nand unlocked everything. just in the meantime except what you have please. You don't always have to have the latest! I
If a serious issue is found requiring a real update we will get to it.
Please don't take this as a demand, or dissatisfaction. I am very happy with what you folks have done so far and can certainly wait for whatever the team decides to do I was just reading that some versions of Clockwork were having trouble with Froyo and was looking to the future. Thanks for replying
sdorn is correct. Hitting recovery from ClockworkMod is 2.0.1.3 and a fresh boot into recovery (adb, hboot) is 2.0.1.0. The recovery will probably have to be flashed from unrevoked's tool to get up to the latest version or until NAND is unlocked outside of hboot.
not sure how but i have clock work 2.0.1.3 as my clockwork and it says in every time i bring it up if i knew how to take a screen shot in recovery id show ya,
junjlo said:
not sure how but i have clock work 2.0.1.3 as my clockwork and it says in every time i bring it up if i knew how to take a screen shot in recovery id show ya,
Click to expand...
Click to collapse
Power the phone off, and then boot into recovery by holding Vol Down + Power and selecting RECOVERY. You have 2.0.1.0 installed.
Lock
Mods may want to lock this thread ... it continues to be a debate when the question was answered by Shadowmite.
fennellchrid said:
This makes sense. This is how I rebooted into recovery. Thanks!
Update - Sorry, you were right. What he said is true. Mine is still 2.0.0.7, just shows up at 2.0.1.3 when you reboot via the ROM Manager. Again, I apologize.
Click to expand...
Click to collapse
Very classy response.
I searched and read through some of the threads and really didn't find a conclusive answer to what I am looking for. So I decided to create a new thread.
My question is: Is there any way to root the N1 that has Stock FRF91? I'm not a noob in rooting, just wanted to make sure. I don't really care about unlocking the bootloader (warranty isn't an issue for me).
Can I just use the fastboot oem unlock command to unlock bootloader then install the custom recovery and install custom roms? Or is there a new method to rooting Stock FRF91 currently.
Thanks
Yes.
http://forum.xda-developers.com/showthread.php?t=715798
You're welcome. Get familiar with the search tool.
Frankenstooge said:
Yes.
http://forum.xda-developers.com/showthread.php?t=715798
You're welcome. Get familiar with the search tool.
Click to expand...
Click to collapse
The instructions in that link wont work for stock FRF91 with stock recovery. I couldnt get the Amon recovery to load onto my phone in order to flash the root. I have tried to ADB it 5 times and each time it says successful, but when i go into recovery all i get is the android with the !.
By all means OP, you can try this and if you get it to work, let me know what you did. I tried 5 times and couldnt get it to work.
my bootloader is unlocked also.
ecapox said:
The instructions in that link wont work for stock FRF91 with stock recovery. I couldnt get the Amon recovery to load onto my phone in order to flash the root. I have tried to ADB it 5 times and each time it says successful, but when i go into recovery all i get is the android with the !.
By all means OP, you can try this and if you get it to work, let me know what you did. I tried 5 times and couldnt get it to work.
my bootloader is unlocked also.
Click to expand...
Click to collapse
after you pushed custom recovery, did you press Volume Down button while rebooting to go directly into recovery? because after you install custom recovery and let the phone reboot, the stock recovery will remain; you should try to go into recovery immediately after pushing the amon ra recovery without letting the phone boot up
let me know if that works
What is the method for rooting "without using SDK tools"? There are emulator apps in the market but they refuse to work without super user permissions? I have stock frf91 and looking for a way to root my nexus one?
jblazea50 said:
after you pushed custom recovery, did you press Volume Down button while rebooting to go directly into recovery? because after you install custom recovery and let the phone reboot, the stock recovery will remain; you should try to go into recovery immediately after pushing the amon ra recovery without letting the phone boot up
let me know if that works
Click to expand...
Click to collapse
that did it sir. thank you. Was it like this in 2.1? I dont remember having it revery back to stock recovery when following the tutorials. Then again maybe i never let it completely boot back up...
ecapox said:
that did it sir. thank you. Was it like this in 2.1? I dont remember having it revery back to stock recovery when following the tutorials. Then again maybe i never let it completely boot back up...
Click to expand...
Click to collapse
that's great; it was the same on 2.1, you probably just can't recall at the moment
glad it worked
jblazea50 said:
that's great; it was the same on 2.1, you probably just can't recall at the moment
glad it worked
Click to expand...
Click to collapse
Interesting. So once you use the Amon recovery it sticks as long as you dont reboot after you install it. I guess i was just lucky the first time!
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").