Database Info

[DEV][P940] LG Prada 3.0 Development

{
"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"
}
LG P940 development thread
Prada 3.0
Various threads about the P940 are lingering around all over the forums.
This thread is dedicated to have all info about development process, root, custom additions, etc for the LG P940 (Prada 3.0) in one place.
Recently, I started to get some custom awesomeness going on the P940.
The current status can be seen below. Please don't ask for ETA.
Status
Clockworkmod recovery: released (http://forum.xda-developers.com/showthread.php?p=30862503)
CyanogenMod 9 (Android 4.0): released (http://forum.xda-developers.com/showthread.php?t=1973100)
CyanogenMod 10 (Android 4.1): released (http://forum.xda-developers.com/showthread.php?t=2044274)
CyanogenMod 10.1 (Android 4.2): released (http://forum.xda-developers.com/showthread.php?t=2092937)
Click to expand...
Click to collapse
Device repository: https://github.com/milaq/android_device_lge_p940
Kernel repository: https://github.com/milaq/android_kernel_lge_p940
Click to expand...
Click to collapse
fastboot access via omap4boot / install CWM, root, etc: http://forum.xda-developers.com/showthread.php?p=40694480
Click to expand...
Click to collapse
LG update tool root prodecure by Walhalla: http://forum.xda-developers.com/showpost.php?p=28568521&postcount=8
Service manual (thx to Ygrek-Ix & BigBoyPL): http://milaq.net/downloads/android/p940/EN_LG-P940_SVC_ENG.pdf
Signing keys leaked! We can now sign any boot/recovery image and even bootloaders.
http://forum.xda-developers.com/showthread.php?t=1971014
Click to expand...
Click to collapse
But either way, you can participate here to show lg what crap they were up to:
Petition to unlock bootloaders on LG Phones: http://www.change.org/petitions/lg-...opportunity-to-unlock-bootloader-in-lg-phones
P940 now fully supported in the "LG Notifications" app: https://github.com/mborjesson/LG-Op...mmit/74999b2ccfeffc1f5829cf554a24b734cd7a6955
WARNING: The following stuff is ONLY for advanced users, who know what they are doing. I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, etc.
These are now update.zips. That means they can be conveniently be flashed via recovery.
Cifs module (for mounting remote shares): http://milaq.net/downloads/android/p940/cifs_p940_v20d.zip
Patched framework with power animations (CRT screen off animation when display shuts off): http://milaq.net/downloads/android/p940/framework_power-animations_p940_v20d.zip
Click to expand...
Click to collapse
Feel free to report any findings and/or contribute (e.g. pull requests, sharing thoughts or investigations).

OEM stuff
Stock images (V20d)
Recovery: http://milaq.net/downloads/android/p940/v20d-recovery.img
Boot: http://milaq.net/downloads/android/p940/v20d-boot.img
Partitions
x -> /dev/block/mmcblk0p1
u -> /dev/block/mmcblk0p2
boot -> /dev/block/mmcblk0p3
recovery -> /dev/block/mmcblk0p4
divxkey -> /dev/block/mmcblk0p5
misc -> /dev/block/mmcblk0p6
nv -> /dev/block/mmcblk0p7
fota -> /dev/block/mmcblk0p8
reserved -> /dev/block/mmcblk0p9
system -> /dev/block/mmcblk0p10
userdata -> /dev/block/mmcblk0p11
cache -> /dev/block/mmcblk0p12
system2 -> /dev/block/mmcblk0p13
fat -> /dev/block/mmcblk0p14
persist -> /dev/block/mmcblk0p15
mlt -> /dev/block/mmcblk0p16
Click to expand...
Click to collapse
Stock kdz image list: http://lg-phone-firmware.com/index.php?id_mod=14

Stock rom tweaks (v20d)
build.prop tweaks
Code:
ro.lge.capp_lockscreen
[true/false] - set to false to use the default ics lockscreen
Click to expand...
Click to collapse
Code:
ro.lge.capp_touch_scroller
[true/false] - set to false to have the default ics scrolling (fling) behaviour
Click to expand...
Click to collapse
Code:
persist.sys.sound_enable
[0,2] - 0 to disable bootsound, 2 to enable
Click to expand...
Click to collapse
service menu
In dialer enter
Code:
3845#*940#
Click to expand...
Click to collapse

cwm for prada
1. Root your phone first.
2. Dump your boot.ing and recovery.img.
dd if=/dev/block/mmcblkp03 of=/sdcard/boot.img
dd if=/dev/block/mmcblkp04 of=/sdcard/recovery.img
3. run install install-2nd-init.bat within adb env.
4. check my snapshot.
5. At this time, staill have isuue here, let's go on.
Credit wkpark. http://cafe.naver.com/androidhacker/98
http://dl.xda-developers.com/attach...3ee8733d1/50257299/1/2/5/2/5/4/4/12080006.jpg
http://forum.xda-developers.com/attachment.php?attachmentid=1252543&d=1344581863

thanks for pointing this out but unfortunately, this is a 2nd init recovery.
the whole purpose of a recovery is to not only serve as an installer/backuptool but also as a second chance if you mess something up. if you screw up your system partition your pretty much OOL.
in order to start building custom roms, we need at least a fake flash version of a recovery. but this is not possible atm because the bootloader sends "--wipe-data" on recovery boot, which ultimately results in not beeing able to apply a custom update.zip.
we need to either hack the b/l to not send any arguments (which is risky) or we need a signed recovery image which ignores the wipe-data argument.
we can then utilise 2nd init to tweak the system/serve an own initrd. but for a recovery we need the real deal.
cheers

WOW~~!
nice work!!!
:good::good::good:

well folks,
i revisited the 2nd-init recovery idea after countless efforts to circumvent the drm and writing several mails to lg internals w/o getting any further.
i'm just digging deeper into the method utilized here:
http://forum.xda-developers.com/showthread.php?t=1826378
i'll keep you posted,
cheers

I wait to cwm and cm 7 or miui based on gb

milaq said:
well folks,
i revisited the 2nd-init recovery idea after countless efforts to circumvent the drm and writing several mails to lg internals w/o getting any further.
i'm just digging deeper into the method utilized here:
http://forum.xda-developers.com/showthread.php?t=1826378
i'll keep you posted,
cheers
Click to expand...
Click to collapse
hello milaq, p940&ku5400 is opensource now. we can ge it here:
http://www.lg.com/lgecs.downloadFil...merModelCode=LGKU5400&DownFileType=opensource
hope this useful.

thanks for the headsup. any of such is much appreciated (as many stuff for the prada is in korean, chinese, etc.)
these are the opensource gpl components for the ku5400 (which essentially is the p940 for the eastern market). you can get the zips for the p940 here http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP940
this includes the kernel sourcecode which allowed me to build e.g. the cifs. module.
unfortunately we are still st(r)uck with an encrypted bootloader. therefore it is not possible to boot any custom kernel atm.

Cwm is ready?
do you have plans to port cm 7 or miui?

1. yes, but i'd rather test it a bit before releasing it publicly.
2. no. gb is deprecated and i wont spend any minute on it. even ics is getting old so why should anyone would want to maintain gb if ics is up and running

1.on ~ you know when it will be made ​​available to the CWM
2. You can enter service are init.d for scripts?

milaq said:
thanks for the headsup. any of such is much appreciated (as many stuff for the prada is in korean, chinese, etc.)
these are the opensource gpl components for the ku5400 (which essentially is the p940 for the eastern market). you can get the zips for the p940 here http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP940
this includes the kernel sourcecode which allowed me to build e.g. the cifs. module.
unfortunately we are still st(r)uck with an encrypted bootloader. therefore it is not possible to boot any custom kernel atm.
Click to expand...
Click to collapse
can we have a custom rom based on the LG's kernel ?

any news?

Support! P940 has great spec with low price!

managed to write CWM for locked bt?
that is not the oc kernel?

Does anybody know if it is possible to make the light in the navigation buttons stay on when you use the phone? I think they turn out very fast.

any news mr Milaq?

Clockworkmod release (testing)
I decided that the custom recovery is ready to be released publicly.
For information and downloads see this thread:
http://forum.xda-developers.com/showthread.php?p=30862503

[Q] Infinite Start Up Loop

My Samsung Galaxy Tab 2 7 (3113) seems to be stuck in an infinite start up loop. I waited for at least 15 minutes and yet it just kept showing the Samsung intro.
This happened after I was trying to install the JB 4.1.2 stock ROM. I was on Cyanogen beforehand, and I had wiped dalivk cache, cache, then did a factory reset couple of times. I'm not sure what went wrong, as I've done this before and it never happened.
I can't seem to get into recovery, only download mode.
Any ways I can fix this?

Use Odin to flash a stock package
Sent from my GT-P3110 using xda app-developers app

bIagginspaziyonokip said:
Use Odin to flash a stock package
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
No see format system in cwm and yhen try if not reflash stock
Press thnks

PyroKirby said:
My Samsung Galaxy Tab 2 7 (3113) seems to be stuck in an infinite start up loop. I waited for at least 15 minutes and yet it just kept showing the Samsung intro.
This happened after I was trying to install the JB 4.1.2 stock ROM. I was on Cyanogen beforehand, and I had wiped dalivk cache, cache, then did a factory reset couple of times. I'm not sure what went wrong, as I've done this before and it never happened.
I can't seem to get into recovery, only download mode.
Any ways I can fix this?
Click to expand...
Click to collapse
I have the same problem.
I had GT-P3113 with stock android 4.1.1, Kernel: 3.0.31-523998, Build number: JRO03C.P3113UECLK7
The I rooted it installing P3113_CWM_RECOVERY-6.0.1.1_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5 with Odin.
It worked fine.
But I wanted to have the latest Clockworkmod. I found a .ZIP file with 6.0.2 which I copied to the sdcard, booted in recovery mode and flashed from there. And the problems started - I got the infinite reboot. After that I tried several things to fix it but without success. Even installing the the original stock rom did not help. When in recovery mode with the stock rom it complains about bad /efs or not able top mount /efs - the battery is dead at the moment so I cannot check the exact message.
Any ideas to to fix it? I only tried to flash different rom with Odin so far hoping that this will fix it.
I haven't tried to use adb and fastboot yet although I have no idea what to do.
Any help is really appreciated.
Thanks!
{
"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"
}

pit file ?
I got access to another tablet like mine and was able to backup all the partitions using adb shell and dd
I am going to try and flash these to the broken one using Odin or Heimdall.
Heimdall needs a .pit file. I found one for GT-P3110 but my device is GT-P3113. I am not sure if I can use the one for 3110.
While was in the adb shell I found out how the partitions were mapped:
Code:
[email protected]:/dev/block/platform/omap/omap_hsmmc.1/by-name $ ls -alF
ls -alF
lrwxrwxrwx root root 2013-06-16 02:11 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-06-16 02:11 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-06-16 02:11 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-06-16 02:11 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-06-16 02:11 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-06-16 02:11 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-06-16 02:11 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-06-16 02:11 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-06-16 02:11 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-06-16 02:11 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-06-16 02:11 SBL2 -> /dev/block/mmcblk0p3
You can see that EFS is mapped to mmcblk0p1 - I think p1 means partition 1.
When loading the pit file in Heimdall it shows EFS as partition 4:
Is the partition Id important? Can I go ahead and flash with the .pit file I have or I need a .pit file specific for my device.
I am also curious how these .pit files are produced. Can I create one myself having in mind I have a second working tablet of the same type?

anichin said:
...
I am also curious how these .pit files are produced. Can I create one myself having in mind I have a second working tablet of the same type?
Click to expand...
Click to collapse
I found the answer to my own question. You can extract the .pit file with Heimdall (Utilities tab):
The Print button will give you detailed information about the partitions. It turns out efs indeed has identifier 4.
I also compared the two (gt-p3110.pit and gt-p3113.pit) files and can confirm they are identical. I used cmp in cygwin to compare them.

[Guide] [How To] Downgrade I9505 4.4.2 to 4.3.1

:laugh:Hello guys,
This is my first tutorial on the XDA-developers forum, in order to improve myself and be more efficient, do not hesitate to comment, or ask questions, I will be more then happy to answer since I have spent so much time on this, using two different I9505, mine and my boss's. So without further ado, let's get started
Here is a full guide on how to downgrade your I9505 from 4.4.2 to 4.3. KNOX WILL TRIGGER, there are other tutorials that show how to downgrade 4.4.2 to 4.3 without triggering the knox, I will explain some of them, but they are not 100% successful.
Do it on your own risk, neither me nor XDA-developers will be responsible if you brick or damage your phone.​Nevertheless, if you follow those exact steps, you won't have any problem (you may actually have some, but we can solve them together).
Requirements:
Samsung galaxy S4 I9505
Rooted phone
CWM or any custom Recovery
CyanogenMod 10.2.1 [click here] (jellybean 4.3.1) or any other custom with its proper kernel
Google apps jellybean [here]
(May need) Modem FNC4 or any above FNB8 [here]
(May need) Pit File to resolve some problems [here]
[KNOX 0x1 (triggered) WORKS 100%]
[Step 1: Optional, only if you can root your phone]
Before we start, I advice you backup your phone, save your EFS folder which contains your IMEI and other "sensitive information" related to your phone:
To do that, first you need to root your phone, then use a file explorer such as "ES FILE EXPLORER".
{
"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"
}
Go to your explorer and turn on "root explorer".
Once you have done that, go to your root folder.
Copy the folder called EFS to your SD Card.
(Optional)Make another copy on your HDD or file-hosting provider.
[Step 2: Installing the rom]
Copy your CyanogenMod or any other 4.3 custom fw + Google apps into your sdcard
Shutdown your phone
Press and hold down volume up, home button and power button to start in recovery mode (for about 5secondes)
Wipe data/cache (if you have philztouch, chose that you will install a new rom) and press YES
Advanced -> Wipe dalvik cache YES
Install zip from sdcard -> chose cyanogenmod zip file -> YES
Install zip from sdcard -> chose gapps zip file -> YES
Reboot your computer.
[Step 3: Resolving some problems]
If the phone application crashes whenever you try to make a phone-call, then you should flash your modem.
1.Shutdown you phone.
2.Press and hold down volume down, home button and power button to start in download mode until you see the confirmation, then press up to continue
3.Plug your micro usb cable into your phone, go to odin
4.Select modem (or CP for odin 3.09) and select the modem file
5.Uncheck Autoreboot
6.Click Start
7.Once done, unplug your cable, take off the battery, put it back, redo steps 2 to 4
8.Check this time Autoreboot and Start the process
If you flash your phone and you don't have the sound, then I advice you go back to 4.4.2, and follow this guide from the beginning
[KNOX 0x0 (not triggered) WIFI OFF]
I do see the point to go back to 4.3 (a lot of applications don't work properly on Kitkat + better performances for the S4 on Jellybean), however, I don't know if someone can use his phone without the wifi. Anyway, if you want you can try this method, for simply go back to 4.3, use saferoot and install mobile odin to go to 4.4.2 rooted, without triggering the knox (be aware that there is a simple method which roots the 4.4.2 but this doesn't work on newer 4.4.2).
I remind you that KNOX triggers only if you use a custom rom or modified kernel, in that case Knox turns to 0x1, and this cannot be undone.
Instead of writing my method, I find out two threads on xda.
First one, you cannot make phonecalls unless you flash the modem, and then you won't have the wifi anymore.[here]
Second, not tested yet, but it is promising, you can find out [here]
That's it guys, hope this will help you find your happiness.

I get 'No SIM' after 4.4.2 update. Any solution dear?

Sim adapter?
tariq2kn said:
I get 'No SIM' after 4.4.2 update. Any solution dear?
Click to expand...
Click to collapse
Ohhh noo sim, did you have a nano sim with an adapter or something ? I get this with my nanosim with the adapter

cefkiller said:
Ohhh noo sim, did you have a nano sim with an adapter or something ? I get this with my nanosim with the adapter
Click to expand...
Click to collapse
No adapter used.
My phone seems to be region locked, btu. I had an unlocking pin code to use another sim. But, when I am using the phone in India, It doesn't asks the pin but I get No SIM, I can see the signals on the statusbar & in about/status. It is not able to resolve the network. The /system/csc/customer.xml file states the mmc 404 as network blocked. The changing of network bands is also not possible. It is set by default at lte/wcdma/gsm.
I tried downgrading to 4.3 but got the phone in emergency mode, probably due to the locked bootloader. The Service Mode by *#0011# doesn't moves after the initial page.
How do I get through this mess? Kindly help in solving the issue.

tariq2kn said:
No adapter used.
My phone seems to be region locked, btu. I had an unlocking pin code to use another sim. But, when I am using the phone in India, It doesn't asks the pin but I get No SIM, I can see the signals on the statusbar & in about/status. It is not able to resolve the network. The /system/csc/customer.xml file states the mmc 404 as network blocked. The changing of network bands is also not possible. It is set by default at lte/wcdma/gsm.
I tried downgrading to 4.3 but got the phone in emergency mode, probably due to the locked bootloader. The Service Mode by *#0011# doesn't moves after the initial page.
How do I get through this mess? Kindly help in solving the issue.
Click to expand...
Click to collapse
Mmm I am afraid your phone is region locked, in this case it is very difficult to resolve the issue, for example if you are in Turkey your phone must be registered through a service, or purchased locally, I don't know maybe in India it is the same, meanwhile, try using your original sim Card, if it works, try using another sim card, i have a sim card that works on my Oneplus One but doesn't on the S4, it is crazy but what can we do. Finally, (before selling or throwing out your phone) try to visit this thread it might be helpful to follow those steps, visit all the links there, each one propose a solution. Hope you will find your happiness.
Regards.
Moncef

[ROM] N920PSPT2AOK3_SPR Stock Factory Build

Sprint Build OK3 Stock Full Factory Tar
This is for the SM-N920P Galaxy Note 5, do NOT attempt to flash this on any other model.
5.1.1 Lollipop
This tar will allow you to restore the full factory load via Odin.
Download Link -->> N920PVPS2AOK3_N920PSPT2AOK3_SPR.zip
Installation
• Download the factory build and unzip it. The result will be a xxx.tar.md5 file.
• Download Odin attached to this post
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the tar.md5 file to AP / PDA (depending on version of Odin)
Note: it may take several minutes to verify file integrity, be patient
• Click the start button and let the Odin flash complete, the phone will automatically reboot when completed
{
"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"
}

Thank you. Root messing with my phone and i need this. Thanks

tdunham said:
Sprint Build OK3 Stock Full Factory Tar
5.1.1 Lollipop
This tar will allow you to restore the full factory load via Odin.
Download Link -->> N920PVPS2AOK3_N920PSPT2AOK3_SPR.zip
Installation
• Download the factory build and unzip it. The result will be a xxx.tar.md5 file.
• Download Odin attached to this post
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the tar.md5 file to AP / PDA (depending on version of Odin)
Note: it may take several minutes to verify file integrity, be patient
• Click the start button and let the Odin flash complete, the phone will automatically reboot when completed
Click to expand...
Click to collapse
Are you building a rom from this? Keep up the good work.

rogerandgina said:
Are you building a rom from this? Keep up the good work.
Click to expand...
Click to collapse
Not right now. Moar Rom is based on OI6 and there aren't enough significant changes to warrant a rewrite. I'm holding off for Marshmallow/Android 6.0 I think.

Thank you sir. Good to have this file stashed away if something bad happens. Like zombies, plague, ect.

Thanks for what u do been using it since day one.
Sent from my SM-N920P using XDA Premium HD app

I'm assuming Android Pay and Samsung Pay will not be available still after installing this.
Sent from my SM-N920P using XDA Free mobile app

amase005 said:
I'm assuming Android Pay and Samsung Pay will not be available still after installing this.
Sent from my SM-N920P using XDA Free mobile app
Click to expand...
Click to collapse
Not if you have rooted and tripped knox!!!!!

Will I lose root after flashing this?

tayatl said:
Will I lose root after flashing this?
Click to expand...
Click to collapse
Yes.

tdunham said:
Yes.
Click to expand...
Click to collapse
Can this be rooted?
Will this wipe all my files on the phone or just the rom itself?

I'm thinking of picking up a Gear VR later today & I'm pretty sure i'll need to flash this .tar to get it to work properly? My current setup is MOAR & SkyHigh 3.0. I heard that kernel will allow it to work but must be on a OK3 build. Am I correct?
edit: yep, Need OK3
& double thanks for uploading this

@tdunham will your Moar rom for N5, will it work on my N5 with OK3
**Edit**
Nevermind I found my answer in Q&A thread.

Josephigloe said:
@tdunham will your Moar rom for N5, will it work on my N5 with OK3
**Edit**
Nevermind I found my answer in Q&A thread.
Click to expand...
Click to collapse
is that a No .... the answer is not in the thread,....

Globel said:
is that a No .... the answer is not in the thread,....
Click to expand...
Click to collapse
Yes, Moar rom will run over the OK3 firmware.

So wait, Android Pay functionality is lost after rooting the Note5 the same way Samsung Pay is? Like, forever?

MooreAJr said:
So wait, Android Pay functionality is lost after rooting the Note5 the same way Samsung Pay is? Like, forever?
Click to expand...
Click to collapse
Yes it is
Sent from my TW Slim v1 N920P using XDA Premium HD app

i had done flashing through this tar file. i am stuck on galaxy note 5 screen . i had tried all tar files . same issue. pl help

javed91214 said:
i had done flashing through this tar file. i am stuck on galaxy note 5 screen . i had tried all tar files . same issue. pl help
Click to expand...
Click to collapse
Are you sure this firmware is for your exact phone?

What is advantages of flashing this build

Question Bootloop after removing com.android.location.fused [SOLVED]

I rooted my phone a while back but did NOT install TWRP. Using System App Remover (Root needed), I started removing all sorts of bloatware after a bit of research for anything that sounded important.
Now I'm facing bootloop after removing com.android.location.fused. A little research shows other people facing similar issues were able to fix it using adb shell and TWRP. So I looked up elsewhere and got TWRP up and running.
Basically, the method is this:
https://www.reddit.com/r/PokemonGoSpoofing/comments/b1njwr
But there is no users folder under system on my phone!
I figured it's ok though. Because removing system apps using System Apps Remover, apps are not deleted but rather placed in a folder somewhere in the internal storage (can't remember the default location and can't find it using TWRP File Manager either).
Now here are my questions:
1. Is it possible for someone to share their own version of com.android.location.fused with me along with the correct storage location for me to put it into? Would it work?
2. Could someone please tell me what I am doing wrong that I get no users folder under system?
3. Is there a way for me to restore my own version of com.android.location.fused which is located god-knows-where on my phone?
P.S. Tech rookie here; bare with me...

Did you tried mounting all on twrp? system partition, data etc...? I correctly see that folder.
{
"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 can try to send the apk, but I don't think it will work, because you need to enable the package again on /data/system/users/0/package-restrictions.xml.
If all fails, why not flashing stock rom using HOME_CSC instead of CSC so all data will be preseved?
Spoiler: home csc
HOME CSC​If your purpose is to just re-install the firmware or update your Samsung device’s software without wiping your apps, all user data, and settings, you should go with the HOME CSC binary. Choosing this file will only affect the software version of your phone while keeping everything intact.

Ehhh, never remove GPS location services! Clock go brrrrr!

Oneplus# said:
Did you tried mounting all on twrp? system partition, data etc...? I correctly see that folder.
I can try to send the apk, but I don't think it will work, because you need to enable the package again on /data/system/users/0/package-restrictions.xml.
If all fails, why not flashing stock rom using HOME_CSC instead of CSC so all data will be preseved?
Spoiler: home csc
HOME CSC​If your purpose is to just re-install the firmware or update your Samsung device’s software without wiping your apps, all user data, and settings, you should go with the HOME CSC binary. Choosing this file will only affect the software version of your phone while keeping everything intact.
Click to expand...
Click to collapse
Thanks for the quick reply.
Mounting all selectable (some are not clickable) locations still gives me no users under system.
As for flashing stock rom, based on what you are saying, I suppose I should select all other options (BL, AP, and CP) except for CSC (which I go for USERDATA instead) and for that, I've got to select HOME_CSC file, correct?

Cactus1ne said:
Thanks for the quick reply.
Mounting all selectable (some are not clickable) locations still gives me no users under system.
As for flashing stock rom, based on what you are saying, I suppose I should select all other options (BL, AP, and CP) except for CSC (which I go for USERDATA instead) and for that, I've got to select HOME_CSC file, correct?
Click to expand...
Click to collapse
Yes, u need to select all in odin like u are flashing normally.
AP, BL, CP, and HOME_CSC
only use HOME_CSC instead of CSC
Spoiler: info
do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Don't know if it will work but is a try at least. Hope will fix

Oneplus# said:
Yes, u need to select all in odin like u are flashing normally.
AP, BL, CP, and HOME_CSC
only use HOME_CSC instead of CSC
Spoiler: info
do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Don't know if it will work but is a try at least. Hope will fix
Click to expand...
Click to collapse
Thanks for the clarification. Definitely gonna give it a try. Currently downloading the latest from sammobile.
Will post an update in a couple of hours.

Ok, so I flashed the latest stock rom from sammobile and it worked; just as @Oneplus# suggested it would.
Still don't know why I had no users under system but I'm just gonna call it a day and leave it.
Thanks again Oneplus#

Cactus1ne said:
Ok, so I flashed the latest stock rom from sammobile and it worked; just as @Oneplus# suggested it would.
Still don't know why I had no users under system but I'm just gonna call it a day and leave it.
Thanks again Oneplus#
Click to expand...
Click to collapse
Happy to hear that