Database Develop

help with g1 cant get into recovery

hi, after installing the rom manager premium and installing the latest nightly build i no longer can access the recovery. i installed the latest recovery the rom manager said to do, and now i reboot my phone and hold the home button and it just stays in the g1 screen. if i reboot and hold the home button while the phone is connected to usb the phone enters the fastboo g1 bootlader but in the same g1 screen but with red letteres on the corner. i need help. thanks.
fastboot still works but i dont want to have to do all that process again

I would just flash another recovery with fast boot. You won't ned to re root
Sent from my SGH-T959 using XDA App

how do i do this?

djbootleg said:
how do i do this?
Click to expand...
Click to collapse
1: use ADB :
connect ur device with PC , use CMD : type path to ADB folder and then
type : adb shell : enter
type : #mount -a
type : #flash_image recovery /sdcard/recovery.img
reboot
2 : use terminal :
type $Su
type #mount -a
type : #flash_image recovery /sdcard/recovery.img
3 : use Droid explorer tool : download and install newest version
copy img file to sdcard
connect ur device with pc
u'll see a red icon ( Fl ) , click there and show the path to ur img file => ok wait 1' and reboot ur fone
if unsuccessful, u can change ur sdcard and try again !!! ^^

I ran into this issue as well, assuming it's a bug with the latest update of ROM Manager (which I just updated this morning prior to getting this issue.)
Not sure if it had anything to do with the fix but after some fiddling I decided to try reinstalling the ROM Manager recovery (after reinstalling the amon ra recovery from the same app with no success) and it worked, YMMV obviously but that worked for me.

This happened to me too!

How to flash stock recovery.

Hi guys,
I have to send me N1 to htc for fix some problem.
I have RA recovery with lock bootloader, and I want to flash the original, but "fastboot" way doesen't work (signature fail ).
How can i flash it in other way?
Ty
(sry for my eng )

Just flash the stock rom with the recovery image like frf92 original.

evilkorn said:
Just flash the stock rom with the recovery image like frf92 original.
Click to expand...
Click to collapse
How? Through recovery? Because "fastboot" hates me, and won't work.

I'd suggest using a passimg for frf85b and then maybe updating to 91 (or just leave it at 85), you can always re-root when you get it back.
________________________
N1 w/ XDA App

got it, thk to cyanogen wiki
Plug the phone into the computer
Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
Code:
adb devices
​A device name and 'recovery' should be returned
Code:
adb push recovery.img /sdcard/recovery.img
​recovery.img is located on android-sdk/tools dir
Code:
adb shell flash_image recovery /sdcard/recovery.img
​This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
Reboot

nrdmtt said:
got it, thk to cyanogen wiki
Click to expand...
Click to collapse
Thanks for searching!
I hope this encourages other users new to ADB, flashing ROMs, etc. to continue to search after asking for help.
Way to go nrdmtt!!

[MOD-HOW TO] Root with One click root - Superboot.img

Hi all,
Here is a alternative method (faster) to root the Nexus S (I9020 and I9023), not need to flash custom recovery.
The aim of the One click root, by Paul O'Brien method is to replace the stock boot.img by a superboot.img (with su and Superuser.apk) to obtain root access.
APPLY THIS AT YOUR OWN RISK!
Intructions:
1- Prerequisites:
- USB drivers installed
- Nexus S recognised in bootloader mode
- Unlocked bootloader
For these manipulations: here (I9020T) or here (I9023 & I9020a)
2- Process
- Download the file "Build_NexusS_One-click-root.zip" corresponding to your build (very important !) : here
WARNING: GRJ22 version: issue with Bluetooth, don't use it, unless you don't care bluetooth, I will try to solve this problem.
While waiting to find a solution, just flash the stock boot.img (2.3.4) if you have the BT problem, for this:
In bootloader mode, type in the console (or terminal...): "fastboot flash boot boot.img". Bluetooth will work and you keep root access.
Click to expand...
Click to collapse
- Unzip it in a directory
- Turn On the phone in bootloader mode (by holding down the Power and Volume Up buttons)
# Windows:
Just double click "install-superboot-windows.bat" (in the extracted folder)
# Linux
- Open a terminal (Ctrl + Alt + T)
- Change directory to the extracted folder:
Code:
cd /.../"Build_NexusS_One-click-root"
- Type:
Code:
chmod +x install-superboot-linux.sh
- Then:
Code:
./install-superboot-linux.sh
# Mac
- Change directory to the extracted folder:
Code:
cd /.../"Build_NexusS_One-click-root"
- Type :
Code:
chmod +x install-superboot-mac.sh
- Then:
Code:
./install-superboot-mac.sh
Your Nexus S is now rooted !
Adapted from: http://android.modaco.com/topic/327000-07mar-gri40-colour-revert-superboot-rooting-the-nexus-s/
PS: sorry for my language.

