Develop Bugs

Unable to flash Rom. Help Suck in bootloader Or Google Logo with Padlock

been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS

Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium

Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.

I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.

??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it

NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before

what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App

Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer

no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex

NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...

i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit

[SOLVED] Can I install stock 2.3.3 on an R800x with a locked bootloader?

I recently acquired a new r800x which came with 2.3.4, and thus can't be zerg'd. I tried to unlock the bootloader but the service menu has no status (yes or no) on the bootloader and sony didn't send me an unlock code when I tried their website. It's my understanding that stock firmware can be flashed with a locked bootloader but I can't make it work. I downloaded the latest flashtool from flashtool.net, installed the flashboot and adb drivers and got a copy of R800x_3.0.1.E.0.88_Verizon ftf. But when I start flashtool and connect my phone (usb debug & unknown source enabled) It isn't recognized and prompts for user selection. I select Xperia play, go to flashmode, select the firmware and get to the waiting for phone screen. Power off, hold back and connect, but nothing ever happens after that.
I've looked for tutorials on here and elsewhere, but none seem to address my problem, or if they do have a solution that doesn't work for me. Any help would be greatly appreciated, I'm hoping I just missed something that can be easily corrected.
Thank you.

raithe said:
I recently acquired a new r800x which came with 2.3.4, and thus can't be zerg'd. I tried to unlock the bootloader but the service menu has no status (yes or no) on the bootloader and sony didn't send me an unlock code when I tried their website. It's my understanding that stock firmware can be flashed with a locked bootloader but I can't make it work. I downloaded the latest flashtool from flashtool.net, installed the flashboot and adb drivers and got a copy of R800x_3.0.1.E.0.88_Verizon ftf. But when I start flashtool and connect my phone (usb debug & unknown source enabled) It isn't recognized and prompts for user selection. I select Xperia play, go to flashmode, select the firmware and get to the waiting for phone screen. Power off, hold back and connect, but nothing ever happens after that.
I've looked for tutorials on here and elsewhere, but none seem to address my problem, or if they do have a solution that doesn't work for me. Any help would be greatly appreciated, I'm hoping I just missed something that can be easily corrected.
Thank you.
Click to expand...
Click to collapse
Go into the flashtool program folder on your pc and then open the folder called drivers, run the program in there select the options for xperia play drivers and flashtool and fastboot drivers.

Many thanks, that did the trick. I had installed the play driver but missed the other two. Sigh, it's always a driver problem with android. Funny part to me is that the driver step varies with every phone and that's the step the tutorials and readme's always gloss over like it's self explanatory. No worries though done and good. Thanks for your help.

[Q] Can not go into fastboot

I'm trying to unlock the boot loader on my phone so i can get cyanogenmod but i can not go into fastboot, i turn off my phone, hold down the search while i plug it into my computer but after a couple seconds it just show the SE logo then the charging symbol, does it have to be charged? i already installed the fastboot driver i have pc companion (I don't mind uninstalling if i have to) is there a certain place i have to install the driver? please help, i also tried google but couldnt find anything like my situation

You need to unlock the bootloader. It may be different depend on which carrier version of the play you have. R800i and R800x can be done freely from Sony website. You have to pay third party drive like WotanServer to get the R800a unlock.
sent via tapatalk

[Q] Trying to unlock bootloader

Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you

Roflmao. Guessing you haven't read any threads regarding root

WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
Sadly unless you have the h815 version you are NOT going to get any further than what you are getting (at least at this point in time). The ONLY version of the G4 that has root right now is the h815 and that is simply because LG released the bootloader unlock via their page.
It is being worked on but you have to remember that this is a very new device and this is going to take some time, so just relax and play the waiting game with the rest of us in the mean time.

Yeah I have read the thread about rooting and I in fact do have the h815. That's why I am trying to root it and that's why I am busy trying to unlock the bootloader with the LG unlock tool. I said I'm a noob, not a dumbass regarding unlocking a bootloader cause before I had a samsung and I never needed to unlock that.
So once again my question stands why is my device getting unresponsive once it is succesfully been rebooted into bootloader via command prompt?
Thank you

WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
Have you enabled the OEM Bootloader In Dev Options? Who is your provider as some of them will force lock the bootloader and not allow it to be unlocked unless you take it to a phone shop but you will void both LG's and Their Warranty and any support from them

Also when you are on bootloader screen with few lines with very litle fonts, try to make sure that in your Windows devices manager, your phone is corectly listed.
For some reason it did happend to me that drivers for the phone in bootloader mode wasn't properly installed.

