I have done a fair amount of research with my problem and would not post unless I was at wits end. So I made a terrible mistake and formatted my phone and took off my back ups. So after researching the problem I learned how to use ADB to either push or side load. Unfortunately my driver for my G2 is not present, and I have had no luck updating it. The device ID presently is USB\VID_18D1&PID_D001&REV_0232
I feel there is most likely an easy fix for my problem that I am overlooking but after hours of trial and error I am now completely out of ideas. My question is simple; how do I fix my driver.
Any help or suggestions would be much appreciated.
There is hope!
Denux2k10 said:
I have done a fair amount of research with my problem and would not post unless I was at wits end. So I made a terrible mistake and formatted my phone and took off my back ups. So after researching the problem I learned how to use ADB to either push or side load. Unfortunately my driver for my G2 is not present, and I have had no luck updating it. The device ID presently is USB\VID_18D1&PID_D001&REV_0232
I feel there is most likely an easy fix for my problem that I am overlooking but after hours of trial and error I am now completely out of ideas. My question is simple; how do I fix my driver.
Any help or suggestions would be much appreciated.
Click to expand...
Click to collapse
I have a sprint G2 Rooted with TWRP I couldn't for the life of me get ADB working when i bricked doing an OTA. Go to this link and follow instructions EXACTLY!!! This is the only thing that saved my G2... let me know...
http://forum.xda-developers.com/showthread.php?t=2432476
Related
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
After reading http://forum.xda-developers.com/showthread.php?t=2433323 I am starting to think a lot of these topics go unanswered and point to a flaw in the flasher, my region.prop is also missing and can only presume the tablet requires this for an update and the factory reset removes the root so cannot push another .prop over. So for all intents and purposes the tablet be fooked. I really do hope I am wrong but if i am right then why is this flashing tool still available after so many screw ups.
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job. I've flashed many things over the years and never screwed one up so this is bit of a shock to the system, My first reaction to your reply was to reply don't be smart then my second was to go check tool again, then third was ah f*#k. 26 letters in the alphabet and sony had to call the next model an S too. I cant say i keep up with tablet technology so thought they same thing pre flash,I didnt expect my tablet to be replaced in market so quickly after i bought one. Oh well lesson learnt now the question is wtf can be done if anything. If i send in for repair do they spot this instantly and try hammering me for a heavy bill to fix. Its under guarantee but they do say software issue they wont touch it.
I did read a lot about these problems but only reference i can find was today on page 36 of the flasher tool post. I blame mondays and my obvious lack of cognitive skills on them.
dex9mm said:
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
Can it be fixed?
nkxtc said:
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job.
Click to expand...
Click to collapse
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
soilchemist said:
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
Click to expand...
Click to collapse
Now thats why i thought it was ok i read that site first too rather than here. Too much reading after the event not before. So who are these idiots at androidadvices.com? The advice below is from that site and is what got me to reset tablet. Now i'm even more annoyed at this.
Note: Just in a rare case if the device doesn’t boot up or show the home screen then long press the power button to turn off and then re follow the instructions.
nkxtc said:
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
Click to expand...
Click to collapse
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
stifilz said:
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Click to expand...
Click to collapse
nkxtc said:
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
Click to expand...
Click to collapse
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Here comes a rant
stifilz said:
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Click to expand...
Click to collapse
I did notice but i eternal optimist and sorta hoped they different files even though filesize gave it away plus I already had that file from your links in sig but wouldnt be first time a company names files the same but different regions. Factory reset did numerous times now.
Didnt realise could get adb from logo screen so got hopes up again when lo and behold there in device manager was MTP device. After couple hours messing with it and getting lots of errors saying no driver etc I figured out putting hardware id in different adb usb driver inf files (USB\VID_054C&PID_05B3&REV_0100) would give me a working driver or so I thought. The PC decided after few minutes to give yellow exclamation and driver no longer works. Persevered with it until got driver stable but from command prompt adb says no devices in list.
Now all this happened early hours since 3am so not having greatest amount of patience (4hours not bad) i took a huff turned everything off and said [email protected]#k it ive had enough. This aint ever gonna work im resigned to this fact.
Now i may have not read one tiny part of the AIO tool which turned out to be biggest mistake i made in all this however for anyone else unfortunate to have a blonde moment would it not be possible to put some sort of checker in the tool to determine what is actually attached to be flashed based on hardware ID or something before any system changes occur. Having flashed many many devices from phones to consoles each and every one has a check of some sort before hand.
However putting that aside I think its disgraceful how Sony have treated this tablet and how locked down it actually is. This pains me but the £300 wouldve been better on a damn ipad.
@stifilz appreciate help you tried to give mate
Hey, so I've looked through these forums, as well as google search, with every combination of words i could think of to address my issue, and so far nothing has worked. So im posting here, hoping y'all can help me.
My phone is the Lg optimus L9 p769 running FW v20h. I had it rooted, bootstrapped cwm recovery is installed and still accessible. Unfortunately for me, i had disabled usb debugging off. Cant remember why, but I did.
I was browsing around for build.prop tweaks, found a good list, and implemented a few. After reboot, everything was going smoothly, hell, faster and smoother than before, which i assume came from tweaking the build.prop. At that point, i chose to implement 1 more and be done. So i added the line and rebooted my phone. SOFT BRICK!!!!!
Now, as i said, ive done quite a bit of searching for a fix, including the offline fix and basic LG Support Tool restoration, but nothing is working. Offline fix says my phone is not connected. Online recovery says im already at the most recent FW available. Ive tried fastboot, but installing the u boot and x loader wont work. CMD doesnt recognize my phone when i try anything adb related (obviously, because usb debugging isnt enabled), nor does it recognize my phone as a fastboot device even with the phone displaying the mirrored logo and says fastboot v0.5 in the top right corner. Also, the bootstrap CWM wont mount my external SD, which has my build.prop backup on it.
So, basically, that what I've read into. A wall, so to speak. As a side note, my wife has the same phone with an unmodified build.prop. in fact, the only thing that i have done to hers is root it with the LGpwn app.
Now, is there anything i can do with this, other than throwing it against the pavement outside? While i think I'd get a sick satisfaction from that, it hardly solves my problem. Also, i called LG directly, but they won't help me at all without payment. Even with their CS rep saying it was their fault (because, of course, I'm not dumb enough to tell them I broke it by messing with the build.prop). However, the slight bit they did do remotely through the laptop had them going through the LG Service Tool.
Anyway, that's about it. It really is a great phone and i really would like to repair, rather than replace, it, but im stuck. Anyone got any ideas?
Hello,
I had a similar problem, offline method didnt worked for me saying that my device is not connected. Then I faund this tool on forum http://forum.xda-developers.com/showthread.php?t=2797190
Use it with described tutorial (use 3GQCT and DIAG) and you are going to unbrick your phone.
Ok, I'll give it a try when i have access to the neighbors laptop again. I'll post the results here. Fingers crossed, my phone is up and running again soon and I'll be able to post my results from my unbricked phone.
IT WORKED!!!!!
Holy hell, it worked! A week of searching and trying with no success, now my phone is up and running again! Thank you sooooooooooooo much! Can i get a solved tag?
You're welcome. I'm glad I could help
Hey guys. I got a phone from a friend and decided to perfom a soft reset just for the heck of it. Well unbeknownst to me, that phone was rooted. And well. You know the rest. Anyways. I looked into ways to fix it and there are so many different methods out I just get confused trying to do any of them I have a computer with Windows seven at my disposal. I have searched and couldn't really find a forum specific to my device but any help would be appreciated. The person who rooted this phone did not set up any recovery on the phone (sigh) but I can get it into a mode where it says "firmware update" and the download is stuck at zero cuz obviously there isn't anything being downloaded. Any help would be appreciated :good:
Actually I just remembered I wasn't trying to reset it I was trying to update it.
Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.
Okay, so I apologize in advance if this cannot be posted here. My reason for doing so, is because I need some help with a Zenwatch 2 by Asus and the thread pertaining to this device seems to be a ghosttown. So if you need, please move this where it should go, but not without offering a word of advice or two first
So obviously I have a zenwatch 2, and I was tinkering with it earlier, and somehow got it stuck in CVC fastboot or something like that. I was able to get TWRP on it (Thank god, im much more optomistic now) but I am still having trouble getting an OS back on it. At first I wasnt even able to read the internal storage from my computer, or even begin to sideload anything, but I went into the TWRP settings and repaired the partitions to EXT4 or something of that sort. Now I am able to sideload, as well as access the storage from my PC, but I have had no success in flashing a working OS.
Im usually pretty familiar with android, rooting and unlocking, but these watches seem to be a bit different.
If anyone has anything that would help, please feel free!
The exact model of watch I have is WREN W1502Q .... I think.
Thanks in advance!
UPDATE:
I got it to boot!! Now I am stuck with a hang on that screen with all the swirly dots (the four separate animations that is right before boot)
So we're making progress, but I dont know if it is just gonna take a long time to boot, or if it is hanging! Hopefully we can get over this last hump. Thanks!
UPDATE 2:
Back up and running!
Praise the Lord!