Database Develop

Boot problem after downgrading

Hi,
I am sorry if there is already a similar thread, but I couldnt find it.
I have a huge problem with my German T-Mobile G1. Today I wanted to root the system. I used the instructions on XDA forum and "successfully" did the downgrading to RC7 but now I cant power on the phone. It stops at loading screen with android text and logo. Nothing happens than.
I have tried with the wipe and manual update with next version of firmware using update.zip but problem is still here. My phone is now totally unusable and I can now just hope that here on this forum can someone help me.
Please give me an advice
edit: there is one more thing: I can not power of the phone without taking the battery out. It automatically turns on every time I put battery in and every time I restart. Switch off button does not work any more.

Is the usb cable plugged in everytime you pull the battery and reinsert it? Because if it is the usb cable automatically turns on your g1. Can you access recovery +/or bootloader?
Recovery = home+power
bootloader = camera+power
If you can't get pass the g1 screen by pressing either combination of buttons you are bricked. If you are bricked () Call your carrier and tell them that you got an OTA update and it never turned on since. They should replace your g1 with a new one

I dont use USB cable. I prepared the microSD card using the USB-reader dongle. But I had pluged the electric cable so that was probably the reason for automatic turning on. Ok, now we can focus on the main problem.
Yes, I can access both recovery and bootloadaer al least. As I said, I have tried with some updating but nothing worked yet. When I use recovery some of files give me message: E: No signature. E:Verification failed.
This thing with carrier could also be a problem. I bought my phone in a shop which is buying them in another country because G1 is not officially being sold in our county. They give me a guarantee but it is guarantee from the shop and not official importer, so there would probably be some problems.
Thanks for trying to help me. I hope with this informations it would be little easier.

