I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.
1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.
Try this guide.
Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)
I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD
There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.
Like ppl said before, try PdaNet drivers it might help.
thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*
Related
So I lent my brother my nexus s that had cm7 on it. He got into the clockworkmod, went to mounts/storage, and proceeded to format everything (bootloader, boot data, etc. everything in there) he said he thought that would fix the force closes, I figured no biggie, but now I can't even get the phone into download mode and I have no idea what to do, the phone will simply not turn on
wow.... dont even know why he would do that.
rule 1: dont lend people your phone.
and i dont know why you would try and get into download mode, Odin isn't the first thing you want to go to.
1. turn the phone off (if it isnt already)
2. hold volume up + power
... what happens? does bootloader mode pop up?
- plug your phone in your computer's USB
- does the sound for USB plugged in occur?
- does computer detect it?
Can't access fastboot.
Phone sometimes recognizes it and says this device is not recognized and it couldn't install the usb driver, sometimes when i plug it in it does nothing.
Didn't want to lend it to him, had no choice. I told him he should have just fixed the permissions on the phone, but then again he's not exactly android literate.
thats just dumb on his part.. i dont know why he would try and mess with your device. if it has problems, just ask you first.
its probably bricked if you cant access download or bootloader... definitely bricked if the computer is unable to detect it
your only way out of it is to get a replacement
In Device/Drivers of windows under Unspecified there's this:
SEC S5PC110 Test/BD
says drivers are not installed
Anybody out there with a solution?
I think there is more than one driver you can try, though I've never flashed anything in Windows (Linux already comes with the driver ), so I don't know for sure. I think I've seen people mentioned a few drivers before, try search for all the "brick" threads here.
Easiest solution might be to download a Linux live distribution (f.e. ubuntu) and run fastboot from there. No need to install any drivers.
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
jruweaver said:
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
Click to expand...
Click to collapse
lmao!!!!!!!!!!
KryPTiCk0d3 said:
lmao!!!!!!!!!!
Click to expand...
Click to collapse
While funny, it doesn't help one bit.
I would try the various methods to get into download mode and use Odin to fix it ...you might be screwed tho
Sent from my Nexus S using XDA App
SphericalPuma said:
While funny, it doesn't help one bit.
Click to expand...
Click to collapse
Unfortunately with the state your phone is in it is probably going to be the best advice you get.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=1000175
any chance that this could help you?
Ddi you ever get your phone sorted ? I'm now in the same situation !
Yes, hit up http://www.mobiletechvideos.com/blog/?page_id=970 For 50 bucks they'll fix your phone and ship it back to you in no time. They got my phone on a Friday, I got it back on either Monday or Tuesday. Of course they're based in Texas and I'm in STL so it could differ for you, but the point is, they're fast, reliable, and professional.
Thanks for that - I'm based in Ireland but I'll give them a shout and see if we can do business......
Thanks a million for the reference PUMA. Please contact me when you are in need of a brick fix. I fix hundreds of Galaxy S / Samsung / HTC variants and several others in a brick of nearly any scenario. I've devoted a lot of time to providing and almost unseen service to people in need versus parting the phone out or trashing it.
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
Last night I switched my SD card (16GB Class10 Kingston) in my O3D and checked the "Use external/internal sd" in CM settings and rebooted my phone.
The /root/sdcard path was located to the INTERNAL sdcard before the switch.
I think that the option was NOT checked BUT when it check it, it became "Use internal" which is incorrect.
Anyway, my phone wont boot, not even when holding down VolUp+Power.
I will keep trying but just a warning to you all, don't do any hardware change with the Nightly builds (assuming that the sdcard is hardware)!
I'm using linux so I'm not sure that it's possible to use any software like the softwares on windows.
have a look at this thread http://forum.xda-developers.com/showthread.php?t=1433274 , they have the same problem as you. Apparently its because you switched the internal/external.
Flash the rom again ??? Power + vol-down 3d button .. for cwm ??
Sent from my LG-P920 using XDA App
It's very important you report this bug to arcee on http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/
He doesn't follow threads on XDA.
gamesz2 said:
Flash the rom again ??? Power + vol-down 3d button .. for cwm ??
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Are you seriously answering my thread without reading my entire post?
--------------------------
No worries, I can flash back the stock with lg support tool using windows, but my current rom and settings will be lost.
Just a heads up if any of you would try the same thing.
And mine doesn't go in to recovery mode either. I doesn't boot whatever I try.
Only thing that can be done is what I said above, Holding down VolUp+Power while plugging in the usb in the computer so the computer can find my phone as a Omap4430 device.
KurdX said:
Are you seriously answering my thread without reading my entire post?
--------------------------
No worries, I can flash back the stock with lg support tool using windows, but my current rom and settings will be lost.
Just a heads up if any of you would try the same thing.
And mine doesn't go in to recovery mode either. I doesn't boot whatever I try.
Only thing that can be done is what I said above, Holding down VolUp+Power while plugging in the usb in the computer so the computer can find my phone as a Omap4430 device.
Click to expand...
Click to collapse
Ow iam sorry man i read it wrong iam from holland :0
Sorry
Sent from my LG-P920 using XDA App
Hi guys,
Same problem to me... A dead phone w/e I do. Won't get my PC recognise it as OMAP4430 device (not running XP, but 7)...
Any ideas? Cannot easily get my hands on an XP PC...
lrpvo said:
Hi guys,
Same problem to me... A dead phone w/e I do. Won't get my PC recognise it as OMAP4430 device (not running XP, but 7)...
Any ideas? Cannot easily get my hands on an XP PC...
Click to expand...
Click to collapse
You don't need XP, will work on 7 aswell.
Haven't had time to fix my phone yet but I will fix it through 7 so I can post the result here when fixed.
same problem here, too.
any solutions yet?
omgomg said:
It's very important you report this bug to arcee on http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/
He doesn't follow threads on XDA.
Click to expand...
Click to collapse
I already did that many days ago, but it seems this rootzwiki forum is totally dead. No arcee, no other dev replies. I also reported other bugs, no answer too.
In fact, I´m afraid CM7 development for our device has stopped completely, since all changelog entries we get are for general CM7. Nothing is getting done for the O3D specifically.
I know CM is done by busy developers, who get no money for their work, but they could at least share their knowledge a little more, so more people could jump in to help! I´m trying to do that, but I need some pointers from more experienced people.
What pisses me off is to have an important project like this in the hands of 1 or 2 guys, with bugs that bricks expensive phones, and we have no one to talk to.
Marcovecchio said:
I already did that many days ago, but it seems this rootzwiki forum is totally dead. No arcee, no other dev replies. I also reported other bugs, no answer too.
In fact, I´m afraid CM7 development for our device has stopped completely, since all changelog entries we get are for general CM7. Nothing is getting done for the O3D specifically.
I know CM is done by busy developers, who get no money for their work, but they could at least share their knowledge a little more, so more people could jump in to help! I´m trying to do that, but I need some pointers from more experienced people.
What pisses me off is to have an important project like this in the hands of 1 or 2 guys, with bugs that bricks expensive phones, and we have no one to talk to.
Click to expand...
Click to collapse
My point exactly all these people are getting big headed if they opened it up people can fix stuff and get it done much quicker but i guess they get money for it.. I'm going to have to let go of this phone shame was a good phone though..
I had almost same thing I formatted my ad card on cm7 38 build for p925g. Total brick it's in a disconnect reconnect loop and no comm conection so very. Close to a full brick taking it in tomarow.
Posted from my crap ass slow as f*** 3GS iphone
Phone in unusable state.
Same issue here coming from CM7 build 16. All I see is the disappearing/reappearing OMAP4430 device in device manager.
THIS PROBLEM SHOULD BE STICKIED]
Any idea what to do guys??
Yes it should i was lucky my phone was under the 30 days still so they just handed me a new phone on the spot wich was nice but im going to stay away from cm7 like the plague yes this should be sticked her andin the thrill forum as well.
I had to take mine in there was no way to get the computer to see the phone to flash it.
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
omgomg said:
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
Click to expand...
Click to collapse
Indeed, he says he reads it, but that forum is completely DEAD, no posts for 2 weeks. I already reported this bug, had not a single answer. And the nightlies have no P920 specific work for weeks. And since arcee seems to be the only mega-master-guru around, a person no one can talk to, this is what we have: a dangerous half-working CM7 that will destroy many more O3D around, and there´s nothing we can do.
omgomg said:
Guys, don't complain about this here, as arcee already said he doesn't follow XDA threads.
Do report it at http://rootzwiki.com/topic/4883-cyanogenmod-cm7-nightlies-for-optimus3d-and-thrill/ where he reads it.
Click to expand...
Click to collapse
Im. Just posting hear so every one else. Dosent make the same misstake as me and end up with a paper weight on tbere desk.
I have a Sprint Nexus S 4G that I've recently rendered without service or USB connection as a result of a fastboot accident. I'm currently running ICS 4.0.3 (Dooderbutt-aosp-v-5 build), but have tried restoring multiple backups on CM7 to no avail. Wiping all user data in CWM doesn't fix it either. I have also tried flashing the LC1 radio zip with no results.
The way I see it, my two best courses of action would either be to try and return to a stock ROM so that I can send the device in under warranty or to continue to try to fix it myself, which has been less than successful so far. Every process I have found online to return to stock seems to end in fastboot oem lock, which won't do anything for me as my phone doesn't show up in fastboot devices, file explorer, or seem to be recognized by my computer in either Ubuntu or Win 7. I've tried connecting on my friends' computers with the same results. I've also tried using another USB cable. No dice.
Sorry if I missed something obvious before posting. I tried to do a lot of research online and have reached the end of what I know what to do. Any suggestions?
Bump.
After some more researching, it appears that there is no way to lock the bootloader except through USB connection with a computer. Does this mean I'm out of luck? Any suggestions as to how to solve this issue? Since my first post, I've flashed ICS 4.0.4 with no improvement on the above symptoms. Also, auto-rotation doesn't seem to work. My Baseband version in About is listed as Unknown. Does anyone have any clue? Replies would be greatly appreciated.
have you updated the android drivers on your computer? you wont be able to connect to fastboot without the drivers. you can get it here http://www.junefabrics.com/android/ do the free download(on your computer) then follow the on screen instructions.
simms22 said:
have you updated the android drivers on your computer? you wont be able to connect to fastboot without the drivers. you can get it here ... do the free download(on your computer) then follow the on screen instructions.
Click to expand...
Click to collapse
I'm running Ubuntu, so from what I understand, I don't need any drivers. Prior to this fiasco, my computer recognized it as a storage device in the file system as well as a device in fastboot. It doesn't come up as either now.
I had a similar problem after I updated to ICS 4.0.3, what version of Ubuntu do you have, and does the device show up when you run lsusb?
Also, have you checked inside the usb connector to see if one of the pins is bent or damaged?
I'm running Ubuntu 11.10 and no, my Nexus doesn't show up in lsusb or anything else I seem to try. I have checked the pins in the connector of the phone and even bent them around a little bit, but I doubt that's the problem. Since it disappeared immediately after a bad flash, I'm fairly confident this is a software-induced error.
Ok, the only other thing I can think of is a bad kernel or baseband, but since you've tried several different roms, I don't think that's the problem (unless you put on one that's not for your model).
Sorry I can't be more helpful, hope you figure it out!
Thanks for your help anyway. To be clear, each rom has its own kernel and baseband, correct? Are those things I can flash independently of roms like the radio?
Found something, not sure if you've seen it already : http://forum.xda-developers.com/showthread.php?t=1077168
This bit is especially interesting :
"*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision"
For the usb not connecting, I had the same problem. After trying every computer in the house, I grabbed a can of compressed air for electronics and blew out my micro usb port on the phone itself. There was a small piece of lint in there that was causing the connection to not be made. It's worth a try.
statisticalanomaly said:
Found something, not sure if you've seen it already : http://forum.xda-developers.com/showthread.php?t=1077168
This bit is especially interesting :
"*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision"
Click to expand...
Click to collapse
I'm attempting to try this work around, but I can't seem to find my msl. I've tried putting in an incorrect code and checking alogcat for it as well as the terminal output of getprop. Neither of these give me the number. Sprint mentions using this code for resetting your phone in this tutorial, but I can't for the life of me find the part of their site that shows the msl.
This is exhausting. I really appreciate all your guys' help though. Thanks so much.
Unfortunately, I never figured out how to solve the problem. I took my phone into Sprint the other day and lucked out on the repair technician. He was messing around trying stuff and had a moment of realization when he booted into Clockworkmod. Even though I had voided my warranty, he still let me replace the phone for the $35 fee. I walked out with a brand new Photon 4G. I'm so happy, it's like Christmas in May!
To others who have this problem: sorry, but I don't know what to tell you! Mine was probably bricked. The MSL number didn't connect the phone and neither did anything else I tried. Best of luck to you.
There isn't a thread for this for our phone, so I thought I would make one seeing as i've tried it. A program called mobile odin https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&feature=nav_result Will allow you to run odin from your device without connecting it to your computer. Its super simple to use and it works pretty well. My charging port is hosed so I can't connect it anyways. I was on ICS and needed to go back to GB. Had to use this app and got back on GB no problem. I don't see a free version of the app anywhere so depending on how much you use odin, 5 bucks might be a good investment.
Hmm I ran the program and sent the logs a few months ago and never heard anything back to get our device supported and still doesn't say it supports this device.
It takes 30 minutes to run the system dump to find out our device isn't compatible......after running the dump....and to find out it wouldn't work
Its not worth the hassle when you've only got 15 minutes to get the refund.
I'd like to see screenshots or something to show that this actually does officially work on our device ....considering its not on the list of compatible devices.
Thanks
I guess after 2 days without a response ....there's not going to be one?
To bad I was hoping that it was going to be worth the money
Too bad I'm stuck on ics as well got excited when I started reading this thread.
Sent from my SGH-T959V using xda app-developers app
??? Anything???
Or is this just a bogus post....and in the wrong section....should have went in themes and apps
A search would show that XDA members gets a lite version as with lots of other apps for free.
http://forum.xda-developers.com/showthread.php?t=1347899
Ive run it.....it generates a dump file (mobileodin.txt) that you send in and hope that he incorperates your device in the next update .....and since it does this ...it basically is not suported as of yet.
So the op is saying it works.....but in fact it doesnt.
I would like to see some evidence that it works for him and like to know how it does on his device and not on mine.
Also with the lite version you have to dl a flash kernal specific to your device from that same thread....but since our device is not suported...you wont find one.
Y'all should do alot more reading before posting links to something that doesnt suport our device.
i did read that thread thuroughly....very thuroughly,even flashed a few flash kernals he added that were for the other models similar to ours in great hopes of getting this to work.
This is what you get....it does take about 30 minutes to generate the text file to send in
Oh magda623....are you there?
we are awaiting your reply.
Im sure there is hundreds of us that would like to have this running on our phones...please let us know how to make it work.
Ok ok i give up on magda to humor us on how it works on his device.
I urge everyone to use the link a couple posts up and dl the mobile odin lite,run it and send your mobileodin.txt to chainfire and plead with him to include our device....im sure he will eventually get our message.....after all he does say he is only working on samsung devices at this time.
****wouldnt it be awsome to flash back and forth from mtd to bml roms without ever having hook up to your comp!!!****
Lol am i seriously the only one that finds this to be something that would make life amazing on the sgs4g?
new ealsjur
Mobile ODIN did not recognize the device when I was on CM9
Something about flashing the phone from the phones makes me uneasy. What if you need to repartition using a pit or something, while the phone is on and in use.
Btw short I sent a dump file a long time ago and have been retrying ever since with no luck so far, maybe I'll make another dump today after work
Sent from my SGH-T959V using Tapatalk 2
getochkn said:
Something about flashing the phone from the phones makes me uneasy...
Click to expand...
Click to collapse
I've stayed out of this one for just that reason. It's bad enough to be messing with the underpinnings of an OS when you don't have true single-user mode, a "safe" boot, kernel, and emergency filesystem available, nor alternate boot media if things go really bad. Doing all that from user-land while the system is running all services sounds like just asking for trouble.
You can do most of what you are asking for in Recovery
Flash kernel/boot/recovery
Flash /system
Flash other run-time partitions
Flash modem
If you can't get into recovery, are you really able to run some Android program?
I'm not really seeing the need for this, except for people who have broken their USB connector and can't connect to a computer. Even then, when would you need ODIN? When things are so hozed up you need to start from scratch, yes, but if you have a broken USB, what are you doing flashing risky things?
If someone can show what this would do that you can't do in recovery, as well as a meaningful use case for it, I'll mull over how to do it. Basically, if an app can do it, a script in recovery sure should be able to as well.
I tend to think the reason we dont have support is because of the quirkiness of this phone.
I agree eollie ....I gave up on this a while ago...really it doesn't matter to me anyhow....I mostly thought it was a great idea.
I don't tend to have issues with flashing...or recovering.
And even if I did....I wouldn't be dumb enough to post here lmao.