Database Develop

Rooted, but no recovery

I have a rooted G1 with CM 4.0.4, as I have been unable to upgrade without cm's new recovery image. But in my pursuit of installing this, I have encountered a new problem. I don't have any recovery image! When I try to boot into recovery, it reboots once after the G1 screen and then goes to a blank screen, where it eventually just turns off. Any ideas on how I can get cm 1.4, or any recovery for that matter? Oh, and I used to have a recovery image (jf 1.43 I think) but I somehow lost it. I then had some weird one that wasn't from a specific developer, and was feature limited. Now I don't have one at all, and really want to get to the newest rom. Please help me!

Have you tried puting the recovrey image on you sd and flashing from terminal

just check cyanogenmod.com website and goto wiki and read on how to install cyanogen's or amon's recovery image

yeah..ill be that guy this time...
wRong section fool I pity you, use Q & A....

I've tried all that, and at least twice or three time each.

If you cannot boot into regular recovery, your best bet would probably be holding camera and power button together (bootloader)... if you can do that then you should be able to use the recovery image (rc 29) you used to root your phone to restore the recovery... It will no longer be rooted after recovery is done but you can always just reroot the phone... hope that this helps

And sorry for posting in the wrong section, I'm not exactly sure where everything is supposed to go yet, and I thought this was the right area. My bad.

Heh I was just joking... its only a matter of time befor a XDA bully comes n makes you feel like crap. Because they been using this site for years. N think they are better then us XDA noobs..... n e ways good luck with your issue!

Recovery
coolbrett007 said:
I have a rooted G1 with CM 4.0.4, as I have been unable to upgrade without cm's new recovery image. But in my pursuit of installing this, I have encountered a new problem. I don't have any recovery image! When I try to boot into recovery, it reboots once after the G1 screen and then goes to a blank screen, where it eventually just turns off. Any ideas on how I can get cm 1.4, or any recovery for that matter? Oh, and I used to have a recovery image (jf 1.43 I think) but I somehow lost it. I then had some weird one that wasn't from a specific developer, and was feature limited. Now I don't have one at all, and really want to get to the newest rom. Please help me!
Click to expand...
Click to collapse
any recovery problems can usually be solved by this:
# cat /sdcard/recovery.img > /system/recovery.img
whereas /sdcard/recovery.img refers to the file you want to use

Rules
cali50ex said:
Heh I was just joking... its only a matter of time befor a XDA bully comes n makes you feel like crap. Because they been using this site for years. N think they are better then us XDA noobs..... n e ways good luck with your issue!
Click to expand...
Click to collapse
it's strange that you would refer to them as a bully simply for enforcing rules that no one seems to follow .. everyone has been asked to post general questions to the Q&A and specific questions to the appropriate thread that has already been started

coolbrett007 said:
I have a rooted G1 with CM 4.0.4, as I have been unable to upgrade without cm's new recovery image..... Please help me!
Click to expand...
Click to collapse
Did you let the HTC recovery image boot all the way . The one you have to install before installing Cyanogen 4.2.5. You should of lost root d/t this. When you try and pull up recovery is there a phone with a "!" ? If so try Atl L or Alt S to see if it pulls up anything.
Also do you have the newest Radio? ( could be the issue also )

I broke recovery mode ?

Hi...
Ok.. I was on rogers 2.2 stock, I was trying to follow instructions to install paragon, anyway, it didnt work, my phone was still working great tho.. so i tried flashing stock jh6 with the one click from the wiki here... That worked and I now have a rogers phone with att stuff loading up. anyway, I am trying to complete the instructions for paragon but I can no longer get to recovery mode.
the att logo keeps rebooting if i keep holding down vol up and down, what do I do now ?
Edit : I cant seem to even get to download mode Recovery mode always worked before, download mode was always tricky, but it refuses now

