Debrand LG G4 - G4 Q&A, Help & Troubleshooting

Hi folks, I'm considering buying one of these beautys, but I have question about branded rom. I want to buy one from Orange as far as I know it has own branded software. Model of phone is h815 or h818 is there any possibility of instaling international europe rom without unlocking bootloader?
Wysłane z mojego Nexus 4 przy użyciu Tapatalka

I dont think it's possible w/o unlocked bootloader - U hv to have root to either remove bloatware or to install new ROM. But maybe there is a way thru KDZ of int ROM if there is one for exact model
Odoslané z LG-H815 pomocou Tapatalku

You are going to have to have an unlocked bootloader if you are going to flash a different ROM (As you need a Custom Recovery to flash ROMs and you need bootloader R/W access in order to get TWRP).
If you get Root Access you can remove bloatware and do lots of customizations (assuming we get Xposed Framework working and all that), but that is about the best you are going to get with just managing to get Root Access and not an unlocked bootloader.

Please just correct me if I am wrong. When I buy Orange's G4(h815) which has branded software. Then using this method http://forum.xda-developers.com/showthread.php?t=2785089 can I install 815 v10c non branded software i.e. this http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/ one? Its still same model H815. Main goal for me is to get non branded software without unlocking bootloader.

I don't think so. I bet,that w/o unlocked boot loader, yuo aren't able to enter bootloader. Try enaabling usb debugging and via adb enter cmd:adb reboot bootloader and write what happened
Odoslané z LG-H815 pomocou Tapatalku

I don't have G4 yet, because of this bootloader, debrand problem I am considering buying it. I am Nexus user right now, and I will be missing this unbrickable clean piece of software. I need to know this before buying one of G4, because I do not like crappy applications that operator adds. Besides still when using stock rom I am sure when some update will be on air I will receive it sooner then I would receive it from Orange.

phsnake said:
I don't think so. I bet,that w/o unlocked boot loader, yuo aren't able to enter bootloader. Try enaabling usb debugging and via adb enter cmd:adb reboot bootloader and write what happened
Odoslané z LG-H815 pomocou Tapatalku
Click to expand...
Click to collapse
IF he had the device (which sadly as he stated he does not) I am pretty sure it would just result in the phone rebooting (as this is the case with almost all variations of the G4).
The only method you MIGHT be able to use in order to do this would be the .KDZ method and even then I personally would only use that to flash the Stock ROM that my device came with (For me that would be ONLY Firmware for the LGUS991 variety of the phone)

Fortunately i have int version EU,1st thing I've done was unlocking bootloader &installation of twrp&superSU, i doubt that w/o unlocked bootloader he'll be able 2 do anything
Odoslané z LG-H815 pomocou Tapatalku

Related

[Q] First steps on an new Z1 compact

