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!
Related
I have tried to root my HTC Magic, using the Hero 1.4 ROM found on this homepage.
But something has gone wrong. i have followed the instuctions and done the same as all the other times i have root'et my phone.But now the phone won't start, it's "frozen" and only show the HTC MAGIC startup picture, and stays that way until i take out the battery.
Im getting more and more affraid that the phone is broken.
So i was wondering if anyone here could help me with this problem.
I can enter the recovery menu, and its possible for me to push a new update.zip file, and flash that and i have tried it but that dosn't help so all suggestions are welcome
Per
Home + Back when power up so you could get into fastboot menu. You then can flash your nandroid backup back into your phone.
Or get a ROM that worked for you in the past and flash it in recovery menu (update.zip).
I think you flashed the ROM that is designed for 32B board (HTC Magics with Google experience) in your Magic, which has the 32A board.
I did exactly the same thing! i first tried the HTC hero firmware from this thread: http://forum.xda-developers.com/showthread.php?t=531617
But after reading bachviet's response i got the other version from this thread:
http://forum.xda-developers.com/showthread.php?t=534464
So thanks Bachviet
Hey, thx for the answers, but i found another way of getting my phone to work again, kind off.
I used the recovery .img file found here on this forum (http://forum.xda-developers.com/showthread.php?t=530492) and then i just Nandroid restore, and it restored my phone back to when i bought it.
Now i only have a problem with the camera. it restarts my phone when i press the camera button in the menu. So think ill need to drop it off for repair, damn.
hi, here is an other method to resolve this problem.
I dont have sd card adapter, that is way I use adb to push a right update.zip and I use fastboot to wipe and apply the update.
(Sorry for my english)
1. put the right update.zip on "...\android-sdk-windows-1.5_r2\tools"
2. connect your phone using usb and start it (if is not)
3. open terminal in "...\android-sdk-windows-1.5_r2\tools" and type:
adb rmount (if is not success wait 10s and repeat it )
adb push update.zip /sdcard/update.zip
adb shell reboot (at the same time hold volume down button)
4.type:
fastboot boot recovery-magic.img
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 I'm trying to use the tutorial here to root my girlfriends HTC Magic 32A. It is currently on 1.5.. but I think the latest version? or patched version of 1.5?..
Anyway... When the phone is booted and running I can adb devices and it shows up fine, however when I boot the phone in fastboot by holding back then pressing power if I adb devices nothing shows up... and when I try to send the command 'fastboot boot recovery-new.img' it just fails. Any help guys?
I'm trying to get it running Cyanogen 5.08... I've spent 3 hours reading and searching and still stuck.
LevitateJay said:
Hey I'm trying to use the tutorial here to root my girlfriends HTC Magic 32A. It is currently on 1.5.. but I think the latest version? or patched version of 1.5?..
Anyway... When the phone is booted and running I can adb devices and it shows up fine, however when I boot the phone in fastboot by holding back then pressing power if I adb devices nothing shows up... and when I try to send the command 'fastboot boot recovery-new.img' it just fails. Any help guys?
I'm trying to get it running Cyanogen 5.08... I've spent 3 hours reading and searching and still stuck.
Click to expand...
Click to collapse
Reboot your phone, then press vol down + power and the android skateboarding should come up then navigate to fastboot, plug in your usb when in fastboot and fast boot USB should pop up, try your commands there. if that doesnt work that means your SPL is perfected. Are you on rogers? casuse if you are you had the same problem as me and I can help you. Anyways always look in the WIKI for your answers (located in the android development section for the HTC Magic)
Cheers.
No one is able to offer a solution to this issue
I have the EVO with CM7 and after flashing phone it enter a boot loop with
White back ground and HTC Logo.
Other post have same issue..and we are not able to get into recovery
please see post: http://forum.xda-developers.com/showthread.php?t=1340267
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
Just so you know, this belongs in the Q & A section...as it doesn't offer any 'development' of roms, kernels, ect.
Anyways, did you try flashing a boot.img via fastboot?
P.s....prepare to be flamed.
dirtysausage said:
No one is able to offer a solution to this issue
I have the EVO with CM7 and after flashing phone it enter a boot loop with
White back ground and HTC Logo.
Other post have same issue..and we are not able to get into recovery
please see post: http://forum.xda-developers.com/showthread.php?t=1340267
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
Click to expand...
Click to collapse
The things people do for CM7 =)
Is there a way to get to fast boot using adb? Im not able to get the phone to boot now
just shows connected under device manager as MY HTC **again black screen no boot**
teh roxxorz said:
Just so you know, this belongs in the Q & A section...as it doesn't offer any 'development' of roms, kernels, ect.
Anyways, did you try flashing a boot.img via fastboot?
P.s....prepare to be flamed.
Click to expand...
Click to collapse
Is there a way to get to fast boot using adb? Im not able to get the phone to boot now
just shows connected under device manager as MY HTC **again black screen no boot**
Was a problem a few months back with some users, no solution was ever found. The only thing they were able to do was flash a radio and pull the battery to cause an intentional brick and then have it swapped.
RileyGrant said:
Was a problem a few months back with some users, no solution was ever found. The only thing they were able to do was flash a radio and pull the battery to cause an intentional brick and then have it swapped.
Click to expand...
Click to collapse
wow thought someone would have answer for a fix!
Wonder why it shows up in device manager...but not able to accept any commands
I see adb > My HTC would be nice to access the phone some how this way but abd says no device
dirtysausage said:
wow thought someone would have answer for a fix!
Wonder why it shows up in device manager...but not able to accept any commands
I see adb > My HTC would be nice to access the phone some how this way but abd says no device
Click to expand...
Click to collapse
Well I had the same issue, but my adb skills are next to nill. I just upgraded from the kyocera zio. I was able to flash a new recovery image through the zio clockwork mod fastboot program. Now I wont promise it will work for you but it is worth a shot.
jlmancuso said:
Well I had the same issue, but my adb skills are next to nill. I just upgraded from the kyocera zio. I was able to flash a new recovery image through the zio clockwork mod fastboot program. Now I wont promise it will work for you but it is worth a shot.
Click to expand...
Click to collapse
Yeah I did try a recovery the RA recovery for the EVO...I was able to update and tried to enter recovery but was not able to. I tried with another recovery by adding it to the root of the card and attempted to load the file with adb..BUT after the power down the phone no longer boots to bootloader...black screen and it vibrates once. I can only see it register as adb device >My HTC under device manager. But please not that running adb shell and no device detected.
Can anyone help?
had the same problem alot of times .
What did you do?
Sent from my SCH-I500 using XDA App
Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?
Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..
No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.