Database Develop

Stuck at Boot up Help?? plz!

ok so last night i decided to root my HTC HERO SPRINT..
so i put on this dialer and task bard and what not cool worked fine( its by Godzson) now i tryed doing other stuff like the main screen start up and stuff nothing seem to work..I downloaded this Nexus 1 start up
its colors going into eachother into a X so that was cool
then i put a theme on my SDCARD to see if worked it booted it up working fine then all of a sudden phone was being weird and it loads the nexus thing but nothing else
it freezes with the nexus thing someitmes but im stuck at boot up! help
i tryed a wipe and recovery to factory settings now im stuck..im stuck at this X thing..help!!!
im phoneless..

AndroidFAN101 said:
ok so last night i decided to root my HTC HERO SPRINT..
so i put on this dialer and task bard and what not cool worked fine( its by Godzson) now i tryed doing other stuff like the main screen start up and stuff nothing seem to work..I downloaded this Nexus 1 start up
its colors going into eachother into a X so that was cool
then i put a theme on my SDCARD to see if worked it booted it up working fine then all of a sudden phone was being weird and it loads the nexus thing but nothing else
it freezes with the nexus thing someitmes but im stuck at boot up! help
i tryed a wipe and recovery to factory settings now im stuck..im stuck at this X thing..help!!!
im phoneless..
Click to expand...
Click to collapse
Restore from the nandroid I'm SURE you made before you started messing with things.
If you for some reason didn't do a nandroid backup then wipe data/factory, dalvik cache, and SD:Ext if you have apps2sd installed.

my dumbass didnt do the nandroid :/
i did this already i restarted phone and that gay ass Nexus X with the colors still comes on and stays like that sometimes the colors would freeze but it would fix itself and keep moving
im totally F'd..

Easy fix - you will start from scratch (like a brand new phone)
- Go to http://www.geekfor.me
- Download the 1.56.xxxx RUU onto your PC (not Mac)
- Double click RUU file and let it extract 9you may have to click 'OK' or 'Extract All' - It will create a folder of stuff - dont click anything yet...
- Power off your phone (remove battery and put back in if needed) and hold volume-up while it boots. You should see a white screen with text on it.
- Plug it in to your PC now via USB
- Back in that folder you just extracted double click the HTC logo icon (i forget the name) to start the process. It'll flash your phone to stock.

scirio said:
Easy fix - you will start from scratch (like a brand new phone)
- Go to http://www.geekfor.me
- Download the 1.56.xxxx RUU onto your PC (not Mac)
- Double click RUU file and let it extract 9you may have to click 'OK' or 'Extract All' - It will create a folder of stuff - dont click anything yet...
- Power off your phone (remove battery and put back in if needed) and hold volume-up while it boots. You should see a white screen with text on it.
- Plug it in to your PC now via USB
- Back in that folder you just extracted double click the HTC logo icon (i forget the name) to start the process. It'll flash your phone to stock.
Click to expand...
Click to collapse
BEFORE you try that...because it has problems for some people:
Did you:
A. Wipe data/factory reset
AND
B. Wipe Dalvik-Cache?

Alright cool thanks ill try this..
if you guys dont know what the hell im talking about i can probably hook up this webcam i have and make a video lol

Yes i did.

Well lame..it says my battery is not charged up past 30 percent..ima have it charge for a little bit and see what will happen
wish me luck!

Good luck. I've RUU'd 3 times without issue and it was dead simple.

some people have problems with ruu and some don't. I would get back to recovery, enable sd card (forgot which option it is), and put a downloaded ROM onto the sdcard. wipe everything and then flash the ROM. sounds like you might have tried flashing something for 2.1 if you have 1.5 or the otherway around. Flashing the ROM should work.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

