okay i am on mik's cm7 2.3.7..old baseband..i wanted to to get the new baseband so i tried flashing the stock rom..but kdz is not detecting my phone..getting a PHONE NOT FOUND error..tried that in emergency mode too but still the same error..i tried lgmdp too but it does not show my phone..i've disabled lg modem..reinstalled all drivers...nothing works..please help!
This happened with me too
My phone got a shock from pc as their was no earthing in the socket
After that the pc only charged my phone
So i did:
Downloaded stock rom and recovery from
forum.xda-developers.com/showthread.php?p=23168177#post23168177
put it on my sd via sd card reader and flashed
this made my phone completely stock
Then I took the phone to lg to get free repair
(shock also desroyed my old nokia phone but who cares )
Related
while rooting i lose connection** omg sorry
So this is how the story starts
i got my fasciante, rooted it fine using FascinateRoot_v02
but then i tried to flash cwm using odin and it wasn't working so i was trying some different stuff and i ended up going back to stock 2.1 and losing root.
so now when i try to root using FascinateRoot_v02
it finds my devices reboots it
but then while it is in its waiting period of 5 minutes it loses connection with my computer and then cannot find the device and thus cannot finish root
i also cannot get the OTA 2.2 update from verizon
i get an error
anyone have any ideas on what i can do? i am at a loss and feeling completely useless
now my computer isn't recognizing my phone at all
drivers are installed
and it worked four days ago
i dont know what i did
how can i fix my phone if i cant get root back.
gaaah
this is so frustrating
this is what i did
first time i rooted it i had sdcard A in my phone
i took it out afterwards and replaced it with memeory card B
everything was fine until i tried to odin clockwork on my phone then i lost root and 2.2
i put memory card A back into phone and like magix root is back and 2.2
what am i missing? how does this effect the phone?
i still want to put clockwork recovery on my phone but now i am too scared.
Make sure that your phone is connected to your computer motherboard with the cable it came with, sometimes other devices can cause it to disconnect. Make sure to disconnect other devices if need be. If you want you can always put it into download mode and flash recovery. You should be ok
Also, my laptop will sometimes not connect to teh phone. A quick re-install of the drivers corrects that immediately.
Likewise, if you try Heimdall instead, you set teh drivers when you launch the application, so it is always fresh. I am not certain if Heimdall and Odin are interchangeable for everything - I use whichever is recommended on the DIY's that I am following (I know little about this stuff other than what I am taught in those DIY how-to's that we get when doing all this cool ****...)
So I would:
a) re-install the drivers to get Odin seeing the phone (if I read your problems right that was an issue).
b) follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1048380 - this will get you up on the ComRom/KangBang with the EC01 Modem. You will be rooted and have CWM.
Hello, I have a problem with restoring original SE rom, and it is not because I don't have an USB cable, but rather something wrong has happened to USB socket in the phone. I am able to charge (sometimes) phone, but computer doesn't see any device. X10 is still on warranty and I'd to return it to service, but I'm afraid that they could reject it because of custom rom...
My configuration:
Rom: Wolf_Xperia_7.0.0s
Android version: 2.3.3
Kernel (stock): 2.6.29-00054-g5f01537 [email protected] # 1
Baseband: 2.1.71
I have also installed xRecovery 0.3 on this phone before and maybe this tool could be used to restore original rom?
EDIT: I think I found proper tutorial http://forum.xda-developers.com/showthread.php?t=1054818
EDIT2: Now I'm looking for nandroid/recovery backup for Baseband 2.1.71.
About a month ago my device was like yours and suddenly it went to a way that USB didn't charge it either pc didn't recognize it,
Then I have bought a new USB cable and from that time it works properly good.
For changing rom you must access your SD to put the rom's zip file there and then flash it with xrecovery..
Sent from my X10 using xda premium
if u wanna claim your warranty, u should repair/update phone via SEUS..
I mean ur phone should be totally clean
no any recovery
unrooted
all stock...
but try comment no 2 suggestion first
if you found nandroid backup also,maybe SE will findout recovery system on ur phone
Ok, I used stock rom from this thread http://forum.xda-developers.com/showthread.php?t=1192152 and tutorial from here http://forum.xda-developers.com/showthread.php?t=1054818
It seems that Master Uninstaller script for Android 2.1 works also with 2.3.3. The only uknown was if chargemon from this package will work with Android 2.3.3, but it looks like that everything is fine. This script is removing xrecovery, su, charger and other stuff from xbin.
I think that now my X10i is ready to send to warranty service.
EDIT: Btw. I tried another USB cable but no changes, only charging works.
Just for your information.
I restored rom as I wrote in previous post, and warranty service accepted and repaired my phone. They had to replace mainboard, but now I finally got my phone back and it works!
Gentlemen, I couldn't find a section for Xperia Pro, please excuse me if this is misplaced.
I rooted my MK16i from ICS 4.0. according to a guide here on XDA forum, with no problems (from 4.1.a.435 .. i think).*
Then I installed system tuner and backed up the bloatware and what I believed was obviously named as packages that support them. Things were working great and the phone gained some performance improvements.
UNTIL, I installed Viber and Skype, and niether were working. I thought I would fix it by restoring all the backed up services and apps. Once I did that and rebooted the phone, it became useless
THe phone keeps rebooting. I get to the XPERIA loading screen and then it restarts again
I tried to connect it to the PC to flash another ROM with the Flashtool, but it is not recognized. All I get is in the computer screen a removable disk drive, that is not accessible.
Note: I didnt update the firmware after I rooted.
Can anybody help?
have you worked with flashtool before ? because there hardly could be any wrong with flashtool. use the latest version with proper drivers.
and since you have rooted phone, have you unlocked your bootloader ? if yes, then flash any custom kernel, go to CWM, then place rom zip on sdcard and stright flash rom via CWM.
flashtool should work though. you can try on different computer.
If flashing a kernel or installing custom ROM sounds a bit out-of-reach, you can always go for the repair option in PC Companion. It worked for me when I had soft-bricked my Neo V (it wouldn't go past the SONY logo). However, be advised that this repair option will erase your phone's internal memory. Also, your phone will be brought on the latest stock ROM, so you will need to root your phone again.
Good Luck!!! :good:
acemccloud1 said:
If flashing a kernel or installing custom ROM sounds a bit out-of-reach, you can always go for the repair option in PC Companion. It worked for me when I had soft-bricked my Neo V (it wouldn't go past the SONY logo). However, be advised that this repair option will erase your phone's internal memory. Good Luck!!! :good:
Click to expand...
Click to collapse
I tried to do somethingn like this but sony companion itself cannot detect the phone either.
My question is, is there a brick that cannot be fixed? I took it to a shop today and still they cannot fix it.
Have you tried to use sony update service?
How are you connecting your phone to flashtool?
Can you show us log from flashtool?
New development:
Now I tried to flash the phone with flashtool 32bit rather than 64-bit and it detected the phone! I could even flash the only firmware in Aeonworld's post Here.
Now I can see the phone connected in my computer.
However, the phone still won't boot but when I power on it gives black screen and after a short while, the led on the side becomes green.
For some reason though, I cannot continue with the rooting steps in his guide.
So anyways, after the second reboot, not the first for some reason, the phone gets detected in PC Companion, and I installed the update and now it is working again :victory:
Thank you all for your support.
moeness86 said:
New development:
Now I tried to flash the phone with flashtool 32bit rather than 64-bit and it detected the phone! I could even flash the only firmware in Aeonworld's post Here.
Now I can see the phone connected in my computer.
However, the phone still won't boot but when I power on it gives black screen and after a short while, the led on the side becomes green.
For some reason though, I cannot continue with the rooting steps in his guide.
So anyways, after the second reboot, not the first for some reason, the phone gets detected in PC Companion, and I installed the update and now it is working again :victory:
Thank you all for your support.
Click to expand...
Click to collapse
Good to hear that bro!!! R&D always makes a man better
Hi there,
Im having some trouble trying to put my L9 back to stock firmware. I have a P768 which is running artit's CM10.1 with TWRP. Im struggling to get the phone to be recognised with the LG mobile support tool. The phone doesnt seem to connect to my pc, if i put USB debugging on, then it connects fine but the software doesnt find the phone. Can anyone help me out here, feel like im missing something obvious!
I was thinking if i restored a CWM backup of a stock rom, it would then give me LG software mode when I connect the phone and then the support tool can put the stock rom back onto the phone, right?
Thanks, donk165
Problem solved: flashed jelly cream v1 then used LG software mode on that rom, all is good
Sent from my C5303 using xda app-developers app
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
muddled said:
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
Click to expand...
Click to collapse
Hey Mate,
Firstly we all are noobs here helping each other, secondly from my experience of S3, it is such a device that under any condition, if your hardware is intact, you can recover your phone from almost anything, so yeah you might have a solution to your problem.
Coming to the problem at hand, i had the same thing happen to my S3, (only twrp logo showed, couldn't access recovery, no ROM, only download mode available) the way i fixed it was using odin, now i know you say that odin is not recognizing your device, the thing is firstly Kies is useless in this situation acc. to me, it only works stock ROM and that too with difficulty, what i would say is go here - http://developer.samsung.com/technical-doc/view.do?v=T000000117
and then install the drivers to your PC, next up download the official firmware from sammobile or any other site (careful of the version you are using), now put the phone in download mod, start odin and then connect your phone. Now, hopefully odin will recognize your phone and you can flash the official firmware, also i would recommend to stay on the official firmware for like a week before returning to flashing again as i have noticed that constant flashing and wiping leads to not only errors like "unable to mount EFS" but also serious errors like "Unable to mount /system" or "Unable to mount /Data" ,which clearly sucks
Please try the method and tell me if it worked , if not we'l try something else but we sure as hell will get your device working again
If still not recognized then here is a suggestion :
Exit/uninstall from nokia/ovi suit.
Exit/uninstall bluestack. (if u r using it)
Update your drivers(phone specific)
Use correct odin version acc to ur phone
Sent from my Micromax E352 using XDA-Developers mobile app
I'm just gonna throw my 2 cents in too. I didn't read your whole thread as I'm in a slight rush right now.
But basically -
Can your PC recognise your phone when it's plugged into USB in Download Mode? If so, use ODIN to flash any stock firmware and you're back to square one (working, but stock) phone. Then go from there. Obviously try to flash the right firmware or you'll end up no further forward.
If it can't recognise it, try reinstalling the drivers, uninstalling the programs mentioned above and using another USB cable. My experience with my own S3 has shown potential wear with the USB port on the bottom of the phone presumably due to it's age and as a result it doesn't recognise many USB cables.
Regards