Unlock bootloader for lg G4? - G4 Q&A, Help & Troubleshooting

For LG L90 file was created file giving the opportunity to unlock the bootloader through the terminal emulator would give something to the possibility of installing TWRP , ROOT and installation CostomROM . Bootloader were left unlocked until the installation of the official stock KDZ file. Is it possible to create the same file for LG G4 ?
If someone wants that file I can send it but this is file only for Lg L90 D405n
Wysłane z mojego LG-H815 przy użyciu Tapatalka

Related

[SHARE] [4.3] Superuser Mod Xperia M Single

Only for Xperia M Single
Note : You must UBL, CWM, root and deodex Full
could you please tell us, how to install this?
yogesh448 said:
could you please tell us, how to install this?
Click to expand...
Click to collapse
In the main post is says you need to be rooted, have CWM and be deodexed fully.
1) Deodex your ROM, there's a guide in this section to help with this. I also did a guide in that thread for if you have a locked bootloader.
2) You can either use the method above and flash through CWM or you could use adb shell.
Method to install through adb (assuming you're on windows and adb is an environment variable).
1) Download the file from the OP and then extract the file 'services.jar' from the .zip file.
3) Copy the file to the root of your SD Card, basically so when it is on the phone the directory listing is /sdcard1/services.jar
4) Connect your device to the computer with USB debugging enabled.
5) Open up command prompt and then run the following code individually and line by line:
Code:
adb shell
su
stop
mount -o rw,remount /system
cp /sdcard1/services.jar /system/framework/
mount -o ro,remount /system
reboot
This will now have your replaced services.jar on your device and installed superuser mod for you. You will notice that when you reboot your phone it will say android is upgrading, this is normal.
Sent from my C1905 using xda app-developers app
On 4.2 it was enough to just copy this file manually via root explorer and reboot phone. Anybody tested that on 4.3?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
iks8 said:
On 4.2 it was enough to just copy this file manually via root explorer and reboot phone. Anybody tested that on 4.3?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
Click to expand...
Click to collapse
It works like that, sort of. It made my phone hang for about 5 mins and then bootloop until I did a battery pull.
Sent from my C1905 using xda app-developers app
I have already Deodex my rom, then i directly flashed OP file via CWM.
it upgaraded successfully and on first boot upgradng andoroid also comes
but im not it installed successfully or not?
is it any way to check?
yogesh448 said:
I have already Deodex my rom, then i directly flashed OP file via CWM.
it upgaraded successfully and on first boot upgradng andoroid also comes
but im not it installed successfully or not?
is it any way to check?
Click to expand...
Click to collapse
Install one of the downloadable themes and then apply it. It should change the bottom bar (the ones I use do anyway).
Sent from my C1905 using xda app-developers app
gamer649 said:
Install one of the downloadable themes and then apply it. It should change the bottom bar (the ones I use do anyway).
Sent from my C1905 using xda app-developers app
Click to expand...
Click to collapse
But it's superuser mod, not theme runtime mod xD
iks8 said:
But it's superuser mod, not theme runtime mod xD
Click to expand...
Click to collapse
I don't know, until I installed the superuser mod themes wouldn't change anything but the lockscreen picture, background picture and the accent colour.
You could also try installing a mod what requires the superuser mod to be installed (like the z2 system UI by Rizal Lovins).
This not superuser mod for theme, maybe you need theme fixer for m 4.3 bro

How do I get to root on my Xperia T3 D5106 ???