I appreciate you trying to help but if an unlocked bootloader and drivers are required then why not just fastboot flash recovery and install the su zip in recovery. IMO this is unnecessary really.
Sent from a lounge chair on my deck.

What is the easiest and fastest ?
1- double clic on a file or
2- flash recovery + flash su.zip in recovery ?
This method isn't necessary you're right, like I said it's an alternative "method".

Chamb' said:
What is the easiest and fastest ?
1- double clic on a file or
2- flash recovery + flash su.zip in recovery ?
This method isn't necessary you're right, like I said it's an alternative "method".
Click to expand...
Click to collapse
Flash recovery + flash su zip gives you, more control I think also I'm tired of people flash ROMs and then having problems and whining about how they need step by step directions when you suggest adb to help them fix it... I mean if you are gonna mod and hack at least learn what you are doing first....
/end rant
Also yes clicking is easier but IMO installing, the drivers (which your method requires) IS the hardest part.

This worked perfectly for me. Couldn't figure out the other way of rooting but this was simple so thank-you
Sent from my Nexus S using XDA App

Bluetooth cannot be enabled anymore
After rooting the Nexus S with Android 2.3.4 with this rooting instruction I cannot enable Bluetooth anymore. When I try to enable Bluetooth it says "Turning on.." but stops after two seconds and goes back into disabled Bluetooth state.
Bluetooth worked before just fine. Why did this happen and how can I resolve it?
Log file entries when switching on BLuetooth:
Code:
DEBUG/BluetoothService(120): Bluetooth state 10 -> 11
VERBOSE/BluetoothEventRedirector(562): Received android.bluetooth.adapter.action.STATE_CHANGED
INFO/bluedroid(120): Starting hciattach daemon
ERROR/bluedroid(120): bt_enable: Timeout waiting for HCI device to come up
DEBUG/BluetoothService(120): Bluetooth state 11 -> 10
VERBOSE/BluetoothEventRedirector(562): Received android.bluetooth.adapter.action.STATE_CHANGED

This is a problem I've seen occur after the root, not with this method but it can happen apparently, some people had this issue.
But I do not know the cause, the kernel is 100 % stock.
Try this:
- delete the superboot folder (/) and the su file (/system/xbin) with a root explorer
- then reboot the phone in bootloader mode and flash the stock boot.img (2.3.4) by typing "fastboot flash boot boot.img"
Now you're unroot
- then retry the one click root

[ROM] Unmodified AOSP 2.3.5 compiled 8/11/2011

This is nothing more than a download and compile of the code from android.git.kernel.org compiled with target=crespo
It has absolutely no mods, and 1 file was added to the build to fix the accelerometer. (Many thanks to BuglessPete for informing me the file I needed)
Again, it doesnt get any more basic than this.
I was looking for an unmodified AOSP build, and couldnt find one that didnt seem to have some mods, so I figured i'd build it and share incase anyone else is looking.
Instructions:
Download the zip file.
You will need fastboot and adb for windows.
once you've got these files, extract everything into one directory.
eg, fastboot adb AND the rom files are in the same directory.
If you've never modded your phone (really?) you will need to unlock it.
open a command prompt and go to the dir you extracted everything to and run:
THIS WILL WIPE ALL DATA. BACKUP FIRST.
Turn on USB Debugging.
Connect the phone to your computer.
run these commands:
adb reboot bootloader
wait until android BL screen appears and then type
fastboot oem unlock
You should now have an open lock below the google logo when the phone reboots.
Let it go through its paces, then when the screen comes up to the "Welcome to Nexus S" and skip everything, and go make sure USB debugging is enabled.
then run:
adb reboot bootloader
when at the bootloader, you may do:
fastboot -w flashall (This should flash the entire phone, boot,recovery,system & userdata)
If the doesnt work for whatever reason, use these commands:
fastboot flash system system.img
fastboot flash recovery recovery.img (omit this if you have CWM and want to keep it)
fastboot flash boot boot.img
fastboot flash userdata userdata.img
This should get you a basic, straight AOSP of GB 2.3.5 WITH NO GAPPS.
I used the latest from CM7.
Other considerations:
If you are on a 9020A (ATT) 2.3.5 will not allow you to flash if your baseband is UCKE1.
This baseband doesnt allow HSUPA, so I recommend ditching it anyway.
Go here and install Radio KD1 (NOT UCKD1!)using window7's instructions.
Obviously, I am not responsible for the any planetary damage done by this, to your phone, or subsequent brickings that may occur (has any one bricked a Nexus S?)
Credit would go to google, and BuglessPete.