do you have adb installed?? if so run adb reboot recovery in command prompt.
OR
Take out battery, take out sim and SD card. press and hold VOL UP/DOWN. put in battery, press power. release power upon seeing AT&T sign. pray.
Works for me about 99 times outta 100 at this point!
but i prefer adb since its much more fool proof!

distortionist said:
so i tried flashing stock jh6 with the one click from the wiki here...
Click to expand...
Click to collapse
<captainhindsight>You should not have flashed JH6.</captainhindsight>
As per the above post, boot the phone, enable debugging and use 'adb reboot recovery'. After you get that sorted, flash the 3 button fix and never flash to stock unless stock firmware is your final destination or your phone is so hosed you have to use download mode to fix it. If you do use odin in the future then use the right one for your phone build so you don't lose your button combos.

opcow said:
<captainhindsight>You should not have flashed JH6.</captainhindsight>
Click to expand...
Click to collapse
Nor should you have allowed yourself to be photographed in a compromising position wit Courtney Love...Sorry, couldn't resist.

but I only followed instructions Everyone that asks was getting told to go try and blah blah, well that was what I was doing.
You know now I am really stuck. I did use adb and restored stock and didnt want to mess with my phone anymore, but the at&t logo kept popping up, im with rogers. I found a fix and was following those instructions when odin screwed up, it started flashing then said it failed, it happened to me once before but my combo key was working then.
I dont understand why it stopped, It seemed to be intermittent, a bunch of issues, after flashing that at&t rom.
I wish I could fix it, I am stressing out over it, ill get the stuff for that jig tomorrow and hope that works. This phone is brand new! I am not a modder or hacker, I got stiffed by rogers and samsung with the voice dial over bluetooth issue, they wouldnt take the phone back.
I would love to have the att logo gone, rogers froyo 2.2, and broken bluetooth.. Its better than a paper weight. Please help me ! You know what.. I can live what that logo.. I just want to get my phone operational.
Goodnight, and thanks for your help.

i'm guessing you didn't flash the 3 button fix that opcow suggested before doing anything else?
if you can get into download mode, flash this:
http://forum.xda-developers.com/showthread.php?t=812434

No I didn't, in its forum it says if you had no problems initially with the 3 buttons, this is not for you. Thats what it said! I was told I shouldnt have done that and should have flashed the 3 button fix after the fact.
I just bought resistors, ill be home later to try and force download mode.
Thanks for your help, I am not as upset as I was yesterday, I was tired.

[Q] [i9000] cyanobricked

Hi there,
I noticed I can't get in download mode anymore. Whatever I try it won't show the yellow triangular download sign. It just boots into cyanogen.
I have tried the 3 button trick but recovery nor download works. That's when I had the idea to apply the 3-button fix. adb reboot recovery brings me in the cwm recovery mode. adb reboot download just reboots the phone. I even tried the 300k ohm jig which always seemed to work as a failsafe. That also just boots the phone into cm.
I have checked with my brother who also runs CM nightly 101 and for him the download mode works fine so it is my phone, not CM.
The phone works fine now, is rooted too so I wondered if there's any way to fix this by rewriting the bootloaders. I want to have this fixed as a failsafe is flashing ever fails or if one of the nightlies gets corrupted.
Is there anyone who can confirm the download mode is in the primary bootloader (boot.bin from a stock rom) and is it safe to just flash_image that to the boot partition or will that be a guarantee to brick. The idea is that I still have root console access so I have to fix it from there.
Any help is appreciated.
Christiaan
Galaxy S
CyanogenMod 7 Nightly #101

Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Sent from my GT-I9000 using XDA Premium App

BHuvan goyal said:
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Click to expand...
Click to collapse
Thanks for the quick reply.
Tried the tricks with and without pc-usb/charger and it made no difference. The 300k ohm jig trick can't be done with power or computer connected since you have to use the usb connection on the phone for it. It usually was my ever working failsafe.
I also tried the quickboot app without any luck. It seems it is responding to the download command but the code isn't there anymore.

Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Sent from my GT-I9000 using XDA Premium App

