Database Info

Need some assistance.

I can get root access. I have RC29. I am trying to install the custom firmware.
This is where i am having the problems:
Install JF's ROM
Download JF's RC30 v1.41 ROM for US users or JF's RC8 v1.41 ROM for UK users or JF's ADP1.1 v1.41 ROM if you have an ADP1 to /sdcard and rename it to update.zip (when you are done it should be "/sdcard/update.zip").
Download the modified recovery and unzip it. Place the file "recovery_testkeys.img" in /sdcard
In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img
Reboot your phone (completely, do not enter recovery yet or your neighbors dog might die)
Once fully rebooted, power off your phone (hold power and select "Power Off"), and hold down home while you turn the power back on.
When you enter the recovery console (which should say "using test keys" if your modified recovery was flashed correctly) hit "alt+L" and then "alt+S" on your keyboard. This will flash the update.zip file that you downloaded and placed there. If you have any problems with this step you missed something above.
I type in all that stuff in telnet and reboot.
Then when I hold the home button and power on I dont see the "using test keys" I see a White triangle with an (!) in it. and a phone. My phones working fine I just cant seem to get the custom JF rom to install.
Please help me out. Thanks in advace.

is anyone havin this problem?

open your keyboard and push "Alt" + "L" when you see the triangle. You should see a menu, then push "Alt" + "S".

wow, it was that easy... i feel like an idiot. sorry for the trouble...

Rooting G1 Help.

Hi. I have tried the tutorial on this site (http://forum.xda-developers.com/showthread.php?t=442480) and a different one (http://www.telesphoreo.org/pipermail/g1-hackers/2009-January/000291.html), but I can't get it to work. I always complete the tutorial with no errors or such, but when I finish, it still says I have RC29. If there are any common mistakes people make, or a different tutorial I should try...I would appreciate any help basically.
Thank you very much!
Edit: I rethought this, and my problem actually is not with rooting. It is with the section "What to do know that you have root". I can't get it to update to RC33.
EDIT 2: I found the problem, when i do the thing where you hold home and power "e:can't open /cache/recovery/command" comes up at the top of the screen.

What exactly are you doing after you are rooted?

Answer
I do this step:
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
And now, the last step! You are still running an old version of Android, but you want to upgrade to the latest and greatest update! You can do this, and not lose root by downloading modified versions of the updates.
First, choose a modified image from the list below:
ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/01/jesusfre...mages-are-out/
RC33: (md5: f24b6c237775147cb4bc42efc2393973)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/02/new-rc33...om-jesusfreke/
RC8: (md5: de2d0d34adbb4015ee3aa5e4e7ca3c07)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/01/jesusfre...mages-are-out/
1. Download the image.
2. Rename it to update.zip.
3. Copy it to your phone's SD card.
4. Turn your phone off.
5. Start up in recovery mode by holding Home and pressing Power.
6. Press alt-W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
7. Press alt-S to apply the update.
Click to expand...
Click to collapse
There are no errors or anything that I experience during it...I just go to about phone after and it still says RC29.

If you want to upgrade to the newest RC, you'll need to download one of the links from the last two "sections" (below)
ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/01/jesusfre...mages-are-out/
RC33: (md5: f24b6c237775147cb4bc42efc2393973)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/02/new-rc33...om-jesusfreke/
These are the files that would upgrade you to RC 30/33 , ADP1.1.
Once you download the file, save it as update.zip.
Turn off the phone, and hold the Home key when you turn it back it.
When it boots to the bootloader, go ahead and update your firmware. It'll change to whatever RC you choose when you get back to the UI

Thanks...
Thanks...but the reason I posted it is that I do the steps you listed, and it still says I have RC29.
The only thing that might help is "e:can't open /cache/recovery/command" comes up on the screen (when you press home and power)

Are you sure you followed the previous instructions (prior to upgrading to RC33/30)?
For example,
1) mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then you need to make sure you correctly flashed the recovery image.
try putting in the recovery image again, and re-flashing (step 3: flash_image recovery recovery.img ) as root

