bootloader 1.01, any SD image wanted - MDA II, XDA II, 2060 ROM Development

Well.. story is, that i am idiot, start upgrade over IR. Yes, i know, who i am, but this phone is gifted to me, and i didnt had cable... so i was thinking i am lucky As result, i have "Serial V1.01", and nothing else. And even cable will come after 1 week, in best condition (if i will find it in Ukraine, where mobile shops looking to this XDA II, like to elephant in kitchen ).
So question, is anybody have any image to recover this device?
As i understand i had ancient version of software (and reason of upgrade was also by this, cause i had problems with stability when i use WModem).
Pleassssee...
Thank u a lot

I began an update without connecting the shipper and the XDAII remained in "serial 1,02".
I connected the shipper, I reinitiated the update and few minutes later it found to the XDAII and it followed with the process.
Now I have 1.72 spanish ROM.

Sorry, had not seen that you do not have cable.

Ok, so as i understand, just i need wait cable and continue upgrade... correct?

Yeah... thats issue... anyway, today cable is coming to train, and i will wait it, till train will pass few countries )) cable what cost on this city $16, will cost me near $70
thats exUSSR

Related

HELP! HELP! Stuck between ROMs after trying to upgrade!

Anybody out there know how to fix this?
All I have is a black screen giving a USB version. Won't connect to or be recognized by ActiveSync.
it's still ok given that the usb is shown. just cradle back the unit and restart the upgrade. don't expect activesync to "recognize" your device. just hit the upgrade exe file and it should proceed. this happened to me once when i upgraded to 2005.
THANKS VERY MUCH, I'm going to try that, I'll report back my success (hope)
You Are Fantastik, Thanks! Thanks! and Thanks!
Now let me ask you, this happen to you when you were updating to Windows Mobile 5? If so I too am looking to upgrade to WM5 just thought I should get O2's final update before doing WM5. Seen WM5 (for Xda IIs)for sale on ebay for about $16 to download, with all instructions.
Do you have any suggestions or advice, I'm feeling pretty brave now.
THANKS
yes this happened to me when i decided to upgrade to wm2005. what happened was the instructions said that i should first do a reset before proceeding with the upgrade (not sure if it was a soft or hard reset). anyway, i forgot to do this and went straight away to the upgrade. after a couple of minutes the upgrade screen (on my laptop) said something like "device error"...of which the screen on my xda said "usb version-something"...with a dark background (i think this is the one you experienced). anyway, i did a couple of resets (even a hard reset) and my screen was stuck with the same info. i believe this is called bootloader mode. i remember reading the instructions that if this happened i simply cradle back the unit and hit the upgrade command on my pc. it worked!
for you, i'm not as familiar with upgrading an xda2s. but in my opinion, as long as you can get your unit to bootloader mode you are still fine. in fact i do remember reading a couple of posts that some chaps had a completely blank screen. they said that they kept on doing hard resets until the unit went back to bootloader. true enough, a buddy of mine upgraded to 2005 and his screen went blank. he did something like 10 or so hard resets and he was able to get it to bootloader mode. from there he proceeded with the upgrade and he succeeded.
hope that helps and good luck
Oh, I should have said, your suggestion worked. I put it back in the cradle and restarted the ROM upgrade and it worked perfectly. I just thought that since ActiveSync was not recognizing it, it was Broke.
Thanks, now weather to temp faith again and try to upgrade from 2003 se to WM5. Did you find WM5 to be a big improvement over 2003se?
nice to know it worked. wm2005 is fantastic in all aspects. the only con i found was that one of my apps was not working due to not being compatible. i use animated today (animation of my baby girl rocking back and forth on her rocker), when i upgraded i couldn't get it to work anymore. however; i wrote to the app developer and he said they're working on an upgrade to make it compatible with 2005. so it's not really a con...more of just waiting until the release is out for the upgraded software. so in your case, there might be some apps which may not work properly (or not work at all) due to it being incompatible. there's a thread somewhere in this forum listing the proven apps that work well with wm2005.
a LOT of people complained about the memory issue when they upgraded to 2005...myself included. however the fixes came out (ramdisc, doc tools, etc) and from there everything worked out fine. for you, when you do upgrade to wm2005 just make sure you follow every bit of tip and instructions so as to make the transition and experience worth it. i read a lot from the forum (as well as buzz's website); a lot of chaps didn't do this and they ended up downgrading to 2003se.
other than that, a lot of my favorite apps work well with wm2005. i still have this app i used 2 years ago (today plug-in) and it works with 2005.
cheers
Sounds pretty cool, watching your daughter rocking when ever you want. What is buzz's website?
buzz was the one who enabled wm2005 to be ported to the xda2. the website is:
http://buzzdev.net/
TONS of info and resources in there.
cheers
Thanks for all your help, I'll check out buzz's website.

Good lie to tell T-Mobile for brickin my phone

Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
CCRDude said:
I don't think using bold letters and the clear word "lie" will help you a lot... you just highlight that you ask for illegal help
Maybe you should take a look at the bricked-devices topic for a chance to revive it?
Click to expand...
Click to collapse
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
vayip said:
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
Click to expand...
Click to collapse
enter the bootloader; try to flash a regular update from your provider to it.
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
I did the same with my Vodafone (UK). I just told them I'd hard reset and this is all I can see on the screen (don't get stroppy etc).
Mine will be back Tuesday, warranty repaired.
Vod UK use an outside repair centre so will probably be the same as T-Mobile if you are in UK. Mine needed a new motherboard, but there is a bit of a shortage in the UK (too many bricks???). I guess it depends on the outside service centre contract whether they charge you or T-mobile (and maybe also because I had warranty and Insurance)..
Just go in and plead ignorance, but if they want to charge you, ultimately it was you that ****ed it and not them
Toast it in the microwave for 5 seconds!
boz said:
Toast it in the microwave for 5 seconds!
Click to expand...
Click to collapse
That's a new one - when car radio codes first came out they always said to put them in the freezer then stroke the chips legs to erase the cmos... never worked for me, but I'd probably get away with the microwave thing with 3 kids at home!!!
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
@ ach2
I was thinking also something like that. That I hard reset my phone and now it's broke. I was also thinking something like I left my phone on the charger for the weekend, and when I came back I did a soft reset because it wouldn't go on and know I only see a HTC splash screen.
vayip said:
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
Can you think of a good reason whey the boot screen has changed from the normal T-Mobile one... just hope they don't turn on the phone. Did you try Olipro's suggestion?
@ Wam7
The T-Mobile splash screen is in the extended ROM. If the extended ROM is ****ed up like mine is, it probably goes back to its embedded splash screen, and that's the one from HTC. But thats not what I'm going to say, I'm going to say how should I know.
If I remember correctly a guy has managed to dump the ROM from a Hermes and flash it to the phone... saw a thread somewhere here. If that's the case then you should just need a ROM from a fellow dutch T-Mobile owner with the newer ROM. I take it your phone is not SuperCID
vayip said:
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
Click to expand...
Click to collapse
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
seriously this is why MS and Carriers HATE us
Olipro said:
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
Click to expand...
Click to collapse
I did what you said. I connected the phone to my laptop in bootloader. I started the RUU from WMXL 0.20. My phone goes to the white screen and at 0% i get a message on my laptop the connection got disconnected. So i start the RUU again, but again the message my connection got disconnected.
So still working on a good lie.
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.
On the new computer:
direct USB connect to rear port only no usb hubs
pc running windows XP
turn off screensaver/Powersave mode
close all other apps
hands off the computer for the 25 minutes or so that it takes
Sleuth255 said:
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.[/list]
Click to expand...
Click to collapse
Does it matter if the phone is simlocked or not. My phone is not SuperCID.
The strange thing than is, i have 2 laptops. Doing the upgrade don't work on both.
Will try a normal pc then. Maybe more luck.
Follow Oli's advice about retrying the update if you get an initial vendor ID error. BL1.04 will flash any rom without SuperCID due to a bug.
You might want to jump in with mtty first to see if your NAND is full of bad blocks. If it is then your device is toast fttb.....
spiritofseth said:
seriously this is why MS and Carriers HATE us
Click to expand...
Click to collapse
I completely agree! If you ****ed up your device, than you should have the courage to stand up for it and if it was not your fault, than just tell them the truth! But suggestions like "put it in the microwave for 5secs".... come on
And just a small hint: If you (for example) really put it in the microwave, than you'll better pray that no technician ever analyses your device - if so you could get into serious trouble, mate.
Btw, if you microwave it, you probalby need a new microwave too.
Edit: And i dont think its warranty would cover "I just put my Phone in there"
"So still working on a good lie."
Doesn't breaking your phone through your own actions and then getting it repaired/ replaced for free by telling lies make you a liar and a thief?
I trashed 8525, and that sucks, but it was my fault so I have to pay for it.
In my adventures flashing Roms, I've only bricked 1 Hermes (Cingular 8525). I actually told the local Cingular shop that I broke it 2 weeks after I bought it. The manager told me to bring it in and she replaced it under the 30 day in-store return policy. I was suprised because I had caused the bad NAND Block problem on the device but she said that since I was able to get an official Cingular Rom flashed onto it and it booted into WM5 (just wouldn't do anything because of memory errors).
Now I also have a very good working relationship with this store. I've gotten a phone about every 6 months from them over tha past 2 years and have given them some great info regarding WM5 devices (reccomendations on screen protectors, software & cases etc). I have 3 lines (2 with Data) and even if they don't know me by name eveyone in the store knows me by reputation.
Tomorrow I will have my spare Hermes (also 8525) so we can begin experimenting with getting some additional storage memory without risking bricking my primary phone.
The way I see it, we are taking a chance when we modify our devices.
I've had to return 2 Wizards for Warranty replacement to Cingular, both were CID Unlocked but the problems were unrelated to flashing Roms (One was because the touch screen developed a dead spot the other was because of Radio hardware issues).

