[Q] Bricked Sprint Intercept. No Debug USB/Recovery - Intercept General

I managed to brick my Sprint Intercept the other day.
I was having problems with the WIFI and Bluetooth so I figured flashing a custom rom may solve the problem. I downloaded and installed BasicROM 1.7 and then rebooted. The phone shows the progress bar and then hangs at the Samsung screen. Holding the button combos for Download/Recovery mode doesnt work. I had also installed CM01 before hand. Even before installing the Custom ROM I wasnt able to enter Download/Recovery on boot. Any ideas of what to do?
Also, I was able to ADB at one point but I accidentally cleared Cache/Data which im guessing turned off Debug mode and now I cant get ADB nor Fastboot to see my phone now.

Did you backup?
NookColor Cyanogenmod 7.1 "Overclocked"

Unfortunately no

Just install another rom, hopefully its a stable rom then backup
NookColor Cyanogenmod 7.1 "Overclocked"

How do I do that without Recovery Mode/ADB?

I thought u had recovery?
HTC Wildfire S VM "S-Off" "Rooted" Stock Rom

Nope. No recovery. I cant get my phone to boot into it nor Download mode. Even before the brick.

Welll it sounds bricked to me man, sorry bout that, always back up, I learned the hard way
HTC Wildfire S VM "S-Off" "Rooted" Stock Rom

Well thanks for helping me out dude. Have good.

i might be able to help, try pulling the battery for about 20mins, reinstall it then power-up (no cables attached) holding the vol-down power and call button, if nothing, then pm me

Related

Is my HTC Magic totally bricked?

I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.

[Q] Help Unbricking Vibrant...if possible?