Thanks, I think I'll try starting over. Is there any way to erase what I have done on my phone so far? Or if I start back on step 1, will that not matter even though I have already done all the steps?

Just type off here what you see in:
Settings > About Phone
Firmware Version = ____
Kernal Version = ___
Build Number = ___
Just need to know, so I can tell you were to approximately start again from.
Regards,

Firmware Version =
1.0
Kernal Version =
2.6.25-01843-gfea26b0
[email protected] #6
Build Number =
kila-user 1.0 TC4-RC29 115247
ota-rel-keys,release-keys

clefky10 said:
Firmware Version =
1.0
Kernal Version =
2.6.25-01843-gfea26b0
[email protected] #6
Build Number =
kila-user 1.0 TC4-RC29 115247
ota-rel-keys,release-keys
Click to expand...
Click to collapse
Ok thanks. Start from the bold:
Instructions:
1) Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2) Download the Hard SPL and copy the zip file to the SD card.
3) All files must be on the root of your SD card.
4) Restart your phone. Wait for your phone to start up fully and show the home screen.
5) After your phone starts up, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6) Download an Android "Telnet" application from the Market and connect to localhost.
7) If you connect successfully, you will have a root prompt "#".
8) Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img

Thanks, I'll update with the results.
Edit: I do not extract the file, and I should leave it named update correct?
Thank you so much for your help!