Place the file on your sdcard again. Down load a fresh copy of the latest hacked RC and make sure (if you're on windows) to name it "update" not update.zip because the .zip is already assumed in windows. Once its on your sdcard wipe and flash it. See if that works.

Can I use hacked RC on G1 that has not been rooted yet - just now very successfully downgraded?

do You place on sd card file "dreaimg.nbh" and turn on the phone with camera button pressed ?

Hettfield said:
do You place on sd card file "dreaimg.nbh" and turn on the phone with camera button pressed ?
Click to expand...
Click to collapse
Of course I did it. How would I run downgrade process otherwise...

Maybe You need RC29 version

I did try with RC29 too.

[Q] Bricked after upgrade attempt

Hi!
I was trying to upgrade my Galaxy Captivate following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=783403
First I tried the KIES option, but ended in the phone stuck on a black screen after 2 minutes of the S logo on it.
So, I then tried with ODIN using both package, first with the original, but ended getting an error "E:Can't mount /dev/block/stL10 (Invaild argument)"
And then with Richthofen's integrated package which seems like fixed that issue. indeed did it, but not fixed the original issue, after this one I ended in the same stage than with the KIES upgrade.
I can enter on recovery mode and move using the volume up and down button, however, the "power" button to select any of the option do nothing.
I tried to connect with adb and indeed see it (when is on recovery mode)
adb devices
List of devices attached
10004cb6cc04 recovery
But can't do anything on the phone, not even reboot it with adb, the process get's stuck and the phone is not rebooted.
Anyone have any idea of what I can do now? send it to Samsung is not an option since I bought this phone in USA and I live in Argentina, this phone is not available in the country yet.
Thanks in advance.

Thread moved to Captivate Q&A.

You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.

http://forum.xda-developers.com/showthread.php?t=731989 saved my life! I was so angry with me for being such an idiot!. I lost all the contents on the phone, but at least got my phone working again.
By the way, to put it in download mode what I did was, remove the battery, put it back, press volume up + down and plug the phone to USB.
Thanks a lot Tazman171

No problem, just passing on info that was passed to me by helpful people at this sight. And yep, the way you did it was right, I was thinking of the recovery menu and selecting reinstall packages option, I actually was able to do it with the way I described above.

tazman171 said:
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
Click to expand...
Click to collapse
Hey right now my phone is "bricked" because of a botched JPC Froyo ROM install and I have no way of getting it into download mode. None of the methods on the "One-Click Stock ROM" work, and a few other ones suggested don't either. I'm curious as to how you did it with tapping menu and home, etc. Would you mind posting up some instructions?

Sorry about the late reply, it was recovery mode that I got into, not download mode. You might have one of the phones that won't support the 3/2 button methods of getting to the download/recovery menus. It worked for me because my phone does support that method, it was just the I-9000 had switched my buttons around.

[Q] Screen Blacks Out After Start Up Screen

I'll preface this thread by saying that I've look all over to help me remedy my problem, but I have not found anything that has resolved my issue. I've tried all the combinations of the the manual buttons to bootloader mode and download mode, and it will not work as my firmware is not the current Bell hardware burron fix (I have the old JH2 firmware, w/o the updated SPL)
What prompted this is that I was trying to reinstall the default android clock app that I deleted on accident. I had downloaded some default apps that were pulled from the Samsung Epic 4G (can't post URLs properly due to my user limitations, thread here: forum.xda-developers.com/showthread.php?t=773142) thinking that the apks in there are the same. I tried installing but that failed. That should have been a red flag, but I wanted to have the clock app back. So what I did next is what I regret. I copied and pasted the AlarmClock.apk and AlarmClock.odex to the systems\app folder using Root Explorer. It wasn't until I rebooted my phone that this problem occurred.
I know that my phone isn't completely bricked as I can still see the battery icon when I plug it in to charge...and the phone does load the start up screen, but it won't get past that and will black out and the capacitive LED buttons (menu and back) will stay lit.
I've been diligent in backing up my information on my home computer (I'm at work now), so data loss is no problem for me. What I would really want is to fix this. My last resort is to return tot the store and get an exchange, which I really don't want to do.
Help is greatly appreciated.

you cannot install/copy (which have .odex file) apps from other firmware versions becuase the .odex is encrypted for a particular version.. if you pasted to system/app and it is a critical app from wrong version you will hang/freeze phone.. try to get into download mode and reflash the firmware..

Do you have access to the phone over adb?
Adb reboot download?
Sent from my GT-I9000 using XDA App

I've read about the ADB Reboot Recovery, but it mentions that my phone has to be on USB debugging mode to work, which I believe is not on =/
Is there a link where I can download to try anyways? I've searched fro it, but I'm not sure if what i searched is the right thing.
I cannot get the download mode to work as the combinations I've been using do not even register...the phone just keeps looping the Samsung Galaxy i9000M screen when I hold the buttons...like it's in perpetual reboot mode. Like I stated earlier, the hardware buttons do not seem to work. I have the old JH2 firmware that was updated from Keis that does not have the hardware button fix.

xlittle_lambx said:
I've read about the ADB Reboot Recovery, but it mentions that my phone has to be on USB debugging mode to work, which I believe is not on =/
Is there a link where I can download to try anyways? I've searched fro it, but I'm not sure if what i searched is the right thing.
I cannot get the download mode to work as the combinations I've been using do not even register...the phone just keeps looping the Samsung Galaxy i9000M screen when I hold the buttons...like it's in perpetual reboot mode. Like I stated earlier, the hardware buttons do not seem to work. I have the old JH2 firmware that was updated from Keis that does not have the hardware button fix.
Click to expand...
Click to collapse
this should work if you take battery out hold down all three buttons and when you first see logo release power button for 1 sec. then repress.
also try it with and without usb plugged in.

For adb u need the android software development kit (sdk). Its available at developers.android.com. Simply run sdksetup and choose sdk tools.
Sent from my GT-I9000 using XDA App

I gave adb (great tool btw) a try, got it to run in command prompt, but I get an error saying device not found. Unfortunately, I did not have USB debugging mode on prior to my phone's screen blacking out on me. I should mention that I have a Bell Mobility Galaxy S I9000M, and hardware button attempts for any mode (volume up and/or down + home + power on, in a multitude of combinations, e.g. USB connected/disconnected) , be it recovery or download, have been futile as that method is not in the firmware I have one my phone. I'll have to use my last resort and get an exchange for the phone at the store I got it from. With any luck, hopefully someone who works there will have the magic touch and revive my phone. *crosses fingers*
Thanks for all the helpful suggestions. I'll keep them in mind to not let this happen again. Thank goodness for my constant backups instilled in me during my Windows Mobile days.

When the phone is ON firmly press volume up + home + power. It will reboot. Keep holding them! Wait a half a second after the gti9000 logo appears then let go of the power button. Keep holding volume up and home! This should boot you into recovery. Try it a few times. I found it is all in the timing of letting go of the power button.
Hope this helps!
Sent from my GT-I9000M using XDA App

Also, I had an i9000 in your state and even after I had it previously working with Android SDK and the Samsung USB driver (essential in Windows but not included the SDK) but after I messed up the ROM (trying to lagfix it) it stopped responding to adb commands on either OSX or Windows. Boot recovery from the aforementioned hotkey combination seemed to be the only way to fix it. But I am a n00b. I'm only passing on what I experienced.
Cheers,
Aaron
Sent from my GT-I9000M using XDA App

Had a similar problem after flashing a new rom, managed to egt past it by reflashing using Odin.

One of my friends has just given me his i9000 in the same state to see if I can fix it, he has been quoted $300NZ to repair!
He says he did it trying to flash a rom after successful root.
I get the galaxy splash screen but no matter how i hold and release the aforementioned keys I just dont get anything all.
ADB returns no device found and not seen by ODIN.
Tried many battery pulls, reboot + three keys and releasing/releasing-reapplying power button at various times during the splash screen. And with/without USB connected.
Pretty sure the device did have USB debugging enabled before this.
I am watching this thread closely, if I fix it I get a box of beer!

Will not go in download mode

I was at 2.1.1 Cognition and for some stupid reason went into ROM manager and tried to apply my original backup I did when I was just Rooted and on the stock software from ATT.
It got to the data partion and couldnt access it, rebooted and now I get force close errors when it boots. I can virtually do nothing cause the errors just come one after another.
I tried to go into download mode so I could use ODIN and start over and it will NOT go in download mode. I am holding the vol up and down and then pressing power. I am holding all three until the screen goes black twice then letting go of the power. It just goes back to the little circle in the middle meaning its charging.
I am hosed....please help me get this fixed!

The force closes comes from within android...its boots up but is unusable.

gocats7 said:
I was at 2.1.1 Cognition and for some stupid reason went into ROM manager and tried to apply my original backup I did when I was just Rooted and on the stock software from ATT.
It got to the data partion and couldnt access it, rebooted and now I get force close errors when it boots. I can virtually do nothing cause the errors just come one after another.
I tried to go into download mode so I could use ODIN and start over and it will NOT go in download mode. I am holding the vol up and down and then pressing power. I am holding all three until the screen goes black twice then letting go of the power. It just goes back to the little circle in the middle meaning its charging.
I am hosed....please help me get this fixed!
Click to expand...
Click to collapse
First of all, for God's sake please post on the RIGHT AREA. This is not develpoment....the mods are tired of saying the same thing and I dont see why is this so hard to understand.
Turn the phone off then Hold Vol Up and Down then plug the usb while holding those.
That is the way mine goes into download mode.

My bad, feel free to move it.
As I posted, I am doing that and cant get into download mode....please help and again sorry for posting to the wrong area. Im kinda freaking out.

Appologies again, I didnt read your post well.
I tried it the way you stated as well and it goes to the charging screen only.
When I post in the future I will pay more attention to where I post, I understand the frustration.

I cant go into recovery or download either one. Am I bricked? I could really, really use some help. I know I screwed it up and it was a great lession...I just dont want it to be a costly one.

1st question - were you able to get into either download mode or recovery mode via the button combos before you installed cognition?
2nd - if you let it boot up will it boot all the way to the lock screen?

1) Yes I was able to get into download mode and recovery mode before I screwed up.
2) Yes, I can get all the way to the lock screen and if i catch it just right I can navigate the os but it is almost impossible.
The backup from within ROM Manager I applied was back to the original OS that came on the phone that was rooted and had rom manager on it.
I would bet that whatever files allow you to get into download mode, etc are gone or something along those lines.
I am about to freak out.

