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
Related
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
PROCEED WITH CARE
OVERVIEW TABLE - UPDATED FOR APRIL 2016
{
"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"
}
* Comment applicable for TV's with QV15.1E chassis:
Below guide does not apply for firmwares QV151E_R0.5.38.41, QV151E_R0.5.38.52 because root can be obtained directly under user 0 using KingRoot on them.
Here you are download links for both firmwares:
1. QV151E_R0.5.38.41 (Use utility FRD v0.94 for easy download)
2. QV151E_R0.5.38.52 (Use utility FRD v0.94 for easy download)
Below guide also does not apply for QV151E_R0.5.38.55 and up, because TP Vision applied necessary android security patches to avoid root...
Upgrade/Downgrade above mentioned firmware via Android system recovery <3e> menu
Good news!!! Now we can get full root access on some ABD enabled 2015 Philips Android TV's
FULL STEP BY STEP GUIDE:
A. PREREQUISITES
1. PC/Mac/Linux computer on the same WiFi / Ethernet network as your TV with functional Android Device Bridge (ADB).
2. Working TeamViewer on above mentioned computer.
3. Familiarity with side-loading APK's using ES File Explorer from USB storage and/or v from Google Play or similar.
4. Readiness and excitement to get your 2015 Philips Android TV to the next level
B. CREATE AND SWITCH TO USER 10
1. Install Terminal Emulator app from Google Play using computer or other device.
2. Execute in Terminal Emulator following command: am start --user 0 com.android.settings/.DevelopmentSettings
3. Enable "Developer options" and enable "USB debugging" in the popped-up window.
4. Install Android Debug Bridge utility (ADB) on the PC preferably at root folder C:\ADB for easy use.
5. Run the ADB utility on PC. PC must be on the same network as TV. Make sure adb.exe is not blacklisted in your firewall rules.
It is better to connect both PC and TV via ethernet cable to the same router instead of WiFi.
6. Execute following shell command: adb start-server
7. Execute another shell command: adb connect 10.0.1.2 (IP of your TV)
8. Execute shell command upon successful connection: adb shell
9. Create new user under shell by performing following command: pm create-user FREE (any name)
10. Note or remember what number was assigned with newly created user. Should be user 10.
11. Switch to the new user profile executing shell command: am switch-user 10 (the number assigned to the profile above)
C. GET ROOT PRIVILEGES UNDER USER 10
12. Execute shell command to enter security settings of newly create user 10:
am start --user 10 com.android.settings/.SecuritySettings
13. Enable installation from unknown sources using slider in the menu.
14. Install rooting app KingRoot v4.8.0 (update to v4.8.1 later within app) under "User 10" and apply root. Navigate through app from PC via QuickSupport TeamViewer application because remote control does not work in it.
15. Exit KingRoot app and execute it again. This time KingRoot will deploy as system application. It can take few more attempts for KingRoot to deploy as system app so be patient. Note: TV may restart itself when root privileges are granted.
16. Install app Root Explorer v3.3.8. Use its re-mounting function by pressing R/W button to gain full read/write access to all files. Install also app Purify v1.2.0.120 which will help us!
17. Edit following XML file: /data/system/users/0/package-restrictions.xml using built in "Text Editor" under Root Explorer.
18. Remove line related to Root Explorer <pkg name="com.speedsoftware.rootexplorer" stopped="true" /> also lines <pkg name="com.kingstudio.purify"> plus <pkg name="com.kingouser.com"> and save file. This will allow Root Explorer and Purify to run under "User 0".
D. GET ROOT PRIVILEGES UNDER USER 0
19. Switch from "User 10" to "User 0" executing ADB command: am switch-user 0 . If you've at this point lost access and can not perform switch via ADB install app adbWireless v1.5.4 from USB stick, allow root access and re-enable ADB. It also works via Ethernet cable. If you are still not rooted and end up in "User 10 trap" focus on getting root privileges. Uninstall + re-install KingRoot + switch to user 0.
20. Restart the TV by unplugging / re-plugging power cord.
21. Re-run KingRoot under "User 0" so it can fully deploy as system app. If you do not see the KingRoot app listed anywhere press gear button on remote and go to Setup/General Settings/Android settings/Device/Apps/System apps and open it from there. Afterwards the KingRoot app will be listed among other sideloaded apps.
E. ENABLE INSTALLATION FROM UNKNOWN SOURCES UNDER USER 0
22. Install app Settings Database Editor v2016.01.26 from Google Play from your PC, run it, grant root privileges when prompt and edit value "install_non_market_apps" under secure tab from "0" to "1". Alternatively set root privileges to it via ADB by running ADB command: pm grant by4a.setedit android.permission.WRITE_SECURE_SETTINGS
23. Edit 0.xml located in /data/system/users/ under line <restrictions no_install_unknown_sources="true" /> and change value "true" to "false" using text editor within Root Explorer.
24. Disable "Google Play Services" and "Google Play Store" apps under Auto-start tab in KingRoot app. Alternatively run app Purify v1.2.0.120 and set "Google Play Services" and "Google Play Store" apps to Auto-kill+Block Start under Purify Apps tab. Other words make sure "Google Play Services" and "Google Play Store" are not on whitelist.
25. Restart the TV by unplugging / re-plugging power cord.
26. Enjoy the root and install any APK under "User 0" you like. . Installation of apps via ADB will also work from here. "User 10" may be deleted at this point using ADB command: pm remove-user 10
27. Attention: If you (or Android system) open "Google Play Services" and/or "Google Play Store" apps than installation of apps from unknown sources will be disabled so go back and start from point 23...
F. TIPS AND TRICKS
1. Find attached below all needed APK's that worked for me. (Except ES File Explorer - no more quota)
2. If wanted you can install BusyBox Installer v1.4 and select BusyBox version v1.20.
3. Launcher that I use in the screenshot picture is TV Launcher v3.0.20. Below is attached APK for it. No root required for this launcher, however uninstall Leanback Launcher updates under system apps otherwise you'll be not able to select "Home App" yourself...
4. I've changed resolution of the UI from 1080p to 1440p. Looks great and so far no issues with it. 2160p does not work steadily (not supported in Lollipop)... Use ADB shell command: wm size 2560x1440 ... To go back use ADB shell command: wm size reset
5. Great app called Root Booster can be found here
6. You can replace KingRoot with SuperSU following this guide. It worked on my 49PUS7150/12, but TV restarted around 3 times. I've used the tool v2.4...
7. You can make your life much easier with Total Commander with Android ADB plugin
Let us know the tricks you tried.
G. ROOT - PROS AND CONS
PROS:
1. Install apps requiring root access
2. Make TV more reliable and faster by deleting obsolete system apps (even preinstalled ones)
3. Improve boot time and increase TV responsiveness by removing bloatware
4. Manage processor and Android system performance
5. Install a better web browser
6. Use an iphone/ipad/mac based airmouse/remote mouse in this browser
7. Tweak and test 4K posiblities
CONS:
1. Potential loss of warranty if not un-rooted before hard brick...
H. GUIDE IS FULLY TESTED AND WORKING on following 2015 Philips Android TV's:
1. 49PUS7150/12 - QV151E - Version: 000.005.038.028, Date published: 2015-12-16
2. PUS7600/12
3. 49PUK7150/12
4. 55PUS7150/12
5. 55PUS7100/12
Let us know if you are successful
I. GUIDE UNFORTUNATELY DOES NOT WORK YET on following 2015 Philips Android TV's due to dm-verity safe boot enabled:
1. 5500 series
2. 50PUT6400
3. 48PUS7100/78 - error message: device '(null)' not found
4. 55PUK6400 - QM152E - Version: 000.005.101.047
Let us know if you are stuck
J. WISH LIST
1. Enable mouse pointer - Enabled since March 2016 firmwares
2. Enable 4K video content from YouTube
3. Enable oscam server
Let us know your wish
K. TROUBLESHOOTING IN CASE OF ISSUES
1. Follow this thread: [GUIDE] Continuous restart / bootloop fix for Philips Android TV with Wipe Data Tool
Let us know if you experience any issues.
QV151E NOTE: Rooting was possible prior to QV151E_R0.5.38.068 firmware. In this particular firmware there were Google security patches applied to avoid this rooting method. Even if you downgrade to prior firmware versions, you will no longer succeed with this rooting method.
@7100p, @Tomzzz4pda - Thanks for great contribution to make this guide reality !!!
Dude. İts really big step thanks for it.
49puk7150
İ rooted tv after this when i run root explorer it says you device not rooted. İ also allowed the ap on king root. Anyway i installed root browser it does work. But i edited the xml file but i couldnt recognize what to delete exactly. So i deleted all lines pkg to other pkg wich is included root explorer also deleted orginal backup . Switch user 0. king root appears in system apps but there is no option 'run'. Just like other apps i have installed on 10. They appears but not runs.
So i back to user 10 i checkt xml file i noticed that file change back to orginal. Tried few time but no hope.
İ dont know what i missed or do something wrong
İf u made a video it will be awesome..
Thanks
byhayati said:
Dude. İts really big step thanks for it.
49puk7150
İ rooted tv after this when i run root explorer it says you device not rooted. İ also allowed the ap on king root. Anyway i installed root browser it does work. But i edited the xml file but i couldnt recognize what to delete exactly. So i deleted all lines pkg to other pkg wich is included root explorer also deleted orginal backup . Switch user 0. king root appears in system apps but there is no option 'run'. Just like other apps i have installed on 10. They appears but not runs.
So i back to user 10 i checkt xml file i noticed that file change back to orginal. Tried few time but no hope.
İ dont know what i missed or do something wrong
İf u made a video it will be awesome..
Thanks
Click to expand...
Click to collapse
You did everything correctly except one step. When you've switched from "User 10" to "User 0" you did not restart the TV (point 20). Without the restart, you can not open KingRoot under "User 0"... Go back to point 15 ...
Okay, so i managed to launch kingroot and root explorer on user 0, but i can't install any app...
C:\Users\Janjaak>adb install tv-armeabi-v7a-release-0.1.2.apk
645 KB/s (19668366 bytes in 29.759s)
pkg: /data/local/tmp/tv-armeabi-v7a-release-0.1.2.apk
Failure [INSTALL_FAILED_USER_RESTRICTED]
Any idea ?
My tv is 55PUS7150/12 QV151E. I installed kingroot and rootexplorer uder user 0 (after couple tries) and they work ok, my tv is rooted (kingroot works as system app). But when i trying install app Settings Database Editor (step 22) it says its restricted to install apps from unknown sources. For me step 18 is unclear. Exactly which lines should be deleted. I remove line about rootexplorer and kingroot. Can you explain this to me.
Wysłane z mojego D6603 przy użyciu Tapatalka
Matt17000 said:
Okay, so i managed to launch kingroot and root explorer on user 0, but i can't install any app...
C:\Users\Janjaak>adb install tv-armeabi-v7a-release-0.1.2.apk
645 KB/s (19668366 bytes in 29.759s)
pkg: /data/local/tmp/tv-armeabi-v7a-release-0.1.2.apk
Failure [INSTALL_FAILED_USER_RESTRICTED]
Any idea ?
Click to expand...
Click to collapse
This means that your "Google Play Services" and "Google Play Store" are still running as system apps and they are disabling/blocking install from unknown sources. Focus on point 24 and double make sure they are disabled after start up in both KingRoot and also Purify! Before you restart TV make sure point 23 is also done because 0.xml is altered by Google Play apps... Once you've successfully performed point 22, this does not have to be performed/repeated again.
But how install purify when i cant install from unknown sources? I cant install settings Database Editor from point 22
Wysłane z mojego D6603 przy użyciu Tapatalka
Grzegorz_Pietrakowski said:
My tv is 55PUS7150/12 QV151E. I installed kingroot and rootexplorer uder user 0 (after couple tries) and they work ok, my tv is rooted (kingroot works as system app). But when i trying install app Settings Database Editor (step 22) it says its restricted to install apps from unknown sources. For me step 18 is unclear. Exactly which lines should be deleted. I remove line about rootexplorer and kingroot. Can you explain this to me.
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
At this point you can still install Settings Database Editor from Google Play store from your PC! I have re-written step 18 so it is more clear what to delete in 0.xml.
Grzegorz_Pietrakowski said:
But how install purify when i cant install from unknown sources? I cant install settings Database Editor from point 22
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
If you are in the situation that you are not able to install Purify under "User 0" than you have to do it under "User 10" and delete the corresponding line under 0.xml. I'll re-write the guide now with your feedback!
I dit it. I installed settings database editor on user 10 and removed line from package-restrictions.xml but after switch to user 0 and reboot i got this
Wysłane z mojego D6603 przy użyciu Tapatalka
Grzegorz_Pietrakowski said:
I dit it. I installed settings database editor on user 10 and removed line from package-restrictions.xml but after switch to user 0 and reboot i got this
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
I've just re-written point 22! Make sure you granted SetEdit root privilages! By the way your kid has got some nice toys to play with
49 puk 7150 root confirmed and apk installation possible without any issue.
byhayati said:
49 puk 7150 root confirmed and apk installation possible without any issue.
Click to expand...
Click to collapse
Thanks for feedback. I'll list your TV model in the guide. Enjoy the root freedom
Thanks. Any workaround for mouse and vpu codec.
İ have tried youtube for mobile version on user 10 There was 1440option but i did same on user 0 but there ıs only 1080. try new screen size and resulotion values by adb. Example changed size to 3840x2160 and 520dpi looks much better.
STRİNG DATABASE VERSİON. FRS 1.0A-2015/SEP./15
byhayati said:
Thanks. Any workaround for mouse and vpu codec.
İ have tried youtube for mobile version on user 10 There was 1440option but i did same on user 0 but there ıs only 1080. try new screen size and resulotion values by adb. Example changed size to 3840x2160 and 520dpi looks much better.
STRİNG DATABASE VERSİON. FRS 1.0A-2015/SEP./15
Click to expand...
Click to collapse
Tried couple of tricks for mouse support but without luck, not sure where exactly it is disabled same for VP9 codec... I tried to play with resolution, but I was not happy with it. When I switched to [email protected] it looked better, but whole system became very slow, picture floated from right to left like on old TV's, TeamViewer's remote control did not connect with message "Initializing display parameters" and when I ran Kodi I just got flickering pictures... Had to set default values [email protected] via commands Resolution: adb shell wm size 1920x1080 , Pixel density : adb shell wm density 320
Ok now everything is working fine. I confirm install unknown sources on 55PUS7150 with this guide. Thanks for help
Wysłane z mojego D6603 przy użyciu Tapatalka
Grzegorz_Pietrakowski said:
Ok now everything is working fine. I confirm install unknown sources on 55PUS7150 with this guide. Thanks for help
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
No problem Grzegorz, I am glad you made it! Pozdrowienia do Polski
ovso said:
This means that your "Google Play Services" and "Google Play Store" are still running as system apps and they are disabling/blocking install from unknown sources. Focus on point 24 and double make sure they are disabled after start up in both KingRoot and also Purify! Before you restart TV make sure point 23 is also done because 0.xml is altered by Google Play apps... Once you've successfully performed point 22, this does not have to be performed/repeated again.
Click to expand...
Click to collapse
After days of fight i finally fully restore my tv, and going step by step with your provided apk. And..... It's working like a charm !
Thank you again for your awsome work
Matt17000 said:
After days of fight i finally fully restore my tv, and going step by step with your provided apk. And..... It's working like a charm !
Thank you again for your awsome work
Click to expand...
Click to collapse
No problem and welcome to the club There is still many things to unlock/discover so let us see where we will get
I finally got Spotify on my home theater..... That's my first reason to do that.
Now i hope Philips will not block this workaround in future update...
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
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
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.