Sounds good. If any errors come up (beside Can't open /cache/recovery/command) lemme know.
EDIT : Correct. Leave the file zipped
Btw : Make sure that you have recovery.img on the SD card also, as you'll need to when you flash the image.
My mistake - I should have just said start it all over again.

Here are the steps I did
Download recovery.img and Hard SPL (still in zip format) to sd card (all I did was drag them into the E folder in my computer).
Safely remove and reboot phone.
Type in telnetd enter.
Go to telnet and type:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
I had two ## in front of each line.
I then turned off phone and did the home and power button thing, then pressed alt s.
Downloaded RC33 from http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
Turned off phone after safelty removing.
I then put this on the sd card and did not delete the other two files currently on there (I named this update.zip).
Then did the power button home thing after I turned off phone and pressed alt s.
Then turned phone back on and had the same things in about phone that were their previously.

Recovery problems

I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.

xxwckdxx said:
I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.
Click to expand...
Click to collapse
how long has it sat there? sometimes you have to give it a few minutes after going thru all that.

By the way if i dont try to boot into recovery it loads fine how can i reload the reocvery?

Probably 5 minutes and no go

How were you loading it in the first place? Have you checked to see if its on your card? When pushing the image, are you using the exact image name, i.e, v1.6.2-(color).img.? Also, are you holding the end-home keys at the same time long enough to see it come up?

when i first was trying i opened the terminal i had on the phone and typed flash_image recovery /sdcard/recovery-1.6.2.img and it kept comming up with bad filename(wwhich i had renamed the file to that so i dont know why) then i put it in the tools folder and tried the same from commander and it got me to here ;\

What method are you using? Try amon ras or the method used to push it to your card thru root.

havent heard of amon ras.....i just pushed it to the sdcard again and tried the same command and end up with the same thing iam trying to unroot again

nope came up with bootloader error for the unroot

tried using kitchen to reroot but it comes up with errors

Okay, these are Amon RAs methods just depending on what your using:
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.imgvia fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Or thru adb try this:
cd C:\android-sdk-windows\tools
adb shell
adb push recovery-RA-heroc-v<name>/sdcard
adb shell reboot
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.

to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it

VoLoDaR1 said:
to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it
Click to expand...
Click to collapse
I had 1.2.3 or whatever it was thats why i was gonna just shoot to 1.6.2 i had done it before but i dont know what happened this time. I tried the way thru adb and it has been sitting so far 10 minutes and it is still sitting at the boot screen

The first one wont work i cant get into recovery.....the second one i get "fastboot is not recognized as a internal command"and the third is the one i have been trying....

im not sure man i had trouble flashing it also try renameing it to something simple like 1.6.2.img and go to better terminal emulator type in su enter than type in the comands to flash it
flash_image /sdcard/1.6.2.img enter
do not enter mount-a before this this was the problem i was having after you hit enter just type in reboot recovery and you should have 1.6.2 also maKE sure this file is the only file on your sd card that helps good luck man let me know what happens

yeah i renamed it to recovery-1.6.2.img and i just downloaded better terminal but how do you get the keyboard up?

just tap the screen

do you have g talk

sent pm to you

ieatstarz1 said:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.
Click to expand...
Click to collapse
This is what worked for me.
The 1.6.2 version did exactly to me like it is doing to you. I couldn't boot in to the recovery screen.
Sooo. I pushed the 1.5.2 image to the sdcard and then I
adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
I was then able to boot into the 1.5.2 recovery
I then pushed the 1.6.2 image again and then it worked.

[Q] CWM and .android_secure problem

Did anyone find a fix for it yet? Anything that winds up restoring .android_secure causes the phone to hang. It's getting really annoying, not sure if I read about a fix anywhere though.
EDIT
Just saw that this is a dupe thread, check here instead:
http://forum.xda-developers.com/showthread.php?p=14728596

FBis251 said:
Did anyone find a fix for it yet? Anything that winds up restoring .android_secure causes the phone to hang. It's getting really annoying, not sure if I read about a fix anywhere though.
Click to expand...
Click to collapse
You need to have made a clean backup with Krylon360's FINAL CWM, not ROM Manager.
CWM Final is v3.0.2.8
I backed up and restored .android_secure via that version without issue. It's related to the Rom Manager version that causes issues.

Iv been looking into it with dsexton and its a file on your sd card. Also you should only use krylons cwm
Sent from my SGH-T959V using XDA Premium App

I had that problem with the rom manager version of CMW too but if you let it sit on the hangup for a few minutes then just hold the power button until your phone restarts let it boot and your phone will be restored
Sent from my SGH-T959V using XDA Premium App

So I flashed CWM v.3.2.0.0 from ROM manager v.4.3.1.5 but have not yet backed up the phone's original stock ROM. Is there a workaround so I can use krylon360's CWM FINAL instead?

(smint) said:
So I flashed CWM v.3.2.0.0 from ROM manager v.4.3.1.5 but have not yet backed up the phone's original stock ROM. Is there a workaround so I can use krylon360's CWM FINAL instead?
Click to expand...
Click to collapse
Just dont use that..only use kyrlons

no CWM love
Looking for some help here. I am unable to get into recovery and therefore cannot do a nandroid backup and get to ROM-ing / hacking on my phone. Here's what I've done.
In linux I used the following commands to write krylon360's files to my phone:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#exit
$exit
adb push update.zip /mnt/sdcard
adb push recovery /mnt/sdcard
adb push recovery /system/bin
Next I've tried the following to get into recovery and make a nandroid backup.
1.) simultaneously hold down volume up, volume down and power button.
result: phone stops at Tmobile/GalaxyS splash screen.
if I hold down the power button and reboot, I get a frozen progress star and large battery icon displayed in the middle of the screen. This is the same result for every variation.
repair- pull battery out of phone, put back, power on and execute:
adb reboot
2.) execute: adb reboot recovery
result: phone stops at Tmobile/GalaxyS splash screen.
repair, execute:
adb reboot
3.) selected recovery from ROM Manager
result: phone stops at Tmobile/GalaxyS splash screen.
repair- pull battery out of phone, put back, power on and execute:
adb reboot
Any ideas?

{HOW TO}[root][recovery][roms][unbrick][LG OPTIMUS NET][LG P690]