AndroidFAN101 said:
my dumbass didnt do the nandroid :/
Click to expand...
Click to collapse
Didn't someone tell you in the other thread you started to do a nandroid backup before you do anything?
Oh yeah... here it is
Jus10o said:
Very first thing you should do is.. Turn off phone.
Hold down home + power button.. Scroll down to backup/restore.
Then do a nano backup... Not the one with ext.
Then boot your phone back up and open up your sdcard on your comp and go to nandroid/file inside it/ then copy that file to your computer. Always keep it safe.
Click to expand...
Click to collapse
I hope you learned your lesson and will do backups.
Another lesson you do not want to learn the hard way is what ROMs you can put on your phone. In case you didn't I read what I wrote in your other thread I will restate... BE CAREFUL WHAT ROMS YOU PUT ON YOUR PHONE!!! There are GSM ROMs which will completely fry your phone and you will not be able to recover. Also, if you put any other phone model ROM on your phone it will be toast.

centran said:
Didn't someone tell you in the other thread you started to do a nandroid backup before you do anything?
Oh yeah... here it is
Originally Posted by Jus10o
Very first thing you should do is.. Turn off phone.
Hold down home + power button.. Scroll down to backup/restore.
Then do a nano backup... Not the one with ext.
Then boot your phone back up and open up your sdcard on your comp and go to nandroid/file inside it/ then copy that file to your computer. Always keep it safe.
Click to expand...
Click to collapse
I hope you learned your lesson and will do backups.
Another lesson you do not want to learn the hard way is what ROMs you can put on your phone. In case you didn't I read what I wrote in your other thread I will restate... BE CAREFUL WHAT ROMS YOU PUT ON YOUR PHONE!!! There are GSM ROMs which will completely fry your phone and you will not be able to recover. Also, if you put any other phone model ROM on your phone it will be toast.
Click to expand...
Click to collapse
I didn't even realize that other thread was from him too. I also told him to nandroid and not to download anything for gsm.
Don't start a thread and not read everything posted in it, especially when you are asking for help.
I did my Rooting the long way through adb, so I don't know how Fresh Kitchen works on that end, but maybe he should say right after rooting to do a nandroid. I have my first nandroid on one of my backup sd cards, my computer, and on my current sd card. I'll be damned if I delete all 3.

[Q] Triangle of Death, Revisited

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

I'm stupid: [Q] convert data partition not enough space on partition

Hey Everyone,
I have made my phone unhappy. That's ok ... I / we will get it sorted...
Was stock captivate and I did the one touch thing to it when I got it (December). And I'm all wanting to get Cognition on it... So I read a little and I see that I can use ClockWork to install it. I download cognition to my phone from http://cognition.designgears.com/
ClockWork does its magic ... Cognition boots ... and ... boots ... and is saying stuff.
Eventually I figured out it is saying "convert data partition not enough space on partition" and it restarts ... and says it ... wash, rinse, repeat. It's stuck in this loop and I need to find the proper steps to fix it.
I've got Windows 7 on a couple computers ... and I've got the usb cable ... and downloading tools. Looking for the google adb tools now.
Would someone please reply with a summary of the steps I need to do to get a working phone again? Hopefully with Cognition??
Thanks and sorry for being stupid...
Chris

Yaaay....
I did this: http://forum.xda-developers.com/showthread.php?t=831453
And I can get into my phone! Yaaay. OK, so now to try and get cognition on I guess.

