Hi all, sorry if this issue has been addressed elsewhere, but I haven't been able to find it.
So, after downloading the latest factory image and doing flash-all in fastboot (to BOTH slots, by using --set-active=other)..... I (maybe stupidly) decided that since I received the phone (replacement) with the active slot being "a", that's how I would like to use it, rather than the state it was left in after flashing the factory images, which was active slot b. So I rebooted, and used fastboot to switch back over to slot a, thinking....well, being as I just flashed the same exact material to each slot, it shouldn't matter which one I used. ...However, after doing that, the phone wouldn't boot. It would get as far as the bright white Google screen and then go black. And for a while, it seemed I wouldn't be able to get back into the bootloader either. I thought I was bricked. But after holding VolDown and Power for MUCH longer than I normally have to, I was able to get back into bootloader, and reflashed the factory images on slot a, and now all seems well.
What the hell did I do wrong? Am I missing something obvious?
Thanks very much everyone.
Whatever it is you did don't do that again. Problem solve. Lol no man I've never actually had this issue, however I've also never tried to switch slots after flashing a factory image like that. Definitely weird. Closest thing I've heard is someone doing something similar after receiving an OTA. I know the way OTAs work are that they flash it to the opposite slot so that if something goes wrong the phone can revert back to the other slot.
:::Edited for grammar.
bump.
Does anyone else have further insight on this? Currently have Pixel stuck in this situation.
bdawwgg, were you referring to the situation that I was in, or the situation Phalanx was talking about -- switching slots after an OTA? Because if you're where I was, there should be a way out pretty easily. What exactly is your situation?
sorry, i can't explain why that happens but something similar happened to me before. i flashed a factory image to both slots, starting with slot a. when i was done, the phone booted in slot b. i wanted to switch back to a, because alphabet, so i used fastboot to do it. after this, my phone started behaving weird. it happened a while ago, so i don't recall exactly what happened. so now, i leave the phone on whatever slot it boots up in. when i flash a new rom, i flash to slot b first.
Well thanks for the replies you guys. This is very, very interesting indeed... because it would appear that quite a few of us (at least) are cognizant of this issue, or have even experienced it ourselves in some cases. And yet, the problerm doesn't seem to be being discussed in a widespread manner. And by the way altwu, unless I'm missing something, your situation was not just similar, what happened to you was *exactly* what happened to me, and we got there by following the *exact* same set of steps.
It would be really great if someone with some advanced knowledge of the inner workings of this phone could explain to us just what is going on, and why. I feel like knowing the answer to this question would provide more insight into the specific way this multi-slot system works, and maybe even establish some further "Dos and Don'ts" for when you're flashing a device like this.
dht2005 said:
Well thanks for the replies you guys. This is very, very interesting indeed... because it would appear that quite a few of us (at least) are cognizant of this issue, or have even experienced it ourselves in some cases. And yet, the problerm doesn't seem to be being discussed in a widespread manner. And by the way altwu, unless I'm missing something, your situation was not just similar, what happened to you was *exactly* what happened to me, and we got there by following the *exact* same set of steps.
It would be really great if someone with some advanced knowledge of the inner workings of this phone could explain to us just what is going on, and why. I feel like knowing the answer to this question would provide more insight into the specific way this multi-slot system works, and maybe even establish some further "Dos and Don'ts" for when you're flashing a device like this.
Click to expand...
Click to collapse
Slot_A-B How to Flash Roms/Magisk/Kernel 8.1??? by Mikkey81
Homeboy76 said:
Slot_A-B How to Flash Roms/Magisk/Kernel 8.1??? by Mikkey81
Click to expand...
Click to collapse
Hey Homeboy! I actually used your guides to get me through the basics of understanding this phone. Thank you so much for your work.
By the way, if you're referencing something particular in the thread you linked, could you point it out?? ...Because... I don't want to be disrespectful, but it sort of seems like quite a bit of the stuff in Mikkey's thread is outdated... for instance, what he says about TWRP versions... according to what I've read from everyone else, and my own experience, the NEWEST TWRP is now the best to use; no reason to use an outdated one. And also, I find his writing a bit difficult to parse, because he's got a number of grammatical irregularities and mistakes... which he actually references at the bottom of his post, in his editing note, "because I can't read or write." Oh and lastly, the last update was back in March...
Anyway, I'm sure he's got some great knowledge, but that's part of the reason I gravitated more to your guides, and a few other people's work, too. Your clarity and organization made for a much better resource.
So if you were pointing out something specific in his thread, could you let me know what it was? Thanks so much.
dht2005 said:
Hey Homeboy! I actually used your guides to get me through the basics of understanding this phone. Thank you so much for your work.
By the way, if you're referencing something particular in the thread you linked, could you point it out?? ...Because... I don't want to be disrespectful, but it sort of seems like quite a bit of the stuff in Mikkey's thread is outdated... for instance, what he says about TWRP versions... according to what I've read from everyone else, and my own experience, the NEWEST TWRP is now the best to use; no reason to use an outdated one. And also, I find his writing a bit difficult to parse, because he's got a number of grammatical irregularities and mistakes... which he actually references at the bottom of his post, in his editing note, "because I can't read or write." Oh and lastly, the last update was back in March...
Anyway, I'm sure he's got some great knowledge, but that's part of the reason I gravitated more to your guides, and a few other people's work, too. Your clarity and organization made for a much better resource.
So if you were pointing out something specific in his thread, could you let me know what it was? Thanks so much.
Click to expand...
Click to collapse
The guide may need some work, what guide doesn't, but the information about what slot to flash what to and the twrp information was accurate. Some custom ROMs still use twrp 3.2.0-0.img.
Related
I ahve been running mightyrom on my tp2 with Cricket. I let it get wet, (a wet towel got thrown on it), and now I have a tri color with errors when turning it back on. I was actually relieved to see something, cause it took a day of it sitting on an AC to get it to do ANYTHING.
Now, the error reads Microp(led) wrong plat (0x0). I figure I lost everything, but now am just trying to salvage the phone.
So the question is, where do I start from here?
I would be happy just to get it working again, but its not a normal starting point and I don't want to do more harm not knowing where to start
Now I have another question as well, just because I'm greedy I'm probably being foolish, but nonetheless, I'll ask it. Would there be any benefit to moving towards android? I know I have been able to save desktops, and hard drives using linux, would this make it easier, harder, etc....?
I did look through the forums, but this seems to be a kind of unique starting point, and the android is new to me as well.
Thanks in advance for any help, and thanks for all the help in the past.
Nick
nickyjpd said:
I ahve been running mightyrom on my tp2 with Cricket. I let it get wet, (a wet towel got thrown on it), and now I have a tri color with errors when turning it back on. I was actually relieved to see something, cause it took a day of it sitting on an AC to get it to do ANYTHING.
Now, the error reads Microp(led) wrong plat (0x0). I figure I lost everything, but now am just trying to salvage the phone.
So the question is, where do I start from here?
I would be happy just to get it working again, but its not a normal starting point and I don't want to do more harm not knowing where to start
Now I have another question as well, just because I'm greedy I'm probably being foolish, but nonetheless, I'll ask it. Would there be any benefit to moving towards android? I know I have been able to save desktops, and hard drives using linux, would this make it easier, harder, etc....?
I did look through the forums, but this seems to be a kind of unique starting point, and the android is new to me as well.
Thanks in advance for any help, and thanks for all the help in the past.
Nick
Click to expand...
Click to collapse
First off this is in the COMPLETELY wrong forum. This is the Android port forum, not the Windows Mobile ROM forum. Please for future reference double check you are posting in the correct forum.
If you are still getting boot loader (tri color screen) then not all hope is lost. You need to get the stock TP2 rom for whatever company's TP2 you have (tmobile, att, etc) not a cooked rom the STOCK rom, from the TP2 Wiki. if you can get your phone to at least connect to USB (when on the tri color screen it will say "usb" on the very bottom if its got a working connection) then you may be able to run the stock rom to save it.
It could still be broken tho, water damage is a funny thing sometimes.
hi everyone! I am seeking your expertise as I came upon this forum trying to help my son fix his phone. He's only 11 years old- but as we call him at home our "tech guy". He got a brand new HTC One M8 (carrier is ATT) yesterday and 3 hours later - the phone was "bricked" as I have been told. Apparently, (these are his words) he "unlocked the bootloader using HTCdev, then flashed twrp, then flashed supersu.zip.
I have no idea what any of that means but apparently he did something wrong because his phone is not working and we don't know how to fix it. If you have any compassion for a frustrated Mom who's trying not to be angry with her son -- I would appreciate any advice you can give on how to fix this.
I have attached a picture of what the phone looks like when we turn it on. I also posted this under the ATT forum too.
Thanks in advance for your help!
You bought your 11 year old son an M8?
Do you adopt?
Bchgirl19 said:
hi everyone! I am seeking your expertise as I came upon this forum trying to help my son fix his phone. He's only 11 years old- but as we call him at home our "tech guy". He got a brand new HTC One M8 (carrier is ATT) yesterday and 3 hours later - the phone was "bricked" as I have been told. Apparently, (these are his words) he "unlocked the bootloader using HTCdev, then flashed twrp, then flashed supersu.zip.
I have no idea what any of that means but apparently he did something wrong because his phone is not working and we don't know how to fix it. If you have any compassion for a frustrated Mom who's trying not to be angry with her son -- I would appreciate any advice you can give on how to fix this.
I have attached a picture of what the phone looks like when we turn it on. I also posted this under the ATT forum too.
Thanks in advance for your help!
Click to expand...
Click to collapse
Going by the pic, the bootloader has been relocked. So that's a problem. The bootloader will need to be unlocked again. I would suggest heading over to Youtube, as I have found video tutorials the most helpful when I was learning this stuff. There are plenty of videos that are even specific to the M8.
Edit: I should also point out that a phone can almost always be saved/restored if it still powers on. So don't panic. It would probably be in your best interest though to find someone experienced to fix it. Trying to explain the process to fix it here is not going to be helpful to someone who doesn't know what they're doing. If you can't find someone experienced, then my best suggestion, as stated above, would be to watch some Youtube tutorials on unlocking/rooting the M8.
Okay. In all seriousness.
When was this screen grab taken? In other words, is this your current position with the phone?
Relocked... etc etc
Are you in the US on AT&T?
Your tech son needs to restore ATT backup.. Hopefully someone in that forum has it
sent from my mobile device
UPDATE on my son
Thank you all so much for your responses! It is much appreciated. Believe it or not - this kid fixed it all by himself. Basically (remember I am not technical) he unlocked the boot loader then flashed a ROM onto an SD card and was able to load. Don't think I worded correctly - but I think you know what I am talking about -- it's fixed and working fine. WHEW!!
I guess he "retraced" the steps he did last night and was able to get it. Actually it's strange the first ROM he put on wasn't allowing him to find or pick up wifi. He found another and got it. This kid is good!
I will certainly keep the info to this forum handy because something tells me that I will be visiting again with this child..................
Have a great evening!!
p.s. I typed the wrong key -- he's 12 not 11 And - sure I'd adopt! But he did save up his own money to get this phone and only wanted it to do these "cool" things as he says to it.....rest of my family - we are simple and use Iphones -- sorry.
All I can say to this is Wow!!
Bchgirl19 said:
Thank you all so much for your responses! It is much appreciated. Believe it or not - this kid fixed it all by himself. Basically (remember I am not technical) he unlocked the boot loader then flashed a ROM onto an SD card and was able to load. Don't think I worded correctly - but I think you know what I am talking about -- it's fixed and working fine. WHEW!!
I guess he "retraced" the steps he did last night and was able to get it. Actually it's strange the first ROM he put on wasn't allowing him to find or pick up wifi. He found another and got it. This kid is good!
I will certainly keep the info to this forum handy because something tells me that I will be visiting again with this child..................
Have a great evening!!
p.s. I typed the wrong key -- he's 12 not 11 And - sure I'd adopt! But he did save up his own money to get this phone and only wanted it to do these "cool" things as he says to it.....rest of my family - we are simple and use Iphones -- sorry.
Click to expand...
Click to collapse
I'm glad to hear everything worked out for you and your son.
It's great to know that you're letting your kid tinker around as he is. I know these are quite expensive devices, but we often do learn from our mistakes, and that is even more true when it comes to technology. I'm sure that I have a bit of a bias being a software developer, but tech is such a huge part of life now, and that is only going to become more so with time. So getting an early start as he is, your son is going to have a leg-up in the world, even if he doesn't choose this type of field as a career path.
MindfulSheep said:
I'm glad to hear everything worked out for you and your son.
It's great to know that you're letting your kid tinker around as he is. I know these are quite expensive devices, but we often do learn from our mistakes, and that is even more true when it comes to technology. I'm sure that I have a bit of a bias being a software developer, but tech is such a huge part of life now, and that is only going to become more so with time. So getting an early start as he is, your son is going to have a leg-up in the world, even if he doesn't choose this type of field as a career path.
Click to expand...
Click to collapse
Agree! But keep an eye on him, so that he sleeps from time to time. And hide your car keys!
Please don't create multiple threads asking the same question.
http://forum.xda-developers.com/showthread.php?t=2750594
MindfulSheep said:
I'm glad to hear everything worked out for you and your son.
It's great to know that you're letting your kid tinker around as he is. I know these are quite expensive devices, but we often do learn from our mistakes, and that is even more true when it comes to technology. I'm sure that I have a bit of a bias being a software developer, but tech is such a huge part of life now, and that is only going to become more so with time. So getting an early start as he is, your son is going to have a leg-up in the world, even if he doesn't choose this type of field as a career path.
Click to expand...
Click to collapse
Thanks!! He's very into all of this stuff and always has been from a very young age -- started with Legos at 2. He doesn't play sports and this is his "thing". He really LOVES all this stuff. He's actually really good and understands most things. As you can see - we certainly have issues now and then but overall we certainly let him "tinker". I really should write stuff down so we can laugh about it in about 10 years. We tried to limit his Internet time a couple of years ago and added a password on his computer that we had to input on his computer to gain access. Little **** put a keystroke logger on the computer to get the password. Then he somehow modified the main password screen to say PENIS when we logged on. The stories go on and on....... We will let him continue his technology building and hopefully he really have a bright future in technology!
Thanks for all of the input and support from this forum!
Bchgirl19 said:
Thanks!! He's very into all of this stuff and always has been from a very young age -- started with Legos at 2. He doesn't play sports and this is his "thing". He really LOVES all this stuff. He's actually really good and understands most things. As you can see - we certainly have issues now and then but overall we certainly let him "tinker". I really should write stuff down so we can laugh about it in about 10 years. We tried to limit his Internet time a couple of years ago and added a password on his computer that we had to input on his computer to gain access. Little **** put a keystroke logger on the computer to get the password. Then he somehow modified the main password screen to say PENIS when we logged on. The stories go on and on....... We will let him continue his technology building and hopefully he really have a bright future in technology!
Thanks for all of the input and support from this forum!
Click to expand...
Click to collapse
I was the same from an early age and always have been. I have taken apart or modified more household items than I can think of. I broke a lot of stuff messing as a kid, but now I have a lot of knowledge and can fix almost any thing properly.
It seems you are not so bad yourself with the technical stuff as most moms wouldn't have a clue or even be able to repeat what you have explained here.
"Tampered" screen. S-On. HBOOT-1.57 with loop. Is there any way to save this phone?
So I was trying to follow the guide to completely return a phone to stock to return it to a seller due to hardware issues (they sent me a not so great repair job. I tried to live with it for a while but just couldn't.) But with missing files and etc I was having troubles getting it all to work. I probably should have just downgraded completely down to 1.10 or something. Anyway, I had the odexed full 4.10 installed but forgot that it wasn't quite 100% stock because I had to grab the TWRP flashable version. The intent was to let it do the OTA upgrade to 5.28 and be 100% stock (plus I wanted to be sure that the OTA function worked so the next person to get the hardware could get the 5.0 update whenever it hits. If. I didn't want them to be stuck with a partially working phone any worse than the already existing hardware problems.) Before the OTA update finished I thought I should S-On since all was working. Ok, I screwed up and I don't deny it. But now what do I do? From what I understand, the only way around the "tampered" bootloop is to flash a stock RUU. But thanks to Verizon's bloody bootloader lockdowns, options are extremely limited there and I can't just flash an older RUU. Since it's HBOOT 1.57, that means that the old 2.10 and lower RUUs aren't going to cut it and I'm not finding anything newer for the Verizon models anywhere. It's ridiculous that this situation even exists IMO since the whole goal here is to go back to 100% stock and their system to force people to stay stock is the very thing stopping me from doing so. But worse, it's now basically a brick...
Is there any way at all to save this phone, or am I utterly hopelessly screwed?
Nazo said:
So I was trying to follow the guide to completely return a phone to stock to return it to a seller due to hardware issues (they sent me a not so great repair job. I tried to live with it for a while but just couldn't.) But with missing files and etc I was having troubles getting it all to work. I probably should have just downgraded completely down to 1.10 or something. Anyway, I had the odexed full 4.10 installed but forgot that it wasn't quite 100% stock because I had to grab the TWRP flashable version. The intent was to let it do the OTA upgrade to 5.28 and be 100% stock (plus I wanted to be sure that the OTA function worked so the next person to get the hardware could get the 5.0 update whenever it hits. If. I didn't want them to be stuck with a partially working phone any worse than the already existing hardware problems.) Before the OTA update finished I thought I should S-On since all was working. Ok, I screwed up and I don't deny it. But now what do I do? From what I understand, the only way around the "tampered" bootloop is to flash a stock RUU. But thanks to Verizon's bloody bootloader lockdowns, options are extremely limited there and I can't just flash an older RUU. Since it's HBOOT 1.57, that means that the old 2.10 and lower RUUs aren't going to cut it and I'm not finding anything newer for the Verizon models anywhere. It's ridiculous that this situation even exists IMO since the whole goal here is to go back to 100% stock and their system to force people to stay stock is the very thing stopping me from doing so. But worse, it's now basically a brick...
Is there any way at all to save this phone, or am I utterly hopelessly screwed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=
santod040 said:
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
Looks like the thread number didn't make it in that URL either.
Nazo said:
Looks like the thread number didn't make it in that URL either.
Click to expand...
Click to collapse
I was mobile, laying down.
Got up to get on the PC to repost the link for you.....
http://forum.xda-developers.com/ver...-3-s-users-t2919442/post56302410#post56302410
Oh, gotcha. I for some reason thought from all those guides and such that you had to specifically flash a RUU zip file manually. I'll grab that and give it a shot. It sounds like just what I need.
EDIT: Thank goodness. This did it. 100% stock. I was afraid I wouldn't even be able to return it. I just hope the next user feels better about the incomplete repair job the seller (or whoever they got it from) did on it than I did. (Though the lack of a LED is a pretty significant problem. They really should have fixed that.)
Nazo said:
Oh, gotcha. I for some reason thought from all those guides and such that you had to specifically flash a RUU zip file manually. I'll grab that and give it a shot. It sounds like just what I need.
EDIT: Thank goodness. This did it. 100% stock. I was afraid I wouldn't even be able to return it. I just hope the next user feels better about the incomplete repair job the seller (or whoever they got it from) did on it than I did. (Though the lack of a LED is a pretty significant problem. They really should have fixed that.)
Click to expand...
Click to collapse
Did the led work at all...? Like when charging?
dottat said:
Did the led work at all...? Like when charging?
Click to expand...
Click to collapse
No LED under any circumstances at all. I can't even imagine how they managed to damage a phone in such a way that the LED would utterly stop working, yet it wouldn't require a new mainboard or something. I guess the only way to repair that would have been to replace said mainboard though. Well, no matter. This time around I decided it just wasn't worth trying to save the money buying a used phone and got one sold as new, sealed in box. If anything is wrong with this one I'll be amazed. (Well, barring the camera issue. *Fingers crossed*) One thing I can say though, the top speaker barely worked at all, so whatever they did probably did a decent amount of damage to the entire top section. I wouldn't be surprised if there were other troubles such as the front camera (I never use it) or maybe the sensors (though the light sensor seemed ok.)
BTW, the program did, in fact, work. I had it restored 100% to factory, tested it out, and found absolutely nothing wrong (at least nothing besides the problems the seller sent it with. I can't fix those...) I really hope the next person who gets stuck with it is happier than I was with those issues. I guess that's what one gets into buying used, but my previous experiences with such things were a lot better. (For instance, I fried my SGS3 via circumstances I don't want to get into right now. I bought one with a broken screen, swapped out the main board from it into mine, and presto, I had a once again working SGS3. Actually, it happens I ended up perhaps better off as it never seems to have had modem issues some others have had and the SoC seems to be stable at ridiculously low voltages if I were so inclined -- well, there's no real reason not to lower the voltage if it's 100% stable IMO, so I went ahead, but I didn't do an in-depth test to get the minimums.)
I'll just put this simply. I've got a splitting headache and I've been staring at various web pages for hours trying to (unsuccessfully) unlock the bootloader on my g4 so I can install twrp and root the thing. I'm about ready to kill someone. don't know who, nobody is around.
anyway.. I need a guide on how to transform my LG G4 US99120c US Cellular mobile device running Android 6.0 Marshmallow from a battery-draining eyeball-paining bright white piece of techno-trash into a rooted device with custom recovery that I can use on a regular basis without experiencing severe migraines because I can't delete stuff off the SD card due to carriers being pricks about released phones.
yes, I've tried google. Yes, I've tried searching the forums. If I hadn't done that already I wouldn't be posting here. please don't waste my time with "try the search feature".. I'm here because this is my last viable option for getting the damn thing working right. Please don't just link me to some random instruction manual either. I have bad luck with links.
If anyone does write me with help, write it for an idiot. Normally I'm pretty good at picking things up quickly but I seem to have come down with something the past couple days so I'm also a bit under the weather.. right around the idiot quotient.
I don't want to downgrade, I don't want to install half a dozen things or flash my whatchamacallit (got arrested last time I did that). I want to root the device, and possibly install xposed so I can change everything thats sharp white to a dull black. I do not want to do anything else at all but make calls, text, watch vids, listen to music and play the occasional game.
Thank you very much for your time, and a colossal chunk of gratitude for anyone who wants to take up this task.
FTR: I'm a former samsung user, so if you need to make comparisons I suggest using those. I'll understand 'em.
Jofreidr said:
I'll just put this simply. I've got a splitting headache and I've been staring at various web pages for hours trying to (unsuccessfully) unlock the bootloader on my g4 so I can install twrp and root the thing. I'm about ready to kill someone. don't know who, nobody is around.
anyway.. I need a guide on how to transform my LG G4 US99120c US Cellular mobile device running Android 6.0 Marshmallow from a battery-draining eyeball-paining bright white piece of techno-trash into a rooted device with custom recovery that I can use on a regular basis without experiencing severe migraines because I can't delete stuff off the SD card due to carriers being pricks about released phones.
yes, I've tried google. Yes, I've tried searching the forums. If I hadn't done that already I wouldn't be posting here. please don't waste my time with "try the search feature".. I'm here because this is my last viable option for getting the damn thing working right. Please don't just link me to some random instruction manual either. I have bad luck with links.
If anyone does write me with help, write it for an idiot. Normally I'm pretty good at picking things up quickly but I seem to have come down with something the past couple days so I'm also a bit under the weather.. right around the idiot quotient.
I don't want to downgrade, I don't want to install half a dozen things or flash my whatchamacallit (got arrested last time I did that). I want to root the device, and possibly install xposed so I can change everything thats sharp white to a dull black. I do not want to do anything else at all but make calls, text, watch vids, listen to music and play the occasional game.
Thank you very much for your time, and a colossal chunk of gratitude for anyone who wants to take up this task.
FTR: I'm a former samsung user, so if you need to make comparisons I suggest using those. I'll understand 'em.
Click to expand...
Click to collapse
ill lay it on wasy for you......... you cant unlock bootloader. you cant install twrp and you cant root MM. not unless bootloader unlocked. wich your phone cant be unlocked..
root only on locked bootloader on LP.
there isnt a way and there will never be one.. to bypass and be able to install twrp..
well that explains why fastboot refuses to acknowledge the existence of the phone. I guess.
never say never tho m8, geohot should be proof enough of that for you. looks like I can't downgrade either.
guess I'll have to stick with my s5.
Jofreidr said:
well that explains why fastboot refuses to acknowledge the existence of the phone. I guess.
never say never tho m8, geohot should be proof enough of that for you. looks like I can't downgrade either.
guess I'll have to stick with my s5.
Click to expand...
Click to collapse
there was a bounty of like 3000 dollars to whoever unlock it.. no one did it.. i said i might never be one.. thats waht everyone says samething.
This is a followup to an earlier post in another area and I've been advised I'd be better served to ask it over here in this area of the forum subset...
(Warning: Antique Phone Issues) - Moto Droid Turbo 2 Firmware update(Nougat 7.0)
I have perused the forums here and there seems to be some answers, but I am a noob, so I am trying to clarify some stuff for my own knowledge. I am NOT a developer and know an insignificant amount of info on phone rooting, bootloading, etc. This...
forum.xda-developers.com
I followed the basic steps provided and my PC doesn't see the phone connected to it, even after I've done the steps and uploaded the Motorola drivers, LMSA, etc on the PC. I am just dumb(again) and really don't know wtf I'm doing with this software/phone so before I brick it, I wondered if anyone would be interested in updating the software in my phone for a nominal fee? Common sense tells me that those that do this regularly can probably do this in a matter of a few minutes. If you are local(Indpls, IN), I can bring it to you, but I really don't want to spend a lot of money dicking around with an old phone. I hate to throw away this good(but old) phone, but Is there any interest in something like this? I am really fighting my common sense here and probably should just be getting rid of it and moving on. Thoughts?
88_pacifica said:
This is a followup to an earlier post in another area and I've been advised I'd be better served to ask it over here in this area of the forum subset...
(Warning: Antique Phone Issues) - Moto Droid Turbo 2 Firmware update(Nougat 7.0)
I have perused the forums here and there seems to be some answers, but I am a noob, so I am trying to clarify some stuff for my own knowledge. I am NOT a developer and know an insignificant amount of info on phone rooting, bootloading, etc. This...
forum.xda-developers.com
I followed the basic steps provided and my PC doesn't see the phone connected to it, even after I've done the steps and uploaded the Motorola drivers, LMSA, etc on the PC. I am just dumb(again) and really don't know wtf I'm doing with this software/phone so before I brick it, I wondered if anyone would be interested in updating the software in my phone for a nominal fee? Common sense tells me that those that do this regularly can probably do this in a matter of a few minutes. If you are local(Indpls, IN), I can bring it to you, but I really don't want to spend a lot of money dicking around with an old phone. I hate to throw away this good(but old) phone, but Is there any interest in something like this? I am really fighting my common sense here and probably should just be getting rid of it and moving on. Thoughts?
Click to expand...
Click to collapse
Windows 10?
might work easier if the Phone is in fastboot mode first.
sd_shadow said:
Windows 10?
might work easier if the Phone is in fastboot mode first.
Click to expand...
Click to collapse
Sorry, I forgot to udpate on the OS. It's old Windows 7(trying to keep it simple) and I tried to do the fastboot mode mode and it didn't seem to see it even after that. The phone doesnt acknowledge that it is in fast boot mode though when it turns on(does it normally say something?) after doing it. I am positive I'm an idiot and doing it wrong.
I am also wondering if there is possibly something wrong with the motherboard because the phone doesn't advise it is on a 'quick charger'(OEM Motorola cable and power supply) when I plug it in. It seems to charge just fine though. Weird...
88_pacifica said:
Sorry, I forgot to udpate on the OS. It's old Windows 7(trying to keep it simple) and I tried to do the fastboot mode mode and it didn't seem to see it even after that. The phone doesnt acknowledge that it is in fast boot mode though when it turns on(does it normally say something?) after doing it. I am positive I'm an idiot and doing it wrong.
I am also wondering if there is possibly something wrong with the motherboard because the phone doesn't advise it is on a 'quick charger'(OEM Motorola cable and power supply) when I plug it in. It seems to charge just fine though. Weird...
Click to expand...
Click to collapse
Is this a Verizon-branded device?
Yes, I did follow the Verizon specific instructions too.
88_pacifica said:
Yes, I did follow the Verizon specific instructions too.
Click to expand...
Click to collapse
So you are using this? http://www.motorola.com/VerizonSoftwareUpdateWin
Correct...
88_pacifica said:
Correct...
Click to expand...
Click to collapse
Try the regular LSMA version
Sorry if you have Windows 7 you might as well use
RSD Lite
Will do. Thank you...
DId you try these drivers?
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
mobilesupport.lenovo.com
I am sure that you are a guru at this type of thing(obviously) and could build your own phone with all the knowledge you've gained, but I've been fooling with this phone most of the day and am getting nowhere. I am to the point that I would either dump it or send it to you and let you do your magic. Would you want to piddle around with it? I am just too computer illiterate to make this work apparently.
Don't feel like you have to do this or give any more advice. I'm about tapped out now on jacking with this thing and just have to know my limits. I can fix any car(or truck) as I am a former ASE mechanic, but this damm phone has me beat...