I'm trying to root my Unlocked T-Mobile G1 via Kingroot. I followed the procedure step by step. (I mean, c'mon, how hard is it to use this program, really?) Obviously I'm very new to most of this, but I have done my research on Rooting! I know the Pro's and Con's, I know there are multiple ways to do this ( Some requiring a bit of know-how with the computer language) and I figure this way is the easiest ((for me)).
Here is my issue.
I downloaded all the drivers. I turned on Android USB Debugging. I've mounted the SD card. I plugged it all in, and got the page with the lovely, red "ROOT" button. I pushed it. I pulls the scripts, it checks the connection, it begins the process. My device goes black very briefly then appears all of these lovely colors (Red, Orange, Yellow, Blue, Green, White) It displays the model number, manufacturer date, phone model, phone company it was sold to, etc. And it sits. The program reads "Waiting for Device." for about 2 or 3 minutes, then it says "Root Unsuccessful! WaitForDeviceTimeOut!" I checked and re-checked the list of compatible devices, and mine is on there. (Though it is called an HTC DREAM instead of T-Mobile G1 but I doubt that truly matters.) I then disconnect the phone, pull the battery, turn it back on, it's fine. I've tried this several times to no avail. I'm not using the original USB cord, but my computer and the program reads it, It stays connected. It charges.
Am I missing a step?? Doing something wrong?? Is there another, newbie proof way I can root this phone?? I figured this was the simplest, without having to manually hack into my phone and type commands into it. I've googled and googled and googled this problem, with no result. Kingoroot seems to be rather new, and though I messaged the support team, I've yet to hear anything back.
Any suggestions would be helpful. Sorry if this is a stupid post.
Thank you!
Rooting the g1 by the "old" method is very simple and I'd be happy to walk you through it, but feel free to use any of the one click apps, most of those came about after I learned things on my own and since that time I've always been against do-it-for-me-tools of any kind as there is no knowledge to be gained
Let me know if you need a hand with the old school way otherwise search out one of the many other one-click-root options for the dream (same thing as g1)
Sent from my Nexus 4 using Tapatalk 2
Related
First off, I want to thank the wonderful amount of knowledge and help here at XDA! Not to be impolite to anyone else, but through all my searching, I have yet to find anything like this forum (and I come from a number of forums); but none have had quite the caliber of kind, knowledgeable, and often humorous: people. So thank you all. Also, another disclaimer is that I've only been on Android for about a month and half, so please bear with me as I might (and probably) misuse vernacular and/or might not completely understand some of the technical lingo' (at least the first time through, but I have spent much time here reading through help guides and threads).
Alright, here's the problem: I cannot get a computer to recognize the Vibrant. Installed all the drivers I have found thus far, followed a number of guides from here at xda, and have tried a number of different computers (two Win7 machines, a Vista, and even two XP machines); all of which recognize my personal Vibrant without a hick-up. Here is perhaps the biggest, and main, problem: the computers/odin won't even recognize it in Download Mode. That is what is stumping me..
If you do not care to know about how I got to where I am, please jump to the 'Question:' part.
Here is the back-story:
I bought a used Samsung Vibrant that came with the JI6 build. This was the second vibrant I had purchased as it was for my sister; and for the most part (other than it being horribly slow on the 'stock' build) it was running, and perfectly functioning.
However, I did notice that it was not able to connect it to a computer; usb debugging, mounting sd, and all the guides I found for troubleshooting just didn't seem to do the trick. Still no connection to the pc. I eventually educated myself on Download and Recovery mode, both of which I could execute without really any problems.
But since I wanted to run a faster OS (And I had already successfully flashed my personal Vibrant to Froyo (Build 21VE) (Here)) I decided to flash my sister's vibrant as well. And since I was unable to connect via usb to use odin to flash to the JFD build (per highly suggested here on xda), I used a nandroid image to flash the stock JFD build from Samsung (I can't find the link at the moment, but it was here from the xda forum). All went well, I was on JFD. I then used the above link to flash the Froyo21VE build via clockwordMod; again, it went smoothly. Only one problem persisted at this point: the wifi would not work.
My brother had experienced a similar issue with his Vibrant's wifi a few weeks previous, but had resolved it by flashing a different Froyo build. Naturally I thought I might do the same. This is where things went South.. Perhaps I was multi-tasking too much at the time, or possibly I just wasn't paying attention, but after a quick google search I found this Froyo build here on xda: [ROM] Froyo (RS)JP5 - "K9" [25/11/2010]. Moved it onto the internal sd card; flashed via clockworkMod; and then it froze on its boot-up after installation. Not cool..
Unfortunately, I was not aware that the build was for the Galaxy S i9000 rather than a Vibrant branded Galaxy; once realized though, my gut sank.. As now I am wondering if I completely tanked this Vibrant; or perhaps it had a problem from the bigging in that the usb wasn't connecting?
Question:
First and foremost, is there an 'advanced' way of connecting via usb from a computer, or some other way of doing it? I have tried numerous usb cables (as I've read a couple different people were having success with that) on several different computers (all of which, though, seem to be working perfectly on my personal vibrant, just not this one). Or is there a special driver that allows for just the 'Download Mode' on the Vibrant to communicate to the pc? But from my understanding, it seems as though the 'download mode' is pretty much as basic as you can get, am I correct in that assumption? Additionally, would using the android sdk help at all? (Or again, doesn't it have to be able to be recognized from the computer first?)
And lastly, just in case I thought it wasn't complex, when I had a functioning OS on the Vibrant: when I plugged in the usb, the Vibrant would show that it recognizes the pc; I even could 'mount the sd', but the computer still wouldn't recognize it apart from a few times that it would show it as 'unknown device' and would not seem to load any drivers; and I was having difficulty locating the device in Device Manager. (But that only seemed to work when I had a functioning OS, now that it only can go into ClockworkMod or Download Mode, I have yet for the computer to acknowledge its presence)
Alright, there it is. Please let me know if I missed something, or if more information would be helpful. Again, I want to thank anyone who would be able to help me out, or give suggestions. I really am at a loss for ideas; and the past week of analyzation is hardly showing any signs of improvement.
Thanks for taking the time to read.
EDIT: it occurred to me that I didn't mention that I am unable to load any *.zip files while in ClockworkMod (thus being able to flash a different build). It continually gives a 'No File Found' or Error/Wrong command. I believe that was caused by the i9000 firmware messing up the file system on the Internal_sd, does that seem logical?
Have you installed kies from samsung? I tried installing just the drivers on my win 7 pc and they wouldn't take either. I then downloaded kies and installed and it seemed to properly install the needed drivers.
Sent from my Axura injected voodoo possessed Vibrant.
I believe I have installed it twice now, but I will try again. Thanks for the suggestion, I'm pretty much all ears at this point.
EDIT: Well I installed the Samsung Kies mini Apllication and it did its update thing and now I have v1.0.0.10104_1. Doesn't appear to have helped the drivers out..
Question: would anyone think that this particular Vibrant has a defective usb port? I realize that's a long-shot, as well as I would definitely not like hearing that.. but any thoughts?
shalom24 said:
I believe I have installed it twice now, but I will try again. Thanks for the suggestion, I'm pretty much all ears at this point.
EDIT: Well I installed the Samsung Kies mini Apllication and it did its update thing and now I have v1.0.0.10104_1. Doesn't appear to have helped the drivers out..
Question: would anyone think that this particular Vibrant has a defective usb port? I realize that's a long-shot, as well as I would definitely not like hearing that.. but any thoughts?
Click to expand...
Click to collapse
It appears that you have a defective USB port on the phone.
Do you have an access to a Linux box? If a current linux distro cannot see your phone via USB it will confirm the DOA USB port on the Vibrant.
Thanks for the reply lqaddict, although it's somewhat sad to hear.. Forgive my ignorance, but by 'Linux Box' you are referring to a Linux machine, correct? If so, then I do not have access to one. Again, forgive me for not knowing, but would running linux (possibly via a bootable Linux cd) on a computer be equivalent?
Since I purchased it used (through Craigslist about three weeks ago (which he said he had purchased two weeks previous)) do you think I might be able to retrieve the receipt from the original owner and perhaps Samsung would be able to help with some sort of warranty?
Thanks again for your response.
EDIT: Well I am running Live CD of Ubuntu 10.10 on another one of my pc's, however, I'm not quite sure I know how to 'check' to see if usb port is properly functioning (sorry I'm not very familiar with Linux, but I imagine I will become increasingly more accustomed to it in the near future). Any ideas for trying out connectivity on Linux?
shalom24 said:
Thanks for the reply lqaddict, although it's somewhat sad to hear.. Forgive my ignorance, but by 'Linux Box' you are referring to a Linux machine, correct? If so, then I do not have access to one. Again, forgive me for not knowing, but would running linux (possibly via a bootable Linux cd) on a computer be equivalent?
Since I purchased it used (through Craigslist about three weeks ago (which he said he had purchased two weeks previous)) do you think I might be able to retrieve the receipt from the original owner and perhaps Samsung would be able to help with some sort of warranty?
Thanks again for your response.
EDIT: Well I am running Live CD of Ubuntu 10.10 on another one of my pc's, however, I'm not quite sure I know how to 'check' to see if usb port is properly functioning (sorry I'm not very familiar with Linux, but I imagine I will become increasingly more accustomed to it in the near future). Any ideas for trying out connectivity on Linux?
Click to expand...
Click to collapse
When you connect your phone via USB, does a USB connected symbol show up on your phone? Does the battery start charging?
You can issue the following command in the terminal window - should be in Applications->Accessories on Ubuntu (it resembles MS-DOS window under Windows OS)
Code:
lsusb
If the Samsung device shows up the USB port on your phone should be working, if however it is not showing up you might have a bigger problem with your phone
Thanks again lqaddict, I'll give it a try..
EDIT: Alright, to answer your first question: yes when I plugged it in while off, it does give the battery charging icon, as well as it does give juice to the battery.
Additionally, I ran the suggested "lsusb" in the Linux Terminal while the Vibrant was in Download Mode, and I didn't seem to get too much in the way of interest of the Vibrant except this line:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Would that possibly be the Vibrant? Does "Linux Foundation" refer to a Linux device? Then again, I just ran it another time without the Vibrant plugged in, and it yielded the same results.. So, most likely.. dead usb port?? Or perhaps is this just a weird phenomena? Thanks again, for all the suggestions and comments; hopefully I'll be able to one day return the favours to others here on xda.
Sorry, looks like you have a faulty usb port on your phone
Sent from my Nero powered Vibrant
Thanks for helping troubleshoot that, however unfortunate it was to hear... Perhaps one last question though, as I would like to make sure I 'cover my basis', so to speak, would anyone have suggestions as to what to do when I talk to Samsung? Or would anyone know what the procedure is like; I have dealt with a faulty iPone 3gs before and basically all I did was wait for the replacement in the mail, and ship the faulty one in the same packaging. I realize I will need to contact them, but would anyone know what information they might need from me? (as in would it be a problem that I might not have an original receipt? (I contacted the seller about that, and have yet to hear back))
Simply put, while I have had Samsung products in the past (and have been for the most part very satisfied with said products); I would, however, like to make sure I don't mess something up within the warranty process for the Vibrant (at least in consideration that I wasn't the first purchaser; then again, I would hope that they would cover the 'basic' quality issues of their products for at least the normal 90 days.. but what do I know..).
Whatever the case my be, I greatly appreciate the help I've received here; if for nothing else, perhaps it will be useful in someone else's mishaps in their Android journey. Thanks again, and I will be exceedingly grateful for any further suggestions on the matter.
shalom24 said:
Thanks for helping troubleshoot that, however unfortunate it was to hear... Perhaps one last question though, as I would like to make sure I 'cover my basis', so to speak, would anyone have suggestions as to what to do when I talk to Samsung? Or would anyone know what the procedure is like; I have dealt with a faulty iPone 3gs before and basically all I did was wait for the replacement in the mail, and ship the faulty one in the same packaging. I realize I will need to contact them, but would anyone know what information they might need from me? (as in would it be a problem that I might not have an original receipt? (I contacted the seller about that, and have yet to hear back))
Simply put, while I have had Samsung products in the past (and have been for the most part very satisfied with said products); I would, however, like to make sure I don't mess something up within the warranty process for the Vibrant (at least in consideration that I wasn't the first purchaser; then again, I would hope that they would cover the 'basic' quality issues of their products for at least the normal 90 days.. but what do I know..).
Whatever the case my be, I greatly appreciate the help I've received here; if for nothing else, perhaps it will be useful in someone else's mishaps in their Android journey. Thanks again, and I will be exceedingly grateful for any further suggestions on the matter.
Click to expand...
Click to collapse
Contact Samsung what have you got to lose? The phone comes with 1 year manufacturer warranty, and it has been on the market since mid July 2010, so it is not even 6 month old.
Yea, I don't mean to be too non-committal, I just don't want to mess up a warranty; if that makes any sense. And hopefully the ~210 people who have viewed this thread thus far will find a conclusion of the situation somewhat helpful. I'll update this thread once some of the dust settles.. I'm most definitely a fan of xda! Thanks for all the help everyone!
EDIT: Contacted Samsung, and after listening to the 'did you check this list' for about five minutes, I received a free shipping label and they said it was covered by the 'repair warranty'. I'm optimistic that something good will come of it...
EDIT_2:
Well, what do you know, just got the package/phone a little under an hour ago. First of all, compliments to Samsung! Fantastic communication and customer service! I really thought that the Vibrant was unrecoverable and that I would most likely have to pay for a new one; but I was wrong! Opened the sealed package with the original Vibrant (I knew it was mine since I had already but a BestSkinsEver skin on it) and plugged it into the computer at, Wohla!, Odin recognized, Windows/drivers recognized, and I'm up and rolling!
Thank you once again everyone for the comments and helpful input! And know that Samsung rocks! (I won't be going back with apple products anytime soon..)
I recently picked up a Samsung Admire. It has Gingerbread 2.3.4, and my computer's running Vista 64. When I first got, it showed up on My Computer, but then it randomly stopped. I've tried everything I can think of to no avail. I've swapped USB ports, tried uninstalling and reinstalling the drivers, tried getting drivers directly from Samsung's website, tried debugging mode, tried going into Device Manager to find it there (where it does show up under Disk Drives and says it's working properly, but I can't do anything with it from there), etc, and still nothing. I've looked a several posts on here about it, too (which is where I got the uninstall/reinstall idea), but no luck (I'll admit I didn't understand some of what was said, as well...I'm not a phone guy, really). It's a brand new cord, too, in case someone mentions that.
It would be nice to be able to put stuff on it, so if anyone has any ideas, I'd certainly appreciate it.
Are you pulling down the status bar (at the top of the phone), and selecting 'Enable USB Storage'? Most android phones can connect to the computer and be seen by the device manager, but until the phone is told "OK, communicate with the computer", it will not actually let the computer access the file system.
ambiate said:
Are you pulling down the status bar (at the top of the phone), and selecting 'Enable USB Storage'? Most android phones can connect to the computer and be seen by the device manager, but until the phone is told "OK, communicate with the computer", it will not actually let the computer access the file system.
Click to expand...
Click to collapse
Oh yah, I forgot to mention it doesn't show up either way, whether that's enabled or not.
I guess I'll take it into the MetroPCS store and see if they have any ideas on what's up. I need to take it there anyway to find out why my reception is so constantly horrid. Worst reception of any phone company I've ever been with, and I've been with a few.
salihe66 said:
I recently picked up a Samsung Admire. It has Gingerbread 2.3.4, and my computer's running Vista 64. When I first got, it showed up on My Computer, but then it randomly stopped. I've tried everything I can think of to no avail. I've swapped USB ports, tried uninstalling and reinstalling the drivers, tried getting drivers directly from Samsung's website, tried debugging mode, tried going into Device Manager to find it there (where it does show up under Disk Drives and says it's working properly, but I can't do anything with it from there), etc, and still nothing. I've looked a several posts on here about it, too (which is where I got the uninstall/reinstall idea), but no luck (I'll admit I didn't understand some of what was said, as well...I'm not a phone guy, really). It's a brand new cord, too, in case someone mentions that.
It would be nice to be able to put stuff on it, so if anyone has any ideas, I'd certainly appreciate it.
Click to expand...
Click to collapse
Hi, i had the same problem with my admire but i have just recently found newly released drivers for the samsung from their website and now i have no issues with it anymore, you have to download the drivers for the samsung indulge YES THE INDULGE and it will operate perfectly..
Before I explain my problem, let me first say that I am a novice when it comes to modifying phones. Shortly after buying my Razr, I knew that I wanted to root my phone, but I didn't know how. I found a program (that I can't recall now) rooted it, and had no problems. My problem came when I wanted to accept the OTA upgrade. I tried using Voodoo to keep my root while I accepted the OTA update, but that's where things when wrong. I don't know everything that went wrong because it seemed like nothing that I was doing was having any effect. It was having an effect, but not the effect that I wanted. After some uneducated decisions on my part, I found my Razr stuck in a bootloop. After trying to "fix" things, I gave up on it, but I decided to hold onto the phone. I replaced it with an HTC Rezound and moved on. I chose the Rezound only because it wouldn't take long to get it and it was affordable.
Last week, I decided that using the Rezound (it's definitely not all bad) has made me want to revive the Razr. I ordered BlackHat's adapter and used MattLGroff's utility (http://forum.xda-developers.com/showthread.php?t=2192467) to wipe my phone and flash JB.
This worked, with two exceptions. First, the phone still wouldn't charge. I came across a forum post that talked about successfully charging a phone in the car when it wouldn't charge inside with a computer or wall outlet. I was skeptical, but it worked. After charging the phone in the car, I can now charge it inside with a computer or wall outlet.
The second problem remains, and I am wondering if something that I did to soft-brick the phone caused a hardware problem. That seems unlikely, but I am new to this, so anything's possible as far as I'm concerned. In the attached picture, you can see that the bottom third of the screen shows up almost like static on a TV, but it's broken down into a grid. Also, the right half of the screen shifts up almost the height of the screen. Both of these problems come and go, but the "static" at the bottom of the screen comes much more often. I have to navigate through folders and menus before the shifting problem happens. Regardless, if I am at the home screen, for example, and I shift right or left (or navigate anywhere for that matter), the screen will be clean with no errors for a moment. After a second or so, the glitches usually show up.
I almost forgot about the last issue. When I wake the screen, it's quick and responsive; however, when I turn off the screen (by tapping on the power button), there is a lot of lag in the animation. Normally it would be a quick and smooth transition to the thin, horizontal line, and then it would quickly disappear. Now I can watch as it slowly blurs and stretches. It works, but it lags. This happens every time I turn off the screen.
Does anyone know what could cause this? Am I beyond repair? After typing this out, I doubt that it's a hardware problem, mainly because the static and shifting are not constant. But again, I'm totally new to this.
If anyone has any suggestions that involve utilities, then it would be ideal if I can use Linux. I have access to a Windows computer, but not at home.
Thanks in advance to anyone who can offer some insight.
Does anyone have any insight into this? Two months later and I'm still stumped. It doesn't matter how I use MattLGroff's utility...the same issues are still present. Could I maybe use a utility that will revert me to an older system? That way, I might be able to receive an OTA upgrade to JB.
I'm grateful for ANY input...
Thanks!
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
AztekSoul said:
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
neffje said:
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
Click to expand...
Click to collapse
hi,i had the same bug with rds lite didn't show me the spec of the phone,but only --------.
try anyway and remember to have the motorola driver in the pc (i don't know if works with wine,i had try only i my other windows pc)
Sorry if this is in the wrong subforum, and I'm sorry to cause trouble if you have to move it. I've been a google-searching lurker for years now, but I made an account just to ask this question so again, I'm sorry if I placed it wrong.
Yes, I have a good old Pantech Pocket P9060, good ol' 2.3. I love the little thing but like always, I want to get this thing rooted. I've rooted before, but it definitely wasn't as difficult as this thing.
Every website I've been to, and my google searches are all purple links now I've been at this for hours, make it look so fracking easy (it's such an older model, after all), but for some reason mine just won't budge.
I downloaded and installed JDK, I've got the ADT bundle, I've downloaded the packs, I've got the drivers, I've got SuperOneClick, I've unmounted the SD card, I have it in USB debugging mode, I've followed all these webpages to the letter and for some reason it just won't work for me. I've done literally everything, but obviously there's gotta be something I'm not doing hidden in the void that is the steps to get this thing rooted.
I've tried having the SD mounted, I've toggled a few options, I've reset the phone while it was plugged in, I've manually updated the drivers...nothing.
There was even one page that said to dial some #*#* number but it wouldn't let me type in the whole thing, it was one * character too long. I just can't do it.
S1C keeps freezing at "starting adb server" which I see is a common problem, except they usually end up getting it resolved by doing something that, in the end, doesn't work for me. I'm past the point of pulling my hair out. What is this things problem? What am I missing?
Again, sorry if this is out of place.
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