bionic bricked. - Motorola Droid Bionic

alright, hi, guise.
im new to the forums, but not new to rooting. ive sucessfully rooted many devices of my own, and others. however. ive run into a kind of unique problem. i didnt read the description of an ICS rom, and it ended up being a droid 3 rom. not a bionic rom. so, i wiped everything out, and i mean EVERYTHING, and rebooted for some stupid reason. now im stuck on a bootloop. all that pops up, is the m logo. i cant get into my clockwork mod, and my battery is dead. ive been trying to use a direct wire charging method for the battery, but to no avail. is there ANY WAY i can restore my phone?

You can try this:
How to UNBRICK Factory Reset Droid Bionic via FXZ files:
http://youtu.be/tAd7XzL76CA
but you will need a battery at least 80% full
Or this:
http://forum.xda-developers.com/showthread.php?t=1262540
There is another way also on you tube search for easy unbrick factory reset droid bionic one click fastboot restore tutorialhow to. No RSD needed.

thank you, sir!
is there any way to charge the phone, while its bricked? or should i continue to try and not fry it with open wires?

.x0mb3 said:
thank you, sir!
is there any way to charge the phone, while its bricked? or should i continue to try and not fry it with open wires?
Click to expand...
Click to collapse
I have never done it myself but the open wire seems to be what people do just be carefull not to over charge it.
Good luck!

Few options:
1. Find someone with a bionic that will let you charge your battery in their phone.
2. Go to verizon and see if they can charge your battery.
3. Buy an extra battery (they usually come with enough charge to restore your phone).
4. Buy an external battery charger.
5. Buy a motorola factory flash cable. This type of cable has a different pin out and has the +5v on pin 1 which bypasses the battery and powers the device directly even without a battery inserted at all. here is a link... http://shop.teamblackhat.info/

Related

[Q] Bricked Milestone, stuck at Motorola logo

Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result

need help dead phone

I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.

No Bootloader