BHuvan goyal said:
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Click to expand...
Click to collapse
Holding the power button for two seconds indeed brings up the profile/reboot/shutdown options. Selecting reboot only gives two additional options, reboot and recovery which do as they say. I can boot cwm recovery but from there I can't go into download mode either.

Try downloading terminal emulator and then reboot download or ADB reboot download

Nitro_123 said:
Try downloading terminal emulator and then reboot download or ADB reboot download
Click to expand...
Click to collapse
Tried it from the terminal with reboot download. Also tried adb reboot download long before that. It just reboots and starts. I have the feeling the piece of bootblock that's holding the download mode isn't there anymore.

There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?

azzledazzle said:
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
Click to expand...
Click to collapse
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.

cvdveer said:
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
Click to expand...
Click to collapse
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?

azzledazzle said:
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
Click to expand...
Click to collapse
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.

cvdveer said:
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
Click to expand...
Click to collapse
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure

azzledazzle said:
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
Click to expand...
Click to collapse
Thanks for thinking with me. I'll give the nandroid solution a go if there are no other replies within a reasonable time.
I'll post the same question in the CM forum but contacting the CM devs could be hard. They don't give any official support to nightlies and I can't say I'm convinced it has anything to do with CM at all. Though they do have the knowledge to answer the question or build a package to repair it. But you're right there's nothing to lose in asking.
Ofcourse I searched the forum before posting and found out I seem to be the only one ever with this problem. The solution could be as rare so I'll keep you posted if I make any progress beside here. That's what the whole idea behind this forum is for right?

True man !!
And if you get a solution or a dev to make a flashable bootloader. It could help other people in future
Good luck. Keep us posted

http://forum.xda-developers.com/showthread.php?t=1236273

Nitro_123 said:
http://forum.xda-developers.com/showthread.php?t=1236273
Click to expand...
Click to collapse
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.

fixable?
i have a samsung here the S GT I 9000 and i tryed to use odin on it and now this pops up every time i try to up load an os
--installing package...
finding package...
opening package...
verifying update package...
installing update...
successfully install update...
--copy media files...
successfully copied media files..
formatting /data...
E:format_volume: rfs format failed on / dev/block/mmcblk0p2
formatting /dbdata...
formatting /cache..
deleting meta data
data wipe fail.
-- appling multi-csc...
installing multi-csc..
cant access to '/system/csc/bmc/system/' . sucessfully applied multi-CSC
Help!

Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.

Erahgon said:
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Click to expand...
Click to collapse
Errr talking to me or adonai? Sounds like two seperate problems for two seperate topics.

cvdveer said:
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
Click to expand...
Click to collapse
I REALLY liked your answer
BTW , same here

I need help asap

okay i was puttiing a new rom on my phone and long story short i deleted everything and now i get stuck at the htc boot screen and CAN NOT get any further past that, im not sure what or if anything i can do to fix this, some one please help, email me will be quicker, [email protected]
im used to working with samsung phones not htc and im stuck in quicksand with this one.

Did you make a backup in recovery? I tried to flash a ROM once and it got stuck on the HTC screen but I somehow managed to hold the power button for a while and reboot back into recovery to restore to my previous ROM.

Question about situation
Normally in this situation you could hold Vol Down+Power until the unit shuts off then let go of Power and continue holding volume down. This should drop you back off in HBoot/Fastboot from here you could get back to the recovery screen and most recoveries now allow for ADB access to repush or flash another install.
If you are able to get into Recovery what are you currently running?