have you tried pulling your battery, sim card, and any external sd card, let the phone set for a minute, then put back only the battery and then try either the recovery or download button combo?

I am able to get all the way to about phone and here is what it says. I have a combination of mess....man I screwed up royally.
Build Number
ECLAIR
Kernel Verson
2.6.29
[email protected] #237
BaseBand Version
I897UCJH7
Firmware Version
2.1 -Update 1
Again, I was on 2.1.2 Cognition and went through ROM manager and applied a backup which was a snapshot of my phone the day I got it, rooted it, and added ROM Manager. Which isnt there now.
I know what I did was really stupid, I know what I should have done. I would just really appreciate any help getting this back or getting it to a point that I could send it back and not get charged for it. I got it from amazon. Do you even think they would look at the file system? I am within my 30 day window.

Yes, it boots up normally meaning not into download or recovery mode. The specific errors I am getting in the os are as follows:
The process android.process.media has stopped unexpectedly and i have to click force close. I do get a few others about browser, phone, gallery, calendar, but in the end the media one is the one that comes up over and over. Since I can get this far surely there is a way to get me back to a workable state that I can fix it.
If not, I wonder if I could connect via usb and try to wipe every file off the darn thing and send it back? Obviously I would like to avoid that but I am running out of options and frankly this is over my head.