HII GUYS THIS THREAD IS ALL ABOUT LG P690:-
FIRST
/////////////////////////////​ROOTING:-​/////////////////////////////​
Code:
http://forum.xda-developers.com/showthread.php?p=21348926
2)Custom Recovery for LG Optimus Net - Clockwork 5.0.2.7
DOWNLOAD ALL THESE FILES:-REQUIREMENTS​FLASH_IMAGE
RECOVERY IMAGE
ADB RUNNING
http://developer.android.com/sdk/index.html
The Recovery can be installed as follow:
•Download recovery.img from the link attachment
•IMPORTANT: Check MD5SUM - This is to ensure that during the download / copy the file is not corrupted
•Copy recovery.img to the SD
•download Flash_image, unzip and copy it to SD
Now you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Code:
$ adb shell
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image> /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Note: the command
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.
WILL GIVE YOU SOME ERROR IGNORE IT
If all goes well, the menu with a cheerful hat ClockworkMod background confirms that the boot recovery occurred in CW.
Also ignore the error below: "E: bad boot message" is not a real error.
The recovery functionality is simple:
- The volume keys to scroll
- The back button to go back
- The power button to select a menu item.
If you have problems, you can select Advanced / Error Reporting. This will generate a log into SD (recovery.log). You can use it to understand the problem.
/////////////////////////////
[HOWTO] Flash original firmware on P690
http://forum.xda-developers.com/showthread.php?t=1483192
[HOWTO] Flash DOWNLOAD firmware on P690
http://forum.xda-developers.com/showthread.php?t=1483180
/////////////////////////////
///////////////////////////////
[ROM] DarDroidXD_0.3 [LGP690]
http://forum.xda-developers.com/showthread.php?t=1483206
//////////////////////////////

This guide works 100% , just used it now waiting for custom recovery to download.

Majestic36 said:
This guide works 100% , just used it now waiting for custom recovery to download.
Click to expand...
Click to collapse
Doesnt work for me, recovery just freezes at the LG screen

Need to understand what is recovery and custom installation
May I know what is Custom Recovery for LG Optimus Net - Clockwork 5.0.2.7 and what it do?
and what is installing cyanogenmod 7.0 is it a custom rom and is it better then stock rom?

Hi guys,
I have problem. I rooted my LG P690 and installed CWM bootloader. During installing custom ROM my phone bricked and rebooted after LG initial picture. I was able to enter only RECOVERY MODE by pressing PWR+BACKARROW+VOL_UP. But that was all, I couldn't also repair phone through HDZ_FW_UPD.exe , because problem with USB drivers. I tried everything, but without success. But I was able to connect to phone via ADB commands, downloaded update.zip, added it near fastboot.exe file, run fastboot and install that update.zip. I removed SD card to other phone, connected, uploaded some CyanogenMod 9 and moved SD card back to LG P690. Now I was able to enter BOOTLOADER (BUT I DON'T REMEMBER COMBINATION OF BUTTONS DURING SWITCHING PHONE !!!), and installed CyanogenMod9. Everything looks OK, but after rebbot and entering new Android OS my touch screen isn't working. I don't know why, but I think that problem is in that CyanogenMod9 version - it doesn't recognize touching screen. It reacts to pressing Vol UP/DOWN buttons (setting volume), pressing BACK button or long pressing PWR button. But that's all. I can turn off the phone by remobing battery. When it's ON and I connect it via USB, I cannot use ADB.exe or FASTBOOT.exe commands because PC donesn't recognise device
So now the question - how to enter bootloader during power ON sequence? I tried all combinations:
- pressing and holding PWR+VOL UP
- PWR+VOL DOWN
- quick pressing of VOL UP
- quick pressing VOL DOWN
- pressing PWR+BACK+VOL UP
- pressing.....and so on and so on
I don't know why I cannot access bootloader becasue before I did it without any problem....Can you please write me detailed "butto n sequence" for entering bootloader on LG P690 Optimus Net? Or am I LOL?
Thank you very much
Rado

SOLVED -> entering bootloader works with pressing HOME+VOL_DOWN+PWR_ON