hi there,
so i am slightly new at this and have searched for hours and hours trying to find a consistent formula for rooting and installing my g1 to cyanogen mod 4.2 (or latest stable one, thus not cm 5). I seriously stayed up until 1am last night and now i am at work (started at 8) still searching.. I have used google, youtube, and several other cm sites. Basically the problem is there is not one guide and I am not sure if because I followed the CM wiki guide if i can switch because I am having problems with that one. So one question: does anyone know which is the latest and verifiably the best CM 4.latest guide to installing?
I am pretty sure i have rooted the phone because I successfully downgraded to RC29, the old school android OS. However when I try completing this guide: [cant put a URL in but the webpage title is: "G1 CM4.2 installation" and I already completed this wikiguide title: "Full Update Guide - G1/Dream Firmware to CyanogenMod" but it continues into the next page to install cm)
I get freaking stuck. I put all three files on my SD and when I try to push "Alt-A" there is not an option there for it, its not an option on my recovery mode menu. I tried putting the files back there after reformatting several times but still no 'alt-a' so I am stuck on step 5 because there is no option for step 5 on my recovery mode on the above web guide..
Does this mean I did not install something? should I try and install the ota radio, cm update, drc83 zip files separately (like load one on the sd card and install it, then reformat the sd card and then repeat with the other two files?) ? If so what order should I do that in??
Sorry I suck and have not been able to find these answers, there are just a plethora of guides and I am not confident in my modding to start deviating away from the wiki guide in case I brick my beautiful g1..
thanks so much, this has been a huge headache for me.. i literally spent 4 hours yesterday trying to get to this step.. aww...
At Step 5 select "apply any zip from sd" in Recovery.
Select "DRC83_base_defanged.zip" on your SD.
Press Home to confirm flashing.
Then select "update-cm-4.2.x-signed.zip" on your SD to flash CyanogenMod.
After everything is completed reboot your Phone normally.
Edit:
Here is the Link to the Tutorial.
zerocoolriddler said:
At Step 5 select "apply any zip from sd" in Recovery.
.
Click to expand...
Click to collapse
Yup you hit the nail on the head. Sorry I must not have been too clear on what was I was saying earlier. That is exactly the problem, you see I would select that in recovery mode, But "apply any zip from SD" is not there! Did I load some file wrong??
It only gives me:
Android system recovery utility
E: Can't open /cache/recovery/command
Home+Back - reboot system now
ALt+L - toggle log text display
Alt+S - apply sd:update.zip
Alt+W - wipe data/factory reset
could it be this: "E: Can't open /cache/recovery/command" that is the problem? I only found one reference to this message during my internet searches and the guy said it always says that..
So you have CM-Recovery?
Flash Amon_RA`s Recovery, it´s more comfortable to me. I´m using 1.6.2.
For G1: http://forum.xda-developers.com/showthread.php?t=566669
For MT3G(Magic 32b): http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1
Nope. I am also using Flash Amon_RA's recovery.. (v1.6.2)
I loaded it up on the flash drive and also used telnet app to flash it in (wrong terminology? I typed it in the telnet box and hit return and it gave me the # # which I read means I did it right)
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
maybe i get something wrong
but did you boot into the recovery menu already? (press home and power when you turn the phone on)
from there you can choose your task with the trackball nice and easy...
(you r from vienna?)
zerocoolriddler said:
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
Click to expand...
Click to collapse
those points are not listed!
I did not try flashing via fastboot before but rather via terminal app.. Do I need some special software for fastbooting? Amon_RA's post says i need "Requires engineerings SPL!" which I do not have ..
and I now I loaded it via fastboot and I cant get out of it! how do I reboot out of fastboot? Because I can do not know how to "fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img" .. can you explain that in more detail?
skarboy- no i am not from vienna but the USA. and yea I tried to boot from the recovery menu but when i am there it does not show the option of flashing zip from sd (see above)
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
mejorguille said:
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
Click to expand...
Click to collapse
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
austriker27 said:
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
Click to expand...
Click to collapse
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
mejorguille said:
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
Click to expand...
Click to collapse
okay so I tried all that.. and freaking a! awwwwww no success it just gave me the old screen like before
when I typed in "su" it said permission denied so I think I have to go back and do something that I missed. I cant keep track of how many times I have done everything, then erased then tried again.. I wish someone would be specific and just walk me through this without skipping a single detail..
zerocoolriddler said:
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
Click to expand...
Click to collapse
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
austriker27 said:
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
Click to expand...
Click to collapse
the 2.22.23.02 radio is newer and its supposed to have better reception and less battery usage as compared to the .26I radio but the difference should be minimal. Everything is supposed to be in a zipped folder exept for the recovery image. Terminal is similar to telnet in that you can put in commands but it works a little different. It is what I usually use to flash recovery's, etc, so since telnet was not working for you I though terminal might make a difference.
Again, open terminal and type:
Code:
su(enter)
flash_image recovery /sdcard/recovery.img(enter)
reboot recovery(enter)
Tell me if this works.
Edit:look at my next post
austriker27 said:
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
Click to expand...
Click to collapse
The "su" command signifies root access. If it says permission denied, then that means that you are not rooted or you skipped a step.
CYANOGEN WIKI said:
Rooting the phone
You need to have root (or 'admin') access to the phone so that you can install whatever software you want and not just what your provider gives you. This is not the same as unlocking your phone.
Finish booting up your phone, and sign-in to your Google account.
If you don't have access to a 3G network, then follow the G1 logon to google via wifi guide to sign-in via wifi. The original guide to do this is out of date.
You could try and add your networks provider's APN. To do this press Menu key -> APN Settings, press Menu again -> Add APN and enter 4 things: Name, MCC (Mobile Country Code), MNC Mobile Network Code and APN - all this info should be available here: http://en.wikipedia.org/wiki/Mobile_network_code and on your network provider's site. The image you booted with might also have the extensive APN list. If so, and you can't get a data connection, then you might try the wifi guide.
Once you're at the Home screen, open the keyboard, and press the Enter (Return) button twice.
Type
telnetd [enter]
Typing will bring up the Contacts screen, but you can just ignore that.
There will be no indication to let you know you did it right. Just continue on to the next step.
If you get an error when trying to connect (step 5), try pressing Enter twice and type "telnetd" and press Enter again
Open the Android Market, and install "Telnet" by ClockworkMod (Formerly by Koushik Dutta)
Open Android Telnet Client, enter "localhost" in the large text box and press connect. (You may have to enter "23" in the smaller text box on the right)
Click to expand...
Click to collapse
Do those steps again.
okay so I am in the telnet client and have entered localhost and 23 and hit return. so now i am in a black screen. i typed in what cm wikiguide told me and it gave me :
## (good sign!)
now do I turn off the phone and go into recovery mode or this where I am missing a step??
Sorry I am so ornery (wow and i can spell) there are just a number of things frustrating me.. besides me knowing this should only take like 2 hours at the most and knowing I keep messing up some mundane detail or something.. Also I am doing it in windows on my macbook and the wireless keeps disconnecting. Also I would take photos of the screens to show you but I do not have any photo software on the windows partition of my laptop (i mostly use mac os x) so I cannot... and i am very tired from working 6 days a week (and only getting 6 hours of sleep last night due to this issue) and frustrated from this whole fiasco.. And I have a headache.. yup call me a whiner if ya want but i am just trying to explain why i am kinda mad...
HALELUJAH! it worked and the android system recovery looks like your image mejor!!!!!!!! hopefully this works, i will let you know.. thanks soo much! i have no idea what i did differently
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
wow so that wasnt a giant headache, although now i pretty have the process memorized and have learned tons in the process. I think I may have the longest time to root a g1 record so far of any human haha... Lets see I worked on it yesterday from 8pm-1am while kind of watching world cup. This morning for about 2 hours from 9-1130 at my job. And this afternoon for about 2 hours..So like 9 hours give or take an hour of two.. NEW RECORD!! haha
THANKS SO MUCH for you help guys I love you. Especially mejor because he/she lead me down the finishing stretch... Now to install apps2sd (after my class 6 card comes) and take a nap
Related
I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
Sounds like you need to flash a good hardSPL in terminal and then with fastboot-usb, flash recovery.
Hard SPL
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.
crxforya said:
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.
Click to expand...
Click to collapse
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
NOTE: Here's a good Wiki on SAFELY flashing hboot/radio/recovery images that I found in Firerat's sig. As someone who has bricked a G1 by willy-nilly flashing, I implore you to have a look-see:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
rynosaur said:
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
Click to expand...
Click to collapse
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue
Firerat said:
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue
Click to expand...
Click to collapse
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?
Ill have to check
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???
crxforya said:
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???
Click to expand...
Click to collapse
No problem at all doing that, nbh overwrites radio, hboot, recovery. Just make sure you have the rooting files stored locally, i.e. custom rom, custom recovery, custom/hard/eng SPL, new radio, recovery test keys, etc.
crxforya said:
because I dont have access to install adb at my location.
Click to expand...
Click to collapse
rynosaur said:
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?
Click to expand...
Click to collapse
did you read the post?
no adb = no fastboot
@crxforya'
your best bet is
Code:
su
ash
flash_image recovery /sdcard/recovery.img
if it fails, scroll up with track ball, and hit enter again, repeat until it works
crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
read this it might help it did for me when i try 2 use ROM MANAGER APP n i lost my recovery-->>> http://forum.cyanogenmod.com/index....toasted-not-bricked-phone-thread/page__st__40
No luck
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.
ur recovery is corrupted try this
To boot into fastboot you need to hold back and power.
Then plug the original usb cable into your pc then into phone. your phone should say FASTBOOT USB
If not you will have to use USB deview (a few posts above). Then using it unistall anything that says Android or HTC or ADB or Fastboot... You get the idea.
Then unplug and replug the usb cable to your pc.
Windows should say that there is an unrecognised item or something, go into device manager and there should be one with an "!" mark, or a wizard to install the drivers appears.
When it asks you where to find drivers, click the option that says select where the drivers are (advanced), or something. Then point it to the folder were the USB drivers are and let it do its work.
After its finished start cmd and use the command "cd" to go to the tools folder where your sdk is extracted if it was at "C:\android-sdk-windows\tools" you would type in cmd "cd C:\android-sdk-windows\tools"
Then put in "fastboot devices" and it should give you your phones serial number, as long as the drivers work and you are in fastboot (phone should say FASTBOOT USB)
If that works we are back on track
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok now download the latest Amon_Ra recovery XDA link
Now check the md5 using this tiny standalone app Download.cnet.com link this is self explanatory, as the md5 sum is on the XDA link.
Ok, so now you have checked that its not corrupted, move the .img file to the tools folder. For me it would be "C:\android-sdk-windows\tools" . (The .img file needs to be where the fastboot.exe is, so it finds it.)
Now this is where you get the stuff you type in to cmd.
Fastboot devices
Fastboot erase recovery
Fastboot flash recovery recovery-RA-dream-v1.7.0.img
Click to expand...
Click to collapse
same problem
i have the same problem except i have danger spl, i noobed it up and tried to flash recovery with cm 5.0.7...
i tried to flash the recovery a bunch of times, and i treid to get into fastboot, but idk where the drivers are, and idk how to find them.
help plz
crxforya said:
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.
Click to expand...
Click to collapse
ok, thats interesting
straight after you do that
logcat
<track ball> then c
( or in terminal preferences, change the control key )
I'm guessing you see
I/flash_image( 2410): header is the same, not flashing recovery
so, try flashing a different version ( 1.6.2 ) , then 1.7.0
edit: or
Code:
erase_image recovery
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
I need to start over
What does changing the control key do??? I know Im a noob!! Sorry and thanks for your help
Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App
Well im back at the out of memory messg
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???
crxforya said:
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???
Click to expand...
Click to collapse
well, I have a spaming script here
http://forum.cyanogenmod.com/index.php?/topic/3867-broke-recovery/page__view__findpost__p__39273
spamming the flash in CM5 seems to be working for most
Code:
#!/system/bin/sh
test=1
while [ "$test" = "1" ];do
flash_image recovery /sdcard/recovery.img
test=`echo $?`
done
echo "we got there in the end....."
[attachment=1106:spamflash.txt]
get that onto your sdcard
rename the recovery image to recovery.img and put on the sdcard
then
Code:
su
sh /sdcard/spamflash.txt
that will keep trying to flash until it works
another way is to flash before android starts ( plenty of free memory available )
this is a firstboot.sh script
Code:
flash_image recovery /data/recovery.img
if [ "$?" = "0" ];
then
rm /data/recovery.img
echo "recovery flashed"
else
echo "recovery flash failed..."
fi
[attachment=1107:firstboot.txt]
get that onto your sdcard
then
Code:
su
cp /sdcard/firstboot.txt /data/firstboot.sh
again rename the recovery image to recovery.img, but for this method you need to put it on /data/
It will 'self clean', i.e. if it works it will delete the recovery image, and the bit which runs the firstboot.sh deletes that ( but it will delete that regardless of it working or not )
Click to expand...
Click to collapse
deltawye said:
Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
When my phone does not recognize the USB connection I simply reboot my G1 while the USB is is still connected and that seems work for some odd reason.
I had the same problem. All I did was install rom manager, flash the rom manager recovery nothing. From there flash RA- recovery nothing and then did that back and fourth until it worked I also tried flashing it with one click root hope all help. Also tried the terminal. Hope you fine a way. Good luck!!!!!!!
-------------------------------------
Sent via the XDA Tapatalk App
So far, this is going to be a guide for noobs. Please read through this, and ask any questions that you have. This has been compiled from different guides around XDA, and information has been stripped that does not relate to our phones. More will be put up here when I find it, and all credit will be provided. This will be from 'duh' to 'didn't know that'. The idea is to provide a beginning to end explanation: Stock Incredible to Rooted with custom Rom.
Topics so far - ADB, Rooting (reflash), Unrooting, Nandroid, Remove/Install Apps, roms, kernels...
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE DOING ANY OF THIS.... REGARDLESS OF WHY. Yadda, yadda, yadda...
**********At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done).**********
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Now, we get USB drivers to work. Some use HTC Sync for drivers, however HTC Sync does not like to play nice with the reflash tool (later on this), so we will use the generic google USB drivers.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.
============================================================
2) Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
============================================================
3) Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in:
cd C:\**your sdk name**\tools (Press Enter)
adb devices (Enter) You should see your device listed
adb shell (Enter) you should see $ in the next line
**After you obtain root**
su (Enter) you should see # in the next line if you are already rooted
**you may need to allow adb shell to run as root. Look at the phone and see if Superuser.apk is asking for your permission to allow adb root access. Click on "Remeber my selection" and select yes.
Now you are all set to run adb commands as root or as a regular user
**Note: for a list of commands that you can type using adb type "adb" in cmd
All Credit for Topics 1 - 3 go to user XDA member nephron. I mostly copied all of his guide, but updated some information on it to make sense for our phones. Also, removed some stuff I didn't see necessary. Please go to the original thread for the G1: http://forum.xda-developers.com/showthread.php?t=532719&highlight=nandroid+guide for a list of further Credits, and for information I've left out. If you like this thread, please donate to HIM
============================================================
4) Rooting your phone - READ THIS WHOLE SECTION BEFORE GOING TO ANY EXTERNAL LINKS PLEASE. At this point, running the UnrEVOked reflash3 tool will root your phone and install a custom recovery. To try to make it really easy to understand, recovery allows you to access your phone to make PERMANENT changes (something we can't do while booted yet), flash custom roms, and save your sorry little @$$ if you do something that you weren't supposed to
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it), and that you have the Google USB drivers installed (i.e. you read at least some of this post). The first thing we're going to do is:
1) Read this: http://forum.xda-developers.com/showpost.php?p=6875912&postcount=1
2) If you read #1, you already went here: http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
and downloaded the MODIFIED (i.e. changed, not the same, DON'T SKIP THIS STEP) driver and installed it
3) If you read #1, you already downloaded the reflash tool executable
4) If you read #1, you've already done #2, and 3, and this is just a worthless step of me explaining how important it is that you did #1
5) Lets do this. #1,2,3 and 4 were "get ready" steps. By now, you installed the modified driver, went to the webpage and downloaded the UnrEVOked3 reflash tool. HTC sync is also uninstalled. Plug in your phone (normally booted) to your pc and select "Charge Only" when asked how to connect to PC, and click on "remember my selection". Click Done.
6) Unplug Phone from PC.
6a) If you have double twist installed, at this time open the task manager on your pc, and kill doubletwist.devicehelpder....
7) Run the "reflash_package" executable that you just downloaded. Notice the path that it lists and click "install". This will unzip "reflash.exe" and a bunch of other stuff that is needed to the directory that you just noted. Go to this directory (usually the same one where the executable you just ran is) and run "reflash.exe"
8) Plug in your phone.
9) When the program is finished, you should see koush's clockworkmod recovery on your phone's screen and reflash will say that it's done. Congrats, you have root and a new recovery.
If something went wrong, and you're not on koush's recovery and reflash says it's done, don't worry, just re-run reflash. You can run it as many times as necessary. It will not hurt anything AT THIS TIME (this may change later)
10) Koush's recover works a little differently:
a) Vol+ and - scroll up / down
b) the Power button work as a "Back" button, and will turn off screen if you're at the root of the menu. If your screen goes blank, don't read, just hit Power again
c) To make a selection, click the optical trackpad
11) Reboot your phone by highlighting the selection and choosing it
For the most part, these instructions were written from memory, but all credit goes to UnrEVOked, Shadowmite, and anyone that they've given credit to in original links.
============================================================
5) Unrooting - I didn't want to re-invent the wheel, so I'm posting an external link:
http://androidforums.com/all-things...ideo-howto-unroot-incredible-downgrading.html
Just follow the instructions. Credit goes to the OP. If this link ever goes to a 404, pm me and I will find another link with instructions and update this. Also, if you don't understand something, just ask in this thread, someone will answer (maybe even me ).
============================================================
6) Whats is a Nandroid Backup?
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
Nandroid Backup is a tool allowing your Incredible that has koush ClokworkMod Recovery to create a full system backup and restore it, which, when flashing and testing different roms can be very useful.
A) Creating a Backup using Nandroid
Boot up your phone in recovery (Turn off, then turn on while holding Vol- and Power. Press Vol- once to highlight recovery, hit Power once to go into it)
You will now see your new koush recovery
Scroll down (Vol -) to "nandroid" and select it (press the optical button in)
"Backup" will be highlighted. select it
Let it work, it might take a while for a full system backup
Once its done, your backup is complete and is saved on your sdcard in the "clockworkmod" folder. Normally it's stored in the "nandroid" folder, however our Recovery does things a little differently.
B) Recovering to Your Nandroid Backup
Make sure u made a backup and its in the clockworkmod folder on your sdcard
Boot up your phone in recovery (Explained Above)
Go into "nandroid" in the recovery (also explained above)
Select "restore backup" and select from the backups you have (if you have multiple) that you want to restore; this will do a simple, "restore all" of your latest nandroid backup
:OR:
Select "Advanced Restore", choose from the backups that you have on your SD card, and then what you want to restore. You can individually restore "system", "data", "cache", etc....
In "Advanced Restore", i have not seen a way to restore multiple options (cashe AND system, etc...) Koush, am I missing something?
Let it work
Once its done, restore more options through the Advanced Restore menu, or reboot your phone and your selections will now be restored!
============================================================
7) Remove Apps
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Go into Clockworkmod Recovery (With phone turned off, Vol - + Power, then Vol - to select recovery, then hit Power)
2) Select "partitions" from menu, then select "mount sytem" You can also "mount sdcard" if you want to back apps up to sdcard
3) Connect Phone to PC
3a) Open a command prompt and navigate to your sdk\tools directory
3b) Type: adb remount (it shoud return successful)
4) Open Adb Shell on your pc (Type: adb shell)
It should automatically show #, otherwise type "su"
Type:
cd /system/app (enter)
5)Type ls (this will show you all of the stuff in the /system/app directory)
6) To "delete" apps, type the following:
/system/bin/mv Your_APP.apk Your_APP.apk.bak (i.e. CityID.apk CityID.apk.bak). If you want to clear up space on your internal storage for whatever reason, you can replace Your_APP.apk.bak with /sdcard/Your_APP.apk.bak (this will move the app to the root of your SD Card instead of just change it's name)
If you don't get errors, you're done.
*This does not delete apps, but changes their file type so they will not show up as an app, in case you want to get them back at any time later you still have them and don't have to frantically post threads on XDA asking for them.
============================================================
8) Install Apps to /system/app
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Place your app you want to install into the root of your sd card (this is easiest)
2) Go into Clockworkmod Recovery (Explained in 7)
3) Mount system and sdcard under partitions (Explained in 7)
4) Connect Phone to PC
4a) adb remount in command prompt (should sow successful) (again, in 7)
5) Open Adb Shell on your PC
6)
IF NOT at #, type "su" to go from $ to #.
Type:
/system/bin/mv /sdcard/Your_App_Name.apk /system/app/Your_App_Name.apk
7) If you don't get errors, you're done. You can unplug phone, and reboot
============================================================
9) Flashing Custom Roms
Download a ROM that you want to try. One of the roms from here are a good starting point: http://inc.sodpit.com/. They are mostly stable might get a few random reboots.
Steps:
1. Download Rom of your choice
1a. Right now, there might be two ROM types, a nandroid backup and an update.zip type file. For right now, I recommend sticking with the update.zip kind. These instructions are meant for it, but I just want you to make sure you know which type it is before you try to flash it.
2. Copy and Paste the downloaded file onto sdcard. Make sure it is not in any directory's of SD card, just on the sdcard (the "root" of it).
3. Verify it's there using Astro or some other File Manager just to be safe.
4. Download and Run Titanium Backup from the Market if you haven't already. (If you don't have it, get it, it's must have for root users.)
a. Select Menu, Batch, Backup user apps. (in Titanium Backup)
b. let it run, this will take some time.
5. When that's done open your command prompt, navigate to your sdk\tools directory, and type "adb reboot recovery" (Not within adb shell, but in command prompt in that directory. I'm not going to explain how to do this because it's already explained above. Also, if you're flashing roms then you're already familiar with it, or maybe you shouldn't be flashing roms ).
6. Do "Wipe data/factory reset" and "wipe cache partition" in Recovery **This WILL WIPE your phone**
7. Select "install zip from sdcard", then select "choose zip from sdcard", then select the name of the zip you want to install.
8. When that's done reboot your phone, once your done setting up all the settings, download titanium backup from the market again, and set that up.
9. In Titanium, Select Menu, Batch, Restore User apps.
After that's done you'll have all your apps that you had before, data included, with a fresh new rom to try out. Hope this helps!!
All credit for these instructions goes to tcbert2010, they were suggested to me, and I liked them. I modified them a BIT, so they make more sense to me and hopefully to you. See post #2 in Original Thread = http://forum.xda-developers.com/showthread.php?p=6953608#post6953608
============================================================
10) Installing custom kernels
I'm only mentioning Hydra's kernels. I'm running the Undervolted, NOT overclocked kernel with wireless N to preserve my battery to get more life out of it
**Taken from website's FAQ**
Q: So how do I install the kernel?
A: First step is to either download the kernel zip file straight to your phone, or download it onto your computer and put it on the sdcard of your phone. Next you turn the phone off hold volume down and power at the same time. When the phone is in HBOOT wait a few seconds for it to initialize then hit volume down once and then power to boot into Clockwork recovery. Once in clockwork recovery you want to select "Install zip from sdcard", then "Choose zip from sdcard". You will now see a listing of files on your sdcard select the kernel zip you downloaded, or if you downloaded strait to your phone go to the Downloads folder and select the kernel zip file. The kernel will now install to the phone and once it's done it will say install complete. Now you can hit the power button once to return to main menu and select "reboot system now" . Your phone will now reboot with the new kernel.
***
Go to: http://hydrakernel.net/ to download the kernels
Please read: http://hydrakernel.net/faq.htm to educate yourself. It's worth it.
Credit to EJHEART for the wonderful kernels! Where are my 2.2 kernels EJ ?
============================================================
Again, if you have suggestions, requests, or whatever please post or PM me.
PM Me if I missed giving someone credit. PLEASE!!!
reserved
reserved for future.
Reserved
reserved for future
Great thread topic... reserved for future use
Updated
Updated with Reflash instructions.
dreamersipaq said:
Help I'm stuck at waiting for system to settle
check these common issues:
- You switched your driver to the one from this post? It's NOT identical to the SDK one.
- You don't have any usb applications that might be taking focus while we are working with the phone right?
- Is the SD card present in the device?
- You did give su permenent access when you allowed it in superuser right?
More to come...
Click to expand...
Click to collapse
Good start, iPaq! I just want to plug Linux AGAIN. I had zero problems using reflash for linux and using Gparted in Ubuntu/Debian/Linux Mint mint means one can do all kinds of things that will become helpful very soon if not already (e.g., manipulate ext and swap partitions on the sdacard!). Aside from linux being Android's native file system, using a Linux distro just makes 110% good sense if you plan to do any developing for the DI/Android. Why poeple struggle so much with Windows when Linux is free is beyond me
2 cents deposited!
Additional items to add
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Great topic
Sent from my ADR6300 using XDA App
...
jdmba said:
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Click to expand...
Click to collapse
1) - Will update soon
2) - I BELIEVE that this works:
1) Go into Clockworkmod Recovery
2) Mount Internal Storage under partitions
3) Connect Phone to PC
4) Open Adb Shell on your pc
Type:
su (will change to #)
cd /system/app
mv CityID.apk CityID.apk.bak
you're done.
Not in front of my phone at this sec, but if mv does not work, try
busybox mv CityID.apk CityID.apk.bak or
/system/bin/mv CityID.apk CityID.apk.bak
*This does not delete it, but changes the file type so it will not show up as an add, in case you want to get it back at any time later.
If I'm wrong please correct me.
3) The easiest way to update recovery at this time is through Koush's Rom Manager. However, at this time I've read somewhere that it's not persistent. Let's give this a few days.
Updated
First Post Updated.
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
qwho said:
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
Click to expand...
Click to collapse
Take this opportunity to flash up to HBOOT 79, wipe, and re-root. Start fresh. Re-reflash w/unrevoked2. Alles in Ordnung! At least, that solved all of my problems. Start with the big headache to avoid later headaches. Once you have a nandroid of a "proper" root, you'll never have to do the annoying initial root again.
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
qwho said:
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
Click to expand...
Click to collapse
Exactly. Doing will wipe out all userdata, everything not stored online, on your card, or on internal disk. It's really the best way to go, to start fresh and remove all the little variable piecemeal rooting has placed in your path to date.
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
qwho said:
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
Click to expand...
Click to collapse
Just down this, run it in Windoze, and before it tries to flash (you don't need your DI connected!), go into your AppData/temp directory, find the ~142mb rom.zip file, rename it to PB31IMG.zip, put it on /sdcard root directory, boot into bootloader, let the card/file get picked up while holding down-volume, ok the flash, no need to ok the reboot, then boot into to recovery and proceed with adb shell/rooting process one
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
sanchagrins said:
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
Click to expand...
Click to collapse
Not sure what you mean. Go into Hboot, and select recovery. When Koush's recovery loads, use Vol- to highlight "nandroid". Click the optical button in, and you'll enter another menu. Select the first option, which should be highlighted by default, which should be "Create Backup" or "Backup Device" or something like that.
Let me know if that works.
When I go into recovery the only options I get are:
Reboot System now
Apply sdcard: update.zip
Wipe data/factory reset
Wipe Cache partition
----------------------------------
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
sanchagrins said:
When I go into recovery the only options I get are:
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
Click to expand...
Click to collapse
You can't install anything to recovery that will stick until you get root via procedure 1, then reflash with unrevoked 2. Sounds to me like you've gotten ahead of yourself
This thread is primarily intended for n00bs.
I would like to say thanks to xda forum members: Noejn, Zecanilis, drellisdee, The_ERROR etc. Also thanks is due to Godlike! at tech-mania.com for his tutorials. Thanks is due especially to The_ERROR for proofreading the post and to other users for their suggestions written in the thread.[/SIZE]
---------------------------------------------------------------------------------------------
NEW - 3 May 2011 - Simplified Guide to Root & install version 1.2 of Custom Thunderg Recovery by AmonRa/modified by Drellisdee on LG P500
ALWAYS MAKE A BACKUP BEFORE CUSTOMISING YOUR PHONE.
[CUSTOMISING A PHONE USUALLY INVOLVES: ROOTING >>>> INSTALLING CUSTOM RECOVERY >>>> INSTALLING CUSTOM ROM]
The instructions written below have been tested by me using an Indian unbranded GSM model of LG P500 which came with stock Android 2.2.1 (V10C). The procedure to be followed for any LG P500 phone is the same.
This post is split into 4 major sections -
1. INSTRUCTIONS FOR ROOTING
2. INSTALLING ANDROID SDK ON A WINDOWS PC (This step is needed to install Custom Recovery on phone using adb from PC. Can be omitted if Recovery is installed from phone using Terminal Emulator)
3. INSTALLING A CUSTOM RECOVERY
4. INSTALLING CUSTOM ROMs
MUST READ: If you haven't read this thread already, please do read it - Dictionary for n00b - What is.../What does ...mean?
---------------------------------------------------------------------------------------------
1. INSTRUCTIONS FOR ROOTING
To know your present firmware version - Go to Settings/About Phone
Only phones which come with stock android 2.2 could be rooted till recently.
UPDATE - 24 April 2011 : A tool called 'GingerBreak APK' is able to root phones running stock android 2.2, 2.2.1 & 2.2.2. Read about it HERE. This tool enables rooting without the need for downgrading the firmware to 2.2. If 'GingerBreak APK' doesn't work out for you, continue reading to understand the procedure to root your phone after downgrading your firmware. Note: 'GingerBreak APK' permanently roots your phone. Also,GingerBreak might not install BusyBox and SuperUser apps properly on your phone. These apps are required by many rooted apps for their proper functioning. So, use Root Checker from android market to verify the proper installation of these 2 apps.
If your phone runs stock android 2.2, enable 'USB Debugging' on Phone (Settings/Applications/Development). Install z4root (copy the apk file to the sd card and open the file after browsing to the location using the phone's file manager), run it and root the phone. Find it HERE.
Choose the permanent root option as it is still possible to force unroot if needed.
Restart the phone and launch z4root to check the root status. A successful rooting should show 'Unroot' option when z4root app is opened.
{Note: z4root automatically installs Busybox and Superuser application(which appears as an icon in your app drawer) on the phone.}
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
For phones that came with stock 2.2.1 or 2.2.2 installed, rooting first involves downgrading the firmware to 2.2.
Downgrading the firmware can be done with KDZ-FW-UPD.exe (procedure outlined below)
(KDZ-FW-UPD.exe has been claimed to work best with windows xp 32bit.)
FIRST: DOWNLOAD THE Android 2.2 FIRMWARE FOR YOUR DEVICE. For this, go to: [ROMS] Original LG Firmware list and read about the procedure to download the original firmware.
{Tips: Use Ctrl+F in browser to search for Country name, Remember to change the alphabet in 2 places in the final link to download the firmware, Do not bother about the 'CDMA' tag attached to country code. It works for the GSM model phones too. If the link to find out the country codes doesn't work, use the 2nd method mentioned in the post to find out the country code using your phone's IMEI or ESN number }
Download the required Firmware onto your PC.
Links to Original firmware versions for Indian P500 are mentioned in THIS POST
Procedure to install original firmware using KDZ-FW-UPD.exe ( KDZ FIRMWARE UPDATER ) This procedure can also be used to restore the stock firmware and recovery onto your phone in case you want to give your phone to the service centre during warranty period as the phone will appear similar to as you bought it from the store.
[Note: This procedure was used to install V10B_00.kdz(android2.2) over V10C_00.kdz(android2.2.1) on an unbranded Indian GSM model of LG P500 using a Windows 7 Ultimate 64bit updated to date PC.]
1. Install LG PC Suite IV from SD card which came with phone by connecting the phone to PC through USB cable. This is done to install the drivers for the phone on the PC (the procedure is as follows)
- Enable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard & Phone Storage menu.
- Connect phone to PC with the USB Cable.
- Press the 'Turn on USB Storage' button which appears on phone.
- Browse to the folder containing the 'LG PC Suite IV' on the phone's SD card using Windows Explorer and run the LG Installer file. PC Suite will now install on your system along with the required drivers for your phone.
- Cancel setting up PC Suite or continue setting up PC Suite if you want to Sync or backup the phone data.
- After closing PC Suite, Safely remove the USB device from your system.
- Press the 'Turn off USB Storage' button on phone screen.
- Detach the USB Cable.
- Disable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard &Phone Storage menu.
Alternatively, I also tried installing the latest drivers via LG Mobile Support Tool from LG's website (available HERE) but KDZ-FW-UPD.exe (mentioned below) crashes when run. This could be happening only to me, so please try for yourself before writing off this method.
2. For my comfort more than anything else, I switched off the screensaver and other power saving features on the PC and also set the screen timeout delay on the phone to 30 minutes.(Settings/Display/Screen Timeout)
3. Charge the phone to the maximum.
4. Enable USB Debugging on Phone (Settings/Applications/Development).
5. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
6. Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.)
7. Unmount the SD card from the phone (Settings/SDcard & Phone Storage).
8. Open phone back and remove the SD Card.
9. Download KDZ_FW_UPD_EN.7z onto your PC and extract it to a folder. Available HERE.Direct Download Link. (MD5 of 7zip file - 813A28BE9182AB604A1D43E745CE7AD7)
10. Run the msxml.msi file and complete the installation.
11. Connect the phone to PC with USB Cable.( If you are using a desktop PC, make sure you use USB ports that are in the back of your PC, avoid the front ports.)
12. Run KDZ_FW_UPD.exe from the extracted folder.
13. Chose TYPE as 3GQCT & Phone Mode as DIAG.
14. In the 'KDZ file' space, browse for the firmware you want to install. (In this case V10B_00.kdz)
15. Press the 'Launch software update' button.
16. The firmware flashing process is now underway.
If all goes well, in 5-10 minutes the phone will be flashed with the new firmware.
I shall describe in detail what happened with my phone - 10-15 seconds after launching software update on PC, my phone screen turned blank and in a couple of seconds the phone entered the 'Emergency Mode'. During this mode the screen was yellow with Emergency Mode written along the middle of the screen. The phone stayed in the same way till the Software update procedure finished on the pc and the phone turned blank. I waited a while for it to reboot but after a minute or so, I manually switched on the phone. The phone came alive and following the LG boot animation, the android logo screen came up. The phone spent about 2 whole minutes in that state before booting up fully and entering the home screen. Update: Wait till phone reboots by itself or wait for a while before manually switching it on.
17. After booting up fully, detach the phone from the pc.
(If the phone gets stuck in the android boot logo screen during first boot, doing a hard reset by pressing and holding the VolDown+Home+Power buttons may resolve the problem.)
Go to 'About Phone' in Settings and confirm the change from 2.2.1 or 2.2.2 to 2.2.
Root the phone using z4root as mentioned before.
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
IN CASE OF PROBLEMS DURING DOWNGRADING FIRMWARE, read the following thread completely. Various types of errors and various measures to correct them including some innovative ones like shaking the phone etc. are mentioned here - [HOWTO] Phone not responding at all - last chance to repair. It is advisable to read this thread completely before attempting to downgrade the firmware using KDZ_FW_UPD.exe to become aware of all the possible problems you might encounter and their possible solutions.
PS: Here is the link to the phone drivers that came with my SD card. One user reported a problem wherein kdz updater would recognise the phone but the update process would fail during kdz unpacking. the problem was resolved by using the drivers i sent him. So, if anyone has the same issue, it might be worthwhile to try out the following drivers. I wouldn't advise everyone to follow this method, but those of you who are feeling lucky might try it out. Download Link
---------------------------------------------------------------------------------------------
2. INSTALLING ANDROID SDK ON YOUR WINDOWS PC
This step is required to install Custom Recovery on your phone using adb from your PC. Using a Custom Recovery, you can make a backup of your current ROM, restore backups, create partitions on your SD card, wipe your phone and the SD card and then also go on to install Custom ROMs using the Flash from Zip option.
Installing a Custom Recovery can also be done in other ways. Using Android SDK from your PC is just one method.
(Custom Recovery can alternatively be installed on your rooted phone using the commands given in the next section using a Terminal Emulator. This method removes the need for installing Android SDK on your PC and connecting your phone to PC. Download Terminal Emulator from Android Market. Install on phone. Run it and give it root permissions when prompted by the 'Superuser' application. As mentioned in the next section, copy the 2 files (flash_image & the custom recovery image file) needed to install Custom Recovery onto the root directory of SD card. Reboot phone. Open terminal emulator and type 'su' without the quotes and press Enter. This will take you to the root shell (#) from the default user shell($). Carefully type in the 7 commands mentioned in the next section one after the other. After typing in the last command (reboot recovery) and pressing enter, WAIT. The phone will reboot. Custom Recovery will have been succesfully installed on your device.
Hint: Copy the installation commands as a text file to phone & copy and paste the commands one by one into terminal emulator using a text editor. Please make the necessary changes to the installation commands depending on the recovery version used)
To install Android SDK on PC, there are a few requirements/downloads which have to be completed first:
JDK (Java Development Kit) - Download Here
JRE (Java Runtime Environment) - Download Here
Android SDK installer - Download here
So after all the downloads are completed, you are good to go. Run PC as Administrator.
First of all install the JDK, then the JRE and then the SDK Installer.
{If when android sdk installer is run, you get an error that JDK or JRE is not detected even after their installation, wait for a while, shut down the computer and restart and run the SDK installer once again.}
Make sure that while installing the android sdk, the installation directory should be the root of a partition i.e. it should be in the following form: C:\android-sdk, where you should replace the letter C with the letter you have assigned to the partition that you want to install it in.
Now that the Android-SDK is installed, go to the installation directory and start the SDK Manager. You need to add the components of the Android SDK to your installation. Before that I would like to inform you that you can save time if you download only what is necessary. If you are on Android 2.1 then you should download the 2.1 sdk, for 2.2 the 2.2 sdk and so on. You do not need to have all the versions for this thing to work. Just your version would do. So to start adding components, I recommend that you read THIS
After installing the desired components, you need to do perform some simple steps in order to use the adb terminal just like the cmd terminal for Windows.
For that purpose, here are the steps to be followed:
Right click My Computer, select Properties, and click Advanced System Settings. (Windows XP users - Right click My computer and just click Properties and select the Advanced Tab)
Click on Environment Variables, in the System Variables box, scroll down to the variable name 'Path' and double click to edit it
It would read something like " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static".
Here you need to add a semicolon ( ; ) and add the path of the tools folder in android-sdk.
It should finally be like this " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\android-sdk\platform-tools {or the location where adb.exe resides on your system}
Click OK wherever asked and then restart your computer.
Now open a command prompt window and type adb and hit enter. If a terminal window is displayed, you have done it all right.
If it gives some error message, read the article carefully and see what you have messed up with.
---------------------------------------------------------------------------------------------
Tip:
Using adb - How to install apps from PC without having to copy them first to the SD card?
If you want to install apps in one click, all you need to do is download the .apk file of your application to your PC and set the open with option to this batch file which you can download HERE
Save the batch file on the desktop of your PC before setting the option to 'Open With'.
---------------------------------------------------------------------------------------------
3. INSTALLING A CUSTOM RECOVERY
(Procedure of installing Custom Recovery using a terminal emulator from your phone instead of installing android SDK on your PC and connecting your phone to PC is mentioned in the last section.)
UPDATE - 3 May 2011 : Very simple way of installing Custom Thunderg Recovery by AmonRa/modified by Drellisdee version 1.2. Originally posted by ungaze in this post.
1. Download Android Terminal Emulator from Android Market. Install it on your rooted phone.
2. Download the file "amon_ra_recovery_installer.zip" from here or here. Check the MD5 hash value of the downloaded 'zip' file using tools like HashTab etc. before proceeding further. Correct MD5 value : 86db8a52b01f049cadb8f097a4c5bd9e
3. Extract the contents of the 'zip' file to the root of the sd card (ie. not inside any folder) using tools like 7-Zip or WinRAR or any other similar tool.
4. Open the terminal emulator app on your phone and type in the command 'su' without the qoutes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions to the terminal emulator app. Click 'Allow' and proceed. You will notice that the shell prompt has changed from the previous user shell '$' to root shell '#' in the emulator app.
5. While in the root shell '#', type in the following command and press Enter. Wait and the phone will reboot into the Custom Recovery.
Code:
sh /sdcard/rf.sh
Once you are up and running with a rooted phone, you will need to download the 2 files needed to install the Custom Recovery. They are:
Download No:1: flash_image - (This file is the same one needed to install any of the 3 versions of Custom Thunderg Recovery by Drellisdee given below)
Download Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link - requires registration at androidforums.com. (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Download No:2: Custom Recovery image file - Choose & download any version among the 3 available after reading what is written below.
Custom Thunderg Recovery by Drellisdee has versions 1.1, 1.2 and 1.2.1 at the time of writing this. I personally prefer version 1.2 as it supports backup & restoration of ext4 Partition on SD Card. Version 1.2.1 is a little experimental in nature & it may not fit all devices as it has a size near 5 MB.
Link to xda-forum thread for Custom Recovery P500/Thunderg - HERE.
The different versions of the Custom Recovery image files are available at the following pages
Custom Recovery P500/Thunderg v1.1
Direct Download link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Mirror Link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Custom Recovery P500/Thunderg v1.2
Direct Download link - (MD5 of zip file - 217FC9115899A41195CF124CAF07B880)
Custom Recovery P500/Thunderg v1.2.1
Direct Download link - (MD5 of zip file - 388aac16b1184ab15b5500b2b32d914c)
Please check the MD5 hash values of downloaded files to ensure that files are not corrupted using tools like HashTab etc.
Now to install Custom Recovery, Copy the two files [ the chosen recovery image file (*.img) & the flash_image file (flash_image) ] and paste in the root of your SD card (root means the directory L:\ where L is the letter for your Phone's USB Storage. In short, don't create a folder and paste the files inside it on your SD card).
{Note that the recovery image file should have an .img extension and flash_image file should have no extension when placed on the SD card}
Reboot the phone. Connect phone to PC.
The next step requires Android SDK to be installed on your PC.If you have installed the Android SDK, follow these steps:
Go to Start Menu & Run and type cmd (run as Administrator)
In the cmd window, type adb. If you have installed it correctly, you will see a lot of text on the screen. If you get an error message then you have probably not installed the Android SDK properly.
Type adb shell and hit enter
Type su and hit enter
See your phone at this time and touch the 'Allow' option which SuperUser shows you
Now the terminal window will have a # sign appended to it instead of the previous $ sign. See this screenshot for a better understanding
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now one by one, copy the following lines, in the serial order and paste it into the terminal window and press enter following each line(right click on window and paste, CTRL + V won't work)
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 (if it gives error message here, simply proceed to the next step)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (If the recovery version chosen is different from v1.2, type the appropriate file name of the recovery image here instead.)
reboot recovery
Click to expand...
Click to collapse
Wait. The phone will reboot now.
Note:{If you get this error after step 4
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
Simply move on to the next step.
If you get any errors other that those mentioned here, please do not proceed with the last command of 'reboot recovery'. If you do so, recovery may not be correctly installed and you will lose all data on the phone as the phone will be reset to factory defaults. Please go back to the instructions and see what you have done wrong.
NOTE: If on booting into the recovery you get the following message at the bottom of the screen -
E: 'Bad Boot Message'
Don't panic, it's perfectly normal and you can proceed with what you want to do from the recovery.}
Detach the phone from the PC.
To access the Custom Recovery, turn off the phone and then press & hold Home+Vol Down+Power buttons to boot into the Custom Recovery.
---------------------------------------------------------------------------------------------
Once you have booted into the recovery, the touch screen won't work. The actions assigned to the different buttons are given here. Use them to navigate through the different options in Custom Recovery.
Up & down: vol-up and vol-down key
Select: Menu key (left most)
Back: Back (3rd from left)
---------------------------------------------------------------------------------------------
What does Custom Recovery look like & What does it do?
Note: In Custom Recovery versions 1.2 and above, zips can be extracted from inside folders. So, save the zips in a folder named AAA and flash the zip after browsing inside the folder through recovery. The folder name should be named 'AAA' so that it appears among the first on the recovery screen, since scrolling is not an option in recovery.
Note: There is also an unofficial port of ClockworkMod Recovery availble. I do not recommend this recovery for newbies as it isn't compatible with all Custom ROM's out there.
---------------------------------------------------------------------------------------------
4. INSTALLING CUSTOM ROMs
BEFORE FLASHING ANY ROM, DO A NANDROID BACKUP FROM CUSTOM RECOVERY
Since all the ROMs have their own kinds of partitions to be created and other requirements, you can check them at the ROM specific pages.
General procedure to follow for installing a Custom ROM
Boot into Custom Recovery
Wipe your cache, dalvik cache, SD card
Make partitions according to the ROM requirement
Wipe cache again.
Connect Phone to PC
Toggle USB MS and paste the ROM zip file to a folder called AAA in the root of the SD card
Disable USB MS.
Detach phone from PC.
Select 'Flash from zip' option in Custom Recovery menu
Select the ROM file
Flash the ROM file
After flashing is finished, Reboot the phone.
Note: It will take some time to flash and reboot into your new Custom ROM. The phone may stay with the boot logo displayed for a number of minutes. Do not switch off phone during this period.
---------------------------------------------------------------------------------------------
In case of problems with phone, read: [HOWTO] Phone not responding at all - last chance to repair
Also read: [READ FIRST] [REF] Repository of howto's, roms, kernel, etc.
If you feel benefited by this thread, I humbly request you to rate this thread and vote it to the front page. The option to rate and vote is present in the title bar of the thread on the right side.
Please post your feedback. Also THANKS is always welcome. Use the THANKS button (below right) if you feel that I deserve it.
Update - 24 April 2011 - New rooting method without needing to downgrade firmware.
Update - 3 May 2011 - Very simple way of installing Custom Thunderg Recovery
Update - 3 May 2011 - Added Simplified Guide to Root & install Custom Recovery on P500
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
FnH84 said:
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
Click to expand...
Click to collapse
Have you installed the drivers for the phone on your computer? If you haven't, your phone will not be detected when toggling usb mass storage.
saileshchowatia said:
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Click to expand...
Click to collapse
Did you read the thread I have linked to at the end of the article? it may help you.
FnH84 said:
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
Click to expand...
Click to collapse
The procedure for downgrading the firmware is included in the article. The procedure is the same for installing any version of original firmware on the phone.
Procedure to change from one custom rom to another various with each rom.some may need a wipe while others might need repartitioning your sd card.
victortangocharlie said:
Have you installed the drivers for the phone on your computer?
Click to expand...
Click to collapse
Yes. It worked fine before. I tried to flash with CM7, and something went wrong. The whole SD-card is empty, works on another phone though. However, Windows will not recognize it no matter what I do
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
victortangocharlie said:
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
Click to expand...
Click to collapse
Both. I put the memory card on another phone and it said it was empty. Also, custom recovery says it's empty and from mount menu, I can see it keeps unmounting.
Have you tried another card on your phone?
victortangocharlie said:
Have you tried another card on your phone?
Click to expand...
Click to collapse
I managed to get the card work via another card reader. I put the zip files on it and trying again now. Hope it will work.
EDIT: It works!!!
nvm.....................
Glad to hear it.
Sorry for noob question, but after downgrade to 2.2, root, can I flash any rooted 2.2.1 ? And is there any?
Once you have rooted your phone, you can install any custom rom meant for p500. This includes all android versions. And, you don't have to apologise for being a noob, this thread is meant for noobs primarily. everyone has to start someplace. There are many rom's accessible on this forum including android versions 2.2 to 2.3.3. I suggest you try Nessy#Euridice ROM by Dookmatt. I am using it and it is easy to set up.it is based on android 2.2.2
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Guess, you will have to ask the people who make the rom's. I don't know about the cm7 rom.haven't used it myself.
IFLPI said:
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Click to expand...
Click to collapse
rooting a stock Rom is hard where as as rooting a custom made rom is easy because u only need the framework to create ur custom rom....
and about CM7 u can choose between many flavours.... its upto u ..
hi
hey man thanks for the wonderful tutorial!!
i just broght my phone 2weeks back. got it after lots of requests to dad!!
i wanna try all the stuff but im damn scared if i would brick my phone..
although i have the exact same phone as yours..unbranded indian optimus one with v10c
should i try it or is there a risk that ill brick it..?
if i brick it.. is there a chance that i can get it repaired? or will the lg ppl refuse to support me because i screwedwith it??
thanks in advance!!
i chose to start this thread as an educational and informative way of answering simple question so new questions arent repeatedly asked.
first off try to use the search window as much as possible before you post a question, chances aer your question has been asked before, so you will find the answer somewhere.when you do have to post a question be patient, the answer will come either in the form of an informative response or with a link to an informative response.
in every thread or be it for a rom ,a mod a theme etc. there are instructions. follow them to the letter and you shouldnt have any problem.
most importantly, be grateful to the devs or members which might assist you , at least say thank you and hit the thanks button, and donate if you can. these individuals work very hard at what they do here to provide you with the information and freedom you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
Root your HTC HERO200 CDMA...
there are many different methods of rooting your device, it depends on your particular device.
they all work you simply have to find the one that works for you. for instance myself i use the regawmod one click method. (thanks regaw) when
i tried to use it on an associates device it didnt work...you have to find the method that works for your device.
youll find the files and programs you need to perform whatever procedure you choose to try on the developers page.
make sure you read the instruction completly before you begin. when you do begin follow the instruction to the letter and you shouldnt have any problem.once again, dont get piussed at the dev because it didnt work, its not that the procedure doesnt work, it just didnt work for you...simply search for another method and try again.and you will succeed.
i was going to post some of the methods but dont have permission from the devs to do so, so for now youll have to search for the precedures yourself. if or when i do get permission ill edit this thread or post the link in order to help yo on your way,,,ehhh for now itll be good practice for using the search window.
method 1.
hhttp://www.gadgetsdna.com/how-to-root-htc-hero-cdma-stock-android-2-1/3628/
The HTC Hero 2.1 exploit is based on the EVO rooting method. Rooting HTC Hero Android phone provides full access to its system files allowing you to modify the phone’s firmware and install third party apps, themes and custom ROMs. You can then spruce up your HTC Hero handset with number of third party applications.
How to Root Sprint’s 2.27.651.5 Release for CDMA Hero (Stock Android 2.1)
Note: If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK.
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here. Run the installer, and reboot your computer when it is finished. Skip to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Navigate to Settings > Applications > Development > and make sure it is checked
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is “Charge Only”, not “Disk Drive” or else this won’t work. You may restart your comuter when prompted to do so.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter. Alternatively, navigate to Start Menu > All Programs > Accessories > Command Prompt
Step 9: You enter the commands followed by pressing ENTER, one code at a time.
1 cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type
adb devices
You will now notice your HTC Hero phone’s serial number. If you get “device not found” error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands one by one:
adb push unrevoked /sdcard
adb push recovery.img /sdcard
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.
adb shell
sh /sdcard/unrevoked
You should now see output that says this:
UNREVOKED
============================================================ unrEVOked: root for HTC evo and hero (http://unrevoked.com)
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it, which is only possible on rooted devices.
Open the Superuser Permissions app. You will see a blank screen.
In the Command Prompt on your computer, type:
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
$ su su #
Now Type
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type
reboot recovery
Your phone will now boot to the custom recovery image you just flashed. In the Recovery Menu on your phone, choose the option:
Flash zip from sdcard
Then Select
boot-patched.zip
and press the Home button to apply. Once Recovery says “Install from sdcard complete” select “Reboot system now” from the menu.
Voila!! You now have full root access on HTC Hero 2.1!
Thanks to the guys at xda-developers and gadgetsdna
or, you can try regaw's one click root method. you can find it here on Xda, just use the search window,,,it's easy
both of these methods have worked well for me in the past, im sure one of them WILL work for you
-----------------------------------------------------------------------------
Flashing a ROM (from clockworkMod)
this is the method i use and i "never" have any problems
download the ROM of your choosing and move to the root of your sdcard
follow the devs instruction for installation which should be something like this;
1. do a nandroid backup
2. reboot into recovery
3. wipe data
4. wipe cashe
5. choose advanced, wipe dalvik
***OPTIONAL***
6. choose mounts and storage
7. format system
8. format data
9. formatcashe
10. go back. and choose install zip from sd card
11. choose, choose zip from sd card
12. find the rom you want to flash and choose yes
13. when its through flashing choose install zip from sd card
14. find the gapps you want to flash and choose yes
when its through with the flash the screen will return to the main menu and choose reboot system
the first boot will take a little longer than usual this is normal. setup your google s#@ts as usual and enjoy your new ROM.
follow these instructions and you shouldnt have any problems, if you do, go back to the thread you downloaded from post a reply to report it to the dev so they know theres a problem and they can determine if its a problem with the rom, a problem with the way you flashed or a problem with your system.
15. "ONCE AGAIN" most importantly, be grateful to the devs, at least say thank you and hit the thanks button, and donate if you can.
these individuals work very hard at what they do here to provide you with the information you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
-----------------------------------------------------------------------------
themeing your new ROM
1. make sure the theme you choose is compatable with the rom you have flashed
2. since alot of the themes have a different procedure for installation,"READ AND FOLLOW THE DEVS INSTRUCTIONS"(sorry for the caps)
they are there for a reason.
-----------------------------------------------------------------------------
boot animations
1. Put the zip file in your tools folder from the android-sdk-windows
2. Load up Command Prompt (cmd) and go to your tools directory inside the android-sdk-windows folder
3. Load up your phone into recovery and mount /system
4. Type in command prompt
adb remount
adb push bootanimation.zip /system/media
adb reboot
or (compliments of user7618)
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----------------------------------------------------------------------------
Flashing a different recovery image
cd C:\android-sdk-windows\tools...got
cd C:\android-sdk-windows\tools>adb devices...got
(recognized phone)>>>>>
cd C:\android-sdk-windows\tools>adb shell
#flash_recovery image /sdcard/recovery-clockwork-4.0.0.2-heroc-20110611.img (enter)
mtd: successfully bla bla bla
#reboot....
or,,,
[edit] Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Copy the recovery.img to root of the SD card.
3.Boot the phone into recovery.
4.Open command prompt, cd to the Android SDK directory & type the following commands:
adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method II
Flash recovery using: RomManager
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.On the SD card, go to /clockworkmod/download/koush.tandtgaming.com/recoveries.
3.Rename the old image there named recovery-clockwork-2.5.0.1-heroc.img to recovery-clockwork-2.5.0.1-xxx.img.
4.Move, then rename, the recovery.img you downloaded to recovery-clockwork-2.5.0.1-heroc.img.
5.Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
[edit] Method III
Flash recovery using: Terminal Emulator Note: Requires s-off, otherwise you'll recieve "out of memory" errors.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Move recovery.img to root of the SD card.
3.Open the Terminal Emulator on the phone & type the following commands:
4.:
su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method IV
Flash recovery using: H-Boot/S-Off Only HeroC Only
See S-Off for CDMA Hero if you are unsure what S-OFF is.
1.Download HERCIMG.zip
Newest Download: (version 3.0.5) HERCIMG.zip <--Updated 01212011
md5: 6dcd265a51cc7090824d7f9f889b370b
Alternate Download: (version 2.5.0.7) HERCIMG_clockwork-2.5.0.7 <--Updated 02-07-2011
md5: 0a367eb1d4445c72f8022769f7edc9dd
2.Move HERCIMG.zip to root of the SD card. Make sure the file is named HERCIMG.zip or H-Boot will not recognize it.
3.Power off the phone.
4.Hold the Volume Down & Power' button until the phone boots into the bootloader.
5.Wait for bootloader to scan and find HERCIMG.zip.
6.Press action to install.
7.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Retrieved from "http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery"
-----------------------------------------------------------------------------
Change sprint insignia (ON AOSP) to whatever you want
1. Download eri.zip
2. Unzip the file to wherever you please.
3. Right click on eri.xml and choose "Open with Notepad"
4. Once you open the file you will see "Sprint" in the 5th line.
5. Delete Sprint and place whatever you would like in it's place. I believe you have up to 16 spaces to work with if need be.
6. Save the file with an .xml extension. Important: Make sure it is eri.xml and not eri.xml.txt. This will cause issues.
7. Place the eri.xml in your /androidsdk/tools directory.
8. Pull up your Command Promt/Terminal/Etc
9. CD to your /androidsdk/tools directory and:
adb remount
adb push eri.xml /data/eri.xml
adb reboot
or, (thanks to user 7618 )
I threw together a simple app to change the Carrier Name in the status bar/lockscreen to whatever you want since my alot of people seem to ask how to change it. Feel free to use it. Tested on Incredible and Eris. Dev's feel free to thow it your roms if you want. No ads and free just a simple tool to change the text. Thanks to the great Eris community.
Currently only works for AOSP roms such as cyanogenmod.
V1.3
While trouble shooting some radio issues on a rom I realized there's no need to reboot the phone to apply the new carrier name. I only needed to cycle the radio so I changed the app to toggle airplane mode on and then back off after you input your text so the change should take place immediately. This should make it a little easier to test and try different things or just change it more often.
I also added some shortcut buttons at the bottom to quickly add the text for the ", < and > signs so you don't have to type it all out. Only tested this with cm7 but should still work with any rom's it worked with before. Again thanks to Psiphon for pointing these symbol fixes out.
http://www.multiupload.com/RO6RZUUL16
V1.2
Fix for phones that don't already have an eri.xml file there
Added version number to bottom of screen so people can be sure what version they are running.
http://www.androidphiles.com/files/g.../ccname1.2.apk
V1.1
Fixed force closes when using symbols.
You can now use symbols except for double quotes. Apostrophe (single quote) seems to work fine.
Some usefull info if you want to use quotes....
Originally Posted by Psiphon
You can use special characters like the quotation marks and greater/less than signs by using entity references (either using an entity name or number):
" (quotation mark) use "
< (less than sign) use either < or <
> (greater than sign) use either > or >
I hope this helps!
Added Toast popup to let you know the name has been set.
If reboot button does not reboot phone just reboot the phone manually
http://www.androidphiles.com/files/g.../ccname1.1.apk
This app does one thing. It takes the input text you type and creates and eri.xml file and puts it in data/ folder on your phone. Then you can reboot for change to take effect. You can uninstall the app after you change it if you want or you can leave it on there(it's pretty small) in case you like to switch it every now and then. If you flash a new rom you will have to rerun the app.
-----------------------------------------------------------------------------
hopefully there will be more info in the future to add to this thread that will make things easier for everyone all around.
-----------------------------------------------------------------------------
***TO ALL DEVS AND OTHER MEMBERS*** i myself cant thank you enough for the help and advice ive recieved in the past, if you might hace any information you feel would be helpful to this thread please feel free to PM it to me and ill see that i edit this post with your procedures. and ofcourse your names will be added to a list of thanks at the bottom of the post,,,Thanks again,
THANX FOR THEIR HELP TO ME IN THE PAST;
flipz
coffeehandle
MattCrystal
laie1472
user7618
PMGRANDS
kushdeck
bierce22
conap
psiphon
kifno(aspentree)
-----------------------------------------------------------------------------
all of the information i have provided here has been compiled from Devs and other membes in order to assist new memberslike myself , and to help the devs and senior members so they dont have to keep answering the same questions again and again.
*** i f you want to thank someone, thank them for passing on their knowlege to me as im passing it on to you***
enjoy,,,
please dont double post
Nice beginners guide.
-----
3vo. That is all that needs be said.
Nice beginners guide.
Also, an easier way to change the carrier banner:
http://forum.xda-developers.com/showthread.php?t=960099
Instead of all that goofy crap with files and whatnot.
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----
3vo. That is all that needs be said.
Thanks man ill keerp adding, i really hope this helps some folks
Kudos. Good guide.
#Root/Hack-Mod_Always*
Also we dont talk about "he who must not be named" around here so you might want to take that out of the credits.
lai and user know who im talking about lol.
Uhhhhh,,,Ooops. My bad....sorry bout that guys.
ha lol i was just kidding but seriously that guy went bannanas and had a severe case of schizophrenia lmao.
lol, i hear ya man, i feel credits given where credits due, but on the other hand,,,,aw well you know what i was gonna say
Yeah, dude was crackers, but if he helped you, then he helped you. I'd leave him in there, personally.
-----
3vo. That is all that needs be said.
Yup agreed. A if he helped he helped that's just how it is. Like the guy or not.
#Root/Hack-Mod_Always*
cool guys i do feel the same way, but dont wanna stir any bees nests either, ill put it back in but we'll just overlook it. thanx for understanding