I dont think your trying the download mode correctly with the battery out. You need to take your battery out, put the battery back into the phone, hold down BOTH the volume up and down keys at the same time by pushing in the middle of the keys and then plug the usb into your phone. This works every time.

I can get into the phones Hard drive via USB and see the folders. I see .img files within clockwork that were suppose to have applied, not that it it matters.
I wonder if I could delete anything that isnt part of the stock image and send it back and just not be an idiot again? I really dont want to do that but I dont know what to do.

I found this log file on the device and the last line was the error that I got right before it rebooted and I was hosed:
Can't mount /data/!
Failure at line 2:
restore_rom /sdcard/clockworkmod/backup/original boot system data cache sd-ext

aNdroidnut I tried it exactly as described and all I get is the lines in a circle stating that its charging then the battery charging. I have tired it the way you said and the way I had done it all the other times.
I think the problem is i have an incomplete OS since it failed in the restore process within ROM Manager because I never should have done it that way.

If you were able to get into download via button combo before you should be able to do it now with after pulling your battery, sim card and external sd card as I mentioned before.
gocats7 said:
I can get into the phones Hard drive via USB and see the folders. I see .img files within clockwork that were suppose to have applied, not that it it matters.
I wonder if I could delete anything that isnt part of the stock image and send it back and just not be an idiot again? I really dont want to do that but I dont know what to do.
Click to expand...
Click to collapse
If you can get to this point you are not bricked and can recover. I am guessing you are connected to your computer in usb debuggin mode -- this is good as there is another way to get into download mode.
use oden3 one click here http://forum.xda-developers.com/showthread.php?t=731989
use download method one in the odin3 instructions if you can get connected to your computer in usb debugging mode. use download method 3 if you can get into download mode via the button combo after a battery pull

i think you failed at reading the warning:
disable the lagfix before trying to use clockwork

Are you trying this with Odin already open?
Sent from my SAMSUNG-SGH-I897 using XDA App

When I try what everybody else explains I too just go back to the loading circle. Then it just goes right back to my charging screen. I figured this method out by mere chance one night when tinkering. I haven't seen it posted anywhere, so hopefully this is what you need:
1) open odin
2) pull battery, sdcard, and sim card
3) plugin usb to phone and computer(NO BATTERY YET)
4) hold down vol up and vol down(NO POWER BUTTON)
5) place battery into the phone
This works every time for me no exceptions.
Hope this helps,
S4NDM4NN

OK, I have made progress thanks to the great tools these guys have and your help!
I am shaking as I type this (yea i know its just a phone). I was able via Odin to do a master clear. It rebooted and now I get into the OS and get NO errors. It seems fine but will not go into download mode no matter what I do and I have gone into it many times in the past. I went from stock (via Odin) to Cognition several times initially to really understand the process. I never had problems getting into download or recovery.
I really think, with you guys help, Im going to be ok here. I saw where you wanted me to do method 3. I have tried method 3 many times and method 2 many times.
Since I am able to get it to boot error free I was considering unrooting, rooting, downloading ROM Manager and trying to put Cognition 2.1.2 on it via Rom Manager. BUT before I do that I want advice if you would. Obviously following what I thought got me to this point to start with.

[Q]<< Solved!!>> Milestone stuck in bootloader screen, need help please

Dear all,
try to upgrade my milestone from 2.1 to 2.2 via the upgrade software from moto, the software finished without any error, but my milestone can load the system anymore, it stuck in the bootloader screen,
bootloader 90.73 battery ok, ok to program
it can detect the usb cable if I insert the usb cable, can I restore my milestone?

first do factory reset, cross fingers, and reboot
Crossing fingers is most important.
That actually happened to me when flashing telus froyo 2.2 update.
It flashed fine but stuck on M logo so did reset by doing left shift+alt+delete, held down X and factory reset option from recovery menu.
You may have to hold down camera instead of X

thanks for quick reply. Sorry, I never did rooting or flash rom, I don't know what is cross fingers, I trid factory reset by holding down the power button and camera button, but I still stuck in the bootloader screen.
Would you please point me to some useful tutorial, howto?

You can try to flash an sbf since you can get the bootloader.

First take the battery out.
then download rsdlite 4.6+
download motorola drivers
install them.
download a froyo sbf file from here---> //and-developers.com/sbf:milestone221 (put "http:" in front of the url)
put the battery in and go to the bootloder mode (in my phone bootloader 90.78 i need to hold the UP key on d-pad and the power botton together)
plug the phone to your computer.
turn on RSDlite and wait for it to show your phone as connected.
select "..." button and pick the sbf file you downloaded.
hit start and wait for it to say "pass" or something like that. DO NOT interrupt RSDlite once you have hit start.

