Bye Bye Chevron - HTC Titan

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!!!

Related

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).

Uh oh, no USB and need to relock my Titan

So one of the 5 pins in the mini-usb connection is missing. This disables any sort of data connection through usb, however I'm still able to charge the phone. Now I think I can get my phone replaced by Verizon but as it is right now I have dcd's 3.2.0 rom and the 3.42.30 radio. I have no problem flashing through my sd card as far as roms and radios go, but can the bootloader be relocked in the same fashion? I know the procedure for relocking is in the wiki but it relies on an activesync connection, which I cannot make. Am I proper f*cked or can I do this relocking?
So one of the 5 pins in the mini-usb connection is missing. This disables any sort of data connection through usb, however I'm still able to charge the phone. Now I think I can get my phone replaced by Verizon but as it is right now I have dcd's 3.2.0 rom and the 3.42.30 radio. I have no problem flashing through my sd card as far as roms and radios go, but can the bootloader be relocked in the same fashion? I know the procedure for relocking is in the wiki but it relies on an activesync connection, which I cannot make. Am I proper f*cked or can I do this relocking?
Click to expand...
Click to collapse
You can't relock unless you have an activesync connection. You can relock using nuespl, but it will relock to 2.07 which is the GPS rom stock bootloader...something that doesn't exist yet for Verizon.
I think ImCoKeMaN @ PPCGeeks has a relocker for the 1.06 bootloader that can be run from SD. It's not recommended for use after running a GPS ROM/Radio, but I've heard of a few success stories. Of course, I've also heard of a number of devices becoming completely and utterly useless after trying this. I don't think he made the version that can run from SD publicly available, but you could try shooting him a PM. He'd be able to give you all the details as well. Might be worth a shot as a last resort.
I might give that a try. If I recall, I can set up an activesync through bluetooth, which is what I'm goin to try first. If that's impossible I'll be pming ImCoKeMaN. Thanks
If you have the insurance it would be unfournate when it takes a trip in to the Shower or Tub.
Big Dawg 23 said:
If you have the insurance it would be unfournate when it takes a trip in to the Shower or Tub.
Click to expand...
Click to collapse
Or even better, falls down into the toilet. Chances are the people at Verizon won't want to poke around with it in that case.
Before I go through relocking or flushing my phone I thought I'd try to bluetooth connect it to try activesync. Well, it seems that the only connect I can make is to use it as a dial-up modem, a serial connection isn't possible. Has anyone else with dcd's rom tried to connect to a pc for file transfers and succeeded?
Honestly, I think the flashing / locking software relies on the USB connection. If I remember correctly, once the connection is made through Activesync... it disconnect Activesync. I'm not sure if this connection stays available for the flashing / locking. I personally don't want to try and brick my phone. LOL
Nitro is correct. The unlockers/relockers that run from your PC place your phone in bootloader mode, and at that point your bluetooth connection would drop.
The real issue isn't the broken USB port. There are ways to relock from SD. Your main problem is that going from a GPS ROM/Radio/SPL to a non-GPS version has been known to brick devices. You could always try and hold out until VZW releases an official GPS ROM, then you wouldn't have to worry about going back to a 1.x SPL. From what I've seen, gc14 may have some insight into when that ROM will actually be released.
I had a similar issue happen to my sprint mogul, I was able to charge but the mini-usb connector was messed up so I could not get a data connection.
I re-flashed the latest stock rom and radio from the sd card and took it in. Both the service reps and the technicians did not notice the bootloader version, and I got a replacement for free within 30 minutes or so. I would think that with all the devices they work with, the vast majority of people do not have unsupported software versions and the techs most likely do not check every time (or just do not care all that much).
Just my thoughts and experience though, yours with Verizon could obviously differ.
EDIT:
Ahh yeah I forgot that Verizon has not released their gps radio yet and that downgrading can be problematic... Best of luck to you.
VerusMaya said:
I had a similar issue happen to my sprint mogul, I was able to charge but the mini-usb connector was messed up so I could not get a data connection.
I re-flashed the latest stock rom and radio from the sd card and took it in. Both the service reps and the technicians did not notice the bootloader version, and I got a replacement for free within 30 minutes or so. I would think that with all the devices they work with, the vast majority of people do not have unsupported software versions and the techs most likely do not check every time (or just do not care all that much).
Just my thoughts and experience though, yours with Verizon could obviously differ.
Click to expand...
Click to collapse
Same exact issue here, except I did go ahead and put the 2.07 SPL back on. They are wanting to charge me $35 though. How long ago did you get your phone? I might try a few other shops and see if they'll swap me a new phone for free.
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
egrzelak said:
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
Click to expand...
Click to collapse
Yeah, this one here.
bedoig said:
Same exact issue here, except I did go ahead and put the 2.07 SPL back on. They are wanting to charge me $35 though. How long ago did you get your phone? I might try a few other shops and see if they'll swap me a new phone for free.
Click to expand...
Click to collapse
I got the original one in late December and got them swapped about two months ago. I was actually rather surprised I got it so hassle-free and without paying anything, I expected to have to pay some warranty fee or something.
I ran into this situation about a month ago, except the data port was hosed enough I couldn't charge or sync. After stressing about it I contacted a major contributor to the board and he said not to worry about it.
So I took the phone in (@ 3 mos. old) and the vzw sales guy was pretty cool about it (I didn't mention anything about flashing the software). He got on the phone with someone else at vzw tech and did some kind of exchange program. A few days later I had a new 6800 and instructions to send the old phone back.
I probably should have secured the phone better in the box when returning, but oh well. I seriously doubt anyone even looked at the rom, since it was a hardware issue.
why not just get a new cable?
deeznuts2 said:
why not just get a new cable?
Click to expand...
Click to collapse
The cable isn't the problem as the pin is missing from the phone.
Alright, so the only way to relock back to Verizon's original SPL is with a working USB. Over on ppcgeeks there seem to be some people who've flashed back to the stock radio and rom without relocking the phone. They only problem they've experienced is it being unable to wake up when it's been put in sleep mode. I think this is what I'm going to do to do the return.
egrzelak said:
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
Click to expand...
Click to collapse
Look at it this way if you brick it who cares....you are trying to get it replaced.....

[Q] Recover data from Nokia 710

Hi guys/gals,
I've been passed a Nokia 710 by a friend of mine. She managed to drop it in a bowl of water at work and has been refused a fix under warranty (not surprising). This was a few weeks ago, so the phone is fully dried out. It boots up, makes the start-up sounds and the three buttons on the front work, but the screen is totally blank - although touch-screen response seems to work still.
I have installed Zune, but whenever I connect the phone I get "Phone setup incomplete" and a message to disconnect the phone and complete the remaining steps on the phone. Without a screen to see I have no idea what I should be doing.
Is there a simple solution to this, or is there some way of connecting to the internal memory to recover the data from it some other way?
SimonTS said:
Hi guys/gals,
I've been passed a Nokia 710 by a friend of mine. She managed to drop it in a bowl of water at work and has been refused a fix under warranty (not surprising). This was a few weeks ago, so the phone is fully dried out. It boots up, makes the start-up sounds and the three buttons on the front work, but the screen is totally blank - although touch-screen response seems to work still.
I have installed Zune, but whenever I connect the phone I get "Phone setup incomplete" and a message to disconnect the phone and complete the remaining steps on the phone. Without a screen to see I have no idea what I should be doing.
Is there a simple solution to this, or is there some way of connecting to the internal memory to recover the data from it some other way?
Click to expand...
Click to collapse
How did she do that, I don't think you can recover the data from your phone, Zune is giving you an update error which means that the update isn't intalled completly.
What you can do, but you had to do that a lot earlier, is to put the phone in a bowl of rice (not water ) and wait a few days, that's the only thing I can think about at the moment.
Succes,
Rataplan said:
How did she do that, I don't think you can recover the data from your phone, Zune is giving you an update error which means that the update isn't intalled completly.
What you can do, but you had to do that a lot earlier, is to put the phone in a bowl of rice (not water ) and wait a few days, that's the only thing I can think about at the moment.
Succes,
Click to expand...
Click to collapse
She had the phone in her pocket when she bent over. I think the problem may be down to a key-lock on the phone which needs to be entered first, but am waiting for her to get back to me.
Thanks for the help though, I didn't expect much else.
SimonTS said:
She had the phone in her pocket when she bent over. I think the problem may be down to a key-lock on the phone which needs to be entered first, but am waiting for her to get back to me.
Thanks for the help though, I didn't expect much else.
Click to expand...
Click to collapse
Plug it into a Linux machine and copy direct from the phone as any other USB flash drive would work
Or uninstall Zune and use the reg hack to allow that to be done in windows
http://shivamsoftworld.blogspot.co.uk/2012/12/how-to-enable-usb-mass-storage-mode-in_14.html
---
*Detection* said:
Plug it into a Linux machine and copy direct from the phone as any other USB flash drive would work
Or uninstall Zune and use the reg hack to allow that to be done in windows
http://shivamsoftworld.blogspot.co.uk/2012/12/how-to-enable-usb-mass-storage-mode-in_14.html
---
Click to expand...
Click to collapse
Fantastic, thank you. Following the link you posted also took me to another site USB Storage Enabler for Windows Phones 7 which might be useful for anyone else coming up against this in the future, or simply wanting to use their device as a USB drive, not requiring Zune.
SimonTS said:
Fantastic, thank you. Following the link you posted also took me to another site USB Storage Enabler for Windows Phones 7 which might be useful for anyone else coming up against this in the future, or simply wanting to use their device as a USB drive, not requiring Zune.
Click to expand...
Click to collapse
I think the phone has been reset
SimonTS said:
Hi guys/gals,
I've been passed a Nokia 710 by a friend of mine. She managed to drop it in a bowl of water at work and has been refused a fix under warranty (not surprising). This was a few weeks ago, so the phone is fully dried out. It boots up, makes the start-up sounds and the three buttons on the front work, but the screen is totally blank - although touch-screen response seems to work still.
I have installed Zune, but whenever I connect the phone I get "Phone setup incomplete" and a message to disconnect the phone and complete the remaining steps on the phone. Without a screen to see I have no idea what I should be doing.
Is there a simple solution to this, or is there some way of connecting to the internal memory to recover the data from it some other way?
Click to expand...
Click to collapse
I think the phone is reset entirely..
and the reason you couldn't connect to zune is because you haven't completed the initial boot procedures...
There are many ways to get your phone started...
But I don't think its of any use unless, you have your screen working..

[Q] Biggest Collective Disaster - Save this 920!

Ok, I'm gonna try to keep this as simple and easy as possible.
I bought my phone in March. Off contract, one year warranty. Golden.
Dropped it in June. Nasty scratches all along the BACK of the phone, so I took the opportunity to replace the colour from black to grey. Everything went smoothly and I was very satisfied.
Ran into some account issues that for some reason wouldn't be solved easily. Tried to do them properly, but got annoyed and said
F*** this, let's just factory reset the phone.
Spinning cogs for 5 minutes, then 15 minutes, then 4 hours, then 3 days. Started doing all possible hardware resets and button combinations. Nothing. Tried to reflash the OS with Nokia Care Suite. Found out it's now locked.
Here's the situation at this very moment:
-Phone does not boot past Nokia logo or cogs.
-Cannot get to the exclamation mark screen.
-No warranty, hardware change voided it.
-Microsoft Store gave up, said buy a 1020 instead.
-Carrier "Rogers" refuses to fix it due to voided warranty.
-No service shops nearby.
Any ideas? I pretty much gave up on the phone, I just don't have another 600 dollars for another.
What do you mean with "Found out it's now locked." ?
Phone is stuck on Nokia boot logo ?
Did you try refurbished method in NCS ? Save my silly ass several times
One time I even thought I bricked until finally manage to get mine 920 in flash mode...on youtube video seems so easy to get it..probably I was too impatience
boril said:
What do you mean with "Found out it's now locked." ?
Phone is stuck on Nokia boot logo ?
Did you try refurbished method in NCS ? Save my silly ass several times
One time I even thought I bricked until finally manage to get mine 920 in flash mode...on youtube video seems so easy to get it..probably I was too impatience
Click to expand...
Click to collapse
When I tried using the program it says I'm not allowed, I heard on other forums that Nokia locked out consumers and made it private....
Not sure about the NCS method, never heard of it. Mind explaining?
yasha.sinitski said:
When I tried using the program it says I'm not allowed, I heard on other forums that Nokia locked out consumers and made it private....
Not sure about the NCS method, never heard of it. Mind explaining?
Click to expand...
Click to collapse
NCS = Nokia Care Suite...here in the forum there were links about version, which is working and connecting OK.

How do I recover from bad flash using WDRT?

It really doesn't work the way everyone says it should. I was trying to unlock the bootloader on my phone, and I made sure to download firmware for the phone that matched the model number. It was a Lumia 920 model RM-820 from AT&T, and the firmware I used was supposedly designed for that phone. The filename of the firmware I found was RM820_3051.50009.1425.2001_RETAIL_nam_usa_100_01_443332_prd_signed.ffu
Ever since I flashed it, it's been bringing up a frowning face and rebooting itself. I've been told to use the WDRT tool, but it won't recognize the phone no matter what I do. It keeps searching for the device and never finding it, no matter how many times I reset the phone or whether I pull up the screen with the gear and the lightning bolt by using volume up. When I use the screen with a gear and lightning bolt, the software tries to detect something, but it never gets any further than the "please wait" screen. Anything other than that mode completely fails to detect anything.
It's very difficult to find information on this problem, because a lot of the FAQs and guides are really old and full of dead links. I don't have any kind of real background in this, and I struggled to make sense of anything I was reading about this. I'm really kind of a moron when it comes to phones, and I was a little overconfident because I know what I'm doing with PCs. I really hate how phones obfuscate all the details, won't tell you what's going on, turn your device into a brick if you make one mistake, and make it so hard to do anything with a device other than what the manufacturer intended.
In all honesty, it's very likely that if I don't get this thing fixed, I'll probably end up putting my SIM card into a TracPhone or similar device for a couple months until I can afford a new phone. Could someone help out a total moron? Please?
EDIT: Well, you can actually go ahead and close this thread... I don't know what happened, but apparently my Mom was able to fix it. The procedure failed on my desktop PC, my Surface Book, and my old laptop... but my Mom tried to use her laptop, and somehow it worked. I wasn't even watching her, so I have no idea how, though. And she doesn't know anything about computers, but she somehow did in 10 minutes what I couldn't do in 2 days.
athenian200 said:
It really doesn't work the way everyone says it should. I was trying to unlock the bootloader on my phone, and I made sure to download firmware for the phone that matched the model number. It was a Lumia 920 model RM-820 from AT&T, and the firmware I used was supposedly designed for that phone. The filename of the firmware I found was RM820_3051.50009.1425.2001_RETAIL_nam_usa_100_01_443332_prd_signed.ffu
Ever since I flashed it, it's been bringing up a frowning face and rebooting itself. I've been told to use the WDRT tool, but it won't recognize the phone no matter what I do. It keeps searching for the device and never finding it, no matter how many times I reset the phone or whether I pull up the screen with the gear and the lightning bolt by using volume up. When I use the screen with a gear and lightning bolt, the software tries to detect something, but it never gets any further than the "please wait" screen. Anything other than that mode completely fails to detect anything.
It's very difficult to find information on this problem, because a lot of the FAQs and guides are really old and full of dead links. I don't have any kind of real background in this, and I struggled to make sense of anything I was reading about this. I'm really kind of a moron when it comes to phones, and I was a little overconfident because I know what I'm doing with PCs. I really hate how phones obfuscate all the details, won't tell you what's going on, turn your device into a brick if you make one mistake, and make it so hard to do anything with a device other than what the manufacturer intended.
In all honesty, it's very likely that if I don't get this thing fixed, I'll probably end up putting my SIM card into a TracPhone or similar device for a couple months until I can afford a new phone. Could someone help out a total moron? Please?
EDIT: Well, you can actually go ahead and close this thread... I don't know what happened, but apparently my Mom was able to fix it. The procedure failed on my desktop PC, my Surface Book, and my old laptop... but my Mom tried to use her laptop, and somehow it worked. I wasn't even watching her, so I have no idea how, though. And she doesn't know anything about computers, but she somehow did in 10 minutes what I couldn't do in 2 days.
Click to expand...
Click to collapse
I've had a similar problem with mine, bootloader unlock process didnt finish correctly and my Lumia 920 won't switch on, respond to Soft/Hard resets or respond to connections to the computer. WDRT and WPInternals no longer detect the device at all.
I hope someone knows how to sort this out

Categories

Resources