[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

How do I root manually?

Hello everyone!
I'm a new member from today but I have read (and read and read...) the threads here and on every forum I could find, in desperate search for an answer to my questions, but so far I have found none.
Don't shop my head of now but could someone please be so kind and help me root my LG Optimus 2x by giving me a step-by-step info AND include the correct files AND then tell me what to do to have them installed?
There seem to be all too many different alternatives and I am really confused!
Here's what I've done so far -
I had Gingerbread installed and got the phone rooted with SuperOnecClick.
Upgraded then the phone to Ice Cream Sandwish 4.0.4 with LG Support Tool and lost root.
Tried to root with SuperOneClick again but constantly got stuck at # 5 or # 7 (waiting for device).​
So, how do I root and where do I find the correct firmware for this?
Android
4.0.4
Bandwithversion
1035.21_20121130
Kernel-version
2.6.39.4
Version
IMM76L.LG-P990-P99030a.1211302332
Software
P99030a
Android SDK
Superuser (not rooted)
SuperOneClick

Hi there,
Since you upgraded to official ICS, you can't use SuperOneClick to get root access again, but fear not as there are alternatives. Here you will find three different methods to root your device. In your case, I believe you need to use either the second or third option listed there.
Be aware that the third option will wipe your device, including your internal SD card, so it'd be a good idea to backup first, just in case. All three methods are harmless, but you never know.

Thank you for your reply! Now I'm on and a step closer in fixing this.
So, my phone cannot be rooted because of Official ICS?! Oh!
- that was new news to me and it could have saved me countless of hours if I had found that information out sooner. A pity I did not write here weeks ago!
I have some more questions though and I think I'm going for the 2nd option in the link you gave me.
"Put your phone into nvflash mode". Do I need a tool for that? (Here I was linking to a nvflash-setup, but as I am a new memeber I am not allowed to post outside links yet). Or do I just hold down volyme + power in order to get into that nvflash mode?
By "unzipping attached archive" I assume it means zipping it on the PC and not on the SD card?
When doing this procedure, do I have the phone in Charging or Mass storage mode?
Just a few questions I hope you (someone) have to time to give me an answer to - Thank you!

MissLight said:
So, my phone cannot be rooted because of Official ICS?! Oh!
- that was new news to me and it could have saved me countless of hours if I had found that information out sooner. A pity I did not write here weeks ago!
Click to expand...
Click to collapse
You can get it rooted, only not with SuperOneClick ^^
MissLight said:
"Put your phone into nvflash mode". Do I need a tool for that? (Here I was linking to a nvflash-setup, but as I am a new memeber I am not allowed to post outside links yet). Or do I just hold down volyme + power in order to get into that nvflash mode?
Click to expand...
Click to collapse
To enter nvflash mode turn off your device, remove the battery, then press and hold Vol- and Power at the same time and plug your phone to your PC via USB. Then follow the rest of the instructions.
MissLight said:
By "unzipping attached archive" I assume it means zipping it on the PC and not on the SD card?
Click to expand...
Click to collapse
Yep ^^ you need to extract the files from the zip to your PC.

Ok, next question :
"boot into cwm and flash SuperSU Root.zip"
How am I suppose to flash anything when the telephone is black and I'm not into it and only work from the computer?
How do I do that?
I'm stuck with a black screen only on the phone.
I heared nothing or saw nothing that sais (sound) that the phone is connected through the USB, but I have followed each step and are now stuck at above question.
Greatful for more help!

MissLight said:
Hm. I have now read more closely on the linked site. Why am I to download ICS again, I already have the same ROM?
Or do you mean I have to change the official ROM to this one in order to root properly?
Click to expand...
Click to collapse
No, there's no need to reflash ICS. The second method listed there just flashes the unlocked bootloader + root + custom CWM, and it won't touch your data & settings.
MissLight said:
I tried Volume down + Power without battery. Nothing happened, the phone was stonedead even when plugged in with USB.
Click to expand...
Click to collapse
That's OK. When in nvflash mode, you won't see anything on screen. All you'll get is the sound it makes when connected to USB.
Don't worry, you're nearly there! Keep going!
Edit: just realized I made one small mistake. To enter nvflash mode, you need to press and hold both Vol+ & Vol- at the same time (this also requires removing the battery first). Sorry about that!

Edit: just realized I made one small mistake. To enter nvflash mode, you need to press and hold both Vol+ & Vol- at the same time (this also requires removing the battery first). Sorry about that!
Oh! That explains why. My next question was published above your question and still remains.
How do I "boot into cwm and flash SuperSU Root.zip"?
Edit : This procedure does somehow not work on XP so I changed to Windows7 and have now come a bit further. The only thing remaining now is that the computer sais that it cannot find the USB device.
I have downloaded the LG modem and USB firmware but maybe I need something else? Does the firmware in a folder on C: just as NvFlash and SU-folder.

Got OK with USB firmware and all set to go now.
But, in NVFlash Recovery it sais :
Please pick bootloader, or exit (1,X)? (I pressed 1)
Attempting to flash bootloader...
Nvflash started
USB device not found
Program will now exit​
So, I'm stuck.
The phone can be found both in Mass Storage mode and I got a OK that the drivers are installed.

MissLight said:
Got OK with USB firmware and all set to go now.
But, in NVFlash Recovery it sais :
Please pick bootloader, or exit (1,X)? (I pressed 1)
Attempting to flash bootloader...
Nvflash started
USB device not found
Program will now exit​
So, I'm stuck.
The phone can be found both in Mass Storage mode and I got a OK that the drivers are installed.
Click to expand...
Click to collapse
Alright, it sounds like you still need the APX drivers. I believe you can find it somewhere on the Development forum (find tonyp's threads, I'm sure he has posted it there). If you already did this, then remember to hold and press both Vol buttons when selecting option 1 so Nvflash can connect to your device and do all the magic.
Don't give up yet, you're a few seconds away from rooting your device (and learning stuff at the same time ^^).

Tried exactly as you said but still no luck. But I'm not giving up!
I found a APX driver. Installed and unziped in the same file as NvFlash. Rebooted PC and tried again.
Still no luck - "USB device not found".
What am I doing wrong?
BEFORE removing the battery from mobile, shall I have Mass Storage or Charging marked?
Do I need to have USB Debugging marked or not?

Latest Update :
I managed to install Nvidia usb boot recovery in the device manager and it's OK.
The device is now found and I got the phone into S/W Upgrade please wait while upgrading-mode.
And there I am - stuck. Nothing more happens. It has freeze.
What do I do next?
A question : How do I "boot into cwm and flash SuperSU Root.zip" - how do I do that?

Nice! Has nvflash finished flashing? If so, it should be safe to unplug the device now.
Put the battery back on, press and hold both Power and Vol- at the same time until the second LG logo appears to enter CWM. From there, select "Install zip from SD card" (or something similar) and select the SU zip file you previously stored onto your sdcard. CWM will then flash the necessary files to root your device! Once done, reboot and enjoy!

Hi again! It's not going as well unfortunately. Very mysterious. *laugh*
"until the second LG logo appears to enter CWM. From there, select "Install zip from SD card"
When pressing Volyme - + Volyme up + Power I get a black screen. Nothing more happens.
And after flashing the flash-boot in NvFlash the phone goes into s/w upgrade please wait while upgrading-mode.
And there it is. Stuck. Nothing more happens. I repeted the procedure for 5 times. I only get to the s/w-mode.
After 3 hours I unplugged it and will restart my search today for what's blocking it to continue.
Hm? Hmmmm....? Any suggestions in what might be wrong?

You have to push and hold only Vol- and Power this time ^^ That will get you into CWM if the flash-boot.bat went right.

Great, I'm in!
But I managed to place the SU zip on wrong device (internal, not external).
How do I get out from cwm-mode, there's no "exit" options?

There should be a Reboot option, use it and your phone will boot as usual. When you're done moving the SU zip file to the external SD card, power off your 2X and do as instructed above to enter CWM again ^^

Thank you for replying so quickly!!!!!
There is a reboot option BUT I unfortunately pressed adb sideload (hoping to install the SU.zip that way, but the device is not to be found on the PC at all in that mode so I can't reach it through cmd either!).
So, I'm completely STUCK at adb sideolad-mode.... (sorry). I'm starting to get grey hair.

Hahahah XD don't worry, just remove the battery and put it back again ^^

*BIG SMILE* Guess what? I have root access! *jumping up and down of joy*
THANK YOU! THANK YOU! THANK YOU so very much for your guidance!
I believe in passing knowledge forward and I will do my best to help others noobs with what you just learned me!​
For a stubborn noob like me I was not reflecting over some obvious things though. As that the SU.zip had to be placed on SD-card (and not being unzipped in C: )
And that I had to get the Nvidia APX in order to make NvFlash to work properly (and search through Google to find it and how to make it work).
And that when I'm stuck in CWM I can always remove the battery.
Once again. I'm very glad and THANK you and all credit to You!

You know, I decided to help you because of your will to learn and do stuff by yourself. Many come here and ask for help without trying anything by themselves first, so I actually enjoyed watching you learn ^^
See? It wasn't that hard. All it takes is a lot of reading and patience.
Good job, and welcome to XDA!