Device is a pretty much new LG V30 from verizon, running android 8.
I have done pretty much nothing with the device yet. No root, no tinkering, nothing. I accidentally accepted the software update request it showed me today, which I didn't want. I shut the device down but everytime I would turn it on it would start the update progress.
The only other option I had was booting into recovery, so I did that. I was presented with the following options:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I went with factory reset. After that the phone won't boot anymore, and all I see is this screen:
What can I do now?
Again: No root. No unlocked bootloader. Nothing. I used LG's "require password on boot" feature though, which I assume is equal to android's full disk encryption. (?)
I talked to LG already since it's under warrenty (got it literally last week) - LG however told me the warrenty is void because there is a small crack on the back of the phone. WTF? Is that even true? I didn't drop the phone. I don't even know where the crack comes from. It's small. Shouldn't the warrenty cover that TOO instead of voiding the warrenty for everything else? Like jesus christ all I want is LG to fix my software why does a crack on the back matter?
From what I see my only option is to access fastboot and re-flash the ROM? The thing is: How do I access fastboot on this phone? Power and Vol- brings me into recovery (stock) everytime. Are there flashable images for the V30?
No one knows what I should try or what I could look into? This doesn't sound like it could be something overly complex to me.
Issue still persists. I had a talk with verzion at their store and they said I'd have to pay a $149 deductible. So what can I do now?
I'm assuming flashing a ROM via fastboot. Two questions:
1) Where can I get the ROM from?
2) How can I access fastboot on this phone? The method suggested everywhere puts me in LG's stock recovery, not in fastboot.
Related
Hey everyone, I've searched thru the forum looking to see if someone had the same issues I did, and the stellar assistance that was given to others with various problems, I'm hoping that I can get the same (haven't seen anyone with my particular issues yet).
As mentioned in the title, I'm using a stock T-Mobile Amaze, unlocked and I'm using it in Barbados. A few weeks ago, a notification popped up on my phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Naturally, I was curious to see what this update was, but after ensuring that everything that was required for the update was in place, I see this...
...which I'm sure means there's some error in installing the update. The phone freezes, and I can't get out of this without doing a battery pull a la blackberry. This is issue 1.
Issue 2 is that a lot of my menus have wrong names, e.g. the 1 for Wireless connections says "Turn It On"
and even the options within the menus are wrong, e.g. In the display menu, to set the screen brightness, that option is entitled "Set A PIN code to lock your UIM Card"
Further to these, often when I try to access many of my settings, the whole shebang crashes, and asks me about sending an error report. Til now, nothing has changed in that regard. Any assistance to these problems would be GREATLY appreciated. Thanks in advance.
Your best bet is just to do a master reset on the phone. It should clear up all those issues.
tried it...didn't work (well, the menus still are screwed up, and the settings keep crashing when i try to access some of them, like the Sound menu.)
Kagr1ffman said:
tried it...didn't work (well, the menus still are screwed up, and the settings keep crashing when i try to access some of them, like the Sound menu.)
Click to expand...
Click to collapse
Have you tried locking your bootloader and flashing the stock firmware?
You already unlocked your bootloader, right?
Just flash a custom rom.
If you REALLY want to flash the 1.43 update then relock your bootloader and flash this: http://goo.gl/KvHzj
Rename it to PH85IMG.zip and store it on the root of your sdcard.
It will update everything.
Then unlock your bootloader again, reroot and you'll be good.
I held off updating my XZU to 4.3 until root was found, as I don't want to live without it (because of: Titanium backup, VPN software, full linux install on uSD card).
My XZU has an unlocked bootloader, too, as well as being rooted. I'd also modified /system/build.props too.
When I saw the OTA, I tried it and it failed without giving a reason, so I booted up Windows and used Sony PC Companion, and it too failed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've looked at many XZU update threads and none seem to mention this specific issue.
When the tool runs, it takes a minute to "prepare" (it seems to have kept stuff it downloaded the first time). The phone does stuff, screen goes blank. Then the update fails giving the above message. The phone is then dead, and I have to unplug the USB before I can turn it on.
I restored the standard build.props from a backup copy. Do I need to relock the bootloader? Remove SuperSU and unroot?
Laptop computer has lots of free disk space, and is running standard win7pro-x64, nothing special installed.
thanks for any ideas.
I think that it is the unlocked bootloader?
I just flashed the ce 290 ftf when I had some error in pcc. Might have been the same one.
Rooting is easy on 290 if you have an unlocked bootloader
it's not root, because I unrooted device, so I am guessing its the unlocked bootloader. I've never managed to get Barclays Bank mobile app to work as it complains about phone being rooted, still doesn't work, so it must be detecting the system modified flag (this is using the older version of the app which was happy to run on a fully p0wned Galaxy Note 2).
OK, it was the unlocked bootloader. OTA update now working.
thanks!
Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
I read a lot in these forums here about OEM unlock S9+ but until now it did not work for me. Additionally there are lot of confusing information around here...
Can anyone (from OWN experience !) please write how unlock, waiting-time and RMM-states are related?
I bought a new phone from U.K., a variant which actually is only available in the Asian market as far as I know.
Color blue with 256 GByte and dual-SIM.
It has EXYNOS CPU !!! As you can see from my attachments, I have already been waiting 7 days for OEM-unlock with no success. I did not boot into download-mode yet.
I assume Samsung has produced phonse, even with EXYNOS, where the OEM-unlock is impossible...
View attachment SoftwareInfoS9.pdf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, so far, only the snapdragon variants can not be unlocked using the OEM Unlock feature.
I had a custom ROM for about 5 days, and to be honest I sort of wish I hadn't done anything at all. Unlocking the bootloader breaks things like Google Pay and Device Certification on Google Play. This stops things like Netflix and other services (seemingly only ones that rely on Googles Windvine DRM - although the APKs can be installed manually). The second you load TWRP, Knox is gone forever. It is unrecoverable. This I care less about, although Secure Folder had its uses for duplicating apps.
Yes, its possible for Root to fix most of those, but its an endless cat and mouse chase and often breaks when Google update things (I could not get Google Pay to work at all despite Magisk Hide)
During those 5 days, the OEM Unlock option was unavailable to me. When I decided to go back to full stock condition (minus Knox) I loaded all the correct things in via Odin, and the OEM Unlock option was available, with the slider in the off position.
What I want to know at this point, is does turning it on re-lock the bootloader? Because if it does that would likely solve my issues with Google Pay (its incredibly handy).
To answer your question though, the standard waiting time is usually 7 days, after which it will re-appear.
I now rebooted to download mode to see the RMM state. It is Prenormal...
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.