Database Develop

[Q] Blank Nexus One (SLCD)

Hello,
Kind of a noob here. tech-savvy but new with android. Had my N1 for 3 days now.
SLCD version with Amon Ra 1.9.0 alpha recovery. Didn't unlock the bootlader
I'm having fun with custom ROMs. Installed CM6 and now wanted to go back to stock. Didn't realise the FRF91 ROM was not compatible with my SLCD phone and I flashed it on my device. Now it boots into a blank FRF91. I can get it to go into recovery console (power + volume down), but when I select Recovery, I see the nexus on logo and the screen goes black (maybe the recovery is not working anymore or it's juste not showing?).
I can't get adb to work since I need to enable USB Debugging. Is there any way I can enable it without the screen. I don't even know if the touchscreen works (I think it doesn't). So to enable it I need to navigate with the trackball I guess. But I don't know where to go to enable it when I don't see anything.
This is fun and all but I like my phones with something on the screen
Can anybody help?
EDIT RESOLVED :
I used the PASSIMG.ZIP trick to flash a stock rom onto it (FRG33 I think) via the HBOOT menu.
Thank you danger-rat and Jack-R1 for your help!

http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images
Try the 'blind' version for locked bootloader.
Sent from my Nexus One using XDA App

danger-rat said:
Try the 'blind' version for locked bootloader.
Click to expand...
Click to collapse
I can't get adb to work, it doesn't detect my phone. I guess it's because I haven't enabled usb debugging on the phone or because I'm not root.
How can I do those things without a screen?

You may have lost root when you reverted to stock (was it a rooted stock image?)
What is not working with adb? Have you tried "adb devices"? What response are you getting?
Sent from my Nexus One using XDA App

danger-rat said:
You may have lost root when you reverted to stock (was it a rooted stock image?)
What is not working with adb? Have you tried "adb devices"? What response are you getting?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I flashed a stock rom, yes. So I guess I lost root.
adb devices turns up an empty list of devices.

Did you try to connect ADB when you're booted to recovery?

Jack_R1 said:
Did you try to connect ADB when you're booted to recovery?
Click to expand...
Click to collapse
If he followed the instructions he did...
Sent from my Nexus One using XDA App

I'm not sure he followed the instructions. He might be missing it, or assuming something wrong. So I want to make sure he did...

I thought the same myself...
Sent from my Nexus One using XDA App

Jack_R1 said:
Did you try to connect ADB when you're booted to recovery?
Click to expand...
Click to collapse
By connect I suppose you mean launching the adb app in android-sdk/tools? Then yes I tried it when I was in the HBOOT menu and after when I was in the black Amon_RA recovery. Still no devices detected.
The ROM I flashed was an unrooted stock ROM.
When I boot into the black Amon_RA recovery or the black FRF91, my computer detects the nexus one device that is connected but I can't see it in adb.
It seems I need to enable USB debugging on my black FRF91 and root it to be able to use adb with it.
I hate the 5 min posting limit

The problem is that you don't have the black Amon_RA's recovery. You have the stock FRF91 recovery, because you've flashed a stock image - and it overwrites everything, including recovery. Amon_RA wouldn't require to enable USB debugging to have ADB working in recovery.
I hope you have the ADB driver installed correctly. Please double-check that.
And after you do, if it's installed and you can't do anything - please look at my signature, go to the link, find "unroot / restore your Nexus", and execute. Download the latest FRG83 ROM from HTC, the link is also in the Wiki.

Jack_R1 said:
The problem is that you don't have the black Amon_RA's recovery. You have the stock FRF91 recovery, because you've flashed a stock image - and it overwrites everything, including recovery. Amon_RA wouldn't require to enable USB debugging to have ADB working in recovery.
I hope you have the ADB driver installed correctly. Please double-check that.
And after you do, if it's installed and you can't do anything - please look at my signature, go to the link, find "unroot / restore your Nexus", and execute. Download the latest FRG83 ROM from HTC, the link is also in the Wiki.
Click to expand...
Click to collapse
My drivers are installed correctly, since I used them to flash Amon_RA earlier today.
Gonna try the unroot thing in the wiki.

Tried the superboot and :
I get FAILED( remote : not allowed) in the FASTBOOT USB recovery page
It hangs at downloading boot.img .... on the HBOOT recovery page. Should it take more the 3-4 mins?
On the superboot thread, he says an unlocked bootloader is required. Don't think it will work.

What superboot?
It was "UNROOT", not "ROOT"! Using PASSIMG method.
DO NOT revert HBOOT to older version. I've updated the page.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus

Use the passimg method, and use a card reader on your PC to get the zip to your SD card...
I think you want FRG83 (not sure what shipped with the SLCD)?
Sent from my Nexus One using XDA App

FRG83 it is.

Jack_R1 said:
What superboot?
It was "UNROOT", not "ROOT"! Using PASSIMG method.
DO NOT revert HBOOT to older version. I've updated the page.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
OK, I'll need to get a SDcard to microSD adapter to try this I guess.

You can always unlock, and use fastboot - but I'm guessing you don't want to?
Sent from my Nexus One using XDA App

danger-rat said:
You can always unlock, and use fastboot - but I'm guessing you don't want to?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You're right, I don't want to
Ok, I downloaded signed-passion-img-FRG83_0923.zip from the htc website, renamed it to PASSIMG.ZIP. Copied it to the root of my sd card then booted into recovery. As soon as it enters it scans for various PASSIMG.XXX files, find the PASSIMG.ZIP file and starts a progress bar which lasts 20 sec. When the progress bar completes, it returns to the recovery menu and I can reboot. It never really asks me anything.
But reboot still leads me to the black screen.
I think it didn't do the update

Kapoue2 said:
When the progress bar completes, it returns to the recovery menu
Click to expand...
Click to collapse
Can you now see the recovery menu, or do you mean boot menu?
Sent from my Nexus One using XDA App

[Q] Clockwork Mod wont go into recovery

FYI, I am new to the game
Been doing a lot of research and decided to root with Z4 and to use Rom Manager (rooting isn't the issue). Flash ClockworkMod Recovery works fine. My problem - When attempting to Reboot into Recovery my hero attempts to reboot but stays at the opening HTC image.
Any ideas?

Try to make it go into recovery through ADB. I think that's the command program. Not sure. I'm very forgetful today.

Open up Rom Manager and flash alternate recovery then re-flash Clockwork Recovery. Hope that helps
Sent from my HERO200 using XDA App

Wonderful! Alternate worked. Thanks!!!

bigbird5788 said:
Wonderful! Alternate worked. Thanks!!!
Click to expand...
Click to collapse
Glad I could help
Sent from my HERO200 using XDA App

EASY ClockworkMod Recovery Fastboot for Cricket! [Updated: 4/23]

[04/23]
It couldnt be easier
Download openZIO-clockworkmod-recovery-pack.zip
Extract to C:\
Run "m6000_setup.msi" in the CWM folder and Follow install.
**you may encounter software signature issues, just 'install software/driver anyway'.
Plug in your phone to USB, power down.
Boot to fastboot (Hold Send/End simultaneously til fastboot starts)
open a command prompt and navigate to the "CWM" directory
Code:
cd\
cd CWM
Fastboot boot into openzio_clockwork-recovery image
Code:
fastboot boot clockwork-recovery.img
Profit.
***You will Lose your Kyocera Logo once you RESTORE (due to the way cwm dumps the boot partition).
Please download the openZIO Boot Fix and install the zip with CWM.
This will flash the correct boot image and restore your Kyocera Logo.
-------
[03/22]
I have edited this initial post because I have found a workaround to get clockwork recovery to load on the ZIO without wiping data/cache.
Unfortunately, until Koush gets the module fixed to run remotely from our phones, you will need to be connected to a PC, and know how to use Fastboot.
blah blah DISCLAIMER blah: I am not responsible IN ANY WAY for people screwing up/bricking their phones as a result of using this image.
....old method deleted by OP....
Thanks go out to Hotaru for compiling this recovery image, and obviously to Koush for making clockworkmod recovery.
Remember to hit the "Thanks" button if I helped you.

try downloading ROM Manager from the Market and then having it install the recovery.

Our phone isnt in the phone model list.
Install from sdcard prompts me to install clockworkmod recovery first.
Sent from my Zio using XDA App

isnt there a custom recovery option???? bet you can save that image from the page to the sd card and then run it through rom manager???
BTW I hate rom manager LOL.... I tryied to use it to format my sd card for link2sd.... and it tried to boot thephone into boot or recovery or something.... and ended up completely factory resetting my phone
hell I had even installed a handfull of apps before it happend LOL and my dumb ass didnt do a TI backup....

dreamstryder said:
isnt there a custom recovery option???? bet you can save that image from the page to the sd card and then run it through rom manager???
....
Click to expand...
Click to collapse
How would this be accomplished?
Everytime I choose to install from SD, it prompts me to install clockworkmod recovery first
*edit: "Flash Alternate Recovery" is grayed out as well.
Sent from my Zio using XDA App

Maybe someone still running 1.6 could try and flash the M6000 recovery?

Spz0 said:
How would this be accomplished?
Everytime I choose to install from SD, it prompts me to install clockworkmod recovery first
*edit: "Flash Alternate Recovery" is grayed out as well.
Sent from my Zio using XDA App
Click to expand...
Click to collapse
'
betcha you have to have the premium version of clockwork to bwe able to flash alternate recoveries... I dont trust it enough right now to buy it and find out lol

dreamstryder said:
'
betcha you have to have the premium version of clockwork to bwe able to flash alternate recoveries... I dont trust it enough right now to buy it and find out lol
Click to expand...
Click to collapse
odd thing about it, is that I _do_ have premium. o.0

maybe you have to drop the image into a certain directory then?????? for clockwork to find it???

dreamstryder said:
maybe you have to drop the image into a certain directory then?????? for clockwork to find it???
Click to expand...
Click to collapse
/sdcard/clockworkmod/*
Nogo either.

how did the people get rom manager to see thier custom recovery when they was experimenting with sprints 2.1 stuff???

dreamstryder said:
how did the people get rom manager to see thier custom recovery when they was experimenting with sprints 2.1 stuff???
Click to expand...
Click to collapse
Well, we used fastboot to load it up.
Then used adb to tell it to boot into recovery. There was also some key combo I forget. It's all around page 30 or so of the 1.6 thread.

What do we need to do to make clockworkmod work?
Sent from my from my rooted 2.2 no bloat Zio using XDA App

I'd suggest that we all send an email to koush at clockworkmod asking for support.
I'm working on building a compatible version, but I'm running into all sorts of build issues.
Sent from my Zio using XDA App

What's the email address?
Sent from my Zio using XDA Premium App

Those images generally need to be flashed through fastboot, and fastboot might not even work depending on the bootloader.
you need the sdk installed first, and adb working and added to your $path.
after that
Code:
adb reboot bootloader
Code:
fastboot flash recovery /path/to/recovery.img
obviously, replace path/to/recoery with the actual path that you downloaded the file to.

That revocery image (I found out) is for the 1.6 OS.
Being as we have 2.2 and an updated kernel: would this recovery still work?
Guess I'll be the guinea pig for this afternoon. o.0
edit:
adb reboot bootloader is for our modem download mode.
To access fastboot, we just power down, then hold the power/end and send key simultaneously.

recovery only cares about the hardware, not the os or kernel, thats why you use it to flash custom roms and kernels. It boots before anything else is loaded.

Spz0 said:
adb reboot bootloader is for our modem download mode.
To access fastboot, we just power down, then hold the power/end and send key simultaneously.
Click to expand...
Click to collapse
Thanks good to know. Thanks.

option94 said:
recovery only cares about the hardware, not the os or kernel, thats why you use it to flash custom roms and kernels. It boots before anything else is loaded.
Click to expand...
Click to collapse
Nice also good to know :-D
I'll flash it when I'm home and post results.
Sent from my Zio using XDA App

[SOLVED]What Happened???

I decide to play with my G1 and it won't let me flash anymore ROMs via ROM Manager and even though I have my SU icon in my app drawer my phone isn't giving any root access to ANY app that requires it to work.
DREAM PVT 32B SHIP S-ON
HBOOT-1.33.0013d
CPLD-4
RADIO-2.22.28.25
I don't know why I have S-ON all of a sudden since I rooted this phone almost 2yrs ago. Does anyone have any advice. Thx in Advance.
Sent from my HTC Dream using xda premium

well in those past two years you have updated to the .13d spl and this a hacked up spl to give you more ram. it isn't fully s-off but rather you are limited.
not sure what you have done to your phone so I can't tell you how to fix it. my suggestion would be to fastboot -w or superwipe from recovery, then flash your rom again (and whatever kernel or mods you want to) also maybe stay away from rom mangaer and also movd to amonra recovery. again only suggestions being I don't know what you did you may as well start fresh
Sent from my HTC Vision using xda premium

But now I can't use all of the apps I bought that require root access anymore. This kinds of defeats the purpose of having root. And I also still have the SU icon in my app drawer.
Sent from somewhere in th US

demkantor said:
well in those past two years you have updated to the .13d spl and this a hacked up spl to give you more ram. it isn't fully s-off but rather you are limited.
not sure what you have done to your phone so I can't tell you how to fix it. my suggestion would be to fastboot -w or superwipe from recovery, then flash your rom again (and whatever kernel or mods you want to) also maybe stay away from rom mangaer and also movd to amonra recovery. again only suggestions being I don't know what you did you may as well start fresh
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Well the phone still let's me flash different roms from my sd card but I would love to use the rooted apps that I paid for 2yrs ago.lol.
Sent from somewhere in th US

Well have you done the steps I suggested?
1) flash amonra recovery
2) either fastboot -w or superwipe or both
3) flash new rom via amonra recovery
Any problems you have had should be fixed now
If you can explain to me a bit better what you did I may have a simpler way of fixing things but if you can't the above method should do the trick
Sent from my GT-I9100 using xda premium

He probably doesn't know how to use recovery -___-
this is why i never liked the whole ROM Manager idea...
OP: You won't lose apps you bought, because Google keeps track of your purchases and lets you re-download them.

frankdrey said:
He probably doesn't know how to use recovery -___-
this is why i never liked the whole ROM Manager idea...
OP: You won't lose apps you bought, because Google keeps track of your purchases and lets you re-download them.
Click to expand...
Click to collapse
I know I won't lose apps the point that I was trying to make was that I can no longer use theses apps because they require root access permission to run/work.

demkantor said:
Well have you done the steps I suggested?
1) flash amonra recovery
2) either fastboot -w or superwipe or both
3) flash new rom via amonra recovery
Any problems you have had should be fixed now
If you can explain to me a bit better what you did I may have a simpler way of fixing things but if you can't the above method should do the trick
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't push files via ADB/USB port anymore because the USB port on my phone has taken a nose dive.

well you can flash the new recovery via terminal emulator if you want, or you can attempt to do it with rom manager (not a big fan of rom manager, kinda sucks)
superwipe scripts can be flashed via recovery (cw or amonra) flashing the rom again in recovery
again not sure what you did, you only said what dosent work, this should make your root apps work
just wiping clean and and a clean install of the rom should make them work
Sent from my HTC Vision using xda premium

demkantor said:
well you can flash the new recovery via terminal emulator if you want, or you can attempt to do it with rom manager (not a big fan of rom manager, kinda sucks)
superwipe scripts can be flashed via recovery (cw or amonra) flashing the rom again in recovery
again not sure what you did, you only said what dosent work, this should make your root apps work
just wiping clean and and a clean install of the rom should make them work
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
My old sd card went bad so I had to replace it with a new one. I also clicked on the github link he has posted in the forum and I downloaded amonra_bootable_recovery folder/file as a zip. Should I also update the SPL?
Sent from the Redlight District.

well updating your recovery doesn't have much to do with updating your spl but it doesn't mean you shouldn't
the most updated spl for the dream is the .13d
if you have something else then I suggest it as you get acess to additional ram if you do (~14mb)
if you do make sure you first have the appropriate radio or you could brick your phone, either the .25 or the .08 are the only radios that work with the .13d spl
to check what you have right now, power on while holding the camera button
Sent from my HTC Vision using xda premium

I have that info on my first post of my thread. Is what I've posted the correct SPL & Radio for this to work?
Sent from the Redlight District.

you have the most updated radio and spl, although with the .13d hboot you can not flash a new recovery via fastboot, but you should still be able to via terminal emulator or if you can find the proper image in a .zip and be flashed through your current recovery. of course you should also be able to flash an alternative (amonra) recovey with rom manager. choose whatever way is easier.
and remember that flashing amonra recovery is only a suggestion and will not by itself fix your problem, I just prefer it over clockwork on the g1
mostly you should be concerned with backing up what is needed, wipeing fully, and the flashing a new rom
Sent from my HTC Vision using xda premium

demkantor said:
you have the most updated radio and spl, although with the .13d hboot you can not flash a new recovery via fastboot, but you should still be able to via terminal emulator or if you can find the proper image in a .zip and be flashed through your current recovery. of course you should also be able to flash an alternative (amonra) recovey with rom manager. choose whatever way is easier.
and remember that flashing amonra recovery is only a suggestion and will not by itself fix your problem, I just prefer it over clockwork on the g1
mostly you should be concerned with backing up what is needed, wipeing fully, and the flashing a new rom
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I'll look around the forum about updating the hboot on my device. Thx for the intel.
Sent from the Redlight District.

ummm, sorry if I wasn't clear, any change to you hboot/spl/bootloader (all the same thing) would be a downgrade. the only benifit you may get would be the ability to use fastboot to flash a recovery (or other partitions) if this really is what you want, flash the orange.nbh (found in ezterrys 2708+ thread) but after flashing a new recovery I would suggest going back to your current radio/spl as it is supperior in every other way
Sent from my HTC Vision using xda premium

demkantor said:
ummm, sorry if I wasn't clear, any change to you hboot/spl/bootloader (all the same thing) would be a downgrade. the only benifit you may get would be the ability to use fastboot to flash a recovery (or other partitions) if this really is what you want, flash the orange.nbh (found in ezterrys 2708+ thread) but after flashing a new recovery I would suggest going back to your current radio/spl as it is supperior in every other way
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
So in other words "If it ain't broke don't try to fix it"lol Plus all I really want is my s-off again, hell it's been so long since I've played with this phone I can't even remember how to get into the recovery screen.
Sent from the Redlight District.

How can I check to see what recovery I have before I do something unneccessary?
Sent from the Redlight District.

like isaid earlier you have the best spl for the dream, the only downfall is the semi s-on. but this is only in the fastboot sense, it isn't true s-on and with th is spl you can still have root
easiest way to boot to recovery (if rom allows) hold power, choose reboot, choose reboot recovery. you can also reboot recovery via adb (adb reboot recovery) or various apps allow this too
if this is to much info, power off. then power on while holding the home button
Sent from my HTC Vision using xda premium

demkantor said:
like isaid earlier you have the best spl for the dream, the only downfall is the semi s-on. but this is only in the fastboot sense, it isn't true s-on and with th is spl you can still have root
easiest way to boot to recovery (if rom allows) hold power, choose reboot, choose reboot recovery. you can also reboot recovery via adb (adb reboot recovery) or various apps allow this too
if this is to much info, power off. then power on while holding the home button
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
So can I flash the new recovery image from there as well or does it has to be done via fastboot?
Sent from the Redlight District.

Help!! can't boot phone

Hello,
I just got my One today, and I've been trying to root it and stuff. I unlocked the bootloader successfully, then tried flashing the custom recoveries. For some reason only cwm (regular) worked; the other ones (cwm touch and TWRP) flashed successfully, but when I tried going into recovery, the phone would be on the "booting into recovery screen", then just turn off.
Anyways, I just continued with cwm regular, but it kept saying "can't mount /cache/recovery/command, log, last_log,..." basically lots of that stuff on the bottom. I ignored that. Then, I put superuser.zip into the SD card, but clockworkmod could not find the sd card stuff.
Finally, in CWM, I formattted /system, /sdcard, /external_sd, /data and /data/media. Then the phone would ONLY boot straight into the bootloader (even if I did NOT hold down), could not even open recovery. So I flashed the same cwm recovery again.
Now I can only go into bootloader and recovery. Sorry for the long post, and thanks for any help in advance.

I'm just guessing but I think it's because you formatted everything and never flashed a rom. So there's just nothing on your phone, it can only boot into the bootloader because everything else was formatted.
Sent from my HTCONE using xda app-developers app

theman97 said:
I'm just guessing but I think it's because you formatted everything and never flashed a rom. So there's just nothing on your phone, it can only boot into the bootloader because everything else was formatted.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
That sounds reasonable. Does anyone know how to "put" something on the phone? even just stock stuff, so I can boot?

Relock your bootloader then use an RUU. Then unlock and try again.
http://forum.xda-developers.com/showthread.php?t=2253182
Sent from my HTCONE using xda app-developers app

twilightnx said:
That sounds reasonable. Does anyone know how to "put" something on the phone? even just stock stuff, so I can boot?
Click to expand...
Click to collapse
Adb push a rom onto the phone. Google adb if you don't know how to use it.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Don't RUU use this tool makes it easy
http://forum.xda-developers.com/showthread.php?p=40341536
Also download a Rom you want and just click on sideload Rom, you may also have to click install HTC drivers first too.
Sent from my HTCONE using xda app-developers app

theman97 said:
Relock your bootloader then use an RUU. Then unlock and try again.
http://forum.xda-developers.com/showthread.php?t=2253182
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Thank you! My problem's been solved.
Can a mod lock this thread?

twilightnx said:
Thank you! My problem's been solved.
Can a mod lock this thread?
Click to expand...
Click to collapse
The thread will eventually drift away. Next time, post in the Q&A forum. More importantly, don't rely on a toolkit to save you. Sometimes, they don't work. The actual fix to this problem is fairly trivial (and to poster above, doesn't necessarily involve ADB either). If were trying to simply push stock software back on, it's three (well, in your case two) fastboot commands:
fastboot flash boot <path-to-boot.img>
flash system <path-to-system.img>
After unzipping a factory .tar. It's worth learning how to do in case this happens again.