I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Oh, and yes I have a factory programming cable if I can make use of it somehow......
queberican351 said:
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
How did the bootloader get corrupted? I was under the impression the phone would not allow you to flash another bootloader unless it was signed... You should ask Moto what was physically damaged, if it was a simple flash they should be able to fix it easily for you.
NEED DD
That was my thoughts exactly. But they claim liquid damage. I've since then opened the phone and inspected all the stickers....no sign of liquid damage. I would think a 2 minute bootloader flash wouldn't constitute this much despair (on Motorola's part) but such is life. Now I'm just looking to get the first couple Mb in a device dump so I can write it to an sdcard and attempt to boot from there and repair the bootloader. It has to be a device dump from a D4 running the a.074 bootloader. Any takers?
You could try looking in the fastboot files, they're on the Droid 4 development boards, they have both Gingerbread ones
D4 6.16.215 MBM files
Here are the D4 6.16.215 mbm.bin and other low level boot files from the leaked OTA update.zip.
I don't think they are going to help you given that there is no way that I am aware of to boot from the sdcard on a Motorola device.
There is a USB boot option for loading a factory I/O image(pre firmware basic input/output interface), but I don't know how you would initialize it nor do I have the factory image for the D4.
It is most likely a touchpoint on the board that needs to be shorted while the factory cable is inserted and that would bypass the EMMC and initialize the USB boot.
I am just guessing here...good luck!
if you somehow unlock it too, let us know what you did
SD Card boot didn't work and couldn't get it to detect on my windows or linux pc's. Therefore OMAPboot was out of the question. So I parted it out. I've acquired another D4 and I'm curious as to what if any advancements have been made on getting them to work on US GSM carriers? If we're still stuck I'm more than willing to jump into Dev on this and open to suggestions. My new D4 is running bone stock GB. I'm going to keep looking into the SD or USB possible fix's for hardbricks.
Thanx for the replies and thanx to [mbm], Jonpry, PhareignQ (think I mightta spelled that wrong), and HashCode for their knowledge, help, and suggestions along the way.
Hey man! You're the second one with same issue. I'm looking to buy new motherboard for droid 4 with same crapped bootloader + broken cdrom partition
For those who is interesting in, motorola factory cable doesn't work with droid 4 for some strange reason.
I can attest to the fact that the factory cable does, indeed, work with the D4 just like the Razr and other Motorola models.
I am not sure why yours doesn't or what condition your phone is in at this point, but the factory cable will power the device directly, bypassing the battery/charging circuit and allow you to flash it as long as the bootloader and mbmloader are not corrupt.
In that case, when the mbmloader fails, then nothing happens on the device at all unless a factory cable is connected, then it will flash the LED white just once as the cable is inserted and then loop continuously trying to load an interface and fails. The screen does nothing and the device is dead except pressing all 3 hardware buttons will arrest then restart the cycle of failed interface initialization once released.
I have a Razr in this state that I unfortunately attempted to flash some unknown files we received that we foolishly believed may have been an OEM bootloader unlock.
If you flash a corrupt image to the mbmloader the device is toast, AFAIK, although I do believe they have ways to recover them and in the past those methods often involved shorting a set of pads on the board with a paperclip while inserting the factory cable, initializing a timed event where the EMMC was bypassed and and factory I/O file could be loaded via a USB boot option.
I don't know if any of these methods could actually save any of our phones in this state, but I would like to believe its possible!
I just wanted to clarify about the factory cable.
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
queberican351 said:
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
Click to expand...
Click to collapse
Any solution on black screen and broken bootloader?
Here I have black screen with AC adapter connected. If I connect the phone to PC, I have green led indicator, but still black screen. Buttons have no reactions.
Anything new? Two users on a German bulletin board do have the same issue. I will get one Droid 4 of them in the next few days to have a look at it. But this thread sounds like there is no solution?
http://db.tt/u31VG45D
http://forum.xda-developers.com/showthread.php?t=2055839
The first link is to the most recent level 4 bootloader repair kit that we have for the Maserati/Droid 4 which is 0a.6c from pre ICS builds.
It is possible you may be able to use the pbrdl.bin and brdl.bin from those files with the mbmloader.bin and mbm.bin from a more current build to restore your device.
Again, these files are a year old now and may not work but you have little to lose in trying.
Use the method in the second link in Linux to try to restore your bootloader with the omapflash-lnx binary from that thread.
This is very likely to fail if the device has a recent firmware build on it but we don't have any of these repair kits for the newer bootloaders.
Good luck!
Thanks.
I got one of these phones. But it isn't even recognized via USB So I can't use these tools...
Is there any way to flash it via JTAG/ISP/...? Maybe this is the last chance - or this phone is dead ^^

[SOLVED] No USB sync, only charge O2X

Ok Guys, I started this thread because last weekend I had an interesting issue with my O2X. From one day to another, whenever I connected my phone to the computer it only charged, I had no USB connection. I’m not yet quite sure why it happened, the last thing I did to my phone was install CM10 nightly of 31 October 2012, and then I changed the default baseband I had (725) to the one GetRil was telling me to install (LGP990AT-00-V20l-EUR-XX-OCT-20-2011 0_CP) (this baseband didn’t fixed the strange noises of in call) two days after that I got the no USB bug, at first I thought it was software related, then after lots of reading and trying different cables and computers I thought it was hardware related, but then I saw an interesting chance of fixing it, and it did in my case
Credit goes to Kohos, I manage to have USB fixed temporary thanks to his post on modaco.com
I’M NOT TELLING THAT CM10 CAUSE THIS BUG, IT JUST HAPPENED TO ME WHILE USING THIS ROM
Specs
Phone: Optimus 2x (p990H made in south Korea)
Rom: CM10 Oct 31 2012 (when got the bug) now CM7 nightly 15 July 2012
Kernel: Symbiosis 2.6.32.59 v1.2
Carrier: Telcel
Country: México
Ril: 0725 (V10d, Europe)
BB: 1035.21_20110725
CWM: 5.0.2.0 (no touch version)
To solve this issue you need to have a stock ROM that can be flashed by CWM. Can be the rom, or a backup of the stock rom (If you don’t have one send me a PM), I didn’t tried stock-based ROM so those may or may not work; I’m not sure but rather use an original stock ROM. You also need to be able to enter CWM recovery, and have LGE drivers up to date.
For this method I used a stock nandroid backup.
I’ll describe step by step all I did to solve this issue so you can give it a shot:
1. If you have a flashable stock rom you may skip this step and go to step 3, if what you have is a nand backup you need to make your partitions back from EXT4 to EXT3 (this is the format that stock rom uses) so need to download the tool R2 found on the first post here:
http://forum.xda-developers.com/showthread.php?t=1021549
put it on your external SD card along with the backup of the stock rom
2. Reboot to enter CWM recovery and install the tool R2 (NOTE: this will erase all information of the internal memory)
3. Install or flash your stock rom or backup (In case you're using my backup, keep in mind, my file IS NOT a flashable rom, it is a backup, so trying to use the option "flash zip from external sd card" WON'T work, what you need to do is unzip the file and put it on sdcard/clockworkmod/bakcup, then on the recovery, you have to use the option "restore from external sd card", that way it should work, keep in mind that if you change the name of the file it will give md5 error for the name won't match the backup's md5)
4. Reboot and start the phone, once it is all loaded, on the phone app dial: 1809#*990# this will take you to the service (hidden) menu (If it doesn’t take you automatically to the service menu (without clicking dial) you’ll need another ROM or backup)
5. In this menu you’ll need to scroll to the option: Module Test > USB Mode Selection, in there make sure the option LG Android USB is selected
6. Then go back to the root of the hidden menu, and go to Port settings, there you’ll see several options, the ones we’re interested in are: AP USB, CP USB, AP UART, CP UART, the default should be AP USB, you can start playing with those options. (While doing this, you might want to play with your computer device manager scanning for hardware changes, that might help detecting the USB)
The recommendation is to select CP UART, wait, if your problem is not hardware related, it should popup a message of new unknown device, or LGE Platfrom Android USB device. If your USB show some life signal, then you’re almost done, if not, keep playing with the four options until you see some life signal.
What I did was select CP UART, click Ok, wait, AP UART, click OK, wait, CP USB, click OK, wait, AP USB, click OK, I waited here about 1 min, and then on the computer device manager I scanned for hardware changes, and suddenly my computer started installing all drivers again, this last option is the one that must keep selected even with reboot of the phone.
7. Once you get all done, reboot the phone and connect it to USB to see if it is recognized again, if not, repeat steps 4 to 6
8. Ok, If everything went fine, you should now have USB connection, now I would recommend you flash your Stock Rom, so everything that might cause this bug gets fixed (if you don’t do this, you might get the bug back eventually). To do so you might need to turn off your phone and plug it to your computer while clicking PWR and VOl- at the same time, if your computer doesn’t recognize your phone, use the device manager and scan for hardware changes, this should reinstall the driver needed to make this happen.
9. Finally I restored my last nandroid backup through cwm
I did this on Monday, and two days later I had no USB connection again, I repeated this steps and I had USB detection once more, today it happended again, and repeated the steps so I’m pretty sure this fix should work every time.
NOTE: This is a temporary fix, I've been trying to identify why the bug keeps comming back
Hope this help you all get over this serious bug :laugh:
Updates
This is my last froyo teclel stock backup
http://www.4shared.com/zip/AEVLSE34/2007-02-01000516.html
http://dl.dropbox.com/u/7867872/2007-02-01.00.05.16.zip
Disclaimer: Even though I'm sure it will work, try it at you own risk, I'm not responsable for any bad behavior or damage that could happen to your phone
UPDATE:
Ok, guys I told you I would make some test to make sure the bug won't come back or identify the problem, what I've found so far is that the problem might be caused by the wall charger (but might not the the only reason), If I'm not wrong, the LG stock charger has output of 5.2V - 650mA DC and I've been using a motorola charger (5.1V - 850mA DC output).
Four days ago I started charging my phone only with my computer (usb port has output of 5V - 500mA) and I've had no trouble at all, the bug hadn't come back, today I charged my phone with the wall charger and the bug immediately came back, so for now that's my theory, the wall charger, stock or not, might fail and deliver more current that the O2X need so it mess the phone, I'm going to make fix on my charger to prove my theory, (I have no money for a new charger xD, but I'm studying electronics) if it fix it, I'll let you know, but you can try and charge your O2X with your computer for a day or two to help me prove my theory or prove me wrong
UPDATE:
It's been some time since I last posted here, I've been busy with my finals, but have had some time to make some tests to my phone. On my last update I told you that I had a theory about the bug, well, so far I can tell you that the wall charger indeed have something to do with the bug, but its not the cause of it, I've been using my wall charger letting my phone connected all-night long and the bug seems to happen again, but letting my phone connected to the PC for a while allows the USB sync and debugging again, so I'm not sure why it happens, I'm about to finish my finals so I'll try to make some tests once I'm done, hope this giude help you
UPDATE:
Well, as I was testing my theory, I go back to zero, this is because, my phone, doesn't have the bug anymore, so I have no chance to keep testing solutions for it, the conclusion I got with this is that the wall charger doesn't create the bug, maybe it triggers it, but not always nor on every device because, I haven't sopped using the same wall charger and the bug haven't returned, the last thing I did was, use my computer to charge my phone for three days, always letting it charge to 100% (unless I have to move from the computer) and the bug didn't happened, then, on a rush I had to use the wall charger, the bug appeared instantly, and then keep charging it with the same charger, two days after that, the bug dissappeared, I made no rom change, nor baseband, nor ril, nor anything, just like that it disappeared, so, I have no way to keep testing, if it ever comes back, I'll make some tests again, but for now, I have nothing to work with, hope this thread help you to get over this bug, at least, for a while, I'll be reading this thread in case you have some trouble with the instructions or so, cheers
UPDATE:
Ok, so I deleted long ago the last backup you told me was not working, and since I went to CM10 from Pengus I haven't had the no USB bug, so, one person asked me for the backup, I just made a new one, (this one is 204 MB on zip, read step 3) and uploaded it to 4Shared and Dropbox, so, remember to read and follow the instructions as they are, hope this time you can restore this backup, and one more thing, this backup was made just after installing it on the phone, so it doesn't have even a gmail account, you have to put yours and update market if you need something from there, ps. dont mind the date of the name of the file, it is innacurate, cheers
I don't have any stock ROM backup that I can flash via CWM, can I use this instead?
http://forum.xda-developers.com/showthread.php?t=1617458
To be honest I don't see a big difference to my post you probably found while searching except that your version is waaaaay more to read.
kohos said:
when dialing the above mentioned 1809#*990# in the Port menu, switching from default AP USB to AP/CP UART gave me life signs.
After switching to AP UART I linked the Unknown device driver to lgusbdiag.inf located in C:/ProgramFiles(x86)/LG United Mobile Driver.
Suddenly it started installing it and is now recognized as: LGE Platform Android USB Device.
Once disconnected I lose USB again, I'm able to recreate the first steps though even in default AP USB mode by now.
Click to expand...
Click to collapse
But that aside I hope you realize that this is not a solving fix at all. All it does is giving people who got a fresh device the chance to flash a custom recovery. That's all. It won't work with any CM ROM and even Stock based ROMs.
Unless you have an early Froyo version flashed you will also have no ADB and it won't be recognized during the NVFlash process rendering it pretty much useless.
Having seen dozens of people having this particular problem where all the super obvious stuff like other cables, other pcs, other drivers etc. did not work, sending it to repair was the only fix I heard of solving this problem to date.
Of course I'm very curious on how you are going to identify the problem. Good luck.
kohos said:
To be honest I don't see a big difference to my post you probably found while searching except that your version is waaaaay more to read.
But that aside I hope you realize that this is not a solving fix at all. All it does is giving people who got a fresh device the chance to flash a custom recovery. That's all. It won't work with any CM ROM and even Stock based ROMs.
Unless you have an early Froyo version flashed you will also have no ADB and it won't be recognized during the NVFlash process rendering it pretty much useless.
Having seen dozens of people having this particular problem where all the super obvious stuff like other cables, other pcs, other drivers etc. did not work, sending it to repair was the only fix I heard of solving this problem to date.
Of course I'm very curious on how you are going to identify the problem. Good luck.
Click to expand...
Click to collapse
I'm extremely sorry, there's one think I missed, give you credit (fixing that right away), I actually found your post on modaco.com, and tried to access to the hidden menu from CM7 with no success, fortunately, I do have an early froyo backup that can be flashed through CWM, the only thing is that is the Telcel stock rom (I don't know if this can work with other O2X devices, I think there should not be problem at all)
About ADB, it work in full with the latest drivers installed and scanning for hardware changes on the computer device manager, It even work entering the S/W update service on the phone (to install a stock rom)
I know that many people have had this issue, I spent a lot of time reading forums and stuff about it, the only post that actually helped me, was yours, so, credit is yours, I did this post to show people what I excactly did (that's why is a lot to read, but I wanted to make it as easy as possible to follow up)
To identify the problem is a long and slow task, so, I'll be making some tests and let you know what I found, right now I have no much time, 'cuz I'm about to start my final exams, so I'll be busy, but as soon as I finish I'll be more dedicated to it, I'll be making hardware and software tests but can't promise anything yet
vanmarek said:
I don't have any stock ROM backup that I can flash via CWM, can I use this instead?
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
I tried to use that ROM, but couldn't manage to download it (I think it was removed, if you want to give it a shot try to find another flashable stock rom or backup, if not, give me some hours to clean my bakcup and upload it somewhere to let you use it, (it is mexico's telcel stock rom, but it should work)
Well Thanks ocr66 for this wonderfull news. I have the issue with usb connection from long time and i will give a try to your fix. You can post a stock rom here or a link to a rom that works??? In order to instal this fix i could lose the root??? Thank you 4 all!
vladutz9 said:
Well Thanks ocr66 for this wonderfull news. I have the issue with usb connection from long time and i will give a try to your fix. You can post a stock rom here or a link to a rom that works??? In order to instal this fix i could lose the root??? Thank you 4 all!
Click to expand...
Click to collapse
It all depends on what you install, if you manage to install stock rom through CWM or another recovery, yes you will loose root, but will have usb connection so you can root again, later today I'll upload my own froyo stock backup (it's mexican stock for telcel carrier, i think it should work out of méxico, maybe could cause network trouble on other countries, but its just a posibility, the important thing is that you be able to access the hidden menu), this backup I'll upload can be installed through cwm and its already rooted, so its like installing any custom rom, you'll keep your recovery and root
Remember, this is a temporary fix yet 'cuz I still get the bug comming back, maybe its because I am restoring my last working cwm backup, the only thing I haven't tried is clean all, install stock, root, install custom rom, and download again everything, maybe the bug is caused by something on that last cwm backup
I'll let you know as soon as I upload my bakcup
cheers
Well thank you! How i have this issue from one year i learned to live with her, but i could not live without root. So if i will instal a stock rom without root i will be unable to correct the usb connection i will get stuck with stock rom and no root. Will be the end of my phone. In am interesed to gain the usb connection for change the bb, i supose i can be something wrong with my bb 1035.21_20110725 and gingerbread. You can check to change the bb to see if you get again losing usb connection. Cheers and thank you 4 all.
got this after CM10 install
I've only had my phone for 1 day from new and already got this problem.
Rooted with superoneclick
Installed CWM v5.x
Installed CM10 Nightly Nov 13th
Now no USB mode, only charging.
baseband: v10e
RIL: CM10 1106
EDIT UPDATE: Well its working for me again now, I think in my case it was because I was using Linux and CM10.
By going to Settings/Storage then pressing menu button and selecting 'USB computer connection' I was able to change the 'Connect as' option from MTP to Mass storage and it now works.
@tiktok1 Lucky you!!!
@ocr66 Any news about this bug???
vladutz9 said:
@tiktok1 Lucky you!!!
@ocr66 Any news about this bug???
Click to expand...
Click to collapse
Actually yes, I've managed to identify what's triggering the bug at least in my phone, so might be the same for others as well, see the second post
BTW, did you tried already the fix? did you used my stock froyo backup?, if it didn't work, I can make another and upload it
Hi. Looks like I have the same problem with USB as you. Your theory about the wall charger might be correct. Here's my situation:
So, I've got my phone two days ago, bought used, came with a general Sony Ericsson USB charger. It says it outs 850mA at 5.0V (confirmed with a multimeter). The phone is on stock Android 2.2.2, isn't rooted yet. The guy from who I got the phone says that he suffered too with this kind of problem, however he got it working after 2 weeks without the use of the hidden menu. This means, that in those 2 weeks, he might have used a PC or a laptop to charge the phone. I tried the hidden menu port settings, however the only "working" mode is AP UART, but it is not recognizable by the PC, even if I try to link the LG drivers manually. Cycling through the modes did not help. I'll try to charge the phone with my PC, and see if that dose anything.
Details of the phone:
Firmware version: 2.2.2
Baseband: 1035.21_20110218
Kernel: 2.6.32.9-dirty
Build: FRG83G
LGE Version: LGEP990-V10b
Wow. All i can say is wow! Gosh! Just dunno how grateful I am stumbling upon this thread! Kudos to you sir,you just ended my 2 month long frustration about my phone not being able to communicate to my PC. was getting ready to send the phone for service then I read this. I had flashed every GB ROM imaginable from the dev thread with no luck. I am running carburano DM 1.7 now,all I did was to go to the hidden menu,switched one port setting,wait,then voila! PC recognized my phone! Again thanks,great respect to you,and Superskill.
Hi, this is my post to thebgeneral board by accident, didnt even read there was a qanda section lol
It didn't work on my gfs phone unfortunately, notvsure what was wrong.
Maybe I should try stock Rom instead of modded, how long are you guys waiting for the phone to show up?
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Sent from my LG-P990 using xda app-developers app
mondc1088 said:
Wow. All i can say is wow! Gosh! Just dunno how grateful I am stumbling upon this thread! Kudos to you sir,you just ended my 2 month long frustration about my phone not being able to communicate to my PC. was getting ready to send the phone for service then I read this. I had flashed every GB ROM imaginable from the dev thread with no luck. I am running carburano DM 1.7 now,all I did was to go to the hidden menu,switched one port setting,wait,then voila! PC recognized my phone! Again thanks,great respect to you,and Superskill.
Click to expand...
Click to collapse
Lucky you! I was to in DM 1.7 but when i was in hidden menu i chosing another port, don´t want to save the settings. Anyway congrats!
No luck...
I've used my PC for charging for a week now, still no USB connectivity. I think this might be a hardware issue with me as the phone sometimes says it's charging, but it's actually in my hands with no cable attached. I managed to root the stock 2.2.2 firmware with GingerBreak and installed CM7 with RomManager with a downloaded ZIP on the SD card. Thanks for the tips anyways.
Doctor0710 said:
I've used my PC for charging for a week now, still no USB connectivity. I think this might be a hardware issue with me as the phone sometimes says it's charging, but it's actually in my hands with no cable attached. I managed to root the stock 2.2.2 firmware with GingerBreak and installed CM7 with RomManager with a downloaded ZIP on the SD card. Thanks for the tips anyways.
Click to expand...
Click to collapse
Hello, I'm sorry it took me a while to answer, I've been busy with my finals, did you tired the tutorial I posted? the hidden menu modification? I know that you let your phone charging for a while with your pc, actually, it should've worked but, maybe the problem on your phone actually is something else, 'cuz I haven't had that issue that the phone says it is charging but its not connected to the charger, my brother told me that he have had that same issue but with other phone, he changed the wall charger and that "fixed" it, but I think if you haven't tried the tutorial, give it a shot, try changing to CP UART if your phone's usb is working as it should, your computer should detect a new unknown device, if not, myabe your phone is hardware damaged, hope you can fix your phone soon
cheers
monkeyass said:
Hi, this is my post to thebgeneral board by accident, didnt even read there was a qanda section lol
It didn't work on my gfs phone unfortunately, notvsure what was wrong.
Maybe I should try stock Rom instead of modded, how long are you guys waiting for the phone to show up?
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What I did on my phone is exactly what I posted, if your computer haven't detected your phone on CP UART I doubt rebooting will make a change, anyways the most important thing to see if your usb is damaged or not is to try on the hidden menu the option CP UART it almost instantly detect the device, but, not everytime, I once waited there 20 min, so, give it a shot if you want, the stock rom I posted (on second post) is Mexico's Telcel stock rom, rooted, it doesn't delete your cwm recovery nor root, you can give it a try if you want, but read the instructions 'cuz you have to restore the ext3 format of your phone's partition to make it work (it stays on boot loop if you don't restore ext3 format), if the backup doesn't work, let me know to upload a new backup, hope you can fix it
cheers
vladutz9 said:
Lucky you! I was to in DM 1.7 but when i was in hidden menu i chosing another port, don´t want to save the settings. Anyway congrats!
Click to expand...
Click to collapse
Hey did you managed to fix the problem yet? did you tried the bakcup I uploaded? it's Mexico's telcel stock rom, rooted, its made by cwm so it doens't delete your cwm recovery, give it a try if the backup doesn't work, let me know to make a new one and upload it ok?
cheers

Moto X won't turn on

I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Follow the instructions on how to enter stock recovery. This should help.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94946/p/30,6720,8696
Sent from my XT1060 using Tapatalk
Still no luck...
garrettpen said:
Still no luck...
Click to expand...
Click to collapse
Sorry bud. Sounds like you might have bigger issues than I can help you with. However, you should try to connect it to your computer and see if you get anything. Also keep trying to power it on while on a USB or charger.
Hopefully someone with a similar experience can chime in.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2477132
You can try to flash your phones stock ROM using this tool kit if you can get into the Boot loader. I just used it to flash back to stock on my sprint moto x. I know you are in a different situation but I can't hurt to try
Sent from my XT1056 using Tapatalk
garrettpen said:
I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Click to expand...
Click to collapse
hold power button for 1 min if you feel the phone vibrate that is good.
now try holding Volume Up + Power will it boot into the bootloader.
If yes great time to restore to stock
If No then your phone is hard bricked and you will have to get it replaced.
one easy way to find out if your phone is hard bricked is to plug it into the computer and see what drivers it tries to install
if it say qhsusb_dload then i know for a fact that your phone is Hard bricked.
If that is the case call your carrier or go to a local store and tell them that your phone was on 4.2.2 and you downloaded the 4.4 OTA and it rebooted to install it and now it won't turn on at all they should give you a brand new phone because it was the phones problem.
When you get your new phone please post here first with What Carrier Moto X you have and what android version it is on 4.2.2 / 4.2.2 Camera Update / 4.4. and i will help you get your phone rooted and up and running correctly
Good Luck My Friend and please don't be afraid to ask for help
Mist likely hard bricked, you're not the only person this has happen too and won't be the last, if you're getting the driver mussing as previously posted ,I agree and its hard bricked. Which 4.2 stick firmware where you on? Pre camera update? At least you can call you're carrier and say you attempted to install an ota which in fact did brick your phone don't tell them you tried to root it of course, good.luck
Sent on my Moto X

Categories

Resources