partially down MT3G 1.2 - myTouch 3G, Magic General

Ok here goes from what i know.
I went ahead and created a goldcard from the unlockr tutorial. I downloaded the files that he specified and am able to get it to that fastboot\usb screen and the other one. I tried to flash the recovery and it tells me it fails or is not allowed. I try to just normally boot the phone and it says htc magic and ust starts heating up. I have a somewhat knowledge of what im doing but im lost here. If anyone has a suggestion on how to get the recovery to flash or anything to make this phone work again i will be greatly appriciative. I have no phone now and cannot figure out what in the world to do. Thanks

Related

Bricked MyTouch. Please help.

It would appear that I dropped the incorrect SPL on my phone when following this guide (http://android-dls.com/wiki/index.php?title=Amon_Ra_recovery_tool). I used the one that was mentioned, and now the phone no longer fully boots. I can still get into fastboot/hboot, and technically into recovery. The screen is not displaying properly on either mode, leaving hboot difficult to read, but useable, and recovery without a UI (the MyTouch splash stays there, but the phone goes into recovery mode).
I did manage (somehow) to get CM-Recovery 1.4 flashed to it, and that is how I managed to install the SPL. I had the 1.33.0006 SPL prior to bricking.
I also tried fastbooting and it is no longer blocked.
What are my options here? Am I boned, or do I have a way out of this?
Thanks in advance for the help.
If you have a SD Adapter try to add any ROM to your SD and flash it. I did that earlier, and it worked. If you can see the recovery image screen then its not fully bricked. Good luck.
I can attempt to do that. Thing is, I'm blind once I hit the recovery screen. Can't see jack because the video is all messed up.
Should I attempt to keep flashing SPLs till I find one that works? Or is that a very, very bad idea? Given, that, is there a way to go back to 0006?
Thing that sucks is that I just got this thing yesterday and got a little overzealous with the rooting. Whoever helps me through this is definitely getting a case of beer or something ><
---
I guess what would help me the most at this time (I think) is suggesting which SPL I should drop on the phone (2004 is now on there), or helping me get 0006 back on there or something of that nature.
Can I control Recovery via adb? If so, awesome. But can I push an SPL via adb, that is the question?
Also, since I was somehow able to get a different recovery on the phone, do I still need to deal with the goldcard and all in order to install a different ROM?

Flashing problem...

Hi all,
I have a Magic 32b and recently put the Modaco_custom_1_51 rom on, I think with the Amon Ra's recovery image (as recommended on unlockr)
It was working ok, not great, a bit slow and mms wouldnt work, so...
I decided to change the rom, unfortunately I was in a bit of a rush and I kind of forgot what I was doing...
I went straight to the Recovery mode and clicked 'part sd: fat32+ext2+swap'
Then I put the new rom on using usb storage mode, I clicked on apply sdcard:update.zip and of course it wouldnt work (all without applying any recovery image when the phone was working), I rebooted the phone and now after the vodafone image I just get a blank black screen...
I then woke up and realised what i'd done.
I have tried searching what to do when this happens but I couldnt find anything... I've never used abd and dont know how the commands and stuff work... I just flashed and applied the rom using the 'one click' method on unlockr.
I would appreciate any help you can give, theres propably a simple way to do it (well simple for you guys) but I just cant work it out, if anyone can give me some instructions it would be really grateful.
Im new here so take it easy on me
Also... im not sure if I posted this in the right place, sorry if I did.
Regards
Gino
One of the 35 people that have looked at this must know the answer....
Pleasee

Is it truly bricked?

Ok so here's the problem...
I was able to root my Rogers Dream but then I messed up with trying to partition the sd card. It was then that it would not go past the rogers screen. After A LOT of reading I downloaded what I thought would the files I need to simply restore the phone to factory. Long story short, if I just turn the phone on it sits at the Rogers screen, I no longer have recovery mode and my fast boot goes to a RGBW screen with Serial0.
Also on the FastBoot screen it states:
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.2.19.26I
I really just want to return the phone to the state it was before rooting it (store bought state). But because I can't access the fastboot through USB or even get to the Engineering SPL I'm really..really stuck!!
If I can get the proper FastBoot loaded somehow I think I can restore the rest.
Any help would be greatly appreciated.
no it is not bricked, try removing the sdcard
Still nothing.
Also if I press Home+Power or Camera+Power it still ends up at the same RGBW screen.
No, it isn't bricked
You are stuck at the stock SPL. I'm not sure about rogers but for tmobile you would want to put dreaimg.nbh on the root your SD card, load up the SPL. Flash dreaimg.nbh. Then it should boot into rc29 (I believe). Get root access, flash whatever flavor of recovery you want. Then boot into recovery and flash whatever SPL you want. Then you can get back into the SPL and restore whatever nandroid backup you had.
Again, this is what I would do on tmobile. Not sure about rogers, but I would assume since you would be loading your own backup everything will be peachy.
Ya I hear what you're saying. The problem is I can't seem to find an original Rogers DREAIMG.nbh file anywhere. I think I might be SOL and have to take into Rogers to get it fixed. I'm just not sure if I've voided the warranty or not.
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
try here >>>>>> http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32B_Firmware_to_CyanogenMod
dl the rc7 for europe and see if the fastboot recs it. if not try and find the system.img for rogers and ill tell you how to flash it via fastboot. if you had the system img it would already be good. no use of the nbh. also what is dif from dream and g1 besides apns and a small other few things?? if nothing then why not flash the g1 dreamimg?? once thats good then root and get it finalized? just wondering.
EDIT: I searched more for you. dont try my idea. im kinda dumb lol. i forgot that rogers and tmobile have dif boards. so this wont work and might brick you. so dont listen to me. sorry for missleading. im use to g1's in the usa sorry. ill keep searching for anything for you thou.
EDIT2: in fastboot can you >>>>> fastboot boot "name_of_your_recovery.img" ???
try that in fastboot to see if you can get into recovery. if you have no idea what i mean let me know so i can give some sdk instructions.
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
losingmyself said:
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
Click to expand...
Click to collapse
I know! I can't believe out of every bit of information on how to root an Android phone there is basically nothing on how to fix it. At least for anyone using Rogers.
DO what I did, I had the same issue (T-mo) I used a micro Sd "converter" if you will...........and plugged it into my laptop's SD reader, copied the files over, and VIOLA!
I actually thought I bricked it 5 times.
TinBasher77 said:
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
Click to expand...
Click to collapse
I think you've misunderstood.. fastboot mode on the phone enables you to use the fastboot program on your pc to send commands. You can use it to boot a recovery image and flash the files you need to fix this. There's a sticky thread detailing how to set up and use fastboot in Q&A.
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
TinBasher77 said:
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
Click to expand...
Click to collapse
there is no rogers dreaimg.nbh
Hi,
How did you root your phone?
can you still boot into the recovery img? (home+power)
If you cant, try get back the recovery img (e.g. cm-recovery-1.4.img) and then home+power again. From there you should be able to update your spl to hardspl
Unfortunately I can't boot into fastboot any longer I just get the red/green/blue/white screen. This happens with both Home+Power or Camera+Power so I can't even use adb to force the images onto the phone.
Thanks for the help though.
Well problem solved (sort of).
I contacted Rogers and they're going to send me out a new phone and have me return the "defective" one.
Thanks for all your help and suggestions.

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks

[Help] Phone wont boot.

Hi, after hours of researching to find the problem, i cant find it so as my last resort i will ask the mighty forums if there is anything they can do about it.
The problem is that its stuck in a boot loop, i can get in to bootloader and Hboot.
When i press to go in to recovery its just goes to the HTC logo and stays there.
When i try to do a factory reset same thing happened.
Anyway, the facts.
Its a DHD it used to have leedroid latest as rom, atm i have no idea it is supposed to be 1.32 stock rom for rooting and RADIO-26.14.04.28_M, kernel was also leedroid recommended but i guess that also is 1.32 stock.
It was ENG S-OFF but then i tried some PD98IMG and it changed to SHIP S-OFF
Things that i have tried.
Tried different PD98IMG to get the recovery working but nothing same thing happened there.
Tried patched/flashed the recovery part only with no luck.
Tried to get into recovery through pulling the battery inserting the usb and then inserting the battery again, no luck.
The odd thing is when i try to charge the phone and the led goes orange and when i pull the usb out it stays orange, it should turn off.
I suppose i ****ed something over but i have no clue of what that is?!?
Help would be most appreciated
I'm suggesting everyone to give this method a try although i have no experience with it but since it can be used to recover using computer i believe recovery isn't necessary here so that you can recover the firmware using the PC.
Hope this helps
shad0wboss said:
I'm suggesting everyone to give this method a try although i have no experience with it but since it can be used to recover using computer i believe recovery isn't necessary here so that you can recover the firmware using the PC.
Hope this helps
Click to expand...
Click to collapse
Done and failed, same problem no difference what so ever.
SHIP S-OFF is OK!! U got it m8!
If you want to use your own Image do it within this way:
1. Flash this: http://www.multiupload.com/FKJ8B7Q0QM
and after this:
2. Flash this: http://www.multiupload.com/AURLLESU5V
And enjoy it! I don't know why the PD98IMG is not working on your device so I recomend to flash the RUU. Within the RUU you will also get the latest firmware for phone and wifi and so on. It's not a need, it's a must!
The 2nd ROM is same as above but it's ROOTED and contains the 4ext Recovery which will give you the option to flash whatever you want.
BUT!!! This ROM's are ORIGINAL. If you want to use a CUSTOM ROM I would recomend you will format your device by the 4ext Recovery or you are using the FULL WIPE 1.5.
Regards!
Sorry for the insane delay.
That did not work either, anyone else have any idea what to do, installing through PD98IMG.zip files seams not to work, will at this point do anything.
I'am a student so buying a new one is out of the question.
I tend to have to see things to understand them more. Maybe other people are similar. Is it possible you can video the process, put it on YouTube and some of the experts here can see it and talk you through it?
Grant Barker said:
I tend to have to see things to understand them more. Maybe other people are similar. Is it possible you can video the process, put it on YouTube and some of the experts here can see it and talk you through it?
Click to expand...
Click to collapse
Dude, I plus 1 this comment.
Doing exactly that has helped me in the past too.
Well, i am here again with some videos this time, dont really know if it will explain anything but here goes nothing.
youtube.com/watch?v=cHA-k6SadoE
Just a simple start to show what the hell is wrong with it.
youtube.com/watch?v=squwhiGNM3s
Here's me trying factory reset but failed, stuck at the same place as before.
youtube.com/watch?v=aZF1ALz0Z-w
Here is where i go into fastboot, just to show that i can do it and then back again to try recovery, same problem...
Anymore info you need, next time i will answer much faster, anyway there the problem it gets stuck on HTC logo forever, no restart no nothing...
ithen said:
Sorry for the insane delay.
That did not work either, anyone else have any idea what to do, installing through PD98IMG.zip files seams not to work, will at this point do anything.
I'am a student so buying a new one is out of the question.
Click to expand...
Click to collapse
when you flashed PD98IMG.zip does it give you a cid error?. If this is the error then a gold card needs to be made for your device first, then you flash the RUU.
Back again.
No CID error, its skips something called TP when i try to flash it.
I can use any simcard, its an unbranded phone i believe.
And also if it is to any help, when i plug my charger in the phone and then back out again, the little orange led keeps emitting light, as if it stills charging.
My English is not very good.
I want to know what did you do for it before its stuck in a boot loop?
You can get into HBOOT and connect the phone to the computer,then try to run RUU.Before you do this,make sure you have make golden card.
Try another pd zip..i came across a few corrupt ones,the answers in this site somewhere alterbatively google the sentence you want the answer to..or the key words,if the systems still working theres a 98% chance youll get it going boot loops from what i see are just a file or something causing chaos..once its gone voila.
Good luck
Sent from my Desire HD using XDA Premium App
Enter hboot and paste exactly what it says in there.
SHIP AND ENG don't matter as long as it's S-OFF. If you can't access recovery and if you're unable for some reason to flash a PDimg, download AAHK and use it to unroot. That will hopefully get you into the stock ROM and S-ON of course.
Use AAHK again to root. You will still have access to your stock ROM.
Now here's the tricky part. If the phone won't boot at all that probably means there's nothing to boot at all. Happened to me a lot of times. If you can still get into hboot then don't panic. See if AAHK will help you out.

Categories

Resources