Hi there,
I will purchase a Z1 compact this week, and the amount of information in the forums is kind of confusing me, so I want to ask for some advice here. This is my first adventure into the android world as I am using WebOS for many years now, but that does not seem to have a future.
I don't have a google account, and I am not planning to get one.
I want to run cyanogenmod on the phone.
Is it correct that the reasonable steps to follow are:
1. Get the device
2. Check for the firmware version installed and root the device
If 14.4.A.0.108, proceed by rooting the phone like here:
http://forum.xda-developers.com/showthread.php?t=2784900
If 14.4.A.0.157 or older than 108, use flashtool to install the kernel from 108, then proceed with rooting, then install the kernel of 157 again
3. Backup the TA partition (http://forum.xda-developers.com/showthread.php?t=2292598) or rather as I don't use windows, like here: http://www.android-hilfe.de/sony-al...ia-ta-backup-restore-tool-fuer-linux-mac.html ( tool which does the TA backup on linux, but it's german only...)
4. Unlock the Bootloader using fastboot like described here: http://forum.xda-developers.com/showthread.php?t=2440597
5. Install cyanogenmod like described here: http://wiki.cyanogenmod.org/w/Install_CM_for_amami
Did I miss something, or is this overly complicated or outdated?
Many thanks in advance,
Cheers, B
You need to make sure you can unlock the bootloader first if you want to use CM, other than that your steps are correct.
XperienceD said:
You need to make sure you can unlock the bootloader first if you want to use CM, other than that your steps are correct.
Click to expand...
Click to collapse
Thank you! If I buy a new, Sim-Unlocked phone, it should be unlockable, right? Or are there other parameters influencing this?
Cheers,
B
BeerSerc said:
Thank you! If I buy a new, Sim-Unlocked phone, it should be unlockable, right?
Click to expand...
Click to collapse
Correct.
I'd add check build quality to that list. Especially since you seem to be buying one in Germany.
XperienceD said:
Correct.
Click to expand...
Click to collapse
I don't get how SIM-lock and bootloader lock are bound.
IMAO those are two different things.
F308 said:
I don't get how SIM-lock and bootloader lock are bound.
IMAO those are two different things.
Click to expand...
Click to collapse
They are, but Phones that come from carriers that are bootloader locked, generally cant be unlocked.
I have z1c from orange and I have Sim unlocked but my bootloader status unlocked is: no so in my case I can't unlock bootloader but I don't have a simlock so can't install any cm roms or any unstock kernels
Wysłane z mojego D5503 przy użyciu Tapatalka

Can't install update 14.5.A.0.270

As it says in the title, I can't install the new software update.
Oddly, I'm still on the latest KitKat because I didn't got the earlier lollipop updates.
If I try to install the new update, it simply reboots and says that the Installation failed, nothing more like an error code or something else.
I don't think that a previous Custom ROM, which I erased with Sony Emma, bothers that, but if it would, there you go.
Here are all the specs:
Model info: D5503
Software version: 14.4.A.0.157
Previous installed ROM: CyanogenMod 12 (not 12.1), erased and stock restored with Sony Emma
Internal Storage free space: 8.3 GB
SD-Card free space: 24.16 GB
Greetings
leadkro14
Hmm I haven't seen 270 fw for z1c only 252 is latest 270 is certificated but haven't been realesed yet or am I wrong?
Sent from my D5503 using Tapatalk
mosespl said:
Hmm I haven't seen 270 fw for z1c only 252 is latest 270 is certificated but haven't been realesed yet or am I wrong?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
.270 version has started rolling from yesterday
Hmm I downloaded from Xperia firmware Baltic generic and I can't flash it I don't know why but I m downloading again and we will see
EDIT:
nothing happend very sad im trying now to download RU customization becaues i had RU earlier version
Sent from my D5503 using Tapatalk
i'm having the exact same problem. already tried flashing nordic and baltic but none of them work. hope someone comes up with a solution.
Xperiafirm fault. Solution:
After download and extract rom don't bundle it. Firstly remove from folder one file fwsomething.xml I don't remember exactly name of file but is one file with that name. Delete it and after that create bundle with flashtool and after that flash and everything will works superb!
Wysłane z mojego D5503 przy użyciu Tapatalka
mosespl said:
Xperiafirm fault. Solution:
After download and extract rom don't bundle it. Firstly remove from folder one file fwsomething.xml I don't remember exactly name of file but is one file with that name. Delete it and after that create bundle with flashtool and after that flash and everything will works superb!
Wysłane z mojego D5503 przy użyciu Tapatalka
Click to expand...
Click to collapse
fwinfo.xml was causing the issue, fwinfo.xml will be used by the next version of flashtool to create a FTF. just need to remove it from the FTF. anyway, thanks man!
I'm having the same problem, I previously tried rooting my Xperia Z1 (C6903) but it is now restored. However when I tried updating to 14.5.a.0.242, it said "The device contains modified software that cannot be updated". Is it because the phone was not restored properly? (I restored by flashing Android 4.4)
Regards
sony12345 said:
I'm having the same problem, I previously tried rooting my Xperia Z1 (C6903) but it is now restored. However when I tried updating to 14.5.a.0.242, it said "The device contains modified software that cannot be updated". Is it because the phone was not restored properly? (I restored by flashing Android 4.4)
Regards
Click to expand...
Click to collapse
Did you unlock your bootloader...? Is it still unlocked....? If so you need to relock for OTA updates
160lightning said:
Did you unlock your bootloader...? Is it still unlocked....? If so you need to relock for OTA updates
Click to expand...
Click to collapse
wouldn't relocking bootloader cause problems (besides preventing flashing and root)?
sony12345 said:
wouldn't relocking bootloader cause problems (besides preventing flashing and root)?
Click to expand...
Click to collapse
No... locked just means restricted access same as a locked door.... but your device needs locked B/L to take an OTA Sony official Stock firmware update.... personally I would never wait for the official release if I have unlocked B/L I would always search and you can find firmware updates a lot quicker than everyone else waiting for the OTA on their device or thru PC Companion,
I use this very handy tool to get available stock firmware for Xperia devices
Relock bootloader only
If you want to relock your bootloader (e.g. for downloading official sony updates in Sony Update Service) you can do so with flashtool. This only works if you already unlocked the bootloader with the official method.
Note: This does not restore the DRM keys. If you have a warranty issue you should restore your TA parition (which will relock your bootloader and restore DRM keys) with Backup TA.
1. Open flashtool
2. Click on the BLU icon
3. Connect your phone in flashmode (hold volume down and plug in your USB cable)
4. Flashtool will ask you about the device model, choose Sony XPERIA Z1 (if Z1 compact is not in the list)
5. Flashtool will read your IMEI and your unlock code. Check if those are correct (compare unlock code with the one you received by email from Sony when you unlocked the bootloader)
6. Flashtool will save the unlock code in its program folder under custom/mydevices.
7. Click "Lock bootloader" (-> If you want to unlock it again, repeat the steps (it will automatically detect that your bootloader is locked))
Source: http://forum.xda-developers.com/showthread.php?t=2642081 ....thanks @zxz0O0
160lightning said:
No... locked just means restricted access same as a locked door.... but your device needs locked B/L to take an OTA Sony official Stock firmware update.... personally I would never wait for the official release if I have unlocked B/L I would always search and you can find firmware updates a lot quicker than everyone else waiting for the OTA on their device or thru PC Companion,
I use this very handy tool to get available stock firmware for Xperia devices
Relock bootloader only
If you want to relock your bootloader (e.g. for downloading official sony updates in Sony Update Service) you can do so with flashtool. This only works if you already unlocked the bootloader with the official method.
Note: This does not restore the DRM keys. If you have a warranty issue you should restore your TA parition (which will relock your bootloader and restore DRM keys) with Backup TA.
1. Open flashtool
2. Click on the BLU icon
3. Connect your phone in flashmode (hold volume down and plug in your USB cable)
4. Flashtool will ask you about the device model, choose Sony XPERIA Z1 (if Z1 compact is not in the list)
5. Flashtool will read your IMEI and your unlock code. Check if those are correct (compare unlock code with the one you received by email from Sony when you unlocked the bootloader)
6. Flashtool will save the unlock code in its program folder under custom/mydevices.
7. Click "Lock bootloader" (-> If you want to unlock it again, repeat the steps (it will automatically detect that your bootloader is locked))
Source: http://forum.xda-developers.com/showthread.php?t=2642081 ....thanks @zxz0O0
Click to expand...
Click to collapse
Thanks 160lightning. I was just wondering, since I'm a quite new to Android and I just saw the Android 5.0.2 update but was unable to update

Vodafone Carrier / H815 unlock?

Hi Im new in the "scene" of android dev. Got a brand new LG G4 (H815) with Vodafone Germany carrier. I´ve got root on my LG and want to go the next step to unlock my phone. So I followed the official LG Unlock Thread and have all informations that I need to paste in the unlock fields. But that´s what the dev page from LG says...
Unfortunately, your device(Germany,(VODAFONE(GERMANY))does not support unlocking the bootloader.
So I have to wait for an option to "hack" it?
/Edit I´ve called the vodafone support and they said that the phone is not locked... is their a difference between sim and bootlock?
Another question, is it possible to flash an open kdz instead of the vodafone one? and when which?
Bootloader is locked... There is no plan to unlock the bootloader... You can root your phone by using the low effort root for h815... Hopefully some of the devs is able to unlock the bootloader...
Gesendet von meinem LG-H815 mit Tapatalk
Yes, SIM unlock means you can use any carrier SIM card in the phone. Bootloader unlock is completely different. Our bootloader is locked.
If you wanr root, use this thread: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
The international files work for your device.

Root h815 with locked bootloader?

Hi.
I have just purchased a used h815 and when I went to unlock via the official lg website, I was informed that my phone was a US variant, and unlock was not available.
I'm currently running 20h.. is there any way at all given the locked bootloader to
A) get root access?
B) install cm13?
If the answer is no.. i think I'll be sticking this back on eBay...
Thanks!
Sent from my LG-H815 using Tapatalk
llewelld said:
Hi.
I have just purchased a used h815 and when I went to unlock via the official lg website, I was informed that my phone was a US variant, and unlock was not available.
I'm currently running 20h.. is there any way at all given the locked bootloader to
A) get root access?
B) install cm13?
If the answer is no.. i think I'll be sticking this back on eBay...
Thanks!
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
install cm..... NO
root i think yes.. if you are on lollipop..
h815 from us?? only unlockable from us is h811.
Thanks.. that's what I thought but was really hoping I wasnt correct.
Sent from my LG-H815 using Tapatalk
i also have a h815 ... locked bootloader
whenever the phone is rebooted i get an error message saying 'current version is not available for user. Can't find mathed cust for NT-code mcc/mnc[FFFFFF], subset[55]'
i'm planning on selling the device and i wish to do so without that problem
software version is V10c-OPT2-HQ
need help really fast
thanks