So basically I rooted my vibrant, and realized it was hardware locked, as in recovery/download key combinations don't work.
I installed clockwork Mod recovery and backed up my system using the backup function. I then proceeded to flash the "Obsidian V2 - JK2 Official Froyo Based 2.2 - Team Whiskey" rom.
When that was done, I think I made a mistake by restoring the backup before restarting the phone before the first boot. Therefore, I am now stuck on the Vibrant/Samsung first boot screen.
I've researched a bit on how to get the phone into download/recovery mode on hardware locked models and none of the methods I found worked. A friend told me that apparently there was a method by using heat and a soldering iron....but if possible I want to avoid that unless its the last thing I can do to restore it.
Extra Info:
I had ADB turned off on phone before flashing ROM
It is samsung Vibrant Tmobile version, not Bell, and its hardware locked.
What I think the cause of the problem was that I restored a backup from 2.1 immediately flashing the v2.2 rom. Maybe I should have booted first into the new rom before trying to restore any backups...
When I plug my phone into the computer it starts charging (Battery icon with amount and animation of dots works)
I've tried using Droidexplorer as well but it doesn't detect my device.
My device makes the connection sound when connected to windows.
So hopefully, if you have any ideas for how this can be fixed with ODIN or how to get the phone back to the stock ROM, or even how I can force my phone into recovery or download mode without using a soldering iron then that would be extremely helpful. Thanks in advance
just happened to me too. Please help!
I figured it out.
Its because I flashed a backup which was a 2.1 image when I had a 2.2 kernel installed. And that = death.
The soldering method isn't that bad, so i fixed the problem.
That`s what happened to me too. But i just recovered my wife`s phone. While holding volume keys i pluged usb and voila, got into download mode. That means it`s not fully bricked. Then just did the odin recovery and the phone is back to life.
Thanks to all the devs in this forum.
Unfortunately, that method wont work for hardware locked phones, so the soldering jig is the only possible way to force the vibrant into download mode if its hardware locked.
You can still get to download mode using adb even if the phone won't fully boot.
Sent from my SGH-T959 using XDA App
Possible, but if ADB on the phone itself was turned off before the soft brick would it still be possible?
Zeltex said:
So basically I rooted my vibrant, and realized it was hardware locked, as in recovery/download key combinations don't work.
I installed clockwork Mod recovery and backed up my system using the backup function. I then proceeded to flash the "Obsidian V2 - JK2 Official Froyo Based 2.2 - Team Whiskey" rom.
When that was done, I think I made a mistake by restoring the backup before restarting the phone before the first boot. Therefore, I am now stuck on the Vibrant/Samsung first boot screen.
I've researched a bit on how to get the phone into download/recovery mode on hardware locked models and none of the methods I found worked. A friend told me that apparently there was a method by using heat and a soldering iron....but if possible I want to avoid that unless its the last thing I can do to restore it.
Extra Info:
I had ADB turned off on phone before flashing ROM
It is samsung Vibrant Tmobile version, not Bell, and its hardware locked.
What I think the cause of the problem was that I restored a backup from 2.1 immediately flashing the v2.2 rom. Maybe I should have booted first into the new rom before trying to restore any backups...
When I plug my phone into the computer it starts charging (Battery icon with amount and animation of dots works)
I've tried using Droidexplorer as well but it doesn't detect my device.
My device makes the connection sound when connected to windows.
So hopefully, if you have any ideas for how this can be fixed with ODIN or how to get the phone back to the stock ROM, or even how I can force my phone into recovery or download mode without using a soldering iron then that would be extremely helpful. Thanks in advance
Click to expand...
Click to collapse
Just a suggestion:
1:Open ODIN
2:Connect USB cable to computer (not phone)
3:NOW, connect USB to phone
4ress POWER, VOL. UP, & VOL. DOWN at same time and HOLD (yes i read that ur hardware locked but just try )
5:Wait for first Vibrant logo to appear, and as SOON as it dissapears...release ONLY the POWER button. Keep hold on both volume buttons.
Uh sorry if this didnt work but atleast it was worth a try.
*words in caps are keypoints, im not angry
roguly said:
Just a suggestion:
1:Open ODIN
2:Connect USB cable to computer (not phone)
3:NOW, connect USB to phone
4ress POWER, VOL. UP, & VOL. DOWN at same time and HOLD (yes i read that ur hardware locked but just try )
5:Wait for first Vibrant logo to appear, and as SOON as it dissapears...release ONLY the POWER button. Keep hold on both volume buttons.
Uh sorry if this didnt work but atleast it was worth a try.
*words in caps are keypoints, im not angry
Click to expand...
Click to collapse
Doesn't work....it only keeps bringing up the battery charging screen and won't even boot to vibrant screen.
Zeltex said:
Possible, but if ADB on the phone itself was turned off before the soft brick would it still be possible?
Click to expand...
Click to collapse
That I'm not sure on, but worth a shot.
Sent from my SGH-T959 using XDA App
Can you please link me to an article on the soldering method? I couldn't find anything on google.
Well as I said earlier, I just did the soldering method and forced my hw locked vibrant into download mode and restored with Odin. Unless you modify your hardware or flash something special to get rid of the hardware lock, the volume/power key combinations don't work.
Edit:
gonintendo said:
Can you please link me to an article on the soldering method? I couldn't find anything on google.
Click to expand...
Click to collapse
Here's the guide. Its pretty hard to mess up so don't worry.
http://forum.xda-developers.com/showthread.php?t=819551
I have a question about using this method:
once boot the phone by odin, is the phone going back to a
fresh state or with all the saved contacts/apps backed up
with Titanium Backup?
I am having trouble to boot the phone when I tired to restore to 2.1 update1.
Rooted, backed up with TB, then flashed to Obsidian V4, Froyo 2.2.
Now I want to restore to 2.1 so that I can get all my contacts back.
Thanks for help.
roguly said:
Just a suggestion:
1:Open ODIN
2:Connect USB cable to computer (not phone)
3:NOW, connect USB to phone
4ress POWER, VOL. UP, & VOL. DOWN at same time and HOLD (yes i read that ur hardware locked but just try )
5:Wait for first Vibrant logo to appear, and as SOON as it dissapears...release ONLY the POWER button. Keep hold on both volume buttons.
Uh sorry if this didnt work but atleast it was worth a try.
*words in caps are keypoints, im not angry
Click to expand...
Click to collapse
Haven't seen this mentioned yet, but something that has worked for me many times is this:
-Take battery out
-connect phone to the power chord (best to do it while connected to the computer)
-hold both the volume up and down buttons at the same time
- insert the battery into the phone while still holding buttons
You should see download mode pop up and you're ok to release the buttons after that. Now you're free to odin it up.
villaparv said:
I have a question about using this method:
once boot the phone by odin, is the phone going back to a
fresh state or with all the saved contacts/apps backed up
with Titanium Backup?
I am having trouble to boot the phone when I tired to restore to 2.1 update1.
Rooted, backed up with TB, then flashed to Obsidian V4, Froyo 2.2.
Now I want to restore to 2.1 so that I can get all my contacts back.
Thanks for help.
Click to expand...
Click to collapse
By restoring with Odin, all your stuff will be wiped out, but think on the positive side, at least you don't have to carry a broken phone around with you all the time now. Unless you put your backups on the external SD card, not internal 16gb memory, then maybe take out the SD card before restoring.....
And as a precaution to those who don't want to end up in the same situation as me, don't use nandroid to backup and restore a 2.1 backup when you flashed a 2.2 rom.
2.2 roms will flash a 2.2 froyo kernel to your device and then the 2.1 backup will flash a 2.1 image to it, therefore causing your phone to brick.
-----------------------------------------------------------------------------
And again, no method by pressing the physical hardware keys will work on Hardware locked model vibrants. Even taking the battery out or plugging in the USB won't work as these functions have been "disabled" by the lock. I'm pretty sure the soldering method is the only effective way to force your phone back to download mode and to restore to factory conditions. I've spent at least 39882884385820384872 different combinations with the battery pulling, USB plugging, holding key combinations and they don't work.
Zeltex said:
So basically I rooted my vibrant, and realized it was hardware locked, as in recovery/download key combinations don't work.
I installed clockwork Mod recovery and backed up my system using the backup function. I then proceeded to flash the "Obsidian V2 - JK2 Official Froyo Based 2.2 - Team Whiskey" rom.
When that was done, I think I made a mistake by restoring the backup before restarting the phone before the first boot. Therefore, I am now stuck on the Vibrant/Samsung first boot screen.
I've researched a bit on how to get the phone into download/recovery mode on hardware locked models and none of the methods I found worked. A friend told me that apparently there was a method by using heat and a soldering iron....but if possible I want to avoid that unless its the last thing I can do to restore it.
Extra Info:
I had ADB turned off on phone before flashing ROM
It is samsung Vibrant Tmobile version, not Bell, and its hardware locked.
What I think the cause of the problem was that I restored a backup from 2.1 immediately flashing the v2.2 rom. Maybe I should have booted first into the new rom before trying to restore any backups...
When I plug my phone into the computer it starts charging (Battery icon with amount and animation of dots works)
I've tried using Droidexplorer as well but it doesn't detect my device.
My device makes the connection sound when connected to windows.
So hopefully, if you have any ideas for how this can be fixed with ODIN or how to get the phone back to the stock ROM, or even how I can force my phone into recovery or download mode without using a soldering iron then that would be extremely helpful. Thanks in advance
Click to expand...
Click to collapse
had the exact same problem only diff is that i was kinda doing while snoozing off
nd when i was in recovery mode i deleted ALL USER DATE nd stuff.
right now i followed most of the comments nd now i'm on DOWNLOAD mode connected to the computer i'm still trying to find out how to use ODIN to fix my phone think u can help me a lil.

[Q] HTC Wildfire bricked? need help /will give reward

hello i just wanted to see if i still could get help with my useless device
Ok so yesterday ive rooted the phone and today i tried to install cyanogen mod 7 rom
i used rom utility which i ve downlaoded from android marketplace
now sometimes my phone boots and gets to the logo loop
ive heard that clearing cache and settings would work but i cant access these menus as my hboot is not reacting to my key presses , i tried to reflash the phone but nothing came with success.
I used android sdk and RUU but nothing with success .
maybe anyone would teamview me or give me step by step tutorial how to get this phone alive again would be appreciated
You will be rewarded
You rooted the Phone with a App from the Market?
You need if your HBoot is lower then 1.* the unrEVOked Tool.
If its 1.* there is no way to flash it.
Okay, maybe it worked with yout root app from the market, dunno, but i dont think so.
So you cant access while pressing volume down (keep holding) and switching on the phone the bootmanager? oO thats no good.
The Logo will stay up to "15minutes (<-?)" after flashing a new Rom. In this time its possible, that you Phone restarts automaticly. its normal. Switch it on an wait up to an half hour. If it keep staying in the boot sequence while showing the logo you got a problem .
I think there isnt a more unsave way than a "Flash by teamviewer". You have also pay attention to the phone while flashing. on TV you cant keep an eye on it.
But how can you reflash your phone without getting access to the bootmanager/ HBoot? I think you habe to access the clockwork to flash cm7 *thinking*.
If u nowhow to use adb try n get a adb logcat if possible
Sent from my HTC Wildfire using XDA App
Hi borris and daddyspud thanks for your reply ,i cant move around in hboot ,my hboot version i 0.80.0003
Ive rooted it using unrevoked with clockwork mod on it.
now even when i get it to boot it just loops in cyanogen animation,should i leave it for 15 minutes to do its thing?
also im new to this so i dont know anything about sdk and adb,all i did is saw the tutorials using it ,so i thought i would use it just to give it a go
HBoot 0.8 is rootable, so its okay.
If there is still an animation while you see the CM Logo everything is fine.
If it freeze for some minutes is there a problem. The Animation shows you "i am working / installing".
Yes, let him do his thing for some Minutes.
I think everting should be okay and after some minutes it will work like normal.
It reboots sometimes it self, but this is also okay.
I dont know... does the new CM7 also install a new HBoot? So its possible why you cant move around in it.
Do you wait about 10 seconds before you try to move around in it? Because in the first seconds it looks like it freezed an then it start a test or something. this takes about 10seconds then you can use it.
Its not bricked if its turning on.
Can you get into recovery? If you can try flashing the 4.1 kernel.
If that doesnt help, go into recovery and do a full wipe. Clear cache and dalvik, and under partitions menu format everything except SD card. Then flash CM7, then the 4.1 kernel
Remember first boot will take 10-15 minutes. Be patient. If youve done everything right you shouldnt have any problems
Hi and thanks for cooperation ,i left my phone on cyanogen animation for an hour and nothing is happening just animation loop constantly.
I've just tried hboot and it searches for the PC 49 DIAG and says not found after that it freezes and i cant use any menu navigation buttons . in hbot and fastboot.
I dont even know what to do next
Much help appreciated guys
oO
thats weird.
the PC49DIAG is a part of the rom it self. So i think you have to try to re-flash it. Did you try it with or without a goldcard?
before you flash your phone whipe ALL datas on it!!!
If i start in bootloader mode i get also all the "missing" errors but i can still use the vol up/down buttons to navigate around.
That should help.
I think you did something wrong while flashing.
the root failed?
you got an error while flashing?
goldcard?
Try to flash a RUU from shipped roms. DONT flash a Froyo rom, you will get the HBoot 1.* if you do this.
Recoverymode doesnt work in the hboot?
If you try recoverymode you will get a blackscreen with an triangle.
most say "press the power button" to enter the recovery mode. if this doesnt work press the "volum up button (hold it) then the power button" this should enter recovery mode.
**EDIT**
http://shipped-roms.com/index.php?category=android&model=Buzz use a www-rom its without a branding. and use a RUU rom.. and pls dont use a froyo rom. after flashing this your root is gone i think but your phone will be alive again.
dont try the cm7 this time. use a stock rom.
is it alive again?
i talked today to someone who hat exactly the same problem like you.
it was simple to fix the problem... he (you also?) didnt
whipe the phone before he flashed the cm7. thats why it wont stop looping
in the cm7 animation.
after whiping and reflashing everything was fine.
... did you whipe it b4 flashing?

[Q] Magic 32a Flashing problems

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.

She wont boot, what to do now?

Hi.
I was running cm7.1 and flashing to cm9, when the battery fell out (my stupid mistake) when it was installing cm9.
Now all that comes up on the display when I start her up is the Google/cm logo.
Pressing vol down while starting dosent get me in recovery mode, but pressing vol up does get me in bootloader mode. When I plugged the phone to the PC, it downloaded something, so that works...
The problem is that I dont konw what to do from here, I bet the awnser is out here, but I dont konw what to search for.
Anyone got a minute to help, I bet its a simple fix :]
Thanks
I guess the "simple fix" would be using RSD Lite to flash some stock or fixed sfb from Recovery and start over (root, 2nd init..)
Well, thats awsome, installed new stb driver with rds tool, ran the setup, and after a long wait the phone is back in action.
Thanks alot!!

Categories

Resources