Dear all, My bootloader version is 90.73, and I have some err code, but I'm manage to connect my phone with RSD lite, I read some forum mentioned bootloader version 90.78, would it be any different if I upgrade bootloader to 90.78, and how can I upgrade it by RSD?

I saw some forum talked about recovery mode, but I can't get into recovery mode by pressing camera and power button at the same time.

ROBINGAZI said:
First take the battery out.
then download rsdlite 4.6+
download motorola drivers
install them.
download a froyo sbf file from here---> //and-developers.com/sbf:milestone221 (put "http:" in front of the url)
put the battery in and go to the bootloder mode (in my phone bootloader 90.78 i need to hold the UP key on d-pad and the power botton together)
plug the phone to your computer.
turn on RSDlite and wait for it to show your phone as connected.
select "..." button and pick the sbf file you downloaded.
hit start and wait for it to say "pass" or something like that. DO NOT interrupt RSDlite once you have hit start.
Click to expand...
Click to collapse
Just try the SBF from UK, same, my phone boot with the bootloader screen:
Bootloader
90.73
Err: A5,69,35,00,27
Battery OK
Ok to Program
Connect USB
Data Cable.
Any idea?

dreamer1212 said:
Just try the SBF from UK, same, my phone boot with the bootloader screen:
Bootloader
90.73
Err: A5,69,35,00,27
Battery OK
Ok to Program
Connect USB
Data Cable.
Any idea?
Click to expand...
Click to collapse
in this state if you start the flashing with RSDlite does it flash?

the problem was solved after flash the bootloader to version 90.78, thanks everyone for reading and reply!!!

Boot loops can happen to anyone. It is always a good idea to have openrecovery working incase you need to restore your MM.
Sent from my Milestone using XDA App

Droid A855 bootloader 90.78
dreamer1212 said:
the problem was solved after flash the bootloader to version 90.78, thanks everyone for reading and reply!!!
Click to expand...
Click to collapse
Hello, may be anyone still have bootloader 90.78 for Droid A855?
I spend whole day searching it but all links dead.
Thanks

I guess your best chance is this site: http://sbf.droid-developers.org/phone.php?device=26

Erovia, Thanks friend! I really appreciate!:good::good::good:
I tried flash 2C7C.sbf bootloader file , flashed well but no success - bootloop on "M" logo.
9078 bootloader didn't want to flash (phone showed error), I think because this bootloader not for CDMA version (file name BL_9078_umts_sholes_HS_Consumer_replacer.sbf). Also I found the same file on German wiki server for their phones.
After multiple attempt to flash whole ROM like "VZW_A855_FRG83G_QSC6085BP_C_01.43.01P_SW_UPDATE.sbf" and FRG83D I started to think that probable phone has died NAND flash and better disassemble it for parts. RSD showed info from this phone
AP Die ID: 0390010d177d0304000000000400
BP Die ID: 0000000000000000000000000000
AP Public ID: ffffffffffffffffffffffffffffffffffffffff
BP Public ID: 0000000000000000000000000000000000000000
As far as I know ID there should be something but not ffffffffffffffffffff or 00000000000000.
I gave this phone last chance and flashed "MILER_X1_00.26.1_MILER_CDMA_BP_01.07.00R_GEN_1FF_sign.sbf" and miracle happens! In a few reboots it passed M logo and completely turned On. I guess it's not original Verizon firmware, on settings it says model A854 .
Now my question is can it be activated on Verizon? (I don't know will RPL Version (11111) work for them) Or I need to flash original A855 ROM ? Or left it as is and don't torture it more?..

I'd really like to help you, but I don't no much about the Droid, because I have a Milestone.
If I were you, I would torture it a bit more. It booted up, so the hardware is functional. With a little luck, it can be saved.

It was almost two months ago but whatever..
After multiple attempts to flash A855 rom I decided left it on A854 rom (MILER_X1_00.26.1_MILER_CDMA_BP_01.07.00R_GEN_1FF_sign)
All ROMs for A855 which I tried to flash
VZW_A855_FRG83D_QSC6085BP_C_01.43.01P_SW_UPDATE
VZW_A855_FRG83G_QSC6085BP_C_01.43.01P_SW_UPDATE_02
VZW_A855_FRK76_QSC6085BP_C_01.43.01P_SW_UPDATE_01
made phone non bootable.
A854 rom worked fine, only thing customer called after two day using it and said camera doesn't work. But as I never saw him again I have know idea is there was camera problem or it just doesn't work on A584 rom.