Related
Hi folks i don't what i did to my phone! I was trying to apply some
updates, test other builds, but after applying a 1.1 radio image i
can't access recovery mode (using HOME+POWER) or fastboot (tried using
BACK+POWER and CAMERA+POWER).
When i press power the phones shows up the ANDROID logo and the robot,
and stays there forever!
Did i bricked my phone? That is nothing i can do to get i back to
work?
Thanks for anyone that can help me!
Hugs
Antonio
as much as i believe this to be a redundant thread you seem to be at a different point than the other "bricks" you claim to be at the android screen with the flashing robot. at that screen you SHOULD be able to access adb as long as you have it set up correctly on your computer. try it and post your results
EDIT if adb works then try this after placing the JF recovery.img onto your sdcard
Code:
adb shell flash_image recovery /sdcard/recovery.img
if it works great if not someone else might be able to help with any other errors
Hi Tuba and other experienced members, in fact, i don't know what are the singnals that i have a brick!
My G1 won't pass the very first screen, not the flashing droid. Mine get stucked at the first screen that goes on.
ADB won't connect to my ADP!
Is there any way to save my phone? I heard about the G1 Serial Cable (http://www.instructables.com/id/Android_G1_Serial_Cable/) could it done any good?
Will be my G1 like this forever?
Thanks again!
First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.
Hey all. My friend gave me her HTC Magic (Vodafone) today asking if I could fix it. I took a look, and the problem is that it always boots up in recovery mode (white screen, skating androids, etc). Usually this isn't a problem as I can use fastboot to push a new image onto it, however this time I can't.
It tells me to press Back to go into fastboot mode, but nothing happens.
I've spent the past day using various SAPPIMG.ZIP files to try and fix this, but as you can guess, they haven't worked.
Plugging in USB does nothing (PC doesn't see it either), and I can only load SAPPIMG files. It was running the stock build supplied by Vodafone when I got it.
Is there any other way I could get either to fastboot, or is there a suitable image for me to load?
Sorry for the noobish post, but any help would be appreciated.
Regards,
Brett
Just to add: I've created a goldcard that works, and when I apply SAPPIMG files, it asks me to reboot the device. I do so, but I end up back in recovery with the same problem.
Are the fastboot drivers installed corrctly?
Sent from my SpeedTeam Magic using XDA App
You realize fastboit looks virtually the same ss the hboot/ how you load a sappimg correct? Only difference is a red rectangle saying fastboot. When you gret to fastboot open up your cmd prompt. Type this:
Cd\
Cd\nameofyourandroidsdkfolder\tools
Fastboot devices
Sent from my SpeedTeam Magic using XDA App
I can use fastboot on my Hero. I use the Back button to select fastboot and it comes up in red, and it works, and it also changes when I plug in the USB.
With the Magic, it gives me the option but it won't change when I press the button. Plugging in the USB doesn't work either, as neither device detects it. I've tried installing the Magic on my own PC, but without it detecting the hardware, there is very little I can do.
Unless there is a way to fully recover the phone (inc OS) with the HBOOT option, it is beginning to look like I'm holding a very expensive paper weight.
Thanks for the reply.
I don't know what I did when I was trying to install the orginal rom but, now my phone just shows the mytouch 4g picture, then it goes black and the same picture appears again, while the phone is vibrating. I am able to get into hboot but none of the options work. I upgraded the firmware with clockwork and unrooted the device. Is there a way to unbrick, or is the device just a brick?
Any help I would be thankful toward,
Luke
This may seem trivial, but it was not mentioned and therefore I am asking. Can you get into recovery?
Sent from my HTC Glacier using XDA App
No I can't get into recovery its locks up and stays on t mobile mytouch 4g screen. That is after i select recovery.
Good news is its not bricked. You're just hitting a snag on boot. Have you tried fastboot or hboot?
RIP Cotton Eye Jim
When I try the fast boot method it brings up bootloader i selct it and it takes me back to the main screen, at that point I try recovery again and the device show t-mobile mytouch 4g for a second then goes black and goes back to the screen and vibrates and repeats the same thing over and over.
lukecarr said:
When I try the fast boot method it brings up bootloader i selct it and it takes me back to the main screen, at that point I try recovery again and the device show t-mobile mytouch 4g for a second then goes black and goes back to the screen and vibrates and repeats the same thing over and over.
Click to expand...
Click to collapse
You don't choose bootloader in fastboot. All commands need to be run from your machine.
Sent from my HTC Glacier using XDA App
It does not even show the device in adb. I have install the driver for hboot usb plug, but maybe I got the wrong driver. Do you have a link to download that so I can try to reinstall driver, or is the unit bricked? Or how do I fastboot with the unit not loading to android, but its on hboot screen with usb cable attached. Is there a way to do that?
Press and hold the back button while booting to get into fastboot mode. Then download the clockworkmod recovery img and flash it through fastboot. You can find more detailed instructions in the thread where you download clockworkmod. This will enable you to enter recovery and flash a new rom.
When I followed those steps, fastboot in red came up and it gave me choice of bootloader reboot reboot bootloader and powerdown, it does not load, I have tried the bootloader, it goes to the main screen.
Was being dumb needed to hit restart it boots, thank you I will be reading on clockworks. I a noob as you can tell.
I reinstalled clockworks but now I cant get the hboot up by holding the volume down and power key. Any suggestions?
Volume down+power does nothing?
RIP Cotton Eye Jim
Got it working just wasnt holding it long enough I need to be more patience lol
Lol, I had the same problem the mt4g when I first got it. Very different from the mt3g. For future reference, as long as you get fastboot to come up, or at least get adb to recognize the phone, its not bricked. I actually bricked a mt3g 1.2, and when they're dead they're DEAD. Nothing works except an led notification.
RIP Cotton Eye Jim
I'm glad you got help but this is the wrong section to be asking questions. Go to the Q&A next time.
Sent from my PC36100 using Tapatalk
Please post questions in Q&A section.
Hey you guys
I recently installed amon ra's recovery v. 1.7 on my magic 32a (radio 6.3.5 something) after I rooted my phone, of course.
Now, I thought that with the new recovery I would be easily able to flash a custom rom onto my magic. This was however not so easy, because the recovery behaves in a very weird way. Whenever I tell it to flash a new rom from a .zip image, or wipe the phone, or anything, it just reboots my magic and thats it. Also, the recovery happens to freeze quite regularly when I don't act very quickly. E.g. when I boot into recovery mode and don't touch the phone for the first 5 seconds, it wont respond any longer.
So, I'm probably doing something wrong here. I would appreciate any help from anyone. (and btw, i have the official android 1.5 sense rom installed on my magic, os I cant use rom manager either, since it only supports android 1.6 upwards.)
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
mumilover said:
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
Click to expand...
Click to collapse
hey, thanks for the quick response. I still have a few questions though, since I am quite a newb. So when I type all of those commands into cmd, doesnt my device need to be connected to the computer somehow? I read somewhere earlier that I simply connect it using the "mount" funtion, the problem is that that doesnt seem to work anymore for my magic, because after I hit "mount" it simply goes back to "usb connected" without acutally mounting. So ..how do I connect the device to the PC while entering the commands?
ok... my bad..
Try to read the ENTIRE guide... then do the steps i mentioned above :0)
Don't mount it... just connected... but again.. read the guide.
thanks a lot
I didnt use your method to flash the image, but the hero recovery works way better than the one I had before. I managed to flash a rom now. So happy ;D
ok i think i just did a bad mistake
i installed rom manager after i had flashed an android 2.1 rom on my magic. THen i told it to flash some rom from my sd card and also wipe some data, or something. Now my magic gets stuck on the magic bootscreen, like it keeps looping. Did i brick my phone ..or is there a way to fix this? please help me, (
most likely is that the rom you flashed doesn't have a compatible kernel for your phone.
Just boot into recovery and flash a rom that is compatible.
cant boot into recovery ..it just keeps looping
Then you will need to boot into fastboot and reflash a working recovery.
Clockwork has issues flashing the clockwork recovery sometimes.
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
so, guys ..did i brick my phonne..?? :S
da robat said:
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
Click to expand...
Click to collapse
you're probably not doing it right. you should still be able to get into recovery or fastboot and install a different recovery. i'm using RA-magic+v1.7.0.1 recovery it has bugs but pretty stable.
so what am i doing wrong??
just realized when i connect the phone to my pc over usb and then boot it, it connects to the pc for a second or less and then disconnects again. Dont know if this helps anyhow.
pull battery, put battery back in. hold back and push power.
Should be good.
tried that like 50 times. phone just keeps looping ..like, it restart over and over again.
What you have is what hundreds before you had when they used Rom manager.
The system will not boot into anything.
My advice is to never use Rom manager for 32A device.
The fix:
Keep pushing the back button while the system reboots... just mash the **** out of it..
I helped out someone before you, and he did it for over an hour or so...
It's a timing issue...
Good luck
haha ..so is there still hope?
cheers for all the answers ;D
i do have one question though, actually.
Shall i just press the back button continuously ...while it keeps looping, or should i rather restart the device after each loop and hold the back button?
just mash the back button.