I've been playing with this phone for about a month. There have been various problems flashing roms, But I have V30B working now. Maybe.
Software version reports as P92530B instead of LGP925-V30B-... ect.
Baseband version reports as OMAP4430/XMM6260 instead of L6260_MODEM_SIC_... etc.
Maintenance menu is inaccessible. (*#*#4636#*#*)
I'm stuck with fastboot instead of the regular color LG boot logo.
I don't have phone service, So I can't check for cell functionality. I can scan for networks, and see signal strength.
I think the phone works properly, But these things are worrisome. Particularly the fastboot mode. I can find no instructions on getting rid of that.
Thanks in advance
If you don't want wkpark bootloader (some custom ROMs require it and it is usually required for overclock apps) you will need to install stock bootloader. I would personally leave it be. However, be advised that if you install a custom ROM that is not compatible with wkpark bootloader, you may get a 'security error' that either requires flashing/installing a stock bootloader, or flashing a firmware (which rewrites the bootloader).
So the wkpark bootloader is the silver LG logo, And I just have to flash some other one in it's place?
It is annoying that I can't turn the phone off, But I can live with it for now. Later I will want to change that.
Thanks
Yes grey LG logo indicates you have wkpark custom bootloader. It has a bug that causes restart instead of off. Long press power (10 sec. or so) to power off.
I've determined, using the hidden menu functions, That the software versions of the
AP and CP do inded match.
My only remaining issue is access to the maintenance menu. Any help with this would be appreciated.
Don't know what that is.
Related
I have two Verizon Motorola Droid A855's that I want to turn into iPod Touch alternatives since I already own them. The phones will not have an active phone plan, so no 3G, I'll be using Wi-Fi only. This has worked fine, I am able to setup a Google account, install apps, etc. One is working great, the other is giving me fits. I have several problems with it. At this point both phones are running FRK76 (2.2.3). The one that works right updated itself OTA. The other one was at 2.2 and wouldn't update itself to 2.2.3, so I tried doing it via recovery mode and this is where my adventure started.
PROBLEM #1: Can't enter original recovery mode.
I can get into the original recovery mode normally on one of the phones, the other will not show the menu. I use Power+X buttons, the exclamation point graphic shows up, I press VolumeUp+Camera buttons and nothing happens. Works fine on the other one. I've tried the other key combos that are meant for other Droids just in case, nothing happens. I have verified the buttons work. I've also read that if I SBF back to some original rom (I've tried ESD20, FRG83G and FRK76 that I got from Peter Alfonso's site) that it will restore the original recovery mode. It has not helped. No matter what I've tried so far VolumeUp+Camera will not bring up the original recovery menu. I've been searching, and searching and nothing seems to work.
PROBLEM #2: Is there a way to activate the phone after SBF without having a Verizon phone plan?
I was able to root the phone using SuperOneClick, install Droid 2 Bootstraper, and ROM Manager. I used ROM Manager to Flash ClockworkMod Recovery 2.5.0.1 and then pressed Reboot into Recovery in ROM Manager and upon reboot I can get to a recovery menu.
That all being said, I've yet to install a ROM from within recovery that makes the phone work correctly. So, I moved on to doing SBF and ran into other problems. After any SBF install I now get a dark grey triangle in the status bar. I'm pretty sure this means I'm in roaming mode becasue I need to activate the phone using *228 option 1. The problem is that I do not have an active plan for this phone anymore so it won't activate, it asks me to enter the 10 digit phone # of the phone. I tried putting in 123-123-1234 and obviously that doesn't work, it starts to send me to customer service. At this point I just hang up.
PROBLEM #3: SBF'ed phone won't update stock apps.
After I did an SBF on the problem phone and setup a Google account on it, I then used the old Market to install any simple app. Once that is done Market updates itself to Play Store. I enter Play Store and it should show me all a list of the stock apps under the INSTALLED screen plus any available updates to the stock apps, like Facebook, Twitter, Maps, Play Music. Overnight these apps did finally show up under the ALL screen of Play Store, but they just say "Installed" and when I click on one there is no Update button, only open. None of the stock apps show up under INSTALLED. The phone thinks the newest versions of these apps is already installed, but they aren't. I am not sure what to do about this. I would like to be able to update to the newest stock apps (well, most of them). I keep reusing the same Google account on this problem phone, so maybe setting up a new account might work?
This was a long post, it seems around here shorter posts get answered but then people always ask for more info. So, I just gave the info upfront. Hope there is some help or suggestions out there. Thanks!
Problem #2 is a non-issue. You said it will not be active on a line, so there is absolutely no need to do a *228 on the phone. In fact, you will get better battery life if you turn off the cellular radio putting it into airplane mode. Wi-fi will still work if you turn it on after it's in airplane mode.
Recently tried the nightlies for Cyan 10.2, wasn't satisfied, flashed older Cyan 10.1 and proper GAaps. Clean wiped and formatted. Phone has gone bunk. Restarting causes the phone to go into AP Fastboot instead of normal reboot or recovery. However, starting in fastboot and choosing to boot normally works.
Real is issue is, upon restarting, was told to insert SIM card, despite it already being in the phone. Checked the card, seems to be fine, however, there's no network connection, and can't turn on wifi. Best bet I've been linked to is the fact that the APN settings are gone. Tried putting in the same APN settings from a default atrix hd phone, but saving the settings takes me back to the empty list of APN's.
Looking for possible solutions, either to why none of the APN's wont save, why they're gone in the first place, and why booting seems to be messed up now.
What did you format? Maybe the modem by mistake?
http://forum.xda-developers.com/showthread.php?t=2469104
Seems to have been the issue.
Decided after finding out I may be able to trade in my phone for a newer model to just unroot and restore to default. Ran stock ROM with RSD, everything seems fine.
Only other question is, will relocking the boot loader with fastboot keep the phone running presentably so I can trade it in? Stock ROM and recovery are running fine, only thing left if getting rid of the warranty void message.
Can't relock bootloader.
Sent from my MB886 using XDA Premium 4 mobile app
you could flash a new image over the bootloader unlocked image. it most likely would not take much image wise to fool them.
I'm trying to install the DK Zen RLS2 ROM here:
http://forum.xda-developers.com/showthread.php?t=2309928
I figured they wouldn't want me mucking the thread up with my personal problems.
What happens when I install the ROM is that it will start up and get as far as the lock screen. Instead of going into the whole new-phone-setup business, it just stays on the lock screen and doesn't respond to any touch input. I can turn the screen on and off with the power button and I can change the volume, but I can't unlock, pull down the status bar, or open the volume settings. Holding the power button won't bring up the power menu (no real surprise) but it will reboot the phone after 10 seconds.
I'm fairly certain I've used this ROM before, but I recently formatted my phone and relocked it and everything in an attempt to fix other issues. I'm able to use other ROMs just fine without getting this issue. So far I've tried Stock with Goodies (http://forum.xda-developers.com/showthread.php?t=2301672) and SuperBLUE (http://forum.xda-developers.com/showthread.php?t=2520499). It seems, from reading the threads, that each of these ROMs is based on 4.3, but considering the way DK Zen rearranges my SD card, I have a feeling it's different (it adds the "0" folders; does that mean that it's a downgrade from or an upgrade to 4.3?).
Any thoughts? The one thing I can see from this ROM is that it gives me a full 4G signal, whereas the other ROMs only get me a few bars. Maybe the ROM isn't being honest, but if it is I'd really like to get it working for this alone (also volume rocker to skip tracks).
Reading through this thread (http://forum.xda-developers.com/showthread.php?t=2470569) it sounds like going with a 1.31 firmware (which DK Zen is based on) will have touchscreen issues if my phone's firmware doesn't match. Checking the Bootloader screen, I have 3.04.651.2 on the OS line. Is that the cause of my problems? Is it possible to downgrade my firmware, and would that be advisable anyway?
I feel like not many people run into this issue, or if they do they already know why, but I might as well post what I did here.
The touch panel firmware in 3.04 isn't compatible with earlier ROMs (or at least 1.31 ROMs). So, I had to go back to an older firmware. To do that, I just used Rum Runner to get s-off which I hadn't done at any point before. That was a very simple process, though I couldn't do it on my work computer, probably because of all the server and network security software that's installed here.
Once I got s-off, I was able to flash a 1.29 firmware using fastboot. From there, I flashed the DK Zen ROM that I was looking at and the touchscreen worked just fine.
Yay for learning!
Hello,
I need some help with install CyanogenMod 12 - Neo's Homebuilds
I have Sony Xperia T LT30p
Android ver: 4.3
Kernel ver: 3.4.0
Build number: 9.2.A.1.199
Phone is unlocked and rooted.
I have problem on next steps - recovery and flash
In instruction to install CyanogenMod12 doesn't write how recovery I shoud use. I read, most people use CWM, so I was looking for that recovery.
Unfortunatelly, from this post http://forum.xda-developers.com/showthread.php?t=2012738 when I tried run CWM v9 installer for JB, select my phone from list
I have only " deamon not running, starting it now on port 5037* deamon startded successfully" and nothing happens.
I flashed this one: http://forum.xda-developers.com/showthread.php?t=2677553 Installed correctly, I go to cwm recovery, I did a backup, but when I was tried
install rom, I have an error something like "You tried install rom for LT30, but your device is Hayabusa" and installation is aborted.
What recovery (and from where) I need, to correctly install this mod? Do I need install another kernel too? (All kernels what I seen, have older build number than I have on the phone)
Could someone help me to finish this process?
Best Regards
Same issue like here.
http://forum.xda-developers.com/showthread.php?t=3038250
Check this out. :good:
Hey WhiteNeo, thanks for response.
I read this post before, but in there, user has a Xperia V, and has a different Build number, and he has (a good?) recovery (I don't know if this has any significance) and aborts appears, in the middle of installation with different kind of error log.
I have abort message on the beginning, telling that the rom is ok but device is Hayabusa..:/
Could you tell me what recovery I should use? (Or maybe this what I have installed is correctly? I don't tried do this on the TRWP)
I need flash another kernel? or it's not necessary?
Still, the steps I mentioned are the same.. Either remove the first line in updater-script, or flash my kernel via fastboot before installing the rom.
The kernel does include a working recovery from where you may flash the rom itself.
Good news, I finished and it works
I flashed the kernel – boot.img from your rom zip package (maybe it worth add this info to the instruction on first page?)
Thanks very very! much for your hints. So now I join to the „tester” your great rom
For now (using only 1 hour) I found only 2 bugs.
First is a „!” symbol near gsm signal when we turn off cellular data.
Second is a unable to turn on the camera using dedicated button.
Thanks again.:good:
KOMODO404 said:
First is a „!” symbol near gsm signal when we turn off cellular data.
Click to expand...
Click to collapse
Funnily enough, that symbol shows that you don't have cellular data (internet connection); if you don't like the symbol, turn on cellular data or connect to a working WiFi network.
Antiga Prime said:
Funnily enough, that symbol shows that you don't have cellular data (internet connection); if you don't like the symbol, turn on cellular data or connect to a working WiFi network.
Click to expand...
Click to collapse
The "!" symbol, it's not funnily enough, on any kind of system or application.
It's little weird kind of notification about disabled internet connection. Many people save the battery or $ by
disabling cellular data (in stock system you don't have any icon to inform that status) and that should be
something "normal", "!" is unnecessary to inform that fact.
KOMODO404 said:
The "!" symbol, it's not funnily enough, on any kind of system or application.
It's little weird kind of notification about disabled internet connection. Many people save the battery or $ by
disabling cellular data (in stock system you don't have any icon to inform that status) and that should be
something "normal", "!" is unnecessary to inform that fact.
Click to expand...
Click to collapse
Then you should probably complain to Google and it's developers for creating that ugly and disgusting icon, instead of labeling it as a bug. Just because there is something about your phone that you don't like doesn't mean it's a bug; that's like saying my battery only lasting 18 hours is a bug, when in fact I leave my screen on for more than 3 hours.
Also, I didn't know there was an Official Android 5 Stock Rom for either the T/TX Sony phone, so I wouldn't know about how it behaves. Please do share the news.
http://www.androidpolice.com/2014/10/18/lollipop-feature-spotlight-android-now-defaults-to-mobile-data-when-wi-fi-has-no-internet-access-signal-icon-adds-a-for-no-connection/
Also custom ROMs don't always have the same features stock ROMs do, for instance, opening the camera app when clicking on the camera button (doesn't work on any of the custom ROMs I've used), but again, that doesn't mean it's a bug.
You can probably use Xposed + Xposed Additions to get that function.
Antiga Prime said:
Then you should probably complain to Google and it's developers for creating that ugly and disgusting icon, instead of labeling it as a bug. Just because there is something about your phone that you don't like doesn't mean it's a bug; that's like saying my battery only lasting 18 hours is a bug, when in fact I leave my screen on for more than 3 hours.
Also, I didn't know there was an Official Android 5 Stock Rom for either the T/TX Sony phone, so I wouldn't know about how it behaves. Please do share the news.
Also custom ROMs don't always have the same features stock ROMs do, for instance, opening the camera app when clicking on the camera button (doesn't work on any of the custom ROMs I've used), but again, that doesn't mean it's a bug.
You can probably use Xposed + Xposed Additions to get that function.
Click to expand...
Click to collapse
I didn't know that in the original android 5.x symbol "!" near gsm signal, is implemented - is changing, figure things out.
For me, its a little strange, "!" symbol should inform that something is wrong / something damaged but in this case
everything is ok but symbol is displayed. All right, this is only my opinion.
I didn't write nowhere about official android 5 for Xperia T, so I don't know what you mean.
About camera button, it's works, example on the Ultimate PureXT custom ROM, so it is possible to work on custom rom.
If it's designed for something, and now it's not working as it should....how do you call it if not a bug? fault? defect? mistake?
Fortunately, it's only a details and I'm grateful to the authors, for this custom rom and I keep my fingers crossed for next update
to improve this rom.
KOMODO404 said:
I didn't write nowhere about official android 5 for Xperia T, so I don't know what you mean.
About camera button, it's works, example on the Ultimate PureXT custom ROM, so it is possible to work on custom rom.
If it's designed for something, and now it's not working as it should....how do you call it if not a bug? fault? defect? mistake?
Fortunately, it's only a details and I'm grateful to the authors, for this custom rom and I keep my fingers crossed for next update
to improve this rom.
Click to expand...
Click to collapse
What I meant was that even on Stock ROMs, the icons change to show there is no connection to Google's servers (blue colored signal in 4.3 and below, and orange colored in QS in 4.4), so it shouldn't surprise you that the function is still there.
About the camera button... I would probably call that not having access to the entirety of Sony's source code, drivers, etc., in order to implement that function, and custom ROM developers probably just haven't simply figured that out yet; because, for your information, the Ultimate PureXT Rom is not a custom ROM.
Hello,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!
I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?