Database Develop

[Q] cant boot into recovery

so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04

drawde40599 said:
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
Click to expand...
Click to collapse
Use fastboot to re-flash recovery img

lcchan1 said:
Use fastboot to re-flash recovery img
Click to expand...
Click to collapse
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?

drawde40599 said:
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
Click to expand...
Click to collapse
download clockwork recovery from the app store.
Flash its recovery, then boot into recovery after a successful flash.
Out of curiosity, why did you install a non-rooted version of 2.3.3.?

You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.

Rusty! said:
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Click to expand...
Click to collapse
HELL YA !! thank u much

Thread moved to Q&A, a sub-forum dedicated exclusively for questions like these. Please post all further questions here. Do not post new question threads in development, as you are not doing any even remotely related to Android development. That said, I'm glad you were able to figure out your issue.

Downloading clockworkmod will not work. He is not rooted so he can't flash the recovery with it.
Sent from my Nexus One using XDA App

This happened to me 2 days ago (word by word)!!
From Amon Recovery's page, this is what the problem is:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here"
Here: http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
My problem was even more complicated because I tried flashing froyo without a wipe so my phone started going into boot loop!
Thanks to danger-rat's reply, I was able to get into recovery at least once and then everything came back under control. He said "Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to..."
Here's my thread:
http://forum.xda-developers.com/showthread.php?t=980577
edit: I just realized that you are not able to fastboot either? I was able fastboot and flash recovery onto my phone and then without turning the phone off - I was able to go into recovery straight after flashing amon_recovery.img

passimg back to an earlier version of Android, root, then install a pre-rooted GB...
If you get the "main version is older" error, you're out of luck and your only option is to unlock the bootloader or wait for a new method to be found...
Sent from my Nexus One using XDA App

[Q] Is Fastboot the answer to my woes?

I want to flash a new radio and kernel to my G1 that is running CM6. My signal is atrocious and I get a few random oddities each day.
I have tried the recovery flash for the radio at least 6 times now in various ways following various guides and every time I do it it crashes my phone and I end up flashing the image, rooting, etc, to get back to CM6. it takes me over an hour to get back to normal and it just plain sucks!
So my question is..... Can I use fastboot flash to flash the image files for the radio and the kernel without being on the special Hboot 1.33.0013d and such?
I was planning to use the instructions from the ezterry kernel page and just want to check that I wont bork up my phone. I seem to recall that the fastboot flash bypasses all the need for FR-remove and such but want a second opinion before I take the dive this way.

Not trying to drive you away from CM 6, but have you tested other ROM to see if it has the same problem or similar.
I personally myself could not get CM6 to work properly on my G1 back when I was trying to use it.

I couldn't get the radio to recovery flash even on the stock ROM after rooting.
I guess I could try a different ROM.
I just now have proven to myself that i cant flash the EzTerry kernel from Rom Manager and clockwork recovery as I am in the midst of yet another image flash, re-root, and such after it wouldn't go past the reboot screen afterwards
This phone is just an extra toy but I am determined to figure it out.
I suppose I will just try the radio.img flash from fastboot tonight when I get home.
As long as I dont brick it I can always start over from scratch.

so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.

FireRaider said:
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
Click to expand...
Click to collapse
do the same thing with the radio and recovery

maximo360 said:
do the same thing with the radio and recovery
Click to expand...
Click to collapse
I got the recoveryand the hboot to flash but damned if I can get any radio to flash.
I get
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
this is with both version of the radio downloaded from the links in the EzTerry thread
What in the world am I doing wrong that I cannot flash a new radio?

installed the spoofSPL... didnt help
edit: Started over again from scratch, rooted, flashed RA recovery, dangerSPL, then fastbooted and managed to install the hboot and the new radio. I guess CM6 hates the newer radios.
edit: Pretty sure CM6 does hate the radio because now its hung up on the install screen.
off to do more research.

People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App

AndDiSa said:
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to get everything work and am running CM6.1+2708 and 0013d with the .27 radio.
Why do we go to the 0013d if it screws up the fastboot? I notice in your signature you are running it also?
And say I want to flash a different rom now? I can only do it from RA recovery, Correct?
But as it stands now I ought to be able to experiment around with the other radio and other roms using recovery without any more issues? Or do they need to have certain parameters?

Once rooted, (to my knowledge) you do not required to re-root it again.
You can use RA Recovery to flash other ROMs with out having to re-root. (as to what I was told) And I recommend RA Recovery instead of ROM Manager/ClockMod Recovery (bad experience with it personnaly).
So as long as the ROM that you want to try is compatible with your current SPL/radio. You should be fine.

[Q] Rooting without flashing a custom recovery?

Is it possible to gain root (on an unlocked + S-OFF device), without flashing a custom recovery?
I've been searching for a couple of hours, but couldn't find a working solution.
The superboot method doesn't seem to be working, something to do with not being able to boot into an image from fastboot anymore (I'm on the latest firmware/hboot).
Any other methods available?
Thanks in advance.