Thanks so much. I built this the other day, but I hit the same problem with the accelerometer. Please share how you fixed it.

BuglessPete informed me the file that needed to be added. It is libakm.so
I pulled it from CM7 nitely 159 (this is 2.3.5, not sure if they got their hands on source, but figured if it works on theirs and is the same version, it was the best bet rather than using 2.3.4 version that was on my phone)
The file resides in a build rom in /system/vendor/lib
Extract this file and place it in vendor/samsung/crespo/proprietary
then edit vendor/samsung/crespo/device-crespo.mk
add the file to the list of files to copy in the PRODUCT_COPY_FILES += \
then add
vendor/samsung/crespo/proprietary/libakm.so:system/vendor/lib/libakm.so
this is my edited file:
Code:
# Prebuilt libraries that are needed to build open-source libraries
PRODUCT_COPY_FILES := \
vendor/samsung/crespo/proprietary/libsecril-client.so:obj/lib/libsecril-client.so
# Samsung blobs necessary for crespo
PRODUCT_COPY_FILES += \
vendor/samsung/crespo/proprietary/libsecril-client.so:system/lib/libsecril-client.so \
vendor/samsung/crespo/proprietary/samsung_mfc_fw.bin:system/vendor/firmware/samsung_mfc_fw.bin \
vendor/samsung/crespo/proprietary/libsec-ril.so:system/vendor/lib/libsec-ril.so \
vendor/samsung/crespo/proprietary/libakm.so:system/vendor/lib/libakm.so
That should make the accelerometer work.

I accidentally deleted system/lib/hw folder from root browser and there was blackout on screen what shall I do to replace the hw folder

IamAndroidOne said:
I accidentally deleted system/lib/hw folder from root browser and there was blackout on screen what shall I do to replace the hw folder
Click to expand...
Click to collapse
Dirty flash the ROM..

Link doesn't work

[Q] Flashing CM7

Hi all!
Last week I bought a used but still good-looking T-Mobile G1 (HTC Dream). The previous owner has rootet it (Android 1.6 is installed) and this are the infos:
Firmware-version: 1.6
Baseband-version: 62.50S.20.17U_2.22.19.26I
Kernel-version: 2.6.29-00479-g3c7df37
[email protected] #19
Build-number: DRC92
Click to expand...
Click to collapse
I looked through the forums here on XDA and found a laggy ICS-port, so I want to flash Gingerbread (CM7).
I've already flashed my Galaxy S, a friend's Galaxy R and my Asus Transformer tab, without any problems.
But flashing HTC-devices seems a little bit more complicated.
So what do I need to do? In the CyanogenWiki there's 'Danger_SPL' mentioned, guess I'll need it?
I don't need a looooong step-by-step-guide the correct threads or pages would be enough.
Thanks,
Lunch

need to know more about your phone, boot into bootloader mode (hold power + camera)
write down everything on this screen

DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial 0
Click to expand...
Click to collapse
(at the moment it's connected with my PC for chrarging, this should explain Serial 0, right?)
Hope this helps.

ok so even if it is rooted the radio and spl need to be updated, which recovery is on there. (power on holding home button)

Ok, I bought it like this and didn't change anything...
Recovery: Android system recovery <2e>
(blue font)

ok you want amonra's recovery found here
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
this guide will help you root and update your phone, being your phone is rooted do not flash the dreaming.nbh or you will be reverted back to android 1.0 and loose root
you want to skip that step and go to flash amonra via terminal emulator
then update radio via recovery
then update to danger spl (must have radio updated first or you will brick!)
then i recommended flashing cm5 + gapps found in this link
once you finished this and confirmed all is working you want to update radio and spl further to be able to flash the newest roms, info here:
http://forum.xda-developers.com/showthread.php?t=831139
good luck and let me know if you get stuck (also the search function in xda is great and most of your question will have been answered, peek around a bit its more rewarding than having your hand held)

Thanks a lot for your help, I'll try it!

One quick question about the Telnet-app: do I have to write flash_image recovery /sdcard/recovery.img into the left text field and 23 in the right?
Error while connecting to server: localhost/127.0.0.1:23 - Connection refused
What do I do wrong? With Terminal Emulator the command isn't found...

telnet may not work thats ok
in terminal emulator you need to give yourself superuser permissions first
type su
then say yes to prompt
you are rooted right? do you have superuser.apk in app drawer?

Yes, I'm rooted and I'm su in Terminal Emulator.
Then there's this message: flash_image: not found
But the file is on the root of the sdcard, named recovery.img ...
And when navigating to /sdcard via Terminal Emulator and typing ls I see the recovery.img-file...

if you use windows it will auto add extentions, ie if you name it recovery.img it will read recovery.img.img
try naming it just recovery
also if it came in a .zip make sure you extract it so its a .img
Sent from my HTC Vision using xda premium

No, it's definetely named recovery.img ...
Is there another possibility to flash the recovery-file (via ADB for example)?

yes adb should work fine. i cant remember the command to type when you in adb but just by typing adb into the cmd you will get a list of commands including how to push the file/image you need.
Sent from my HTC Vision using xda premium

cd <adb-folder>
adb devices
adb shell
su
adb flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Would this be possible (I can't test it now, phone is charging atm).
Thanks

that might just be perfect, but you said that didnt work from terminal emulator and a shell is nearly the same,
its worth a shot. being you are rooted you can try the orange.nbh and you will have an engineering spl where fastboot commands work and i can easly explain those (i dont use adb much but have used fastboot many time) so if adb dosent work for you check out one of the many guides out there or try ornage.nbh and fastboot
Sent from my HTC Vision using xda premium

Same message: flash_image: not found, but with ls I can see it...
Ok, my phone is rooted, I have the Superuser-app in my app drawer, I'm root when accessing the sdcard, I see the file when typing ls. What do I do wrong?
I've never run in trouble when rooting my Galaxy S or my Transformer tab. But my G1 seems quite defiant.

well not being there its hard to say, now try the ornage.nbh
youll find this file in the development section under ezterry's thread under 2708+ update 14mb ram hack. rename the image dreaming.nbh and put it on sdcard. now boot into hboot (power+ camera) and say yes to the prompt. this will allow you to use fastboot and allow you to flash recovery, radio and spl. when/if this all works then boot into recovery (home + power) and flash rom
Sent from my HTC Vision using xda premium

Ok, I'll try, thanks!
Just to go sure:
- I download orange-1.58......nbh from here: http://forum.xda-developers.com/showthread.php?t=831139 , rename it and put it onto my sdcard
- Flash it in fastboot (fastboot = hboot?)
- Flash Amon_Ra-recovery from cyanogenwiki
- flash spl (radio needed too?)
- ?

Don't want to mix in, but just some few stuff you should know:
Fastboot is a sort of recovery on your pc, although this has much more safety measures.
That .nbh file is a file that is a fresh new start to your phone: Like you have a new phone
From Fastboot you can flash a recovery, that you can take with you everywhere
The SPL/RADIO are BOTH needed to succeed. Cheers and if I made any mistakes, please point me to them

fastboot is within the bootloader. it is a .exe program in your sdk package and works similar to adb. the orange.nbh needs to be renamed dreaming.nbh and when you boot into your bootloader it will rewrite your recovery, radio, system, spl etc
the new hboot you get will have a fastboot option in it. connect the phone via usb and when in fastboot mode you will see fastboot usb in red on your phone. you will open a cmd in the same way as adb and will type fastboot devices just live adb to make sure you are attached.
the rest is explained in the op of that thread
Sent from my HTC Vision using xda premium