Database Users

[TUT]How to install Nokia , Samsung ,HTC app on any Device

Hi , I foun an easy and simple way to Browse and download from market as a third-party device.
I just translate and arrange this
Source:http://www.windowsmania.pl/poradnik...rketu-jako-urzadzenie-innego-producenta-5114/
In response to the two other guides I decided to improve them and make them an easy and quick way to installation of any application from the collection of another manufacturer. I'm not here for the fun of change application ID and connect via USB. The guide (if no one is angry) I used some screenshots of the other instructions on this board go:
TOOLS:
Download and install Fiddler:
Code:
Code:
http://fiddler2.com
And Folow:
1-Go to Tools -> Fiddler options -> Connections and select as below
{
"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"
}
2-Close and Run the program again.
3-Press start+r then enter: Ipconfig
to know what is your IP
4-Enter the WiFi settings on your phone and click on the active WiFi connection (same on you pc , not 3G)
Edit it and type in the IP read the above paragraph and the port number 8888
Then Save Settings
5-Open the store from you mobile.
6-From PC ,on Fiddler'a with the active window Press Ctrl + R ,(it will open the notebook), press Ctrl + F and paste:
Code:
OnBeforeRequest (oSession: Session) {
The location shown in the screenshot paste the contents of the subsidiary as of the manufacturer to browse Market
Code:
if (oSession.uriContains ("Nokia"))
{
oSession.url = oSession.url.Replace ("Nokia", "Samsung");
}
Save changes to the file and close Notepad.
>>First is your phone manufacture and second is manufacture you want to use it's app.
7-Open store and search for the app you want , and once you opened the instal page , leave it and go to wifi setting page and remove the proxy configration , then go to app instal page and click install and have fun.

This is actually same solution as Nokia Portal and Proxy from Reker,
still thanks for the tut's, at least now people who don't have chance to grab nokia portal app & don't want to use proxy from reker can do this by themself...

otonieru said:
This is actually same solution as Nokia Portal and Proxy from Reker,
still thanks for the tut's, at least now people who don't have chance to grab nokia portal app & don't want to use proxy from reker can do this by themself...
Click to expand...
Click to collapse
I search for this after Nokia Portal not work for me
But : after I do this and use some app from nokia and samsung , My battery is drain fast , I do not know why .
Edit: I think here drive+ cause battery drain

better translation and original source (tut by me).
source: http://forums.wpcentral.com/windows-phone-8/236596-download-market-other-manufacturer.html

pawlakpl said:
better translation and original source (tut by me).
source: http://forums.wpcentral.com/windows-phone-8/236596-download-market-other-manufacturer.html
Click to expand...
Click to collapse
your (tut) is missing the last step
you must turn off proxy sitting from wifi page before app download or it will give error
and I mention the link for source clearly before write any thing
any way thanks' for ur efforts

zinzar said:
The location shown in the screenshot paste the contents of the subsidiary as of the manufacturer to browse Market
Code:
if (oSession.uriContains ("Nokia"))
{
oSession.url = oSession.url.Replace ("Nokia", "Samsung");
}
Save changes to the file and close Notepad.
>>First is your phone manufacture and second is manufacture you want to use it's app.
7-Open store and search for the app you want , and once you opened the instal page , leave it and go to wifi setting page and remove the proxy configration , then go to app instal page and click install and have fun.
Click to expand...
Click to collapse
I couldn't get it to work until I made Nokia and Samsung all caps.

Bjd223 said:
I couldn't get it to work until I made Nokia and Samsung all caps.
Click to expand...
Click to collapse
Yes, it must be written uppercase like "NOKIA","SAMSUNG" etc.

when i start fiddler i dont have internet acces either on my pc ( win 8.1) or my phone (ativ s) someone can help? please

miki89 said:
when i start fiddler i dont have internet acces either on my pc ( win 8.1) or my phone (ativ s) someone can help? please
Click to expand...
Click to collapse
do you have the "enableloopback" utility installed and checked the boxes stated in the op?
Sent from my GT-I8750 using Tapatalk

matgras said:
do you have the "enableloopback" utility installed and checked the boxes stated in the op?
Sent from my GT-I8750 using Tapatalk
Click to expand...
Click to collapse
yes and i m still in trouble.. :/

if you need Nokia Here Drive+ try this proxy 103.13.29.118 (no need fiddler) but you must use SysApp Pusher on phone to open app in Store

dxdy said:
if you need Nokia Here Drive+ try this proxy 103.13.29.118 (no need fiddler) but you must use SysApp Pusher on phone to open app in Store
Click to expand...
Click to collapse
i need nokia camera.. smart camera and others nokia apps for cam.. i already tried sysapp pusher but i cant reach these apps..

miki89 said:
yes and i m still in trouble.. :/
Click to expand...
Click to collapse
have you checked the the "confirm" box on your phone after applying the proxy?

matgras said:
have you checked the the "confirm" box on your phone after applying the proxy?
Click to expand...
Click to collapse
which confirm button?

miki89 said:
which confirm button?
Click to expand...
Click to collapse
After starting fiddler you need to open a command prompt as admin on your pc, type "ipconfig" and lookup the ipv4 local adress.
Now install "sysapp pusher" from the market.
Open wifi settings, enable proxy and fill in the ipv4 adress you've looked up before + the port you set fiddler to (change it in fiddler settings to something like 1309)
Now click on your phone the "confirm" button in order to save the proxy.
in the attachments i have a pic with everything explained.
Open sysapp pusher and try to install some apps. Not all of them work but a lot of them do.
On case you're using a lumia 520 for example; Nokia camera beta *will* work, the normal one doesn't.
Sent from my GT-I8750 using Tapatalk

For lumia 520 app Camera beta work without proxy. I know because installed to 520 without problem.
Sent from my Lumia 920 using Tapatalk

matgras said:
After starting fiddler you need to open a command prompt as admin on your pc, type "ipconfig" and lookup the ipv4 local adress.
Now install "sysapp pusher" from the market.
Open wifi settings, enable proxy and fill in the ipv4 adress you've looked up before + the port you set fiddler to (change it in fiddler settings to something like 1309)
Now click on your phone the "confirm" button in order to save the proxy.
in the attachments i have a pic with everything explained.
Open sysapp pusher and try to install some apps. Not all of them work but a lot of them do.
On case you're using a lumia 520 for example; Nokia camera beta *will* work, the normal one doesn't.
Click to expand...
Click to collapse
I did all that and i have eanble loopback and i still dont have internet access when i enable fiddler either on phone or pc.. :/

miki89 said:
I did all that and i have eanble loopback and i still dont have internet access when i enable fiddler either on phone or pc.. :/
Click to expand...
Click to collapse
you needed nokia camera right?
i'll send you the xap
check your pm

miki89 said:
when i start fiddler i dont have internet acces either on my pc ( win 8.1) or my phone (ativ s) someone can help? please
Click to expand...
Click to collapse
before fiddler starting disable your antivirus , then go to internet option from windows control panel then go to connection then lan setting then unchecked (automatically detect......)
start fiddler and follow the tut.

YoyaPhone 201 stuck on Androis 5.0 RU 1.124

Hi,
I searched the forum but couls not find the solution.
I got my Phone as a 201 with Android 4.4.3.
I updated it with the instructions from coolicool to 201 - 5.0 Andriod with Build LRX2 M.5.0.0-HK 1.66.
Second step I took was to uprgrade by the instruction on this forum (Thanks all !) to LRX2 M.5.0.-RU 1.1.124.
This worked.
{
"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"
}
But I still have some problems.
1. Won't update to 134
2. Backscreen (e-ink) "touch" doesn't seem to work. So I am stuck with the notification screen "YotaMirror is enabled" when I try to use the mirrorscreen option. (was working OK before upgrades)
Anyone knows how to get it to upgrade to RU 134 or higher
And has anyone a solution to get Mirrorscreen working again or at least skip the notification screen.

An additional problem started to show up.
The YotaPhone shuts down 5-10 seconds after I switch it on.
Anyone experiences with that kind of behaviour ?

Use this guide here on xda: https://forum.xda-developers.com/yotaphone-one/help/guide-everything-to-yotaphone2-t3547194 to flash from scratch your phone. It will work normally without bugs.

Tried to follow these instructions but it is a bit overwhelming.
When flahsing (select 1. ) I noticed an error passing by ( system.img)
but at the end there was no error message and it said soemting like "you are already on RU 1.124"
Would you a have a step by step guide for my situation ?
Your help is much appriciated !!

robmaas99 said:
Tried to follow these instructions but it is a bit overwhelming.
When flahsing (select 1. ) I noticed an error passing by ( system.img)
but at the end there was no error message and it said soemting like "you are already on RU 1.124"
Would you a have a step by step guide for my situation ?
Your help is much appriciated !!
Click to expand...
Click to collapse
Have you used the reworked version of yotaflasher? How much RAM do you have in your PC? Post screenshots of the passage or the error you mentioned. The guide above is already a "step by step", read it carefully.

TheArt. said:
Have you used the reworked version of yotaflasher? How much RAM do you have in your PC? Post screenshots of the passage or the error you mentioned. The guide above is already a "step by step", read it carefully.
Click to expand...
Click to collapse
This is the error message
target reported max download size of 2147483648 bytes
error: cannot load 'firmware/system.img'
target reported max download size of 2147483648 bytes
sending 'recovery' (13682 KB)...
I down loaded the reworked flasher and unzipped it in a seperate folder.
When I click the exe file ( as administrator), for a very short time the black screenshows up, but it is gone before I can select anything.
When I click the Installer icon on the desktop, It shows the black screen and the selections 1, 2, 3 , and I get the error during the flash procedure.
Thanks in advance

I did paste copy the content of the rework version into the original flasher folder, and this time is worked, that is: no error messages, question to updat radio and user content and reboot .
Problem is , non of the issues are solved. Still stuck on "YotaMirror mode is enabled" , not able to use touch on e-ink screen, sometimes just stops direcly after switching on (seems less now). Still version RU 124. How to get to 134 ??

Try it with a different PC and a new download of the rom.
user content

If trying a new pc doesn't work, start again - flash the oldest Russian kitkat firmware and repeat. I think i got that error message too. Forget any stuff about "radio", that's too complicated and in most cases unecessary, just download and flash.

I now tryed it on other computer, new download latest version .124, complete with deleting all user data .
But the problem remains , non of the issues are solved. Still stuck on "YotaMirror mode is enabled" , not able to use touch on e-ink screen, sometimes just stops direcly after switching the phone on (seems less now). Still version RU 124. How to get to 134 or higher?
Just at the point of throwing it out the the window right now.

5.0.0-EU1.1.124b - 5.0.0-HK1.1.66 - 5.0.0-RU1.1.124 ALL HAVE THE SAME RADIO FOLDER

The same folder name, but different files.

I compared the files and have the exact same size, so it must be the same file

Please don't change the subject of my question. I don't have a problem with the radio , I can use G4 LTE
I have a problem with the version , I am stuck at RU .124 and it wont update to 134.
I have a problem with the Mirrorscreen, ( not able to use it because it is stuck on a notification screen.
I have a problem with the e-ink screen - touch not working ( dont know soft- or hardware problem)
Yotaphone is shutting down within 2-10 seconds after starting up ( far less since my latest update/flash)
I don't have a problem with the radio.
I want to know how to skip the notification screen for Mirrorscreen
I want to know how to upgrade to version RU .134

robmaas99 said:
Please don't change the subject of my question. I don't have a problem with the radio , I can use G4 LTE
I have a problem with the version , I am stuck at RU .124 and it wont update to 134.
I have a problem with the Mirrorscreen, ( not able to use it because it is stuck on a notification screen.
I have a problem with the e-ink screen - touch not working ( dont know soft- or hardware problem)
Yotaphone is shutting down within 2-10 seconds after starting up ( far less since my latest update/flash)
I don't have a problem with the radio.
I want to know how to skip the notification screen for Mirrorscreen
I want to know how to upgrade to version RU .134
Click to expand...
Click to collapse
Hey robmaas99, did you manage to solve the issue? My e-ink screen also gets stuck in the "YotaMirror mode is enabled". I am pretty sure this is not a hardware issue because if you enable the double tap to unlock the screen it gets unlocked... so the taps are getting registered by de digitizer.
Version: LXRX21M.5.0.0-RU1.1.124 with the S01_003_3034_CN1_M05 Radio (the hybrid baseband).

jaboto said:
Hey robmaas99, did you manage to solve the issue? My e-ink screen also gets stuck in the "YotaMirror mode is enabled". I am pretty sure this is not a hardware issue because if you enable the double tap to unlock the screen it gets unlocked... so the taps are getting registered by de digitizer.
Version: LXRX21M.5.0.0-RU1.1.124 with the S01_003_3034_CN1_M05 Radio (the hybrid baseband).
Click to expand...
Click to collapse
There exists a widget that executes some code to start the mirroring on the back screen.
Its part of the yota toolbelt, found here:
https://forum.xda-developers.com/yotaphone-one/development/widget-yota-toolbelt-t3145462
If you have installed that, you can make a shortcut/widget on you normal home screen that will start the mirroring when you press it.
But from what I read, the problem is that it does not turn on the right touch mode for the back of the display, so I'm not sure it will work, even if you can get in to mirroring mode.

tomgaga said:
But from what I read, the problem is that it does not turn on the right touch mode for the back of the display, so I'm not sure it will work, even if you can get in to mirroring mode.
Click to expand...
Click to collapse
Hi Tomgaga, thanks but it didn't work. I still get stuck in the "Yota mirror is enabled". However I found that this is related to the YotaHub application because killing the process, and launching the yotamirror from the normal screen, plus launching it again from the EPD seems to make it work. However, it only works once. As the YotaHub is relaunched and keeps making it unusable.
@robmaas99 Did you make any progress on this?

jaboto said:
Hi Tomgaga, thanks but it didn't work. I still get stuck in the "Yota mirror is enabled". However I found that this is related to the YotaHub application because killing the process, and launching the yotamirror from the normal screen, plus launching it again from the EPD seems to make it work. However, it only works once. As the YotaHub is relaunched and keeps making it unusable.
@robmaas99 Did you make any progress on this?
Click to expand...
Click to collapse
Did you try deleting the data+cache of the yotahub app (Warning this will reset your edp screens config) ?

tomgaga said:
Did you try deleting the data+cache of the yotahub app (Warning this will reset your edp screens config) ?
Click to expand...
Click to collapse
Yes, I have tried to perform full factory settings, and deleting data individually from the app. Seems to be the same... really strange. More ideas welcome! Thanks!

robmaas99 said:
I now tryed it on other computer, new download latest version .124, complete with deleting all user data .
But the problem remains , non of the issues are solved. Still stuck on "YotaMirror mode is enabled" , not able to use touch on e-ink screen, sometimes just stops direcly after switching the phone on (seems less now). Still version RU 124. How to get to 134 or higher?
Just at the point of throwing it out the the window right now.
Click to expand...
Click to collapse
Sorry to say, but sounds like a hardware problem with the epd to me.

[Guide] How to root SM-J730F without TWRP [Android 7.0.0] [Firmware Included]

Note to users: I am NOT RESPONSIBLE for any damage done to your device. I did this on my phone and it worked just fine. Any damages done to the device is your fault. Please make sure to follow the steps carefully.
This is a guide on how to root the Samsung Galaxy J7 SM-J730F without TWRP. I've included a backup stock firmware in case you soft-brick your device.
BACKUP STOCK FIRMWARE FOR SOFT-BRICKED DEVICES:
In case you have soft-bricked your device by doing this tutorial incorrectly, download the stock firmware HERE and follow this guide to re-flash your phone, HERE. Do not attempt to root your device again unless you know what you're doing this time.
I also recommend completely backing up your device after successful root - click here to find out how.
WARNINGS:
1. You will have to WIPE ALL YOUR DATA in order to complete this tutorial.
2. You are at a very high risk of screwing up your device if you proceed ahead with this tutorial. Please make sure you know what you are doing, and that you have knowledge of re-flashing your phone. I am not responsible.
Requirements:
1. A Samsung Galaxy J7 SM-J730F device;
2. PC;
3. An USB cable;
4. Odin v3.12.7 - Download Here;
5. SuperSU .tar file - Download Here;
6. ADB - Download Here.
Instructions:
1. Download Odin on your PC from the link above, and extract everything from the archive to C:\ODIN (create a new folder);
2. Download the SuperSU .tar file from the link above and place it in your C:\ODIN folder. DON'T extract this archive;
3. Download ADB from the link above and extract the contents of the archive to C:\ADB (create a new folder);
4. Make sure USB Debugging AND OEM Unlock are ENABLED in Settings --> Developer Options on your phone. If you don't know how to activate Developer Options, check this out. After you've enabled these, connect your USB cable from your phone to your PC.
Note: If the phone tells you an access request is being received from your PC's fingerprint, accept it.
6. Open ADB on your computer by going to a Command Prompt, and typing cd C:\ADB;
7. Type adb devices to make sure your phone has been detected by ADB, like so:
{
"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"
}
8. In the Command Prompt, type adb reboot recovery and press enter to reboot your phone into Recovery Mode;
9. Once your phone has booted into Recovery Mode, select the Wipe data/factory reset, and then select Yes when it asks for confirmation:
(Note: THIS STEP IS MANDATORY. If you don't wipe your data, the encryption on your phone will remain and you will be unable to root your phone.)
10. After you've wiped your data, BOOT DIRECTLY INTO DOWNLOAD MODE FROM RECOVERY MODE. You can do this by holding down Volume Down + Home Key + Power Button WHILE STILL IN THE RECOVERY MENU.
Important Note: Ideally, you should still be in the recovery menu after doing a factory reset. Then do the instructions above to enter Download Mode. If you reboot AND THEN go to Download Mode, this method won't work, because your encryption will be put in place again and your phone will become unrootable. Please do the above steps with caution.
11. Hold the buttons down. If you did everything correctly, you should see a screen like this pop up:
12. Press the Volume Up button to proceed to the flashing section. You should see this screen:
13. Now, make sure that the USB cable is still connected to your phone. Open ODIN on your PC, and click on the AP button, then select the SuperSU archive that you downloaded. Make sure that your phone is detected, Odin has to say "Added!!" in the log to the right. If it doesn't say that, re-connect your USB cable to your phone, or switch the USB port on your PC. Then press Start to begin flashing SuperSU and rooting your phone:
14. After Odin has finished flashing your phone, it should say PASS! at the top left of the window, under it's name. Your phone will reboot automatically.
15. Once your phone has rebooted, you should be greeted by the usual setup screen that happens when you factory reset your device. Set up the settings as normal, and install SuperSU from the Play Store HERE once the phone is set up. (This is VERY important.)
16. After you've installed SuperSU, download Titanium Backup from the Play Store, and uninstall the system app "Knox" and everything with "Knox" in their name, and also uninstall "Device Security". They could mess with your boot and spam you with "Unauthorized Action" notification. You don't need them anyway -- once you're rooted, those two don't work anymore.
And that's it!
Your phone should be rooted now! I recommend installing Root Checker to see if you have done everything correctly. It should return this result if so:
Thanks for reading my tutorial! I hope it has helped you root your phone. If you did everything correctly, you should be rooted now. If you have soft-bricked your device and your phone is stuck on the Samsung boot logo, please download the included backup firmware and re-flash your phone, and do not attempt to root your phone again.
Hit the "Thanks!" button if my guide helped you!
Please leave any problems you might have in the comments, and don't be immature. I will not help people with a bad attitude. As I said, if you **** up, it's your problem and I am not responsible. But I will still try to help.
-----------------------------------------------------------------
Recommendations (Optional):
I recommend the following root-only apps to enhance your rooted experience.
1. Titanium Backup - Must-have app for rooted users. Useful in debloating your phone, freezing apps (hiding them from app drawer and disabling them - even system apps), backing up apps and more.
2. FlashFire - Useful for completely backing up your phone, flashing your phone with ZIPs, restoring backups and more.
3. Link2SD - Useful for moving apps to the SD card or to the Internal Storage, and more.
4. Greenify - Greenify working in root mode is the best battery saving app there is. It hibernates the apps that you don't use so that you can get the most out of your battery.
5. ES File Manager PRO - The perfect file manager. It lets you back up your apps, has a root explorer function, can let you see hidden files, lets you create shortcuts to any file on your home screen, and much more. There is a free version too, but I strongly recommend the PRO version.
Note: You guys can leave root-only apps in the replies as well, I didn't include a full list of them, obviously, so you guys can help people finding the apps they need to enhance their newly unlocked root experience.
If you want me to send you a list of safe to uninstall system apps, PM me.
Quick extra tip: To disable the ugly white frames for icons in the TouchWiz Home launcher, go to Settings -> Display -> Icon Frames and choose Icons Only.
------------------
Revisions:
- Added extra step about Knox resulting from the feedback of a user.
- Removed system app section. Seems to be giving people boot issues.

good work:good:
i did it and all was good till rebooting.my phone got stuck in the product logo so i had ton get a new software and root again but i'm afraid of rebooting it again.what should i d plz ?
i think the proplem within the device maintenance & security...it says restart to undo the unauthorised actions!!

MEMA1191 said:
good work:good:
i did it and all was good till rebooting.my phone got stuck in the product logo so i had ton get a new software and root again but i'm afraid of rebooting it again.what should i d plz ?
i think the proplem within the device maintenance & security...it says restart to undo the unauthorised actions!!
Click to expand...
Click to collapse
Root again and check every step carefully.
After you've checked everything was done properly, ONLY UNINSTALL KNOX AND DEVICE SECURITY. Don't attempt to uninstall other system applications other than the ones listed in the list.
That's why you're getting "Unauthorized Action" warning. Because Knox is still in effect, and it's detected that you're using a rooted phone. Therefore it warns you. So uninstall it completely, and everything else with "Knox" in its name.
I'm going to add this to the guide so that this doesn't happen again.
NOTE: Also don't worry, once you have completely re-flashed your phone with default stock firmware, it's not rooted anymore and rebooting is safe. Rebooting while rooted is also perfectly safe, if you can do tutorial steps correctly and don't skip over any steps.

I think this guide should be on this forum : https://forum.xda-developers.com/galaxy-j7-2017, but it had very help me, thank you!
After my second reboot (first done after remove the knox things), I'm stuck ont boot screen... I'm not sure, but I think onedrive can't be remove... I will try again

arwandar said:
I think this guide should be on this forum : https://forum.xda-developers.com/galaxy-j7-2017, but it had very help me, thank you!
After my second reboot (first done after remove the knox things), I'm stuck ont boot screen... I'm not sure, but I think onedrive can't be remove... I will try again
Click to expand...
Click to collapse
Don't try to uninstall system apps. I will remove that whole section - seems to be giving people a lot of trouble.

ScarXL said:
Don't try to uninstall system apps. I will remove that whole section - seems to be giving people a lot of trouble.
Click to expand...
Click to collapse
For me, it's the only useful part of the tutos, as I root the phone with trwp... I am tring to remove all systems apps exept onedrive, which always leads me to have issues after reboot.
For now, I've successfully remove
Duo
Excel
Google Play Musique
Google Play Films & séries
Powerpoint
S Health and services
Samsung notes
Skype
Smart Switch
Talkback
Upday
Word
*knox* + device security
EDIT:
Removed too without problems:
*ant* + radio
internet browser
samsung members
voice recorder
maps
my files
choco truc
foundation
roseeukor
samsung push
ScarXL, can you pm me the list you've removed?

arwandar said:
For me, it's the only useful part of the tutos, as I root the phone with trwp... I am tring to remove all systems apps exept onedrive, which always leads me to have issues after reboot.
For now, I've successfully remove
Duo
Excel
Google Play Musique
Google Play Films & séries
Powerpoint
S Health and services
Samsung notes
Skype
Smart Switch
Talkback
Upday
Word
*knox* + device security
Click to expand...
Click to collapse
Well, don't remove OneDrive then. I have no idea what's causing this issue. I uninstalled all those apps in the list on my phone and it works just fine?

this did not work for me. After rooting the device I am stuck with SAMSUNG boot logo. I think I have android 9 might be the issue.
AP: J730FXXS6CTD1
CP: J730FXXS6CTD1
CSC: J730FOXX6CSK6
Model: SM-J730F/DS

[MOD] [DEV] NAVDY Display (HUD)

{
"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"
}
NAVDY FIRMWARE DETAILED INSTALLATION INSTRUCTIONS
Pre-Requisite
ADB/Fastboot Installed.
Installation
1 Download the ROM.
2. Hold down the power button and plug into computer with a micro usb cable ( Power light should turn on red - not green).
3, Install the rom from terminal/command prompt either manually or from sh/bat files.
4. Reboot, Unplug & you'll be good to use in your car.
Current Rom Version - 3060
* Make sure you have migrated to latest here maps 'diskcache-v5' in order to use new features.​
Thanks to coronafire.. assumed dead NAVDY is going to breathe again.
New Features
Build 3060.1: here
Build 3060: here
Previous Builds Changelog : here
Bugs:​
For Updating Maps, app modification - see the below threads.
Modifications & Maps Download
Navdy FW Download
If you are interested to help with development.
Hacking/Development - Developers Only
NAVDY I
NAVDY II

Modifications & Maps Download
Android
Corona's build(s): Versions * Unlocks debug Mode
Working Search and maps on android - DIY Edition : Working Maps - Modify Apk
Now, you can download updated copy of navdy client directly from Google Play Store ... Navdy v2.x
iPhone: Working Search and maps on iOS: Modified IPA
Here Maps: Update Display
New Maps v5 - cache
Download the latest HERE APK from google app store. download the maps and transfer over USB to HUD.
Delete the existing files in here maps & make sure you are at least on fw v3053.
Code:
adb pull /sdcard/Android/data/com.here.app.maps/files/.here-maps
original Here SDK - v4 cache
Install the APK - HERE WeGo Offline Maps GPS v2.0.11480
Note: Later versions are not working.
Download the offline maps for your region. Plug your phone into the computer.
Use ADB PULL to get the maps on your system.
Code:
adb pull /sdcard/Android/data/com.here.app.maps/files/.here-maps/diskcache-v4
replace /sdcard if you have Internal Storage.
Copy this new diskcache-v4 folder onto your navdy, backing up the existing one first. (In case if something goes wrong).
In case you want to update Maps from your computer : Updating Maps from Computer
For HUD Settings, check this thread

Navdy FW Download
Navdy Firmware/Rom Download
My Builds : v3056 , v3057 Beta, v3059.1, v3060.1
Coronafire Build's : Android FIle Host
ALTERNATE LINK FOR FW DOWNLOAD : Navdy_Display
Debug build has Hud and Obd compiled in debug mode (can live debug them with android studio over usb adb connection)
Rom build.prop is set to userdebug. This also results in extra logging which could potentially slow the unit down a little.
The release build has the apk's built as release and the rom build.prop is set to user.
*Note : Don't use fastboot flash * but fastboot-i 0x9886 flash * check the included sh/bat file.
For Clean Installation, use these commands : OSX, for linux add sudo in front.
Code:
fastboot -i 0x9886 format cache
fastboot -i 0x9886 format userdata
fastboot -i 0x9886 format system
fastboot -i 0x9886 flash boot boot.img
fastboot -i 0x9886 flash recovery recovery.img
fastboot -i 0x9886 flash system system.img
fastboot -i 0x9886 reboot
NAVDY FIRMWARE DETAILED INSTALLATION INSTRUCTIONS

Awesome. Hopefully, we can hack the android app too and start getting some new features.

warwagon19792 said:
Awesome. Hopefully, we can hack the android app too and start getting some new features.
Click to expand...
Click to collapse
been partially hacked.. for working google maps, voice search & enable debug menu (useful for hud/map alignment etc.)

You know, I was struggling to connect Navdy with the bluetooth of my car (Android autoradio) and I have tried to look on their forum, but I have realized that the forum was dead... so I understood that there was a BIG issue ahead.
A few minutes later, I have learned that Navdy's end was confimed, and a few minutes later, I saw your post on reddit : you are a huge hope for all people who have trusted Navdy, paid high cost and wait a long time.
So my question is : what does/doesn't work with this hack ?
Thank you very much !

thank you very much, my expensive device is working again.

Thanks, man! I'm excited to see what can be done with a neat piece of hardware that had a crappy business plan behind it.

Great work - update the new firmware - works great
also repacked the modded apk - also works great.
for a while I was wondering if it is possible to add Hebrew support to menus and to voice navigation
any idea how to add this to firmware of navdy?
Thanks

Can't search for addresses
navx2vad said:
been partially hacked.. for working google maps, voice search & enable debug menu (useful for hud/map alignment etc.)
Click to expand...
Click to collapse
I am probably missing something, however I loaded v3052 and hooked Navdy back up in my car. After loading, it recognized my app. I was able to search for an address and Navdy showed the route as normal.
Move ahead a week. I tried to search for another address in the app, no joy.
I tried voice search, no joy.
I went to my computer and loaded google maps. I searched for the address and sent it to my phone. The directions came up in google maps on my phone, but not the Navdy.
What am I missing??
Thanks.
Glad to see Navdy has some life left in it.

volski said:
Great work - update the new firmware - works great
also repacked the modded apk - also works great.
for a while I was wondering if it is possible to add Hebrew support to menus and to voice navigation
any idea how to add this to firmware of navdy?
Thanks
Click to expand...
Click to collapse
sorry for late reply! yes it's very much possible.
go here... ..
you will see values folders.. all you need to do is translate strings/plurals.xml
there are exiting translations which will give you an idea how to do it.

Help me for my Navdy
I want update my navdy, but in my computer I can't see the good driver. Can you help me?
Thanks.
Axel

Jouve said:
I want update my navdy, but in my computer I can't see the good driver. Can you help me?
Thanks.
Axel
Click to expand...
Click to collapse
if minimal installation is not working for you try Installing android studio, it should take care of it.
you can verify by typing adb devices or fastboot devices on command prompt.

I am trying to push a new version of hud.apk, signed and everythingm but I keep getting "INSTALL_FAILED_UPDATE_INCOMPATIBLE". I already uninstalled the old version, the issue persists. Any ideas?

Thank you for all the hard work to the devs. You folks rock.

In case this hasn't been said enough. THANK YOU, all the way from Singapore. I got the firmware and the apk up and running and getting back my search just beats everything else. THANK YOU AGAIN.

Answering my own question...There was an issue with the cert brought on by some naming confusion. The ROM cert is called navdy_cert and the HUD cert is navdvy_alelec. Once it's signed with navdy_alelec it's all good. Now to make some changes

megacrazy said:
Answering my own question...There was an issue with the cert brought on by some naming confusion. The ROM cert is called navdy_cert and the HUD cert is navdvy_alelec. Once it's signed with navdy_alelec it's all good. Now to make some changes
Click to expand...
Click to collapse
great you figured it out. Look forward to the changes.. share on git if you can.

navx2vad said:
great you figured it out. Look forward to the changes.. share on git if you can.
Click to expand...
Click to collapse
Will do. I am working on updating the graphics a little, as I feel that was always a bit of a letdown with the Navdy.

megacrazy said:
Will do. I am working on updating the graphics a little, as I feel that was always a bit of a letdown with the Navdy.
Click to expand...
Click to collapse
my guess is they never cared about graphics, with varying devices they just used generic images, low png graphics.

[How to] - Get VoLTE working for T-Mobile US (yes, it actually works)

Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2. run the following commands (note that you MUST be rooted to enable this. The mod survives returning to stock unrooted, and even survives OTA so you can unroot when finished if you want.):
'''
adb shell
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
'''
3. once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
4. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
5. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
6. click the load button and select the mcfg_sw.mbn you downloaded earlier.
7. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
8. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
9. on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
10. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
{
"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"
}

Can this phone work on Metro PCS network

I tried and tried, but i cannot get PST to see my phone. I loaded qualcomm drivers and ADB drivers, nothing. Any suggestions?
Daha3ker said:
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2.once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
3. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
4. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
5. click the load button and select the mcfg_sw.mbn you downloaded earlier.
6. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
7. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
8.on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
9. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
Click to expand...
Click to collapse

This sounds scary. I thought volte works on band 12. If the band is missing how would it work. How can you confirm it actually works.

Hi!
I am running into the same issue of two computers (Win 7 and Win 10) that cannot see the phone. Anyone willing to help in getting PDC to see the phone? Thanks!

I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.

mymeatb18 said:
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
Click to expand...
Click to collapse
I would like to know this as well.

Ulver said:
I would like to know this as well.
Click to expand...
Click to collapse
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config diag,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.

Hi Daha3ker,
I tried to enable with the mentioned commands and still PDC cannot see my phone.
Daha3ker said:
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config acm,diag,mtp,adb
setprop persist.sys.usb.config acm,diag,mtp,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Click to expand...
Click to collapse

Can't seem to make the phone appear in PDC as well, I've rooted the device with magisk and have tried to input the commands as suggested but it is still not being detected...

This is what I have

Any word on this?

Update, with stock you need to enter the command
setprop sys.usb.config diag,adb
While the phone is plugged in to the computer for it to work. I was using a different set of debug tools.

I had to use the following command to get PDC to work.
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Im running Pixel Experience 20190320 rom with Magisk 18.1.
QPST 2.7.460
I used the QUD.WIN.1.1 Installer-10040.5 drivers on Windows 10 x64.

Could you unroot and relock bootloader and have this continue working and survive OTA updates?
---------- Post added at 11:18 PM ---------- Previous post was at 10:25 PM ----------
Looks like this survives a complete fastboot flash/relock. How would you reverse this and go back to stock?
---------- Post added at 11:30 PM ---------- Previous post was at 11:18 PM ----------
I want to switch back because sometimes when I make calls, it's high pitched and quiet. I can turn off voLTE to go back to the way it was, but would be nice to be stock again.

What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)

joaomiguelsm said:
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
Click to expand...
Click to collapse
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.

Ulver said:
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Click to expand...
Click to collapse
Oh, sad
This is the worst thin of Xiaomi in Brazil

PDC not recognizing phone
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike

mtrohan said:
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
Click to expand...
Click to collapse
im getting same problem... can solve??
pleaaaase... need help.