Friends, I'm there one week direct non-stop trying to root on my Sony Xperia T3 (D5106) 18.1.A.2.25 version, do not know what else to do, I've tried all the tutorials xda forum .. all give error .. when I give in flash D5103 model, error appears here, my T3 only works on the D5106 model .. How do I get to root on my Xperia T3 D5106 ??? For God's sake = ( :crying:
You can follow the tutorials found in other threads like http://forum.xda-developers.com/xperia-t3/help/how-to-root-xperia-t3-18-1-2-25-t3007487 or http://help.howproblemsolution.com/1377446/tutorial-root-xperia-t3-firmware-18-1-a-2-25 that show how to root a D5103. It works altough your phone will complain at startup that you have the wrong version (but it still works). To circunvent this you must flash an ftf file for the D5106. If you don´t find one you can generate your own ftf with flashtool, that should be installed in c:\flashtool.
1) start flashtool and go to Devices/Check Updates. Double click on D510X then click on D5106 tab. If you find the brand of your phone, double click it and flashtool will start downloading. If you don´t find your brand, you can add it to the list in flashtool\devices\D510X\D5106\custlist.properties. In my case I added 1 line with "1286-6141=AMERICAS-LTE" without the quotes. You find this information about your phone in C:\program data\Sony\Sony PC Companion\<youremei>\default-capability.xml , almost at the end under <filesystem> <productnumber> and <cdf> <productnumber>.
Save custlist.properties and you will see your brand in flashtool. Be patient waiting for download - it will bring almost 1 GB.
2) when download is finished, flashtool will automatically decrypt the filesets and open the "Bundler". There you should mark the whole folder list and move it to the right to the "firmware content". Now you can click on "create" and your ftf will be generated in the firmwares folder.
If the process ends successfully you will have generated an ftf and a torrent file.
Follow the steps in the tutorial to flash the .14 firmware, run the rootkit to root your device and use your generated ftf to flash the .25 firmware. Flash only the Kernel and unmark the wipe Data in flashtool.
I hope this helps, since it worked for me. happy flashing
Hey @low-rider, your method worked perfectly on my D5106 Thanks:good:
anyone can help me to root my xperia t3?
What model T3 do you have?
low-rider said:
You can follow the tutorials found in other threads like http://forum.xda-developers.com/xperia-t3/help/how-to-root-xperia-t3-18-1-2-25-t3007487 or http://help.howproblemsolution.com/1377446/tutorial-root-xperia-t3-firmware-18-1-a-2-25 that show how to root a D5103. It works altough your phone will complain at startup that you have the wrong version (but it still works). To circunvent this you must flash an ftf file for the D5106. If you don´t find one you can generate your own ftf with flashtool, that should be installed in c:\flashtool.
1) start flashtool and go to Devices/Check Updates. Double click on D510X then click on D5106 tab. If you find the brand of your phone, double click it and flashtool will start downloading. If you don´t find your brand, you can add it to the list in flashtool\devices\D510X\D5106\custlist.properties. In my case I added 1 line with "1286-6141=AMERICAS-LTE" without the quotes. You find this information about your phone in C:\program data\Sony\Sony PC Companion\<youremei>\default-capability.xml , almost at the end under <filesystem> <productnumber> and <cdf> <productnumber>.
Save custlist.properties and you will see your brand in flashtool. Be patient waiting for download - it will bring almost 1 GB.
2) when download is finished, flashtool will automatically decrypt the filesets and open the "Bundler". There you should mark the whole folder list and move it to the right to the "firmware content". Now you can click on "create" and your ftf will be generated in the firmwares folder.
If the process ends successfully you will have generated an ftf and a torrent file.
Follow the steps in the tutorial to flash the .14 firmware, run the rootkit to root your device and use your generated ftf to flash the .25 firmware. Flash only the Kernel and unmark the wipe Data in flashtool.
I hope this helps, since it worked for me. happy flashing
Click to expand...
Click to collapse
hello my friend,
i have de Xperia T3 D5106, and the last Flash tool. i don't kwon how creted the tft file.
Which folder files i have to move to the firmware content? to them Created,
Please help me
MDC413I said:
hello my friend,
i have de Xperia T3 D5106, and the last Flash tool. i don't kwon how creted the tft file.
Which folder files i have to move to the firmware content? to them Created,
Please help me
Click to expand...
Click to collapse
"C:\Users\(username)\.flashTool\firmwares"

Unlock bootloader LG G4

For LG L90 file was created file giving the opportunity to unlock the bootloader through the terminal emulator would give something to the possibility of installing TWRP , ROOT and installation CostomROM . Bootloader were left unlocked until the installation of the official stock KDZ file. Is it possible to create the same file for LG G4 ?
If someone wants that file I can send it but this is file only for Lg L90 D405n
Wysłane z mojego LG-H815 przy użyciu Tapatalka

Issues with AOSP Built From Source - Bullhead