totoguy said:
Is it possible to gain root (on an unlocked + S-OFF device), without flashing a custom recovery?
I've been searching for a couple of hours, but couldn't find a working solution.
The superboot method doesn't seem to be working, something to do with not being able to boot into an image from fastboot anymore (I'm on the latest firmware/hboot).
Any other methods available?
Thanks in advance.
Click to expand...
Click to collapse
If you want to use superboot then use an hBoot of 1.44. other then that you have to flash a custom recovery

These directions are based on Win7 pc...Assuming you have ADB, drivers and fastboot on your machine:
You need a recovery to use temporarily. Download (to your computer) the one you like and proceed:
Reboot phone to bootloader, enter fastboot
The next step temporarily boots your phone to a recovery. On a command prompt, CD to the directory where you downloaded the recovery image, then enter this:
fastboot boot "recovery.img"
You need to replace "recovery.img" with the file name of your choice that you downloaded: CWM or TWRP...also, do not use "quotes"
You should be in CWM or TWRP now.
Backup your phone with the recovery's nandroid...DO IT.
All you need to do is select the option to reboot. When you do, the recovery will ask you if you want to install root. Select "Yes" and you're basically done.
When you phone reboots, it will maintain the stock recovery and you'll have su in system/bin as well as the superuser apk in system/app. Now install busybox from the play store.

oophlamer said:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
I've tried that with the superboot method, and it looks like it's not working anymore with the latest stock rom (or might be a 4.3 change). It just hangs and the phone freezes, until I hard reset with the power button.
I did another search now and it seems that the command might have been replaced with "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img", at least on the Nexus 4.
I'll look into it when I get back home.

totoguy said:
I've tried that with the superboot method, and it looks like it's not working anymore with the latest stock rom (or might be a 4.3 change). It just hangs and the phone freezes, until I hard reset with the power button.
I did another search now and it seems that the command might have been replaced with "fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img", at least on the Nexus 4.
I'll look into it when I get back home.
Click to expand...
Click to collapse
"fastboot boot ..." no longer works as of hboot 1.54+, it used to work on hboot 1.44.

nkk71 said:
"fastboot boot ..." no longer works as of hboot 1.54+, it used to work on hboot 1.44.
Click to expand...
Click to collapse
Exactly what i was going to reply. I had tested this on my stock Hboot 1.54 to keep a 1:1 backup but failed miserably.

I have the same problem...
Any solution?

Help, accidentally deleted OS and recovery

Tried a new ROM but it froze on me. Then tried my back up and it would reboot after like a minute. So decided to do a full wipe but it deleted everything. I can get into the bootloader screen and TWRP but Windows can't read the phone and when it tries to install the drivers some of them fail. I have a copy of my recovery but need to know how to push it back to my phone and get the drivers installed right so that my PC can read my phone. Help.
TWRP seems to now act funny too where it'll like go to sleep and I have to press the home button or power button for a while before it turns the screen back on. Sometimes though I have to do the button combo to get back into recovery.

RUU

So I RUU'd the phone and it's working now, thanks. But it still shows unlocked and with S-OFF. So at this point can I just proceed with rooting it or do I have to lock it and put it back to S-ON before trying to re-root it? Or can I just try rooting it and putting a recovery image on it? It's been a while since I rooted it and obviously there was no 4.3 out at that time.

No need to re-lock or s-on just flash recovery and flash a rooted rom

bigdaddy619 said:
No need to re-lock or s-on just flash recovery and flash a rooted rom
Click to expand...
Click to collapse
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?

QuiQNeZZ said:
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
Click to expand...
Click to collapse
You should be able to flash right over the older version make sure you download a fresh version of 2.6.3.0 from here http://techerrata.com/browse/twrp2/m7wls
Also remember after flashing the recovery.img type fastboot erase cache
The other thing is go into settings/screen and disable screen timeout that should take care of the "freezing" problem

[Q] [Help] Incompatible Bootloader

Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH

Bossk128 said:
Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH
Click to expand...
Click to collapse
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)

072665995 said:
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)
Click to expand...
Click to collapse
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!

Bossk128 said:
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!
Click to expand...
Click to collapse
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually

072665995 said:
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually
Click to expand...
Click to collapse
OK, same as my HOX then. Anyway, I've followed your instructions.
Hm, ROM installed and now trying to flash boot.img (from the rom zip).
Fastboot devices shows one device.
Command line states "sending boot (2182 kb)..." but hasn't changed for over 3 minutes. Handset says Fastboot USB and is unresponsive (as expected) at this moment.
I'll leave it until it errors.
RH
Edit: 30minutes later i pulled the usb cable.
"FAILED (status read failed (Too many links))"
Handset is in the same state, i.e.fastboot/hboot and recovery are fine, but ROM doesn't boot and handset stalls at white screen with green HTC letters.
Any ideas why I can't flash the boot.img?

Success! After reinstalling the the drivers and moving the USB cable to another port, the boot.img was successfully pushed, and booted into CM.
I'll now go for downgrading!
thanks for the help.
RH