bleuxeon said:
Also when you are on bootloader screen with few lines with very litle fonts, try to make sure that in your Windows devices manager, your phone is corectly listed.
For some reason it did happend to me that drivers for the phone in bootloader mode wasn't properly installed.
Click to expand...
Click to collapse
When I go into bootloader my PC does make that sound where it's like I disconnected a USB device. But as far as I can tell there's nothing unusual going in Windows device manager. Which drivers have you installed? I installed the pc drivers via my phone. And I saw adb drivers in there when it got installed. I thought that would suffice.
But it also freezes up. I can't close the phone anymore even with the 10-second power hold. It just locks up

Im having the exact same problem did everything right but as soon as i enter bootloading mode my pc just doesnt reconize it anymore or something

WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
I had exactly the same problem with the same model. When the device is in fastboot mode and not responding open up devices and printers. For me it was now showing as android instead of G4 and the USB disconnect sound means you dont have to correct drivers even if you installed the LG drivers.
For me the fix was going to windows updater and allow it to update drivers. Now right click the android device and trouble run it. It updated the drivers for me
and I was able to run the command to get the device-id.
Hope it helps

Legion377 said:
I had exactly the same problem with the same model. When the device is in fastboot mode and not responding open up devices and printers. For me it was now showing as android instead of G4 and the USB disconnect sound means you dont have to correct drivers even if you installed the LG drivers.
For me the fix was going to windows updater and allow it to update drivers. Now right click the android device and trouble run it. It updated the drivers for me
and I was able to run the command to get the device-id.
Hope it helps
Click to expand...
Click to collapse
I have the same problem, what do you mean by "windows updater"? do you mean "windows update"?
And what is "trouble run it"?
Thanks in advance.

Sony Ericsson Play R800AT Boot loop.

So, here's the deal with this phone. It's sat untouched for many many years. The original owner can't remember why she got rid of it (family friend). So I volunteered to take it, and turn it into an emulator device. However, it was made clear as to why she got rid of it. The phone is stuck in a gnarly boot loop. The boot loop is, Sony Ericsson screen lit up, and then goes to an unlit version of the logo. After a while, the phone will restart repeat. The phone will get into flash mode (green light) and will not continue the loop but stays on the unlit version of Sony Ericcson. I've gotten it into fastboot once, maybe twice, but I can't remember exactly how I did it (holding menu doesn't work)
I have installed the drivers for the phone, however, the phone is listed as:
E:\
Device Type: Portal Device
Manufacturer: SEMC
Location: on Volume
The drivers that it is apparently using is wpdfs.inf
Things I have tried to correct this issue.
-The Xperia app (tells me to enter flashmode in its own way and never does anything after)
-Flashing using "FlashTool"
It sees a phone but just says.
"19/025/2018 22:25:46 - INFO - Device connected with USB debugging off
19/025/2018 22:25:46 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I've attempted using a fastboot method but nothing substantial as fastboot rarely happens.
Accessing the device through ADB (ADB shows not devices connected
Accessing the device through FastBoot (FastBoot shows "waiting for devices")
I have crawled through dozens of pages worth of information, similar questions, similar problems and come up short. Any advice would be super helpful.
Will provide images, and further information if requested. Thanks for your time.

I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.

inaroom said:
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
Click to expand...
Click to collapse
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.

Disenfranchised said:
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Click to expand...
Click to collapse
to install flashtools drivers in win 10 you need to disable uac but maybe you already did that. make sure the adb drivers are fully and correctly installe. have you tried flashing a kernel in fastboot mode by pushing the search button? also i would try to install r800i or r800a drivers. then i would suggest to make a little bit of search (i know you already did a lot...) to ensure that you can flash r800i or r800a firmware on your r800at and also try that route. i´m sorry i can´t help you more but i´m in europe and never worked on a r800at..

Hey, dont worry about it. This post is basically a hail mary for a phone that super old. I haven't tried flashing in fast boot because I have only ever gotten in fast boot once or twice. Fast boot is menu key correct? Cause I see conflict information all over the place.

i´m pretty sure it´s the search button for fastboot mode

Do you need a new battery?
Hi Disenfranchised,
I recently got out my old r800i GSM which was regularly being flung across the lounge by my kids, attached a charging cable and I had exactly the same boot loop issues as yours, but only as long as the phone was being charged. I ended up biting the bullet and buying a new battery and the phone started up. I ended up flashing Gin2Kat and it has been working well other than occasionally reverting back to the same behaviour for about an hour if the battery was completely discharged. The funny thing is when i finally manage to boot the phone at the right point during the boot loop cycle, the battery is only at 2%, meaning during the boot loop the battery is charging for maybe only a fraction of the on-off cycle.
It's a bit of an outlay (my battery was about GBP £10 - ebay). I now play SNES games on this every day during my commute. There are a few quibbles - the audio out port doesn't work (bluetooth audio works) and I get a wifi error but I ended up using Gin2Kat's apk installer to install my apps from micro-sd.
Anyway, it's a bit of a risk but see how it goes.
Fuzzy