mortal.glitch said:
Normally in this situation you could hold Vol Down+Power until the unit shuts off then let go of Power and continue holding volume down. This should drop you back off in HBoot/Fastboot from here you could get back to the recovery screen and most recoveries now allow for ADB access to repush or flash another install.
If you are able to get into Recovery what are you currently running?
Click to expand...
Click to collapse
there is absolutely no rom on it now, so theres nothing on the phone. i think my only hope would be trying to run something of an sd card or hope that i can run some program on a computer.
twrp isn't installed as well. everything got erased, i think what i have to do is send the files over through terminal if i can get it connected via usb, idk. im not sure, i feel like I've really done myself in on this one, some one save my skin please

drewd66 said:
there is absolutely no rom on it now, so theres nothing on the phone. i think my only hope would be trying to run something of an sd card or hope that i can run some program on a computer.
twrp isn't installed as well. everything got erased, i think what i have to do is send the files over through terminal if i can get it connected via usb, idk. im not sure, i feel like I've really done myself in on this one, some one save my skin please
Click to expand...
Click to collapse
You could download recovery image on the PC flash via fastboot, download rom copy to sd card then flash rom in recovery
Sent from my EVO using XDA Free mobile app

gstanke said:
You could download recovery image on the PC flash via fastboot, download rom copy to sd card then flash rom in recovery
Sent from my EVO using XDA Free mobile app
Click to expand...
Click to collapse
i don't want to sound like a noobie but how would i get that to flash i can't pull up any screens besides the htc white screen

Have you tried pressing power while holding the vol up button then when the screen goes black pressing and holding the volume down button to get into the bootloader? If you can get into the bootload (and I suspect you probably can if the phone still gets to the white HTC screen) you can flash a recovery and then flash a rom.

nothing is wrong with your phone nor do you need an sd...if u know how to use adb...push the rom back to the phone in recovery..simple as that..sd card works too but youll be fine which ever way...u have no problem

DruoGaby said:
nothing is wrong with your phone nor do you need an sd...if u know how to use adb...push the rom back to the phone in recovery..simple as that..sd card works too but youll be fine which ever way...u have no problem
Click to expand...
Click to collapse
Greetings,
No need to be disrespectful to others. I edited your post.
Thanks,
BD619

BD619 said:
Greetings,
No need to be disrespectful to others. I edited your post.
Thanks,
BD619
Click to expand...
Click to collapse
umm sir i dont know how u could have possible taken that to be disrespectful...i wasnt trynna cause any issues at all...thats how i talk..not a damn things wrong with it...just wanna let him know his phone is okay..u used your judgement wrong that time bruh...hahahahaha

oh jesus. i got it now! thanks guys (specially food not poking fun at me!) i got it very easy fix! :good:

[Q] [Q&A][G-I9000]Phone wont get past boot logo/wont go into recovery

Hi there! Now, firstly, ive always used Windows Phones but, would like to join Android and discover what it is really like to use... It really does look like fun to use
Anyway, last night i got my mums old Samsung Galaxy S1(G-I9000) and tried to root it and put CyanogenMod on it so i could get arid of the broken TouchWiz(I don't know what the new versions of it are like, but this one was broken and horrible to use) and get updated to Android 4+. Now, the root was successful and i am very happy with myself for doing that.... But here is where it all fell apart....
So, i jumped on their guide on their cyanogenmod wiki and it turns out that doing that first step(The "Installing a custom recovery on Galaxy S") was not needed because i already had ClockWork on my phone and that doing it would apparently break my phone.... I did not realise that till afterwards.
When i tried to reboot into recovery mode to install CM it got stuck on the boot screen. I think to myself maybe its stuffed and ill just reboot it again and see if it work... Nope. Now i try to reboot normally and leave it alone.... Nope. Turns out, all i can do is get into download mode. Now, from what ive found online, using Odin to reflash my phone with the stock ROM is how to fix my phone, problem is, Odin is not finding the phone and Hard Resetting the phone by holding down Lower Volume button and power is not working.... How can i fix this?

I think you can still recover it. However, the reason Odin might not recognize it it's probably because you haven't installed the Samsung USB drivers
If you install them and try to go into Download mode again you might be able to flash the stock ROM back onto your Samsung phone