Hermes won't power up. Double bricked?

Well, I'm just not having a good year.
Before anyone jumps on me -- I've been digging through the wiki and forums for the past few days, and it doesn't seem like anyone else had had a similar problem...
I just received my JASJAM back from the service center. They said they couldn't fix the trashed radio ROM (good ol' Windows XP blue screened on me), and needed to replace the motherboard ($590), and it wasn't covered under warranty due to the "non-iMate software" I had installed. doh. I declined, and had them send it back to me. In the time between them receiving it and me getting it back, all of the cool new stuff from pof and olipro have come out (Hard SPL, etc). So I'm thinking I could fix it myself.
I put HardSPL on there, started to flash a new radio ROM, and it locked up for 90 minutes before it just went blank. It was getting power from the PC, the PC didn't fall asleep.. it just.. died.
Now I just get the red LED when it's plugged into power, and no LED when the battery is installed. The LED turns off when the battery is installed while there's power going into the unit.
I'm pretty sure this thing is a goner.
I've left the battery out for an hour or so, plugged it back in, same results. I tried the "pull power, pull battery, plug in power, plug in battery, reset" technique from the wiki - no difference.
Too bad this didn't happen before -- I bet iMate would replace the stupid thing now because it won't power up (I already called them -- the serial number has been blacklisted so they won't do anything for me, even if this is a hardware problem). :-\ ... I've considered sending it back and pay them to replace the system board... but I can buy a new TyTN for $650... and I'm sure something better is right around the corner from HTC, so I don't really want to spend the money on a system board replacement.
So I guess this post has two purposes: does anyone have any last resort ideas on how to get this thing to at least come back up to a boot loader... I'd be happy if it would even try to power the LCD panel back up.
If not... anyone want to buy a toasted JasJam off of me, for parts? It's got a front camera.. *wink wink* 8525'ers..
That sucks; but if there's no power at all, I'm guessing it's pretty toasted.
So, how much do you want for it?
im willing to buy the case and screen from u... hehe msg me or email me
my case has a few dents and scratches im want to take out... and the screen.. well =(
I assume that you can't get to bootloader mode?
Before you give it up for dead at least post your info in the "dead hermes? corrupted radio? Post comments here" sticky thread. The experts will review your post and they have been known to provide tips that fixed phones that others had given up for dead. Can't hurt to try and it could save you a few $$$.
How much do you want.. i may be interested!
Well, imei-check.co.uk does offer a repair service... Send them an e-mail (they'll ask you whether you used Pof's unlocker - which they call "cloned/cracked" - answer NO! else they'll add 20 pounds to it!)
Yannick
Even though there is nothing on the screen, while the red button is on try and go into the bootloader.
I am having the exact same issue after trying to upgrade to the new AKU 3 ROM from my SD card.
My screen went blank just at the beginning of the upgrade and since it does not power at all.
I follow the instructions mentioned in thread about this issue:
http://forum.xda-developers.com/showthread.php?t=286469&p=1077622
but after inserting at different time the battery when it is powered on, the red light goes off, so I am enable to do any soft reset.
Do you think it could be a related battery issue (my battery is a 3 months old original one).
Any suggestions are welcome!
Wam7 said:
Even though there is nothing on the screen, while the red button is on try and go into the bootloader.
Click to expand...
Click to collapse
No such luck. My PC isn't even recognizing it on the USB bus. I tried on two other machines, and it doesn't show up there. Nothing on my Mac or Linux boxes, either. :-\
Grr.. I wish it had done this before I sent it to iMate for repair -- they would have swapped out the systemboard without giving me the grief of "you put non-iMate software on here, no warranty service for you!"
Heh. Expensive lesson learned. This is what I get for constantly trying to tweak and improve something that really didn't need to be tweaked and improved.
I'm probably just going to replace it with a TyTN/HERM200 now - I like the layout/d-keypad on it better.
I guess that planned Las Vegas vacation will have to wait a few more months. doh.
Cuivienor said:
Well, imei-check.co.uk does offer a repair service... Send them an e-mail (they'll ask you whether you used Pof's unlocker - which they call "cloned/cracked" - answer NO! else they'll add 20 pounds to it!)
Click to expand...
Click to collapse
Already tried; they replied that it sounds like a hardware/system board issue and to send it in for service.
Of course, iMate refuses to fix it because they saw the 1.01MFG bootloader on there from when it originally died on me and have declared it out of warranty.
Originally I messed it up when I flashed the newest HTC ROM on there -- my windows machine blue screened. It toasted the radio rom. This was before HardSPL/etc, so I tried to downgrade it to 1.04 with no luck, then I managed to get 1.01MFG on there. From there, it refused to let me update anything, and I couldn't get back to 1.04 (in other words, it wasn't acting like *anyone* had said it would in the forums/wiki). From there, I was stuck with the HTC Rom (that had a big "TEST ROM" on the screen), booting into AKU3, and no way to put the JASJAM ROM back on it. So. yeah. I screewd myself by sending it to them for repair and not waiting for HardSPL/etc to be released.
Last night I was able to get the latest oilipro bootloader on it, and it was happily accepting a new radio ROM when it just powered itself off in mid flash. The red LED went on, and it just sat there. It hasn't done anything else since.
So I guess final word is: if you brick your device, before sending it in to the warranty... Well you should brick it a little more!
I hear microwaves can help you there
jmat said:
Last night I was able to get the latest oilipro bootloader on it, and it was happily accepting a new radio ROM when it just powered itself off in mid flash. The red LED went on, and it just sat there. It hasn't done anything else since.
Click to expand...
Click to collapse
Well, If it let you get olipro on it there is still hope! Maybe a bad battery causing the shutdowns?
Cuivienor said:
So I guess final word is: if you brick your device, before sending it in to the warranty... Well you should brick it a little more!
Click to expand...
Click to collapse
Exactly. Make sure it won't even turn on. LOL
JasenR said:
Well, If it let you get olipro on it there is still hope! Maybe a bad battery causing the shutdowns?
Click to expand...
Click to collapse
Nope; I've tried a different battery and different power cables. Tried direct power, USB power.
There's nothing showing up on the USB bus at all -- it's not even showing up in USB monitor. On my Linux machine, the USB Host isn't seeing it.
It's dead. Other than the single red LED when it's only plugged in (with no battery).
I've done every key combo, tried to get into KITL (but without a USB link, it's a no go).
LegolasTheElf said:
I hear microwaves can help you there
Click to expand...
Click to collapse
Hah. I bet sending 12-24 volts up a USB cable would do the trick as well.
jmat said:
Hah. I bet sending 12-24 volts up a USB cable would do the trick as well.
Click to expand...
Click to collapse
go for the gold and apply 110
I had the smae problem with my 8525...It was toast, I sent it back to Cingular who repleaced it under warranty.. ."I dunno..it jsut died, you think a power surge or soemthign could cause this?"
short answer according to everything i read here when it happened to me...you're done.
Damnit and double damnit.
I've the EXACT same problem, but I didnt flash mine (at least in the last 5 days) Orange will not replace mine as the battery "moisture alert" has turned red spotted meaning - according to them, that I have kept it in my Speedos while I have been swimming, which isnt the case. It has been in humid environments tho, but what argument do I have?
If anything does work, ill be sure to let you know.
@scibot : this is abusive from them. I would try again at a different store if I were you. Tons of reasons this could happen, none of them your fault. I'm sure you'll find a decent explanation for the presence of that spot

[REQ] Help to recover my partially bricked Fuze

The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Q
Have you tried to flash from the SD card?
Hi Captain_Throwback,
Try copying Raph Radio 1.11.25.01 to the root of a FAT32 SD Card ... you'll need to rename the .NBH to RAPHIMG.NBH.
Pull the SIM out of the phone and power it back on as per usual; I've noticed that the phone "blacks out" for a bit but then switches to flash mode.
Good luck.
PS: suggest getting the large carry-on with the wheels for the guilt trip - heaven knows it's come in handy for me
That's a bummer, man. You gotta at least 'fess up part of the story to prevent someone else from falling into the same trap (however unlikely that may be). And maybe, just maybe, it will help someone else figure out how to fix your problem.
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
I have done this a few times on my tilt, all I did was put it into the boot loader, it worked from hard reset screen as well, and flashed the rom via activesync. I am assuming that you are not able to get a sync, or have you tried yet? I know my fize will also sync [to flash] from bootloadr.
Captain_Throwback said:
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Click to expand...
Click to collapse
Damn I'm sorry to hear about your issue and i feel for ya because I did some stupid **** myself a lil' while back if you remember. Your advice to reflash the oem rom worked for me 100%. Have you tried hard resetting and then trying to get into bootloader mode?
AllTheWay said:
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
Click to expand...
Click to collapse
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Captain_Throwback said:
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Click to expand...
Click to collapse
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Intertrochanterica said:
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Click to expand...
Click to collapse
It is insured, and paying $125 is better than having to buy a brand new phone, but if I can avoid spending money, my wife would be much happier .
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Captain_Throwback said:
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Captain_Throwback said:
I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
You could make it worse if you get the white sticker wet and make it turn pink, but that would be very bad for you.
You are at the point to where you cant move beyond your current predicament in wither way. Im afraid I see no other alternative than to pay the $125.
Maybe you could sell your Fuze on Ebay for 125 to cover your insurance cost and you could make a notation on the Ebay site saying something like 'PARTIALLY USED FUZE' like that Carfax commercial does.
update
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Keep us updated dude. Also, if you slip the guy $50 he may do the free warranty replacement for you... it might save you $75 and you wont have to use up one of your insurance claims.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
iceman4357 said:
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
Click to expand...
Click to collapse
That might work, if I hadn't bought the phone from my best friend, who just happens to manage an AT&T store. He actually knows that I had a custom ROM on my phone, and called ahead to the repair shop to let them know I was coming, and he said hopefully they won't notice the SPL in my bootloader if they try and hard reset it. So it is possible they'll just give the phone a cursory look to make sure its really not working, and then go ahead with a warranty replacement. I'll be sure to let everyone know what happens. In the meantime, the word of the day is "dumbass", LOL.
Farmer Ted said:
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Click to expand...
Click to collapse
That's what I would do.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
P1Tater said:
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
Click to expand...
Click to collapse
I'm curious what it is you told him, in case i'm in a similar position at any point !!
Lemme kno please here or PM is cool!
Thx
JFlitt
AllTheWay said:
That's what I would do.
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Click to expand...
Click to collapse
Agree with this. If your friend works at the store and knows what you have done, I wouldnt go there. Call the number, fry the damn phone and get a new one. We need you back on your feet to help solve ROM issues my friend.

Bye Bye Chevron

Well,
Today I did the unthinkable.. I connected my Chevron Unlocked titan to the computer to reinstall a homebrew ap that had started to get glitch. I made sure Zune was turned off and wasn't loaded up and was set to NOT load when the phone was connected. I connected the phone, it synced up with windows phone device manager and started to install the ap. It seemed to lock up 3/4 threw and I closed windows phone device manager. Upon restarting windows phone device manager it said the phone was locked... NOOOOOoooo!!!!!
I use Nokia Maps 3.0 as my gps guidance as I like it way better then Navigon and others. I immediately went to see if it still worked. Nope! Son of a B.....
I was hoping to get away with NOT connecting the phone to my pc till the new windows phones came out with Nokia Drive built in. Doesn't look like that's going to happen. I have a construction company and use GPS about 4-8 times a day going from job site to job site. Serious pain here as now I'm going to have to purchase Navigon which I wont use once Windows Phone 8 is released. *sigh*
This might not be an issue if the AT&T phones were able to be unlocked (and yes I know some have gotten them to work but more often then not they get stuck and aren't able to be)
Long story short... word to the wise.... If your phone is chevron unlocked don't connect it to your PC no matter WHAT! Not unless you want to loose your unlock.
Not looking for sympathy here just wanted to remind people that apparently even having Zune shut down the phones can still relock
You could still try HSPL. A lot of people get stuck about halfway through the process but no one has bricked their phone by trying.............yet. And the funny thing is they get stuck with an SPL update. So the worst thing that can happen to you is you updated your SPL.
Use the built in navigation, it works well enough that you could stand to use it until the end of october, you don't need to shell out money for navigon.
link68759 said:
You could still try HSPL. A lot of people get stuck about halfway through the process but no one has bricked their phone by trying.............yet. And the funny thing is they get stuck with an SPL update. So the worst thing that can happen to you is you updated your SPL.
Use the built in navigation, it works well enough that you could stand to use it until the end of october, you don't need to shell out money for navigon.
Click to expand...
Click to collapse
With the New Windows 8 Phones coming out perhaps as early as the End of October I just went ahead and bought the monthly subscription to HTC Locations. 5 dollars for the US for a month, By then the new phones will be just about out and I wont have any worries when I upgrade. It was really just a precaution to anyone who wanted to connect their phone to their PC's and still have Chevron unlock NOT to do so.. I actually hadn't seen any thread regarding anyone who lost their unlock so... now there is one.
Chevron Unlockers it WILL relock!!!

Categories

Resources