OK i've searched and read until my eyes crossed but even the most promising threads seem to peter out when people run out of ideas.
I'm clinging to the popular assertion that "if it boots it's not bricked", someone please help me prove it?
The trouble began when was i was starting over with the instructions here:
(Google - How To: Recover your G1 from a bring Bricked. - Project Hosting on Google Code, involving installation of RC29)
That's as far as i got. The flash seemed to go OK but then it booted to the white triangle with the exclamation point.
The only keys that work are ALT+L and ALT+S. I can't get an adb or fastboot connection. ALT+W doesn't do anything at all and it doesn't reboot from pressing Home+Back, i've got to remove the battery.
Message at the top of the recovery screen says "E:Can't open /cache/recovery/command.
Help?
Thanks
- joe
I don't think it is bricked as recovery is trying to run something ( and failing )
can you boot to the bootloader with power + cam?
what hboot version do you have?
is it 1.33.2005 ?
if it is have you got the newest adb drivers ( this is assuming you are using windows )
assuming the above is true, then get to fastboot mode with power + back ( or power + cam, then press back )
then try
Code:
fastboot erase cache
and try to get to recovery again ( reboot by pressing menu and then hold home )
if that doesn't work then supply the version numbers you get on the bootloader screen
it will help to workout what nbh files you can flash etc
also do you know what recovery version you have?
Effdee said:
can you boot to the bootloader with power + cam?
Click to expand...
Click to collapse
All i get from any button combination is the white triangle with the excalmation point and the dead phone, whatever all that is supposed to mean.
Effdee said:
what hboot version do you have?
is it 1.33.2005 ?
Click to expand...
Click to collapse
I'm sorry i don't know what that means. ALL i get is the triangle screen, i have to press ALT+L to toggle a log display with instructions for what the other button combinations (should) do. There are no numbers of any sort.
My drivers are all up to date and prior to this incident fastboot and adb both worked and i could tether my phone. But since i can't get a connection now and ALT+W (wipe) doesn't do anything, i seem to be limited to loading update.zips and watching the log as they fail to do anything helpful. Generally they fail (as, e.g., Ohsaka's Superwipe) with a "No Signature Verification Failed" or in the case of signed firmware updates, with a much longer and inscrutable error.
But thanks for the response, any advice or possibilities are appreciated.
- joe
passingthru said:
All i get from any button combination is the white triangle with the excalmation point and the dead phone, whatever all that is supposed to mean.
I'm sorry i don't know what that means. ALL i get is the triangle screen, i have to press ALT+L to toggle a log display with instructions for what the other button combinations (should) do. There are no numbers of any sort.
My drivers are all up to date and prior to this incident fastboot and adb both worked and i could tether my phone. But since i can't get a connection now and ALT+W (wipe) doesn't do anything, i seem to be limited to loading update.zips and watching the log as they fail to do anything helpful. Generally they fail (as, e.g., Ohsaka's Superwipe) with a "No Signature Verification Failed" or in the case of signed firmware updates, with a much longer and inscrutable error.
But thanks for the response, any advice or possibilities are appreciated.
- joe
Click to expand...
Click to collapse
so you are trying to flash custom zips with stock recovery?
you need to flash an official update ( with official signatures ) then you need to root and flash a custom recovery so that custom zips will work
http://forum.xda-developers.com/showthread.php?t=442480
flash the appropriate nbh as instucted
you didn't specifically say that powering on whilst holding the camera button doesn't work so I will assume that it does actually work
then follow
Rooting your RC29 or lower phone
using recovery.img from here http://forum.xda-developers.com/showthread.php?t=566669 )
that will give you RA1.7.0 , which you can then use to flash custom zips
but you will need to flash spl 1.33.2005 (danger), which is redundant , you want 2708 for extra 15mb which needs spl 1.33.0013d
http://forum.xda-developers.com/showthread.php?t=831139
read that post a few times, the bit you need is Flashing From a Stock SPL
( which will get you to this post http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76 )
make sure you read all of those links a few times so you understand everything you need to do before you try to do it
Its a learning curve , but it is easy once you understand it
I did get lots of help from a couple of guys in a pub, Mike and Wil , especially Wil who pointed me here ( xda ) and told me who to trust ( ezterry ) and who to just ignore ( pretty much everyone else )
Effdee said:
so you are trying to flash custom zips with stock recovery?
Click to expand...
Click to collapse
Well in my initial ignorance, yes i did try to do that but it didn't work. So i tried e.g. an official signed RC30, which failed with aforementioned inscrutable error. I can try again if the specific error is relevant, but i've tried it at least a half dozen times, with different downloads and verifying same and formatting my SD card FAT32 and only putting the update on it and then safely ejecting the card and ensuring that the file is named update.zip and not update.zip.zip and etc and so on. I've been reading a lot...
Effdee said:
you didn't specifically say that powering on whilst holding the camera button doesn't work so I will assume that it does actually work
Click to expand...
Click to collapse
I said "any" button combination gives me the same result, i.e. the screen with the triangle and exclamation point. So specifically, no the camera button doesn't work, it would be great if it did. I don't think the button itself is broke though, because it had to work in order to get me into this mess.
The link you gave is approximately the process i was attempting, (as a new user i'm not permitted to post links yet), and it was directly after flashing to RC29 that my phone booted to this triangle screen.
So like i said, i am pretty much limited to flashing update.zips since that's all that this interface provides apart from wiping, which doesn't do anything. I was hoping someone could point me to an official signed firmware upgrade (or downgrade or anything really) which would give me some sort of starting point. Or, something. Anything... i'm really in a pickle without my phone.
Thanks again,
- joe
EDIT: Just for the sake of curiosity, i see that Windows recognizes my phone as a storage device only with "no media" so i wonder if that's an ext3 partition, which makes me wonder if i could mount it with a Mac and wipe it so i could try the RC29 flash again. I know very little of *nix or Macs, i'm just going "hmmm".
Something...
I managed to install the CRB43 cupcake update, or anyway according to the console the process completed. I was hoping it would make all my buttons work so i could start over but it booted right to the triangle again.
At the end of the upgrade process it wants me to use Home+Back to reboot but that doesn't work so i have to remove the battery... could this be the problem and if so is there anything else i can do instead?
Thanks,
- joe
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
passingthru said:
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
Click to expand...
Click to collapse
If you are in recovery (Ie alt-L gives you some options) you are in theory not bricked)
Depending on what is installed powering on with power+camera, pawer+back, power+send (send seems only on the 2000 series dreams and only with some bootloaders) you can access fastboot and at the least use an nbh to restore a working system.
In some cases however there is a stuck home button forcing the booting of recovery and a stock recovery.. or an issue with the misc partition failing to cleae the boot mode.. In these cases booting fastboot is hard and something needs to be done with the hardware issue. in particular if you have a stock recovery w/o test keys.
Last if you are not in a recovery (stock or otherwise) and can't boot to recovery, system, or fastboot; and niether fastboot or adb works, you are "bricked" however if you power on while holding the trackball and see the led turn blue the jtag methods can restore your phone as long as all hardware buttons are operational.
Most of us (including myself) have not been stuck in recovery where rebooting holding camera didn't switch us to fastboot.
passingthru said:
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
Click to expand...
Click to collapse
you need a custom recovery, ( the triangle is stock recovery and is very limited )
to install a custom recovery you need root
to get root , read the links I gave
ezterry said:
...however if you power on while holding the trackball and see the led turn blue the jtag methods can restore your phone...
Click to expand...
Click to collapse
Thank you for that. I was panicked because i didn't have a phone but now i've gone out and got a shiny new HD2 and i have a G1 in my desk drawer, the JTAG thing looks like fun. I still want to resurrect my old phone because i still love it.
ezterry said:
...as long as all hardware buttons are operational.
Click to expand...
Click to collapse
Could a few drops of water, like from getting a little bit rained on, have permanently messed up my buttons?
Thanks much,
- joe
EDIT: Also, you said,
ezterry said:
...or an issue with the misc partition failing to cleae the boot mode..
Click to expand...
Click to collapse
If this were the case would i see an error to that effect in the recovery? I had hoped that "E:Can't open /cache/recovery/command" would be a major clue but all the Google returns on that error were people who could still access fastboot.
passingthru said:
If this were the case would i see an error to that effect in the recovery? I had hoped that "E:Can't open /cache/recovery/command" would be a major clue but all the Google returns on that error were people who could still access fastboot.
Click to expand...
Click to collapse
in the recovery log.. /tmp/recovery.log .. but if you have a stock recovery w/o test keys, or adb I'm not sure how to go about checking it. (without somehow getting a custom recovery installed)
misc is not cache.. so misc errors are not reported as cache errors.
ezterry said:
misc is not cache.. so misc errors are not reported as cache errors.
Click to expand...
Click to collapse
Understood, i was just trying to eliminate (or confirm) possible issues. So i wondered if the /misc error would be reported in the recovery console like my /cache error is, and/or if they might represent a similar sort of failure. Because you seemed to be classifying that (the misc error) as a hardware issue which would need dealt with apart from the JTAG procedure.
I was researching the process and it doesn't seem worth the money when i can get a broken G1 from eBay for $35, so maybe whether it's hardware or software, i'd be likelier to get it fixed by mixing and matching parts?
Thanks again.
- joe
Related
did the flash_image recovery /sdcard/cm-recovery-1.2.img part then my now my phone freezes every time i hit hold home and power does this mean i cant do updates or anything anymore
Did you thoroughly read before doing this? No issues here at all
Just reflash the recovery...
A frozen recovery is really really no brick.
g1201 said:
did the flash_image recovery /sdcard/cm-recovery-1.2.img part then my now my phone freezes every time i hit hold home and power does this mean i cant do updates or anything anymore
Click to expand...
Click to collapse
quickest fix, setup your system for ADB (if you haven't already). once done, copy cm-recovery-1.2.img to the root of your C:\, reboot your system to fastboot, run cmd prompt and type this:
Code:
PROMPT>fastboot flash recovery c:\cm-recovery-1.2.img
and reboot your phone
OP, would you mind re-naming this thread and not throwing the word "brick" around in such a cavalier manner?
op please read me
Ok, first you flashed the spl before you knew how to do it, so if you are truly bricked you did it not the spl, guns don't kill people, people killpeople with guns, see the metaphor?
But I think u should change the post title to: I jumped into the deep end before I learned to swim and now my phone is pooched, like somebody said don't bricked is a unrecoverable condition, and when you are flashing the spl,bootloader or recovery, you are messing with your failsafe, that you need to recover from a bad OS flash, so yes it is possible to brick your phone if you don't get a good flash, which is why all newcombers should take this story as a cautionary story, if you are new to writing flashes or just learning to "hack" htc devices, stick to OS and radio flashes only cause you always have your failsafe(bootloader or whatever u want to call it) to get things going again.
I've been "hacking"(4 lack of a better term) my phones and pda's for years, had my palm IIIx connected to the net wirelessly via a moto startac on sprints cdma in 1999 and I always read and reread everything I can find before I muck about with anything other than OS & Radio updates before I jump, look b4 u leap.
Even tho I'm guilty of flaming a bit, somebody should close this thread, if he is bricked there are threads for that already
Bhang
If you see any signs of life at all, it's not bricked
People who think they might have bricked thier phones may still be looking at this thread. If you get anything out of your phone at all, it's not bricked.
The last resort and fixall, afaik, is copy DREAIMG.nbh to your formatted to FAT32 sdcard.
Then go into bootloader mode by (from power off) holding down the camera key (until you're there) and powering up with the red power button. The nbh file should load automatically. Wait for this to finish, or you will brick your phone, likely.
One thing that's kind of confusing to newbies (anyone whos been avidly at this for less than a couple of months) is that there are three modes for your phone:
1. Bootloader (powering up with camera button held)
it runs/loads nbh files
2. Recovery (powering up with home button held)
it runs/loads update.zip files
3. The OS (just powering up)
I've only run img files from Telnet and Terminal Emulator (or the SDK adb.exe on my PC, but I don't mind the small keyboard)
If you have either Bootloader OR Recovery modes intact, you can recover the other, and the OS with either (the methods are different from each, though).
To many this will sound so insanely basic it shouldn't be posted. From what I've experienced on the WinMo fora, it will need to be posted over and over and over until someone stickies it so it can't be missed.
Please feel free to correct me on any of these points. HTH.
Denkai said:
quickest fix, setup your system for ADB (if you haven't already). once done, copy cm-recovery-1.2.img to the root of your C:\, reboot your system to fastboot, run cmd prompt and type this:
Code:
PROMPT>fastboot flash recovery c:\cm-recovery-1.2.img
and reboot your phone
Click to expand...
Click to collapse
thanx man im goin to do it now
Oh my god its all my fault!
cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
naw it aint ya fault i was jus so mad last nite but im not blaming you
i have 2 quest.
1. can u help me get it back 2 normal
2. how can i change this title
you can also re-flash the recovery rom through terminal.
that way you don't have to run into getting 'stuck' by pressing home + power button.
g1201 said:
naw it aint ya fault i was jus so mad last nite but im not blaming you
i have 2 quest.
1. can u help me get it back 2 normal
2. how can i change this title
Click to expand...
Click to collapse
edit your first post, go advance, edit....
mrcrs said:
you can also re-flash the recovery rom through terminal.
that way you don't have to run into getting 'stuck' by pressing home + power button.
Click to expand...
Click to collapse
thats the 1st thing i tried
the thing is when i 1st did it it went threw i got the lil # symbol so i thought every thing was good but i power off and pressed home and power thats when i got stuck
g1201 said:
thats the 1st thing i tried
the thing is when i 1st did it it went threw i got the lil # symbol so i thought every thing was good but i power off and pressed home and power thats when i got stuck
Click to expand...
Click to collapse
what i would suggest is after flashing the next command you input is: reboot
instead of manually powering it down.
mrcrs said:
what i would suggest is after flashing the next command you input is: reboot
instead of manually powering it down.
Click to expand...
Click to collapse
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
Of course it is your fault. You are a celebrity now.
g1201 said:
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
Click to expand...
Click to collapse
how about.. download the file again.. rename it recovery.img and run those same commands
flash_image recovery /sdcard/recovery.img
sounds dumb.. i know..
Cyanogen is a great Dev!
It worked perfect for me as well and I am a rookie
g1201 said:
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
Click to expand...
Click to collapse
you can not just type
Code:
$reboot
in the terminal. you have to
Code:
$su
#reboot
you have to have SuperUser privileges to reboot.
cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
It's your God damned fault I <3 my phone so much. Arse.
I rooted the nexus one as it said on the "theunlockr" web site
and the process went smoothly, the phone restarted and was working properly
next thing I wanted to add the Arabic scrpt to the phone
so I did as the "android-devs" web site said I should
and it went as it says it should
up to the point where I had to reboot, I did so
and since then the phone wont open beyond the G1 logo
I tried rooting again, but it says the phone is already Unlocked
I tried removing the files I pushed to the phone by using other Command Prompt orders such as DEL and PULL, but it didnt change anything
It goes on the Nexus one logo (the colored X) or the Android mascot with an exclamation mark in a triangle!
what to do? please help!
empty-ness said:
and since then the phone wont open beyond the G1 logoQUOTE]
erm... does it really say G1? do you mean the multicolored X?
Click to expand...
Click to collapse
yes, the four colored nexus one logo
Assuming you have installed a ROM such as Cyanogens, hold the volume down button in while the phone starts and choose recovery. In here wipe the phone then flash the .zip file again. As long as you can get into fastboot you should be fine
nDrg said:
Assuming you have installed a ROM such as Cyanogens, hold the volume down button in while the phone starts and choose recovery. In here wipe the phone then flash the .zip file again. As long as you can get into fastboot you should be fine
Click to expand...
Click to collapse
I did not install a ROM at all
I wrote down everything I did!
and im not familiar with the "flash the .zip file" process!
can you please explain?
I pressed the down volume button and the power button!
chose FASTBOOT and clicked RECOVERY
and restarts and shows the ANDROID MASCOT WITH AN EXCLAMATION MARK IN A TRIANGLE! and stays that way </3
should I install the ROM thingy or what? someone give me an idea please!
empty-ness said:
I pressed the down volume button and the power button!
chose FASTBOOT and clicked RECOVERY
and restarts and shows the ANDROID MASCOT WITH AN EXCLAMATION MARK IN A TRIANGLE! and stays that way </3
should I install the ROM thingy or what? someone give me an idea please!
Click to expand...
Click to collapse
You first need to fastboot flash a custom recovery, then you can use recovery to wipe and flash a custom ROM.
Yeah, the ! screen means you need to flash amon ra, do a search and you will find many a thread, start here, -----> http://forum.xda-developers.com/showthread.php?t=611829&highlight=amon+ra+recovery There are guides in the stickies on this section and several others available with a quick search. From there you can put a rom on the sd and flash it. Just relax, a little searching for instructions and you will be up and running.
I smell a "HELP I BRICKED MY N1!!" thread starting really soon......
Heads up man, DON'T FLASH RADIO IF YOU HAVE NEVER FLASHED A ROM!!!
Had to post, just feel bad for people that don't research first.....Good Luck
martin0285 said:
I smell a "HELP I BRICKED MY N1!!" thread starting really soon......
Heads up man, DON'T FLASH RADIO IF YOU HAVE NEVER FLASHED A ROM!!!
Had to post, just feel bad for people that don't research first.....Good Luck
Click to expand...
Click to collapse
How about, "don't mess with your phone if you're a noob and don't know what you're doing..."? The OP should have read a lot more about the process prior to trying to unlock and flash.
uansari1 said:
How about, "don't mess with your phone if you're a noob and don't know what you're doing..."? The OP should have read a lot more about the process prior to trying to unlock and flash.
Click to expand...
Click to collapse
+1.... Just hope he don't blame google and HTC when he bricks her!!
Arent you a bunch of helpfull joyfull ppl
yes im a noobie, all great pro ppl started as noobies!!
and no I will not NOT PLAY WITH MY NEXUS ONE, it is the reason I got one!
if you have advice for me, please share .. advice on how to fix the prob not how I could've avoided it .. in case you havent noticed it's unavoidable now!!
should I try to flash recovery image!?
Yes, you must flash the amon ra recovery. Read the available tutorials available up in the stickies in this section. The amon ra thread I linked to in my previous post also has instructions. Basically you want to download it and put the image in the same place as fastboot. Boot your phone into fastboot mode by powering on while holding the trackball. Connect your phone via usb. Open a command window in the same folder where fastboot was and where you just put the amon ra recovery image by holding shift and right clicking inside the folder and selecting open command window here from the resulting menu. Type or copy paste "fastboot flash recovery recovery-RA-nexus-v1.7.0.img" without the quotation marks. Again read some of the tutorials so you have a good idea of what you are trying to do, many of them walk you through step by step. Once you have done that you can move on to flashing a rom.
krabman said:
Yes, you must flash the amon ra recovery. Read the available tutorials available up in the stickies in this section. The amon ra thread I linked to in my previous post also has instructions. Basically you want to download it and put the image in the same place as fastboot. Boot your phone into fastboot mode by powering on while holding the trackball. Connect your phone via usb. Open a command window in the same folder where fastboot was and where you just put the amon ra recovery image by holding shift and right clicking inside the folder and selecting open command window here from the resulting menu. Type or copy paste "fastboot flash recovery recovery-RA-nexus-v1.7.0.img" without the quotation marks. Again read some of the tutorials so you have a good idea of what you are trying to do, many of them walk you through step by step. Once you have done that you can move on to flashing a rom.
Click to expand...
Click to collapse
Done it
worked wonderfully
thank you for the help <3
Ok, glad you got er done. Next time and there will be a next time if you continue to play with this stuff, relax. Its almost always something that can be fixed as long as you dont pull the battery during boot or a radio flash.
I usually don't get mad if someone post this for a 1st gen android device but when someone buys one of the BEST android phones on the market, did not do any research at all, then messes up their phone without them knowing what to do......that TICKS ME OFF.
UberMario said:
I usually don't get mad if someone post this for a 1st gen android device but when someone buys one of the BEST android phones on the market, did not do any research at all, then messes up their phone without them knowing what to do......that TICKS ME OFF.
Click to expand...
Click to collapse
and on top of that posts hearts in thier posts, androids have no love, they are androids
uansari1 said:
How about, "don't mess with your phone if you're a noob and don't know what you're doing..."? The OP should have read a lot more about the process prior to trying to unlock and flash.
Click to expand...
Click to collapse
2x .........
Would be nice if people would post these so called links they say are all over the forum would help people out if they decided not to search like most of us do and find this by just clicking the Nexus One Q&A
What is the Mac equivalent of opening a command window. I have to do this on a Mac.
Is there a file in the android system that, sort of like an autoexec.bat, lists what to do on startup? For example forcing the system into recovery or download on power on?
I flashed the latest Vibrant firmware and did so with the option to repartition, which Im now finding out was not the right way to flash this one.
Long story short, it didnt contain the dbdata directory information and now, I am unable to boot and unable to get to download. I still have ADB access, it just isnt responding to ADB reboot download, it just comes right back up booting into recovery to flash the last stage of odin before it starts up.
Is there a way to force the phone back into download mode or force it to stop rebooting into recovery?
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
OP said that he isn't able to boot so I believe he's stuck on the loadup to Android.
zephiK said:
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Click to expand...
Click to collapse
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Viralblack said:
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Click to expand...
Click to collapse
Try every step here: http://forum.xda-developers.com/showthread.php?t=771247
Have you successfully gotten into Download mode with hardware buttons before? Or are you one of those vibrants with "locked download?"
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Viralblack said:
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Click to expand...
Click to collapse
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
zephiK said:
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
Click to expand...
Click to collapse
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Viralblack said:
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Click to expand...
Click to collapse
Why did you change update.zip? Update.zip should always lead to Clockwork :|
zephiK said:
Why did you change update.zip? Update.zip should always lead to Clockwork :|
Click to expand...
Click to collapse
I didnt! But when I was formatting and it failed to reapply the nandroid completely cause of the section it couldnt mount, now when I hit reinstall packages it just reboots. Same with shell, it just yells at me and tells me to die in a fire.
if you didnt figure this out, the way to fix it is to first flash WITH ODIN the original JVD firmware and check repartition, then flash the new one IN ODIN without the repartition box checked.
first update includes the dbdata that the phone is looking for.
Yeah, I figured it out now, but Odin is seriously the devil if your phone doesnt have the hardware buttons enabled.
Now heres a question, if I can still get into stock recovery... is there a way to like, you know, recover using the stock system? lol
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Viralblack said:
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Click to expand...
Click to collapse
lol looks like you and I are in the same boat man. Hardware lock FTMFL. I have never been able to get into download mode, or recovery mode with the hardware keys, only with adb reboot recovery/download and terminal emulator app with SU privs. I wish there was a jumper we could reset to unlock it haha that'd be the s*# son. Good old pentium 133 in the palm of the hands, but no . Atleast they are taking care of the people who don't do things properly.
I did the same thing and ended up with the same problem, but i was able to get in into download mode. When i would plug it in it would try to boot into recovery after the battery screen i would use the keys to make it boot to download mode instead of recovery, it was a *****, but i got it, though idk if there is another way for people with locked down phones.
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
Hi p970ies,
EDIT: NEW problems, see last pages.
here is my story:
I was on IZS v1.1, when I decided to go into recovery and make a full-wipe for having a "fresh install" again. You know, the phone was laggy, I had to many apps etc. I pressed the on/off-button for 1-2 secs to reboot into recovery, then my phone turned off and restarted but just with a "bright" black screen, the display was on. I thought "something went wrong", pulled the battery out and put it back in again, started, but then same screen again.
A few months ago an easy "unbricking" method (I know, not really unbricking) was to flash Redy2006's touch-recovery and boot into it with his scripts. So I flashed it (I know it's dumb, because of the u-boot and v30 thing, Idk), same result.
After that, I grabbed smartflash and two .bin/.fls packs of 2 roms, went into that special mode (phone off, press vol+, plug in) but there was no "sign" (screen that shows that you are in that mode) like the other day, the screen kept being black, but on.
Nonetheless the flashing worked and the software said everything alright. I started the phone but same result, in addition that there was now this effect: When the battery is put in and/or the phone is charging, the screen changes from being on and off. I can't do anything, no restarting with buttons, no LG screen, nothing but on and off, on and off. Every few seconds.
Thank you, I hope you experts can help me. (Even when I have the phone 2 years now and I was a ROM-junkie since the first day )
Edit: Tried smartflash with another patched v20 ROM. Tried KDZ Updater, just errors. But now the phone seems to boot, but there's nothing on the display, just the 4 softkeys are fading in and out.
Tomatengelee said:
Hi p970ies,
here is my story:
I was on IZS v1.1, when I decided to go into recovery and make a full-wipe for having a "fresh install" again. You know, the phone was laggy, I had to many apps etc. I pressed the on/off-button for 1-2 secs to reboot into recovery, then my phone turned off and restarted but just with a "bright" black screen, the display was on. I thought "something went wrong", pulled the battery out and put it back in again, started, but then same screen again.
A few months ago an easy "unbricking" method (I know, not really unbricking) was to flash Redy2006's touch-recovery and boot into it with his scripts. So I flashed it (I know it's dumb, because of the u-boot and v30 thing, Idk), same result.
After that, I grabbed smartflash and two .bin/.fls packs of 2 roms, went into that special mode (phone off, press vol+, plug in) but there was no "sign" (screen that shows that you are in that mode) like the other day, the screen kept being black, but on.
Nonetheless the flashing worked and the software said everything alright. I started the phone but same result, in addition that there was now this effect: When the battery is put in and/or the phone is charging, the screen changes from being on and off. I can't do anything, no restarting with buttons, no LG screen, nothing but on and off, on and off. Every few seconds.
Thank you, I hope you experts can help me. (Even when I have the phone 2 years now and I was a ROM-junkie since the first day )
Edit: Tried smartflash with another patched v20 ROM. Tried KDZ Updater, just errors. But now the phone seems to boot, but there's nothing on the display, just the 4 softkeys are fading in and out.
Click to expand...
Click to collapse
Oh man, its sad to hear that.
I can just think on two situations.
One is a broken screen, but thats pretty obvious.
And the other is a broken boot partition. Its very strange that you cant get into software upgrade mode. You sure you removed SIM, battery and SD, and then plugged it to the cable while holding the volume buttons?
I dont doubt you did it well, just making sure. Anyways AFAIK you should be able to enter that mode unless you got a broken boot partition.
Best of luck, sorry Im not of much help.
Grakel said:
Oh man, its sad to hear that.
I can just think on two situations.
One is a broken screen, but thats pretty obvious.
And the other is a broken boot partition. Its very strange that you cant get into software upgrade mode. You sure you removed SIM, battery and SD, and then plugged it to the cable while holding the volume buttons?
I dont doubt you did it well, just making sure. Anyways AFAIK you should be able to enter that mode unless you got a broken boot partition.
Best of luck, sorry Im not of much help.
Click to expand...
Click to collapse
Hi, thank you for your answer.
Yesterday oder so, I connected my phone without SIM, SD and battery while pressing vol+ to my pc and it showed the S/W-Update "Wait while update is in progress" or something. I was happy because the display isn't broken. But then I flashed again and the display is as black as before...
I thought about a broken bootloader. Do you guys know a way to fix it? Or the boot partition?
Tomatengelee said:
Hi, thank you for your answer.
Yesterday oder so, I connected my phone without SIM, SD and battery while pressing vol+ to my pc and it showed the S/W-Update "Wait while update is in progress" or something. I was happy because the display isn't broken. But then I flashed again and the display is as black as before...
I thought about a broken bootloader. Do you guys know a way to fix it? Or the boot partition?
Click to expand...
Click to collapse
Im pretty sure that if you can see the software update mode, you can unbrick the device.
When you said you reflashed something, do you actually mean that you smartflashed the fls and bin files from a stock v20 rom? AFAIK the bin file carries a bootloader with it so it should get fixed if your problem is the bootloader.
And by the way, while the phone has that black screen and is stuck booting... Are you able to use adb commands? You could try to jump to the recovery with "adb reboot recovery" to see if you got a working recovery.
Best of luck, tell me how it goes
Grakel said:
Im pretty sure that if you can see the software update mode, you can unbrick the device.
When you said you reflashed something, do you actually mean that you smartflashed the fls and bin files from a stock v20 rom? AFAIK the bin file carries a bootloader with it so it should get fixed if your problem is the bootloader.
And by the way, while the phone has that black screen and is stuck booting... Are you able to use adb commands? You could try to jump to the recovery with "adb reboot recovery" to see if you got a working recovery.
Best of luck, tell me how it goes
Click to expand...
Click to collapse
yep, I tried every version (10, 20, 30) in bin/fls and kdz. But I never got the screen to show something again.
And no, I can't use adb commands, sadly. It says "cannot find device" or something like that.
Tomatengelee said:
yep, I tried every version (10, 20, 30) in bin/fls and kdz. But I never got the screen to show something again.
And no, I can't use adb commands, sadly. It says "cannot find device" or something like that.
Click to expand...
Click to collapse
Huhmmm... Quite strange.
You can try to open up device manager, look for the phone (will probably have no drivers and the icon will have a yellow triangle) and force installing adb drivers. After that you are supposed to use adb even in middle of a boot.
I'd say that your best chance is to get to your recovery, so you can wipe everything (even formatting system) and start from scratch...
Anyways Im no expert at all... Just trying to help.
Grakel said:
Huhmmm... Quite strange.
You can try to open up device manager, look for the phone (will probably have no drivers and the icon will have a yellow triangle) and force installing adb drivers. After that you are supposed to use adb even in middle of a boot.
I'd say that your best chance is to get to your recovery, so you can wipe everything (even formatting system) and start from scratch...
Anyways Im no expert at all... Just trying to help.
Click to expand...
Click to collapse
Sometimes ADB works, but it says "device offline". When I flashed PRE-IZS fls/bin from the spanish forum, and then V30B bin/fls, something really weird happens: The phone is on, the wake-button works well - it turns on and turns off the display and the softkeys. But the screen doesn't show anything - just black.
Hello there!
Did You try out the B2C tool provided by LG? And there is one other tool provided by LG. Just try these oit. If they dont work, then try claiming it under warranty. They might replace the motherboard.
P.S: If You have the money, sell this piece of **** and get a Sony or Samsung. Cheers!
Sent from my LG-P970 using xda app-developers app
rokr05 said:
Hello there!
Did You try out the B2C tool provided by LG? And there is one other tool provided by LG. Just try these oit. If they dont work, then try claiming it under warranty. They might replace the motherboard.
P.S: If You have the money, sell this piece of **** and get a Sony or Samsung. Cheers!
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to buy a Nexus 4, but I have to convince my parents
Oh and yes, phone is older than 2 years and in Germany we only have 2 years of warranty I think.
Tomatengelee said:
Sometimes ADB works, but it says "device offline". When I flashed PRE-IZS fls/bin from the spanish forum, and then V30B bin/fls, something really weird happens: The phone is on, the wake-button works well - it turns on and turns off the display and the softkeys. But the screen doesn't show anything - just black.
Click to expand...
Click to collapse
An easy, possible fix for The Device offline is to use the latest ADB. Just use the attached zip anywhere and use ADB, its the latest version from the android SDK, but just the files required for ADB. My nexus 4 had the same problem, but Solved it by updating ADB.
ykumar00 said:
An easy, possible fix for The Device offline is to use the latest ADB. Just use the attached zip anywhere and use ADB, its the latest version from the android SDK, but just the files required for ADB. My nexus 4 had the same problem, but Solved it by updating ADB.
Click to expand...
Click to collapse
damn it says "error: device not found" when in S/W or bootloop... or device offline in bootloop
any ideas?
did you try patched bins ? (for being able to boot into recovery right after the flash process, maybe you just need right wipes)
#700th post yay...
Ilko said:
did you try patched bins ? (for being able to boot into recovery right after the flash process, maybe you just need right wipes)
#700th post yay...
Click to expand...
Click to collapse
Yes, I did, but Smartflash works "less" than the KDZ-Updater. Actually the phone beeped today while it was on (with some kdz flashed) :silly:
Is it possible to convert patched bin/fls files to kdz?
I don't know, probably not... what I can say is that kdzu doesn't perform full wipes since it's intended to update the system and keep datas at the same time. You probably need wipes...
Ilko said:
I don't know, probably not... what I can say is that kdzu doesn't perform full wipes since it's intended to update the system and keep datas at the same time. You probably need wipes...
Click to expand...
Click to collapse
Oh ok... But with KDZ-Updater, it's possible to turn the phone off and on (screens is "on" but shows the color black while the softkeys are on too).
I'll try again with Smartflash... Do you know another version of it or a good tutorial? Maybe I've done the wrong method or something...
there are several tuts in this forum. smartflash is the quickest and safest way to restore / unbrick as it erases everything in the internal memory
Ilko said:
there are several tuts in this forum. smartflash is the quickest and safest way to restore / unbrick as it erases everything in the internal memory
Click to expand...
Click to collapse
I know, but it never works. That problem is so weird! :silly:
Man, nothing works... After smartflashing display flashing off and on again, after kdz display on, softkeys flashing
ADB side service is not active while in S/W mode. The only chance to access to recovery is to boot normally, and access to the device via ADB. The problems are : device needs to pass initial boot process for being able to be detected by ADB (even if you don't see the desktop it's ok), and USB debug must be enabled by default...
so, if you can't pass initial boot process, no chance to use ADB, and, if it passes, usb debug must be enabled or device will remain offline...
Ilko said:
ADB side service is not active while in S/W mode. The only chance to access to recovery is to boot normally, and access to the device via ADB. The problems are : device needs to pass initial boot process for being able to be detected by ADB (even if you don't see the desktop it's ok), and USB debug must be enabled by default...
so, if you can't pass initial boot process, no chance to use ADB, and, if it passes, usb debug must be enabled or device will remain offline...
Click to expand...
Click to collapse
Is there a chance to enable it manually?
the only chance is to flash a ROM which have it enabled by default for the most of them.
mine died because of the new twrp 2.6. It has definitively corrupted the boot partition as even smartflash can't ends its process. I had to buy another device...