Hi! I have built AOSP for my Nexus 5X because I want to make a custom ROM for Android. However, I am facing some problems:
Problems:
1. I get a "There is an internal problem with your device" on each boot
2. IMEI is Unknown and SIM not showing up
3. Bootloop when installing Gapps
4. Apps are force closing on first boot
5. Lots of "weird" apps like WebView Browser Tester and Search
6. No setup wizard like normal Google factory images
How can I fix these problems?
Thanks
1. Upgrade vendor to the built actual version
2. Upgrade radio to the built actual version
3. What gapps are you trying to install?
4. May you used for another architecture build?
5 th the same
6. In AOSP it may not be, probably your rom wasn't built properly or some errors occurred
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Domin_PL said:
1. Upgrade vendor to the built actual version
2. Upgrade radio to the built actual version
3. What gapps are you trying to install?
4. May you used for another architecture build?
5 th the same
6. In AOSP it may not be, probably your rom wasn't built properly or some errors occurred
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
1. How do I know which vendor to use? Should that be flashed with the ROM? I used the MNF26F vendor binaries and the N4F26I and I get the error with both.
https://developers.google.com/android/drivers#bullheadnmf26f
2. How do I upgrade the radio?
3. I was using OpenGapps, but I tried Dynamic Gapps and that time it booted but there was no Gapps.
4 and 5. How do I check? They fix after rebooting
6. I guess AOSP just doesn't include that then, because it said the build was successful.
EDIT: Some apps like Music are still force closing, and Bluetooth will not turn on.
Can you post me sources where have you downloaded from?
And compiled rom? I'll take a look of it and let you know if I find out anything.
Domin_PL said:
Can you post me sources where have you downloaded from?
And compiled rom? I'll take a look of it and let you know if I find out anything.
Click to expand...
Click to collapse
Sure, but I'm not at my computer right now. I'll post everything once I get to it. What do you mean by compiled rom? It didn't finish Sorry, wrong thread
ROM and .IMGs: https://drive.google.com/open?id=0Bz_0dM4w0UR1Wkh3SF9aQUo5cWM
I took a look into system.img.
Have you installed by flashing img files or just only zip? I guess by just a zip. I haven't looked into zip, just in IMG
System.img it's built on N6F26Q so vendor should be matching the same version, so if it didn't it's a cause of internal error and probably no imei. I can't see included Google Apps so you need to install Google Apps as you did, but I don't know why it bootlops, maybe AOSP needs decrypted device so try to decrypt if you haven't done it earlier by typing command in fastboot:
fastboot erase userdata
remember this will erase all your user data including internal storage like apps,photos, music etc
About weird apps, as I see they are built in rom, so they had to be built from the source.
Domin_PL said:
I took a look into system.img.
Have you installed by flashing img files or just only zip? I guess by just a zip. I haven't looked into zip, just in IMG
System.img it's built on N6F26Q so vendor should be matching the same version, so if it didn't it's a cause of internal error and probably no imei. I can't see included Google Apps so you need to install Google Apps as you did, but I don't know why it bootlops, maybe AOSP needs decrypted device so try to decrypt if you haven't done it earlier by typing command in fastboot:
fastboot erase userdata
remember this will erase all your user data including internal storage like apps,photos, music etc
About weird apps, as I see they are built in rom, so they had to be built from the source.
Click to expand...
Click to collapse
That vendor IMG seems to be for the Nexus 6. I used one of these 3 proprietary vendor binaries: https://developers.google.com/android/drivers#bullhead.
I saw this https://github.com/anestisb/android-prepare-vendor/issues/49 where they say that they too get the message, and that this GitHub script fixes it, but I get an error when running it. Could you possibly take a look at this?
Thanks
NateDev473 said:
That vendor IMG seems to be for the Nexus 6. I used one of these 3 proprietary vendor binaries: https://developers.google.com/android/drivers#bullhead.
I saw this https://github.com/anestisb/android-prepare-vendor/issues/49 where they say that they too get the message, and that this GitHub script fixes it, but I get an error when running it. Could you possibly take a look at this?
Thanks
Click to expand...
Click to collapse
Oh in this case I don't feel ready to help you enough, but from this what I read start from disabling DM verify in boot. That should bin internal error.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Domin_PL said:
Oh in this case I don't feel ready to help you enough, but from this what I read start from disabling DM verify in boot. That should bin internal error.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
OK OK. How do I disable that? Do other custom ROMs do that? Or do they not get the error somehow?
OK, so I fixed the Bluetooth and SIM errors by including the Qualcomm proprietary binaries as well as the ones from LG, but the Music app still crashes, and I still get the error about an internal problem, even after flashing the correct vendor and erasing userdata. I'm flashing Gapps right now to see if it works properly. If it does, then all I need to do is get rid of the app crashes, and get rid of this popup, and then everything will be good
EDIT: Gapps do not apply after flashing. I used OpenGapps, both Full and Nano.
NateDev473 said:
Sure, but I'm not at my computer right now. I'll post everything once I get to it. What do you mean by compiled rom? It didn't finish Sorry, wrong thread
ROM and .IMGs: https://drive.google.com/open?id=0Bz_0dM4w0UR1Wkh3SF9aQUo5cWM
Click to expand...
Click to collapse
NateDev473 said:
OK OK. How do I disable that? Do other custom ROMs do that? Or do they not get the error somehow?
Click to expand...
Click to collapse
If I'm not in wrong elementarx kernel automaticailly disables dm verify while installing, so try it out instead compiling a new boot, you'll save time.
Go on apkmirror and just download Google Play and Google Services and install it manually by pushing it into /system/app directory.
How can I make it compile an ElementalX kernel boot.img by default, so that dm-verity is disabled, so that the message does not appear? And is there any possible way to get Gapps working, maybe I could make my own flashable ZIP somehow? Because I want to turn this eventually into an actual custom android ROM, and you have to bundle Gapps separatly.

[Guide & Links] Install Android 11 OneUI 3 Βeta 3 to your N975F

