I have a semi bricked Magic, Rogers, and have since Sat and none of the other procedures have worked for me with update.zip always get can't find file or destination directory or bad Installation aborted. Not sure why this is happening and have used 3 diff brand new micro sd's, am now with a semi bricked phone reliant on a card reader, and my last option appears to be going back or trying hard to the roger's stock rom yet no instructions were given? Any help greatly appreciated.
http://www.howardforums.com/showpost.php?p=12768375&postcount=5
Related
Hey GUys,
I'm not new to flashing and roms and all that jazz. Had the random stuck in bootloader that wouldn't resolve itself today (using 3.29) Loaded kaisdiagsd.nbh and flashed stock att rom. (probably should have gone right for the spl patch but I was frustrated and needed my phone) Boot loader is now v3.65
Flashed rine, reboot, same issue. Phone will now only load the stock 6.1 att rom from the micro sd. kaisdiagsd.nbh is stuck on loading as for all other roms. I can occassionally get the os to load using mtty. From there tried jumpspl and it would not connect via usb at all.
When in the stock 6.1 os I get the old unrecognized usb device in both xp and vista.
Is there anything else I can do to reflash spl? All i can think of is trying the task 2a, wiping everything and trying to flash from diag but I don't even want to try that route without something solid in place.
The phone is 2 years old, upgrading when the touch pro 2 hits att in aug sept or whenever, but I need my phone.
I have gone through many many many posts. I'm stuck. Any help would be appreciated.
Is there anything else I can do to flash a n
Have you tried to flash the SPL from the SD card? Worth a shot if not.
thanks for getting back, i have tried..multiple. It will just sit on loading as for everything except that damn att rom. i've been going at this for hours and hours. just to make sure, the spl flash will still be named KAISIMG.nbh correct? or has my frustration gotten to me
Yes but make sure you dont put the .nbh. Just kaisimg or it will be kaisimg.nbh.nbh and wont work
haha, yeap. i'm an i.t guy so i have file extensions showing by default so thats golden
I have the stock att rom up and running so the phone is functional, but that said, its the ****y att rom and I'd really like to change that asap., I'm just tired and fed up at this point really
Also for flashing SPL from SD card you need kaisdiag.nbh. Place it on the SD too. I should have told you that first. Its in my 4shared if you dont have it.
just tried it. it is stuck on the loading screen....
Try reading from here: http://forum.xda-developers.com/showthread.php?t=433835
Ta
Dave
So I went thru the root process shortly after it got figured out. great work to everyone. I had everything running smooth today I did the daredevil process to get back to 32b and all was well. I loaded a hero rom on there and did not repartition my sd card first so was obvious that it was running too laggy. decided to do a restore from last backup to go back to the 32b rom and realized after it was done that there was no backup since I went from 32a. now I am stuck at the red vodafone screen and cant get passed it for obvious reasons. I can get to fastboot but that is it and unfortunatley I am at work so cant update drivers to get sdk tools working to fastboot anything. I dont think I am totally screwed (since I can get to fastboot) but wanted to see if anyone had some ideas. I can download files and transfer them to my sd card as I have a reader with me (just in case)
You should just be able to boot a recovery image via fastboot and reflash a 32b ROM from the SD card. If you can get to fastboot, you're not bricked
guess it was a good thing I created my goldcard on a 128mg sd card that I had and kept the goldcard on that just in case still have that with the sappimg on it. just in case
So, when I got my Dream, I instantly wanted to root it. I did so using with a little deal of difficulty using the goldcard method. It was fine, put ROM's on and everything..
Anyways, it stopped charging, sent it to Optus. They had it for almost a month. When i got it back, it had been unrooted and put back on factory Donut firmware.
Now, im attempting to root it using the same method.
I have a different SD card than when I first rooted it, so naturally, I generated a goldcard for the new SD card. Put the DREAIMG.nbh file on, and tried to downgrade.
And for some reason, I keep getting the 'not allow' error on the 'rainbow screen'..
I've been told it MAY be a 'perfect SPL'.. idk if thats bs or a possibility, but any help would be greatly appreciated=]
Hey guys, today i attempted to root my HTC MAGIC 32A, and install KingKlick's 2.1 Eclair with HTC Sense for Magic v1.1. The rooting went fine, and i partitioned the sd card using the recovery tool (I followed this guide and used the downloads in that: www~theunlockr~com/2009/08/29/how-to-root-the-htc-magic-in-one-click/) for some reason, the device wont boot, and i tried wiping and reinstalling the update rom, with no success, it just stalls at the boot screen. Now i see that i did make the mistake of not updating my radio, which is at 3.22~ something, and im not sure my sd card was CAT 6. so i dont know what to do know. I can still access the recovery root menu , and was wondering what is the next step from here, or how do i return to the stock 1.5 cupcake firmware.
Anybody's insight is greatly appreciated
BTW PLEASE REPLACE CURVY DASHES (~) IN LINK WITH .'s AS I WASNT ALOWED TO POST LINKS BECAUSE I AM NEW
I flashed a new htc touch pro 2 verizon with hardspl, and it was fine - rebooted happily and was fully functional. Then I flashed it with a ROM, and it doesn't boot further than htc logo. I can load a menu with choices to go back to original settings, etc. but nothing can reverse a damage. I tried flashing it from sd card with whatever ROMs - it didn't help. From what I read as long as you use right spl, a phone is not a total brick, but it looks like it is. Any advice is appreciated.
Thanks!
PS. In case you are wandering which ROM killed it: it was an unofficial russian version. I tested it on my t-mobile htc, and it was functional. Then I reversed back to energy rom. I bought htc verizon for my dad, but he asked me to flash it with a russian rom. It didn't go well as you see.
Gorlum_ said:
I flashed a new htc touch pro 2 verizon with hardspl, and it was fine - rebooted happily and was fully functional. Then I flashed it with a ROM, and it doesn't boot further than htc logo. I can load a menu with choices to go back to original settings, etc. but nothing can reverse a damage. I tried flashing it from sd card with whatever ROMs - it didn't help. From what I read as long as you use right spl, a phone is not a total brick, but it looks like it is. Any advice is appreciated.
Thanks!
PS. In case you are wandering which ROM killed it: it was an unofficial russian version. I tested it on my t-mobile htc, and it was functional. Then I reversed back to energy rom. I bought htc verizon for my dad, but he asked me to flash it with a russian rom. It didn't go well as you see.
Click to expand...
Click to collapse
well i dont think it is considered a "brick" unless it wont boot, thats where the term brick or paper weight came from (because thats all it can be used for lol). so with it still starting up, i think there is still hope for you and your device. first off, did u SD flash it in the first place, or is that you attempt at fixing it? cause i think u just got a bad flash. so if you havent tried it, i would try and do it the original way. worth a shot
try finding someone who has a modified version of task29, basically that should take the "bad" rom off of it and only have the boot screen.. i think its an option needing looking into.. hopefully it will work for you.
are you sure its a cdma rom? or else ur phone wont go past boot...check the sticky for cdma roms