I did a stupid thing today. Had issues with my P769 lagging due to different mods I have been doing. I figured I would do a nice clean install.
Rebooted into TWRP and did a full wipe. OK, that's pretty standard with me. I screwed up by forgetting to load a ROM on my SD card. Feel free to laugh, you know what's happening next. Couldn't get TWRP to do any form of mass storage mode so I can connect it to my computer so I had a moment and rebooted. Phone rebooted to the LG screen and nothing else. I can get the device to show up as a mass storage device. Not accessible. I can get into software update, set up for a kdz restore (been there, done that) gets stuck at 15%. OK, tried to update fastboot, no go. PC (Windows 8.1) doesn't recognize the omap so I can even verify drivers. I have soft bricked before and managed to come back. Any suggestions?
Try online update
Use the KDZ update tool, without all the shttps stuff. Just run the tool. Look for a 'recovery option' and use that.
Related
So after searching the vast horizons of XDA I haven't found an answer that really helped me. Nor have I found someone with this distinct issue. I have an unlocked Samsung Vibrant. I have not rooted it. I updated to J16 with that P.O.S. Kies Mini a few months ago. I hadn't noticed this problem until the last month or so but I haven't had time to sit down and curse at my computer long enough or offer supplications to Google until now. I've just been using Awesome Drop to get what few files I wanted onto my phone. I've had enough of that now. And...I also want to update it to Froyo but I can't do that if I can't get my computer to see my phone. I'm running a Toshiba Satellite A205 with Windows Vista 32bit.
I have checked the drivers and as far as I can tell, I'm using the right ones. I downloaded Kies Mini again today (I deleted it after I was finished with J16 because I wanted it as far away from me as possible) and it seemed to say something about downloading drivers as well. I tried plugging in my phone. Nothing new. So, I went in search of drivers again. I have searched and tried a few different ones but nothing has solved my problem.
The phone charges fine from my laptop. It hooks up immediately and charges without a problem. Unfortunately, my phone seems to regard the PC as a complex wall-wart. Debugging on/off, USB Settings on Mass Storage, Kies, or Ask on connection, it doesn't matter. It doesn't give me the option to "mount" as it has in the past. It doesn't do anything except charge. I've seen some people say it's a problem with their cables (I've only got one at the moment) but since my phone charges fine, how can it be a problem with the cable?
Only thing I hadn't tried was a factory reset. So, I sucked it up and tried that. Nope. No change. At this point I'm wondering if it's a hardware problem, not a software problem.
I'm out of ideas. Anybody else?
Well you can always root it, install ROM manager from the market, install clockwork recovery, download the ROM you want to install in flashable .zip format from your phone and flash away. A new ROM might fix your USB issue.
If you don't want to root it, see if you can get into download mode, and flash a new ROM using Odin. I would check with a different cable first, just to be sure that's not the problem though. It might save you some headaches.
If it was me, I would just root it and load a custom 2.2 ROM. I would also get Titanium Backup from the market and backup my apps and would do a nandroid backup from recovery before flashing anything new just to be on the safe side.
There's some good info on how to do most of that in this sticky post.
http://forum.xda-developers.com/showthread.php?t=849028
All sorts of issues here.
I am no longer able to install new ROMs on my Aria. In the past I have flashed many ROMs on the phone. Recently I flashed an ICS rom but I did not like the way it was working so I went back to Cyanogenmod 7.1 RC1. Now for whatever reason, I am unable to flash any other ROMs. I put the new rom on the SD card like I always had then boot to CWM, go to install from SD card and it says that there are no files there. Which is not true and its not the SD card because I can still see the files with a file manager. When I select the ROM from inside ROM Manager it goes through the process but stops shortly after starting the install. I have heard that using a different version of CWM may work but when I try to download one from ROM manager it says an error occurred when trying to download. Also when I hook the phone up to my PC it doesnt recognize that it is plugged in other than its charging. (yes it is the original USB cord and USB debugging is on).
A few details: This phone has never connected with my current/new PC. It did work at one time with my old one. While trying to fix this I did a complete wipe of the phone, the first time I hooked it up to my current PC I got the whole new hardware detected thing on my PC and USB debug was active on the phone, but I don't know if I accidently hit a wrong option on my PC but it went right away and has never connected again.
I also noticed that the phone is S-ON, I thought/assumed it was S-OFF before. Could it have some how turned back on? I cant get it back off now since I cant use ADB without USB Debug connected.
I no longer use this Aria for daily use (replaced with One X ) so I am open to some possible "extreme" ideas of trying to fix this.
Thanks for any help. This is driving me nuts.
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
drumist said:
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
Thanks. I will give that a try.
drumist said:
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
Install this first: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try running the RUU again.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
I have tried installing that before (tried again this time too) and it doesn't help. I still have no connection to the phone. I have Windows 7 if that helps anything.
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
drumist said:
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
Click to expand...
Click to collapse
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
chadd74 said:
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
Click to expand...
Click to collapse
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
drumist said:
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
Click to expand...
Click to collapse
Well,sort of good news here. I had tried different USB ports before but thought I would give it another go, it still was not connecting. So in a bit of a fit of rage I took the micro usb cord at shoved it quite hard into the phone. Well the connection flickered. So it appears over the years the USB slot had gotten a nice amount of pocket lint or whatnot jammed tight in there to where it would connect enough to charge but not enough for a PC connection. I cleaned it all out the best I could and what do you know, it worked.
Foiled by pocket lint.... SMH.
I loaded the 2.2.2 RUU and will give the rest of the problems a go tomorrow and post an update. Thanks again for all the help.
Looks like everything is working like it used to.
Thanks again.
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
Hopefully somebody can help me this this. I was attempting to flash back to the original firmware to get back to the unrooted ROM and it seems like during the process the phone or cable disconnected and now it's stuck on the Firmware Update screen and the little console box on the bottom reads "VUSER B99". The computer seems to recognize the phone in device manager as LGE Androidnet for VZW, however nothing seems to change when I try to run the LG flash program. I've used the program twice before and both times it worked perfectly.
I've tried booting into TWRP recovery, entering download mode, and battery pulls, but nothing changes once it boots. I'm using the LGFlash tool and VS98510B_03.tot. I had the JasmineROM v5.0 on it before I was trying to revert back. Has anybody seen this before? I tried searching and found a few similar problems, but no conclusive solutions and none for the G3.
Update --> solved
In case this happens to anyone else, I found the solution was to use a different computer. For whatever reason, I was no longer able to use the computer that I had previously used for flashing the stock firmware. Apparently, the stock cable that I have, and was using, is slightly worn out and the computer lost the connection during the process, which soft bricked the phone on the update firmware screen.
I downloaded all programs and drivers on a new windows 8 laptop and it worked on the first try. Hopefully this helps if this happens to anyone else.
Hey guys, new member here but been a lurker off and on for awhile.. not sure what to do, you guys are my last hope.
I have a Samsung Galaxy Core Prime from straighttalk. Android version is 4.4.4 (I think).
Anyway, I was screwing with it trying to speed it up using a few apps I downloaded from the store, the apps let you uninstall apps that the normal manager won't let you and manage what system apps are allowed to run at startup..etc. also I was messing with applock and phone encryption.. So I'm not sure what messed things up.
Well needless to say, I shoulda been more careful, because now my phone is screwed! I can't view my home screen at all so can't call/txt and can't access my settings to try to fix the problem..
Before people tell me to reformat it, I have tried 100 times.. I press volume up + power + home to get to bootloader and tried doing a full reformat as well as wiping the cache partition... Reboot phone the setup screen comes up asking for my name/google account..etc but I can't complete it, it always crashes sayin either "hangouts has stopped working" "setup wizard stopped working" or something about a android.keyguard service.
So next I jumped on Google and read to try the Kies software but I can't for life of me get it to detect my phone.. took awhile but I think I got all the drivers installed.. kies will just say it's connecting to my device but never does. Tried kies 2 and 3 and different cords, I think it's because android isn't even truly fully installed since the setup wizard crashes.. so the MTP capability isn't even there.. under my computer I don't see my phone either like I use to, just a blank drive that has no name and can't be accessed.
So then after more reading I decided to try "ADB sideloading".. I'm a newb is to this stuff so idk if I even did it right but hooked usb up went into bootloader and reformatted/cleared cache then I went to ADB and using cmd on my pc I tried to send a zip of cyanogenmod (got it on xda, suppose to work on galaxy core prime) and it said it was successful but it doesn't do anything.. so idk if it's cuz u can't use custom roms with the stock bootloader? I read about other Rom managers but how am I suppose to install them?
if a stock firmware will work, where can I find one?
Sorry for the wall of text, I'm just stuck here and wanted to add everything I could think of that I tried already.
I dont think it's a physical hardware problem, I think i just screwed some system files up somehow which screwed up the recovery partition..
Extra note:
I am able to use the internet browser though, when the setup gets to the step to link your google, in the top right I can go to "enter browser signin" and then I can bypass the fact there's no search bar by clickin privacy policy and clicking a logo to bring me to Google's homepage.
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Mr.cryptkeeper said:
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Click to expand...
Click to collapse
Get a custom recovery (preferably twrp) and then wipe EVERYTHING in the wipe section except your sdcard and then just adb sideload cyanogenmod or any other CUSTOM rom for your phone.
You should just be able to reload the original firmware with Odin. Or Kies will probably work, but you have to use Download Mode to be able to restore it, not while it is booted into the OS.
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Mr.cryptkeeper said:
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Click to expand...
Click to collapse
Yes you have to be in recovery to actually be able to do adb sideload, try adb reboot recovery.