id a nandroid backup then factory reset, then flashed this recovery image off of htc.com http://developer.htc.com/google-io-device.html#s3, then i flashed cyanogens rom then did a restore
thats what i did and i restarted then it started acting up
it has a picture of the image in the background of amon ra's recovery image and it won't go to recovery image, flashboot mode, or turn on. it doesnt even go to the screen that says mytouch 3g, it goes straight to the image. PLEASE HELP! Thank you
Yep, You bricked it.
I did the same when I first got my phone. I flashed the wrong radio (I mis-read the image name) and killed my phone. You can't get past what your talking about to reflash anything else.
You need a new phone.
i fixed thx anyways
i let it sit there 4 a while and it went back to the recovery image and its all better now thanks for replying
Related
Hello, I just messed my phone up and I want to go back to stock 2.3.2 or earlier.
I have just the stock recovery, it was rooted with clockworkmod but I tried installing stock 2.3.2 and it it removed everything and is not bootign up. I'm stock on the triangle sign with the android figure/sign/robot on.
Please help me get back to stock, I dont need root or anything, just original just like I got the phone brand new in box.
It would be so helpful!
Just a quick bump because I need to use the phone urgently within few hours, please if any1 has a solution please post. I'll even offer u something.
thanks and sorry for being inpatient
just download and restore the nandroid stock backups on the DEV section
another alternative is to use Odin, but some people are not fond of it
tempera said:
Hello, I just messed my phone up and I want to go back to stock 2.3.2 or earlier.
I have just the stock recovery, it was rooted with clockworkmod but I tried installing stock 2.3.2 and it it removed everything and is not bootign up. I'm stock on the triangle sign with the android figure/sign/robot on.
Please help me get back to stock, I dont need root or anything, just original just like I got the phone brand new in box.
It would be so helpful!
Click to expand...
Click to collapse
The android with an "!" is the stock recovery. You get into it by pushing/holding power first, then volume up...just the opposite of how you got into fastboot mode.
Does that work for you?
distortedloop said:
The android with an "!" is the stock recovery. You get into it by pushing/holding power first, then volume up...just the opposite of how you got into fastboot mode.
Does that work for you?
Click to expand...
Click to collapse
Yes, but nandroid backups dont work with stock recovery?
If you were running < 2.3.3 bootloader, ie 2.3~2.3.2
Download clockworkmod recovery image, boot into fastboot mode, boot the image, do a nandroid restore.
Code:
fastboot boot recovery.img
tempera said:
Yes, but nandroid backups dont work with stock recovery?
Click to expand...
Click to collapse
No they don't, but you said you were stuck at that screen like it was a broken phone.
From stock recovery you can wipe the phone with a factory reset, wipe the cache also and see if you can boot.
Is your bootloader UNlocked? Are you on 2.3.3. or 2.3.2.
If on 2.3.2 bootloader, or on 2.3.3 with unlocked bootloader, just flash or boot clocwork via fastboot as suggested by the post above this one.
You can always do the fastboot oem unlock command on the phone, this will wipe the whol
Hey everyone,
I got a Nexus S that gets stuck on the Google logo when it starts up. I can get the phone into the bootloader and I can also clear the data from the phone but that hasn't fixed it. If you have any suggestions, please respond to the thread. Thank you!
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
brenix said:
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
Click to expand...
Click to collapse
Yah, i just did it and it didnt solve my problem but thanks for the suggestions
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
lostgoatX7 said:
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
Click to expand...
Click to collapse
No but the person I purchased it from might have. Does anyone know how to load stock android becuase I'm not experienced with rooting.
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
any solution?
hi guys.i have the same issue.does anyone have a solution for this?
i had the same problem.....what i did was cleared everything on recovery and flashed cyanogenmod and now is all good (this was of course after changing my underwear lol )
Smokexz said:
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
Click to expand...
Click to collapse
how can I do it?
I got the same problem.
Nexus S stuck at Google lOgo
I have the same Issue
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....
Similar problem
Ahoy!
I have a similar problem. Bought the phone in the States so I'm not in a position to go into psychological warfare with some poor high school kid working in Best Buy. Plus, all this is totally my fault...
I dropped my phone down the can (if it was a Blackberry I would have flushed) and manged to rescue it through handy desiccant (open shoe box gel packets) and rediscovering religion *cough* until this is sorted *cough*.
When I eventually fired her back up (the battery had flatlined btw) I'm stuck on the Google screen. So battle commenced...
The phone was stock 2.3.4, never rooted, no CW Recovery.
T-Mobile I9020T.
I sorted the Win 7 USB device issue
Can see it with fastboot but not adb.
Can access the bootloader screen so tried the Recovery option but it just goes into Google splash screen each time.
Flashed various versions of CW recovery (herring, mecha) to it but hitting the Recovery menu on the bootloader screen just keeps going to the Google splash screen.
This is where I complicated things because I'm a complete and utter noob to the rooting game.
I'm fairly sure I was careless early on with the appropriate versions of the full stock and singular recovery images I was trying to flash, so this might be useful information.
I downloaded ODIN and tried it briefly but it didn't seem to recognise my phone (I keep reading the ODIN needs to be tricked into recognising the phone). I also keep reading the ODIN is unnecessary if you have fastboot access so let this line of inquiry slide.
I downloaded a full Clockwork Mod Stock Nandroid (Stock-GRH78-Nandroid) and attempted to flash it all. The boot img failed due to a "FAILED exceed blocks" problem, so I tried this (classic noob try anything):
"Got a failure when trying to flash back a 8Mb boot.img?
From example above I started from a boot.img smaller than the full boot partition but if you create a new boot.img or start from an image of the full partition taken manually or with clockworkmod, boot.img will be 8Mb-large (8388608) and fastboot fails with "FAILED exceed blocks 0x00000020 > 0x0000001e".
I'm not really sure about what size the file should be but as it's filled with zeroes till reaching 8Mb, I decided to cut it:
0x00000020 => 0x0000001e means for me 8388608 / 0x20 * 0x1e = 7864320, so I did:
dd if=boot.img of=boot2.img bs=262144 count=30
fastboot flash boot boot2.img"
Click to expand...
Click to collapse
This worked! noob W1NNAR!!!11one111!!
I got the same thing with the recovery and the same "trick" worked. When it got around to the system img it eventually failed with a "Magic number" problem. Checking this problem out made me realise I can't keep messing around and should "get help".
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
hand_of_henry said:
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Click to expand...
Click to collapse
Do "fastboot erase recovery" then flash a different ClockworkMod build. Try 3.0.2.4
Sent from my Nexus S using XDA App
Thanks Matt.
Just tried erasing (hadn't before) and flashing 3.0.2.4 - no dice. Tried erasing and 3.0.2.5 and no luck either.
twitch153 said:
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
Click to expand...
Click to collapse
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
hand_of_henry said:
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
Click to expand...
Click to collapse
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
asafru said:
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks asafru,
I tried booting into recovery but again, no luck. I did it with one of the recovery builds you suggested (the cyan recovery but having trawled that thread I'm not sure what the difference is between the colours).
matt2053 said:
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's a fair point - I had expected to see the recovery screen fairly sharpish.
I've waited 15 minutes now on the splash screen for flashings of cw 3.0.2.4, 3.0.2.5 and the mysterious cyan build of 4.0.0.2.
I imagine this is an appropriate amount of time for the recovery to kick in?
I've tried all these recoveries using the Recovery menu item and also using the booting directly recovery method that asafru suggests above.
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
It's not a brick if it turns on! But I'm fairly new to this phone and I'm not familiar with it at all Normally I would suggest to fastboot flash the new OFFICIAL CWM recovery image, but I don't even know where to begin with fastboot on this phone
chillwillo9 said:
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
Click to expand...
Click to collapse
It would probably be a little helpful (if you want help) if you let everyone know what you were doing when you "bricked" your phone. That way people know where to start in assisting you.
chillwillo9 said:
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
Click to expand...
Click to collapse
I had a infinite loop problem on mine. I just restored to stock.
Turn phone off (pull battery if needed)
Turn on while holding volume down + power button
chillwillo9 said:
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
Click to expand...
Click to collapse
What happens when you try to boot into recovery mode?
OK here is what I did to brick my device.
I wanted to do a factory reset and I used clockwork recovery to do so.
Wat I didn't know what that Clockwork recovery was going to format my system.
I can only get into fast boot via vol up+vol+down+power
Cannot get back to stock recovery or CWM. Tried flashing via fastboot method
My phone just goes to LG screen no loading bar
Currently the only function is fastboot
Did you try formatting via Vol-Down + Power?
xenoletum said:
Did you try formatting via Vol-Down + Power?
Click to expand...
Click to collapse
Yes I did but same result stuck Lg screen no loading bar.
Capacitive touch also are not lit appear to be not working
1) Fastboot flash the official CWM recovery image
2) download http://forum.xda-developers.com/showthread.php?t=1048274
3) put the NANDROID in the correct folder on your sdcard: /sdcard/_ExternalSD/clockworkmod/backup/
4) restore via recovery
Thanks for everyones input, Called t-mobile they are shipping a new one out asap. I'm just going to have to suck it up till tuesday.
I love trial and error they only thing i lost is a little time
omarsalmin said:
1) Fastboot flash the official CWM recovery image
2) download http://forum.xda-developers.com/showthread.php?t=1048274
3) put the NANDROID in the correct folder on your sdcard: /sdcard/_ExternalSD/clockworkmod/backup/
4) restore via recovery
Click to expand...
Click to collapse
I flashed official CWM recovery image numerous times via fastboot and phone just gets stuck at lg screen. Once again vol up+power and vol down+pwer does nothing
Is there another fastboot method or adb method to restore CWM?
did the same thing it bricked my phone does nothing else than start up then freezes. f-ING pissed
The best thing with Nvidia phones and tablets is that its barely impossible to brick your phone. If you think you bricked it - you just need NV flash and either the stock rom or stock recovery and you are back to normal
I have done that with my old G-tablet - it was a piece of cake to fix it.
is there an nv flash for mac?
thought i did the same thing!
if you can get it into format hit the home button. hopefully vol+down+power will get you there. pull your battery and you may just get lucky if done enough times? i would keep trying. good luck
I need to get back to stock.
I did a root byway of revolution...got to cwm 4.0.0.8... then tried to flash a rom that needs cwm ...0.9.. which i did not have. I did not read close enough.
Now I'm stuck on a tmobile my touch splash screen...i can get to recovery and or hboot screen.
I've tried to choose factory reset from hboot sceen.... no luck, it just puts me into recovery...
Please help.
btw.... my fastboot skills suck eggs... can't type correct commands in cmd prompt window.
did u do a backup
Of course not that would have been the smart thing. I was in a fog when i started this.
coach628 said:
Of course not that would have been the smart thing. I was in a fog when i started this.
Click to expand...
Click to collapse
ok well ur screwed jk so im gonna upload a backup for u it will be stock with s off
Awesome Thanks!!
Boot Loop
I seem to have a phone with the same problem. I don't know its history, but it wont do anything but go into recover or bootloader.
it shows hboot -0.89.0005 radio 26.11.04.03
Where can I find this file to put back to stock (I assume it is an RUU?)
I think I bricked the recovery for my phone. The OS does boot, and I can get to "download" mode. If I try to get in to recovery, whether its with vol-up+vol-down+power or rebooting to recovery from the OS, the phone just loops. It shows the Galaxy S logo than the screen goes black than back to the logo. I believe when I flashed the 2.3.3 ROM, it got screwed. It worked before hand. When I flashed the ROM via Odin, on the first attempt, it wiped something than failed. Than I got an icon on the phone (a phone icon with a ! and a computer screen icon) and wouldn't do anything past that. I again reflashed the ROM and the OS came up, but noticed the recovery doesn't work anymore. I've tried to flash the once more for good measures, and I tried the modified recovery binary, but same results. I'd greatly appreciate any help I can get with resolving this.
Thanks
I actually resolved this by flashing http://forum.xda-developers.com/showthread.php?t=1063696.