"Allow OEM Unlocking" grayed in Official Android N 7.0.0 NRD90M

Hello,
Probably im not the only one here with this or even everyone with new version of system go this issue.
I'm talking about option "Allow OEM Unlock" in Developer Menu (have to press 10 times on build version in "Information about phone"). Till I've been on Marshmallow 6.0.1 (till MTC20F) this option was possible to turn it on and off -> what was nice way to make phone safer. First i got message about new (1,1GB OTA 7.0) update, then installed it and find out that this option is grayed, so i flashed full firmware from https://developers.google.com/android/nexus/images with full return to stock and factory reset. It didn't helped still its grayed out (by whole time it is grayed on ON position), so i sideloaded SuperSU without changing system integrity (read only in twrp) - still grayed. Anyone knows how to do this working ??
Well, I would guess your bootloader is unlocked already?
Sent from my Nexus 5X using Tapatalk
Mine is greyed out as well. I don't recall reading any posts highlighting this for the developer previews though. Might run the unlock command for the heck of it.
Sent from my Nexus 5X using Tapatalk
Relock the bootloader in fastboot (will wipe data), then the toggle will be active again.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Relock the bootloader in fastboot (will wipe data), then the toggle will be active again.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Just to gray out asap he unlockes the bootloader again?
NEVER LOCK A BOOTLOADER.
PiousInquisitor said:
Relock the bootloader in fastboot (will wipe data), then the toggle will be active again.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I'm sorry, after locking OEM it will be active yes? But if I unlock it back will it stay active ?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
JaCh0o said:
I'm sorry, after locking OEM it will be active yes? But if I unlock it back will it stay active ?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
If you want the Allow OEM unlocking switch active, the bootloader must be locked. What good is the switch when you are already unlocked?
RusherDude said:
Just to gray out asap he unlockes the bootloader again?
NEVER LOCK A BOOTLOADER.
Click to expand...
Click to collapse
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
If you want the Allow OEM unlocking switch active, the bootloader must be locked. What good is the switch when you are already unlocked?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
This is what I need. When OEM is unlocked but "in system" trigger OEM unlock is turned off it gives no possibility to flash or use any command in bootloader. I want to flash root then switch off that trigger.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
@JaCh0o That switch wouldn't prevent someone from flashing images if the bootloader is already unlocked. That's no how it works. It's there to prevent someone from unlocking the bootloader from fastboot who doesn't have access to the operating system. If you don't want someone flashing images to your phone and you want FRP intact, your bootloader must be locked, and the Allow OEM unlocking turned off. There is no way around that. Root or security. You can't have both.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
@JaCh0o That switch wouldn't prevent someone from flashing images if the bootloader is already unlocked. That's no how it works. It's there to prevent someone from unlocking the bootloader from fastboot who doesn't have access to the operating system. If you don't want someone flashing images to your phone and you want FRP intact, your bootloader must be locked, and the Allow OEM unlocking turned off. There is no way around that. Root or security. You can't have both.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
So till marshmallow it was possibly now it's not since 7.0.0?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
JaCh0o said:
So till marshmallow it was possibly now it's not since 7.0.0?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
No it still worked the same way in MM as far as im aware just let users toggle the switch but served no real purpose.
Oblox said:
No it still worked the same way in MM as far as im aware just let users toggle the switch but served no real purpose.
Click to expand...
Click to collapse
It's not working in same way course there is no possibility to get this working while having unlocked oem. This was best possibility to keep any other person witch can not log into the system from flashing any files or running commands. Under N it is not possible, under MM it is possible.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
No, it isn't! The switch was toggleable bot did nothing since your bootloader stayed unlocked. Just lock your bootloader and then the switch will be active again, but i will strongly suggest leaving your bootloader unlocked in case of any mishaps. You're rooted, you can still make your device unbootable and then it'll be as good as a brick, you won't be able to recover it because of locked bootloader.
Lawstorant said:
No, it isn't! The switch was toggleable bot did nothing since your bootloader stayed unlocked. Just lock your bootloader and then the switch will be active again, but i will strongly suggest leaving your bootloader unlocked in case of any mishaps. You're rooted, you can still make your device unbootable and then it'll be as good as a brick, you won't be able to recover it because of locked bootloader.
Click to expand...
Click to collapse
First of all it is easy to recover from soft brick by download mode and lg flash tool.
Second it did much because its been disabling possibilities of using bootloader while having unlocked oem - without flash tool it impossible to reset phone or enter to system. So it could be rooted, encrypted, secured by pre system pin and with locked bootloader. And this is what I need to do now.
To cut this discussion, I don't need your suggestions what is safe and what's not. I need someone to tell me how to enable this function in-system "enable oem unlock" trigger while having unlocked oem.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
its been disabling possibilities of using bootloader while having unlocked oem
Click to expand...
Click to collapse
That's what we all try to tell you. It didn't, fastboot commands were still perfectly usable.
Lawstorant said:
That's what we all try to tell you. It didn't, fastboot commands were still perfectly usable.
Click to expand...
Click to collapse
Witch one? Fastboot //oem lock/unlock/device-info//boot//flash has not been working on unlocked bootloader with locked function in developer menu.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
It was a delusion then. This setting is only responsible for changing a boolean (true/false) value in memory. Based on the state of this flag, bootloader knows wether it can allow "oem unlock" or not. All the other commands depend solely on device's lock state (locked/unlocked).
A tak btw. to "Wysłane z mojego..." nie pasuje do XDA
Lawstorant said:
It was a delusion then. This setting is only responsible for changing a boolean (true/false) value in memory. Based on the state of this flag, bootloader knows wether it can allow "oem unlock" or not. All the other commands depend solely on device's lock state (locked/unlocked).
A tak btw. to "Wysłane z mojego..." nie pasuje do XDA
Click to expand...
Click to collapse
Its not true. It worked as it should in mm and now it's greyed out -disabled anyone knows how to turn this option on?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
JaCh0o said:
Witch one? Fastboot //oem lock/unlock/device-info//boot//flash has not been working on unlocked bootloader with locked function in developer menu.
Click to expand...
Click to collapse
JaCh0o said:
Its not true. It worked as it should in mm and now it's greyed out -disabled anyone knows how to turn this option on?
Click to expand...
Click to collapse
I think you are confused.
On MTC20F
Settings->Developer options->OEM unlock = disabled
Bootloader = oem unlock
Code:
C:\n5x>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\n5x>fastboot flash recovery twrp5x.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.766s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.922s
sfhub said:
I think you are confused.
On MTC20F
Settings->Developer options->OEM unlock = disabled
Bootloader = oem unlock
Code:
C:\n5x>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\n5x>fastboot flash recovery twrp5x.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.766s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.922s
Click to expand...
Click to collapse
On 8th I'm coming back from vacations will check this again and keep you update
Wysłane z mojego Nexus 5X przy użyciu Tapatalka

Categories

Resources