So Android 11 OneUI 3 beta was announced for your Note10+ N975F in the UK.
I was able to capture the link after enrolling to the beta.
Short guide:
If you do not understand how to install it, please stick to the stable version.
Betas are usually filled with bugs and a user with not much knowledge on these stuff, will frick out if anything goes wrong
After downloading it, rename it to ota.zip to get rid of the .bin extension
Reboot your phone to "Recovery Mode" and sideload the new "ota.zip" through your pc using adb tools to do so
ADB Tools are available here
SD-card method: by @henklbr
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
Links:
Beta1 ONLY FOR TJ4 stable!!
Please install it over TJ4, not older or newer stable versions
Make sure that you have installed the European version and NOT the StarWars themed one
Here is the link
Here is the mirror on GDrive, which is already renamed to BETA1.zip
Beta2
It MUST be flashed over Beta1
Link here
Beta3
It must be installed over Android 10 TL3 and NOT over Beta2
Link here
Warning:
Unfortunately, you wont be able to receive ANY more OTAs after installing this specific update UNLESS you are enrolled to the beta programme!!!
ONLY N975F, NO 5G, NO ANYTHING ELSE APART N975F
After installing the beta update it isn't possible to reboot in to recovery via the VolUP+power button.
You will have to use ADB for that: "./adb reboot recovery"
Video tutorial
Is it possible to install without ADB ??
seboo107 said:
Is it possible to install without ADB ??
Click to expand...
Click to collapse
As far as I remember, it was possible with Note 9 back at A10 days but I havent tried it. Theoretically, it will install just fine
On the S8 +, it was also enough to just upload the zip file
Wysłane z mojego SM-N975F przy użyciu Tapatalka
Dang! You are my man bro!
let someone say if it is possible to upload only the file without using ADB
seboo107 said:
let someone say if it is possible to upload only the file without using ADB
Click to expand...
Click to collapse
@t-shock Could you add this to the instructions?
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
Instalation aoborted for me but i'm remake the file ota.zip using Samsung file app
Wysłane z mojego SM-N975F przy użyciu Tapatalka
BTW, Is it an unusual showing this statement?
serving: 'ota.zip' (~94%) adb: failed to read command: No error
The phone is working properly tho
Adb is the only way? What about update.zip through the recovery mode?
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------
Sorry about that remove the question
Sent from my SM-N975F using Tapatalk
Recovery information
{
"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"
}
Wysłane z mojego SM-N975F przy użyciu Tapatalka
seboo107 said:
Instalation aoborted for me but i'm remake the file ota.zip using Samsung file app
Wysłane z mojego SM-N975F przy użyciu Tapatalka
Click to expand...
Click to collapse
ADB installation worked just fine. I really dont know about sd card method
bkkfunfair said:
BTW, Is it an unusual showing this statement?
serving: 'ota.zip' (~94%) adb: failed to read command: No error
The phone is working properly tho
Click to expand...
Click to collapse
There is no problem. I reinstalled A10 and then applied the update through ADB to verify that everything is ok and yes everything is ok, despite that message
livystewy01 said:
Adb is the only way? What about update.zip through the recovery mode?
Click to expand...
Click to collapse
ADB is the only tested method by me. I havent tested sd card so I cant tell you for sure
t-shock said:
ADB installation worked just fine. I really dont know about sd card method
There is no problem. I reinstalled A10 and then applied the update through ADB to verify that everything is ok and yes everything is ok, despite that message
ADB is the only tested method by me. I havent tested sd card so I cant tell you for sure
Click to expand...
Click to collapse
Thanks bro :highfive:
SD card method works!
Sent from my SM-N975F using Tapatalk
will you say how you did it step by step ??
Wysłane z mojego SM-N975F przy użyciu Tapatalka
seboo107 said:
Recovery informationView attachment 5135529
Wysłane z mojego SM-N975F przy użyciu Tapatalka
Click to expand...
Click to collapse
What is your current firmware-version on your device
Do *#1234# in the dialer, screenshot it and post it here...
henklbr said:
What is your current firmware-version on your device
Do *#1234# in the dialer, screenshot it and post it here...
Click to expand...
Click to collapse
Here is ss
Wysłane z mojego SM-N975F przy użyciu Tapatalka
seboo107 said:
Here is ssView attachment 5135539
Wysłane z mojego SM-N975F przy użyciu Tapatalka
Click to expand...
Click to collapse
You are on the correct build
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
t-shock said:
ADB installation worked just fine. I really dont know about sd card method
There is no problem. I reinstalled A10 and then applied the update through ADB to verify that everything is ok and yes everything is ok, despite that message
ADB is the only tested method by me. I havent tested sd card so I cant tell you for sure
Click to expand...
Click to collapse
Sd card method works perfectly.
sorry everyone. My mistake with the file selection
Wysłane z mojego SM-N975F przy użyciu Tapatalka

Categories

Resources