hello I just purchased a G1 t-mobile off ebay and it came with firmware RC37 working fine, then i had the brilliant idea to put a custom firmware on it , so i downgraded it to RC7 - uk but now im stuck on the activation screen and guess what..i dont have a data plan on t-mobile and no other sim card that supports 3G/internet connection. so I read somewhere that 'donut' lets you bypass the activation screen by touching the screen from top left all the way to the bottom left so I upgraded the firmware to donut 1.6 but i tried all of the possible combinations to bypass the screen and it didnt work. what do you think I should do?I tried connecting the phone with the pc using ADB but i stumbled uppon the drivers problems. its the first time a phone is giving me so much trouble for such a simple task, if anyone knows any simple way to bypass the screen please help me out, any kind of feedback will be highly appreciated. thanks
phr0z said:
hello I just purchased a G1 t-mobile off ebay and it came with firmware RC37 working fine, then i had the brilliant idea to put a custom firmware on it , so i downgraded it to RC7 - uk but now im stuck on the activation screen and guess what..i dont have a data plan on t-mobile and no other sim card that supports 3G/internet connection. so I read somewhere that 'donut' lets you bypass the activation screen by touching the screen from top left all the way to the bottom left so I upgraded the firmware to donut 1.6 but i tried all of the possible combinations to bypass the screen and it didnt work. what do you think I should do?I tried connecting the phone with the pc using ADB but i stumbled uppon the drivers problems. its the first time a phone is giving me so much trouble for such a simple task, if anyone knows any simple way to bypass the screen please help me out, any kind of feedback will be highly appreciated. thanks
Click to expand...
Click to collapse
If you have a friend that has tmobile with data service, pop his sim card in, activate it, then switch back to your own. Otherwise you'd have to downgrade and use the adb shell command to get wifi inorder to activate it.
I dont know anyone with a t-mobile sim, I can use a 3 Phone/sim though that has internet access, any chance to do it through that? I tried using the adb method, but i get stuck on the drivers issue, and since i upgraded to donut i get the 'device is not recognized' error. when i try to put the custom drivers that are issued in the tutorials it wont accept them.
Edit - // - I managed to make it work with ADB flashed and installed cyanogen mod.
I managed to connect the phone with ADB. when I type adb devices in cmd prompt i get:
C:\>adb devices
List of devices attached
HT95NKV02235 device
then i type adb shell and the command to enable the wifi but all i get is this:
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Starting: Intent { action=android.intent.action.MAIN comp={com.android.settings/
com.android.settings.Settings} }
Warning: Activity not started, its current task has been brought to the front
Is it possible to clone a XT1069 Hard Brick with another equal smartphone with QPST or other Software?
Acquired recently another xt1069 RetBR identical to mine, trying to put the same in diagnostic mode and searching the web I have good news, I found out how to put xt1069 in diagnostic mode, just make the procedure to enter fastboot connecting the cell with the volume low down for 4 seconds and select the BP Tools mode (the phone will start normally but with enabled diagnostic mode) in the drivers you need to manually install the existing driver and installed with Motorola Device Manager, go to:
Device Manager
> Has an outdated driver with name Motorola QC Diag Port
> double click on this
> Find driver Software on computer
> Let me pick from a list of device drivers on my computer
> Show all devices (wait while it loads all drivers)
> Select the Manufacturer: Motorola
> Select the Motorola QC Diag Port driver (ignore the driver compatibility information) and ready.
Now is the situation gets a little complicated ... I have QPST Version 2.7 Build 422, see my device that works in QPST Configuration and he appears to me as:
Phone: MSM8626
ESN: 0
Phone Number: Empty
Banner: MSM8626
Port: COM9 (COM9 (Auto add)).
Hereafter wanted a guide to try to revive the other xt1069 that is with hard brick.
Bootloader Unlock = No
Root = No
Android version = 6.0
Patch Level = 1 / Jan / 16
Version of the baseband = MSM8626BP_1032.3113.99.00R DSTV_CUST
Kernel = 3.4.42-gef77327
System = 24.41.34.titan_retbr_dstv_retbr.en.BR.retbr
Version = MPB24.65-34 number
Sorry my English.
You can try with jtag to read from working phone emmc and flash to bricked emmc. (mobileunbrick.com re alive xt1068 16gb on this way)
steva-81 said:
You can try with jtag to read from working phone emmc and flash to bricked emmc. (mobileunbrick.com re alive xt1068 16gb on this way)
Click to expand...
Click to collapse
Yes it's possible with Jtag, but isn't that expensive? A user like me wouldn't pay for example for a medusa pro jtag 300$ to get fixed a phone which has a price around maybe 100$.
k4m1h4ck3r said:
Is it possible to clone a XT1069 Hard Brick with another equal smartphone with QPST or other Software?
Acquired recently another xt1069 RetBR identical to mine, trying to put the same in diagnostic mode and searching the web I have good news, I found out how to put xt1069 in diagnostic mode, just make the procedure to enter fastboot connecting the cell with the volume low down for 4 seconds and select the BP Tools mode (the phone will start normally but with enabled diagnostic mode) in the drivers you need to manually install the existing driver and installed with Motorola Device Manager, go to:
Device Manager.....
Click to expand...
Click to collapse
Not sure if this helps:
http://forum.xda-developers.com/android/general/tutorial-how-to-unbrick-tou-lenovo-k910-t2893932
https://www.youtube.com/watch?v=D-YmQ_8OVuY
But it looks like you still gonna need programmer mbn
Not to bay, go in the repair servis who have jtag, and pay 20$ to unbrick. In Belgrade only one r.s have riff box jtag. And can't do anything with my phone, say can not access emmc (read only) To send in India will cost to mach money, and maybe can not unbrick my moto g xt1068. I will waiting blank-flash to leak, if leak.
Like the topic says, my ZB551KL Zenfone Go won't register network operators and i suspect it's because the IMEI of the phone is 0 after applying official update. I've tried to Root the phone by downgrading to version WW_V13.2.8.13 and installing KingRoot and using Xposed IMEI modules but this fuxed up the phone and sent it into a bootloop. So i reinstalled the WW_V13.2.8.13 firmware again (the only firmware that KingRoot will work on, so basically the only way to root the phone) and rooted the phone again and tried to open the diagnostics port through adb shell, but when i execute the command: "setprop sys.usb.config diag,adb" it says setprop: not found.....so i am guessing i can't open the diagnostics port this way. And Xposed IMEI changer won't work cause Xposed fux up my phone into a bootloop.
So if anyone has any idea how i could change my IMEI back to what it originally was i am all ears. I was reading something about using a HEX editor, but i don't know how to get the IMEI files out of the phone or how to write them back into the phone.
And yes i've tried installing every official firmware, factory reset many times etc.... IMEI is 0 until i somehow change it myself. And when i do my SIM cards will be able to register on the network again. So any help is very much appreciated.
Honestly, they should just ship android with rooting options. Rooting newer devices is a huge pain in the neck right now.
This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.
How we can root zb551kl
same problem here.. pls help
dbfonseca said:
This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.
Click to expand...
Click to collapse
yep enable diag port take the hell out of me
i enabled diagnotic mode
eyobaaa said:
yep enable diag port take the hell out of me
Click to expand...
Click to collapse
how to recover imei from zero ?? i enabled diagnostic mode on this device
Basically you have to boot to fastboot then flash CSC firmware (also called RAW firmware) to enable qualcomm diag port.
Note that there are 2 kinds of this: 1 is the kind that connects via QDLoader 9008/QFIL to recover from hardbrick, and one that installs a very raw form of android and enables the diag port. You need the latter. Since I don't have the files anymore, you basically run this bat script file that connects via fastboot and hot-boots its own kernel that allows the diag port.
Then use this program called FactoryTool_WriteIMEI_v1.0.2 (Factory_tool_wingtech_v1.0.2.0.exe) to write the IMEI (since official qpst dont support dual Sim). You may need to fire up QPST/QFIL to get a proper com port for the software to work. Then flash first old firmware and you're good to prevent it getting corrupt again.
---
Problem is that this seems to be a symptom of a failing board since ever since the LCD started to flicker when in battery mode and OK when USB is plugged in. Baseband and IMEI becomes corrupt again when you update your system. Also periodically phone shuts down and becomes a 9008 device (hardbrick) but also comes back. Left it alone for days and it was fine after but problem came back after trying a game (solder cracks?) Will try to reflow the motherboard.
May I ask if you changed your LCD? This started happening to mine when I installed a system update after replacing the LCD+digitizer. It seems the phone is downloading the Chinese software update since it detects the (chinese?) panel and installs an incompatible Chinese modem baseband firmware. Upgrading to latest downloadable firmware also corrupts the IMEI slowly (Sim 1 first then Sim 2).
hello friends good day
I come to you because I have a problem wanting to change the rom of my note 9
when I try to flash by odin a new rom does not leave me and sends me an error on the screen that says MDM mode Can´t download (xbl)
and there you stay have you gone through this?
Is there anything I can do?
My Note is telcel of mexico
Thank you very much and greetings
Diavoluss666 said:
hello friends good day
I come to you because I have a problem wanting to change the rom of my note 9
when I try to flash by odin a new rom does not leave me and sends me an error on the screen that says MDM mode Can´t download (xbl)
and there you stay have you gone through this?
Is there anything I can do?
My Note is telcel of mexico
Thank you very much and greetings
Click to expand...
Click to collapse
did you find an answer? i am from México too and i am having the same problem
Miroku Asakura said:
did you find an answer? i am from México too and i am having the same problem
Click to expand...
Click to collapse
I still can not find anything, tutorial to do a hard reset but out there nothing
Diavoluss666 said:
hello friends good day
I come to you because I have a problem wanting to change the rom of my note 9
when I try to flash by odin a new rom does not leave me and sends me an error on the screen that says MDM mode Can´t download (xbl)
and there you stay have you gone through this?
Is there anything I can do?
My Note is telcel of mexico
Thank you very much and greetings
Click to expand...
Click to collapse
Hello!
I had the same problem...
I bogth Note 9 from ebay USA... from some guy...
and when I wanted to update Android to 9.0 version... I got MDM mode problem...
solution I found here!!!
All what you need to do is:
activate ADB (anyhow) I will attach application...
and type:
adb shell
pm disable-user --user 0 com.sec.knox.kccagent
pm disable-user --user 0 com.planetcellinc.ressvc
pm disable-user --user 0 com.absolute.android.agent
pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms
reboot bootloader
and than You can flash any firmware you want with Odin.
if you wish to change region (CSC) - you need to disable these knox apps after every reinstall of ROM. (My was for TTT region... and I shifted to MXO).
Sm-n9600 note 9
C:\Users\Suporte GSM!\Desktop
Hello everyone, please need help, customer took this device locked mdm, I went to pass a firmware now it just reboots, but goes into download mode, does not accept any firmware, if anyone has this solution may be costly please help me
FRP OFF
OEM ON
KG STATUS LOCKED
BINARY 3
I would be more concerned about how MDM Mode is enabled in the first place. IIRC MDM Mode is used for either Samsung Retail Mode or Enterprise Enrollment. Considering you bought this phone second-hand its possible this device was stolen. However its also possible this was just a mistake by the previous owner. I would advise contacting the seller for a refund or replacement.
last1youlove said:
I would be more concerned about how MDM Mode is enabled in the first place. IIRC MDM Mode is used for either Samsung Retail Mode or Enterprise Enrollment. Considering you bought this phone second-hand its possible this device was stolen. However its also possible this was just a mistake by the previous owner. I would advise contacting the seller for a refund or replacement.
Click to expand...
Click to collapse
thank you brother bought by olx, paid high value, impossible refund waiting for solution
Zlatomip said:
Hello!
I had the same problem...
I bogth Note 9 from ebay USA... from some guy...
and when I wanted to update Android to 9.0 version... I got MDM mode problem...
solution I found here!!!
All what you need to do is:
activate ADB (anyhow) I will attach application...
and type:
adb shell
pm disable-user --user 0 com.sec.knox.kccagent
pm disable-user --user 0 com.planetcellinc.ressvc
pm disable-user --user 0 com.absolute.android.agent
pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms
reboot bootloader
and than You can flash any firmware you want with Odin.
if you wish to change region (CSC) - you need to disable these knox apps after every reinstall of ROM. (My was for TTT region... and I shifted to MXO).
Click to expand...
Click to collapse
do i need to reenable these after flashing?
deadknight956 said:
Do I need to re-enable these after flashing?
Click to expand...
Click to collapse
I found the guy off the eBay who charged $20 to do it remote within 15 min, and I was up and running since above method won't let you take RAC junk complete off the phone, you will still not have USB debugging enabled.
got it sorted
Diavoluss666 said:
hello friends good day
I come to you because I have a problem wanting to change the rom of my note 9
when I try to flash by odin a new rom does not leave me and sends me an error on the screen that says MDM mode Can´t download (xbl)
and there you stay have you gone through this?
Is there anything I can do?
My Note is telcel of mexico
Thank you very much and greetings
Click to expand...
Click to collapse
i downloaded 4 file firmware and then flashed via z3x, selected repartition and the process failed, but then i got the device to boot in recovery and wiped it, came back on thankfully.
In advance, thanks for all of the prior threads and expert advice on this topic!
In particular, I read this post (21 pages, 201 posts) and gleaned a lot of info, but I'm a bit uncertain of some steps.
In addition, I'm trying to help a friend remotely and am hoping to get some Expert Eyes on this before we embark on this downgrade journey.
Please let me know if there are any steps I'm missing or that should be refined/changed.
Specific Model & OS Information:
Galaxy Note 9 US Unlocked Snapdragon
Model Number: SM-N960UZKAXAA
Model (Settings/About Phone): SM-N960U1
Prior Android 8.1.0 AP/CP N960U1UEU1ARL1
Prior Android 8.1.0 CSC N960U1OYM1ARL1
Current Android 9
Build Number PPR1-180610.011.N9600ZHU1CSB2
Preliminary Questions:
Per this post #171 , is above Build Number Bootloader v1 or v2? Will I be able to install Oreo as outlined below?
Answer: Both Android 8 and Android 9 shown above use Bootloader version 1
Is turning off Software Updates on this Unlocked version SM-N960U1 enough to prevent PIE from being served again?
Answer: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Downgrade to Oreo Steps:
On PC: Download SamMobile 8.1.0 Firmware 2019-01-13 from https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/
On PC: Download/Install Patched ODIN verB: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
On PC: Download/Install Samsung SmartSwitch: https://www.samsung.com/us/support/owners/app/smart-switch
Connect Phone to PC with USB Cable (allow for USB drivers to install)
On PC: Run SmartSwitch and backup all accounts, settings, files, messages, pictures, videos, etc.
note: Un-check any option(s) SmartSwitch to install updates (see post) (very important to do this per IT_Architecht post)
Disconnect Phone from PC
On Phone: Per IT_Architect: Consider Performing a Factory Reset, boot the phone, go through set up but SKIP the WiFi Setup (so it doesn't trigger another PIE Update).
On Phone: Power Down then Remove SIM Card (so it doesn't trigger another PIE Update after installing Oreo?)
On PC: Extract the firmware file downloaded in step #1. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
On Phone: Boot Phone into Download Mode: First Power Down your phone. Then, Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode.
Connect Phone to PC with USB Cable:
connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
On PC: Run Patched ODIN vB:
Install Firmware without HOME_CSC!!! (this will wipe it clean) (the "HOME_CSC" causes boot loop problems?)
Add each file to it's respective field in Odin v3.13.1.
Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
BUT NOTE AGAIN: do NOT use the HOME_CSC option as it may/will cause boot loop problems
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
Click the start button, wait for Odin to say 'PASS' in a GREEN box.
Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
On Phone: After installation of Oreo, Enable Developer Mode (Settings/AboutPhone/SoftwareInformation: Click Build Number 4 times until Developer Mode is Enabled)
On Phone: Turn off Software Updates (to prevent PIE from updating automatically again): Settings/DeveloperMode/"Auto Update System"=Disabled
On PC: Run Smart Switch, restore everything EXCEPT settings (i.e. old Pie settings won't translate to Oreo properly)?
note: Un-check any option(s) SmartSwitch to install updates (see post) (very important to do this per IT_Architecht post)
[*]Use ADB to disable System Updates: See below "STEPS TO DISABLE SYSTEM UPDATES USING ADB" or post See steps here to disable Software Update
On Phone: Insert SIM Card
STEPS TO DISABLE SYSTEM UPDATES USING ADB:
As mentioned in the other post, there are two System Apps named "Software Update":
1) Software update (with a green icon) (underlying com.sec.android.soagent)
2) Software update (with a blue icon) (underlying com.wssyncmldm)
I only disabled com.wssyncmldm.
I did this on four Note 9 US Unlocked and none have since received the PIE update notice since March 22nd, 2019.
Here are the steps I used:
Installed ADB on Windows 10 Computer: Great Overview Here on ADB
Phone: Settings/DeveloperOptions/USB Debugging: ON
Connect USB Cable (watch for prompts)
Computer: Open a Command Prompt; Type in: c:\adb; adb devices; adb shell
Computer: pm disable-user --user 0 com.wssyncmldm
THAT disables the Second/BLUE "Software Update" (com.wssyncmldm)
Phone: Turn USB Debugging: OFF
Confirm it is Disabled:
Phone: Settings/Apps/Menu/ShowSystemApps,
Scroll Down to Software Updates
Blue should indicate "disabled"
Reboot; Confirm
I edited my original post:
1) Answered Preliminary Question #1: Both Android 8 and Android 9 shown above use Bootloader version 1.
With the help of member QNC
qnc said:
Everything looks good. You even mentioned the boot loader number. As long as they match the downgrade will be no problem. 5th number counting right to left.
Click to expand...
Click to collapse
(see post)
I bolded the Bootloader version numbers
2) Answered Preliminary Question #2: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Added the link to last step of the original outline: See steps here to disable Software Update
JohnNadeau said:
I edited my original post:
1) Answered Preliminary Question #1: Both Android 8 and Android 9 shown above use Bootloader version 1.
With the help of member QNC
(see post)
I bolded the Bootloader version numbers
2) Answered Preliminary Question #2: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Added the link to last step of the original outline: See steps here to disable Software Update
Click to expand...
Click to collapse
Great write up. I appreciate the work you've put into this.
For stopping future updates without having to pay for an extra app, you can do the following:
Flash ANY CP file for you SPECIFIC model device as long as it's on the same Bootloader version(for now).
So you can
- flash a CP from any Oreo firmware for your specific model on Oreo or Pie
- flash a CP from any Pie firmware for your specific model on Oreo or Pie
This will stop software update from occurring and will not cause any adverse effects on your device. To resume software updates, just flash the CP for the version of firmware you're on.
I saw this info somewhere on Note 9 thread and tried it myself and it's working. So shouts out to that person.
Jammol said:
Great write up. I appreciate the work you've put into this.
For stopping future updates without having to pay for an extra app, you can do the following:
Flash ANY CP file for you SPECIFIC model device as long as it's on the same Bootloader version(for now).
So you can
- flash a CP from any Oreo firmware for your specific model on Oreo or Pie
- flash a CP from any Pie firmware for your specific model on Oreo or Pie
This will stop software update from occurring and will not cause any adverse effects on your device. To resume software updates, just flash the CP for the version of firmware you're on.
I saw this info somewhere on Note 9 thread and tried it myself and it's working. So shouts out to that person.
Click to expand...
Click to collapse
Hey @Jammol,
Thanks very much for the input!
For clarity, are you saying that in my steps #8 and #11, the act of selecting the CP file to flash (at the same time as the others in that zip file) will cause it to stay on the version of Android that I'm flashing?
JohnNadeau said:
Hey @Jammol,
Thanks very much for the input!
For clarity, are you saying that in my steps #8 and #11, the act of selecting the CP file to flash (at the same time as the others in that zip file) will cause it to stay on the version of Android that I'm flashing?
Click to expand...
Click to collapse
It may cause Odin to fail if you mix then on initial flash. Flash you device to whatever version Android you want, and then go back after reboot and flash CP of choice for your model device.
Hey there. Unfortunately I believe I'm in the out of luck category. As of May 12th, 2019, my device was up to date, and I wanted to downgrade to Oreo as this was the worst "upgrade" in known history (up there with Windows ME & Vista). But after much cajoling with Odin, various PC's, etc. it seems like it's a bootloader impossibility issue. I just wanted to confirm that, for other folks like me.
serialteg said:
Hey there. Unfortunately I believe I'm in the out of luck category. As of May 12th, 2019, my device was up to date, and I wanted to downgrade to Oreo as this was the worst "upgrade" in known history (up there with Windows ME & Vista). But after much cajoling with Odin, various PC's, etc. it seems like it's a bootloader impossibility issue. I just wanted to confirm that, for other folks like me.
Click to expand...
Click to collapse
Looks like there are some Bootloader v2's out there, but you'd need to find one for your specific phone/model (this post references a Poland version at sammobile dot com ) :
https://forum.xda-developers.com/galaxy-note-9/help/how-update-t3927731
Post #4 in that thread references a YouTube video, which I haven't watched, but may be helpful
JohnNadeau said:
Looks like there are some Bootloader v2's out there, but you'd need to find one for your specific phone/model (this post references a Poland version at sammobile dot com ) :
https://forum.xda-developers.com/galaxy-note-9/help/how-update-t3927731
Post #4 in that thread references a YouTube video, which I haven't watched, but may be helpful
Click to expand...
Click to collapse
So if baseband and build are 1CSD1, am I on bootloader v1?
serialteg said:
So if baseband and build are 1CSD1, am I on bootloader v1?
Click to expand...
Click to collapse
Sounds like it.
Check out my original post above, including the link under Preliminary Question #1: That link explains how to identify the Bootloader Version.
What's your full Model Number? Is it the same as mine?
Also, in this original post, under Downgrade to Oreo Steps, #2: Did you download the "patched" version of ODIN?
JohnNadeau said:
Looks like there are some Bootloader v2's out there, but you'd need to find one for your specific phone/model (this post references a Poland version at sammobile dot com ) :
https://forum.xda-developers.com/galaxy-note-9/help/how-update-t3927731
Post #4 in that thread references a YouTube video, which I haven't watched, but may be helpful
Click to expand...
Click to collapse
JohnNadeau said:
Sounds like it.
Check out my original post above, including the link under Preliminary Question #1: That link explains how to identify the Bootloader Version.
What's your full Model Number? Is it the same as mine?
Also, in this original post, under Downgrade to Oreo Steps, #2: Did you download the "patched" version of ODIN?
Click to expand...
Click to collapse
Model # is SM-N960U1. Using patched or unpatched ODIN, it hangs on Setup Analysis or Initializing Connection even if it does identify the phone on a COM port. Tried a different computer but the phone wasn't recognized on ODIN (download mode) at all.
serialteg said:
Model # is SM-960NU1. Using patched or unpatched ODIN, it hangs on Setup Analysis or Initializing Connection even if it does identify the phone on a COM port. Tried a different computer but the phone wasn't recognized on ODIN (download mode) at all.
Click to expand...
Click to collapse
Hmmm... I'm not finding any info or firmware on the SM-960NU1. Is that an unlocked or carrier version?
Have you tried a different/new cable?
Just a typo. I'll try a different cable
serialteg said:
Just a typo. I'll try a different cable
Click to expand...
Click to collapse
Another thing worth noting...
When I first connected my Note 9 to a Windows 10 computer, it took quite a while (maybe even 5-10 minutes) while it downloaded & installed the Samsung/USB drivers. Just make sure they're fully installed before trying to run Odin.
Thanks, different cable different computer and downgrade succesful. Now on to the journey of blocking the push update... done. Many thanks to all of you, for ten years at least XDA has saved the day for me and still is such a great school.
Samsung had a good run there. Finally ran into an update so bad that it made me for the first time in years have to find a way to hack a downgrade or seriously think about selling this device to get a different one (vibrating camera *is* an issue, on my second one, and by now know it's not going to be fixed).
serialteg said:
Thanks, different cable different computer and downgrade succesful. Now on to the journey of blocking the push update...
Click to expand...
Click to collapse
Wow... that's great! Good to hear. Congrats!
Step #15, I used ADB to disable one package and have never received further update notifications... uh... threats :laugh:
Use ADB to disable Software Update: See steps here to disable Software Update
JohnNadeau said:
In advance, thanks for all of the prior threads and expert advice on this topic!
In particular, I read this post (21 pages, 201 posts) and gleaned a lot of info, but I'm a bit uncertain of some steps.
In addition, I'm trying to help a friend remotely and am hoping to get some Expert Eyes on this before we embark on this downgrade journey.
Please let me know if there are any steps I'm missing or that should be refined/changed.
Specific Model & OS Information:
Galaxy Note 9 US Unlocked Snapdragon
Model Number: SM-N960UZKAXAA
Model (Settings/About Phone): SM-N960U1
Prior Android 8.1.0 AP/CP N960U1UEU1ARL1
Prior Android 8.1.0 CSC N960U1OYM1ARL1
Current Android 9
Build Number PPR1-180610.011.N9600ZHU1CSB2
Preliminary Questions:
Per this post #171 , is above Build Number Bootloader v1 or v2? Will I be able to install Oreo as outlined below?
Answer: Both Android 8 and Android 9 shown above use Bootloader version 1
Is turning off Software Updates on this Unlocked version SM-N960U1 enough to prevent PIE from being served again?
Answer: No, turning off Software Updates was not enough to stop Pie from coming back.
I had to disable Software update (with a blue icon) (underlying package is com.wssyncmldm)
See steps here to disable Software Update
Downgrade to Oreo Steps:
On PC: Download SamMobile 8.1.0 Firmware 2019-01-13 from https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/
On PC: Download/Install Patched ODIN verB: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
On PC: Download/Install Samsung SmartSwitch: https://www.samsung.com/us/support/owners/app/smart-switch
Connect Phone to PC with USB Cable (allow for USB drivers to install)
On PC: Run SmartSwitch and backup all accounts, settings, files, messages, pictures, videos, etc.
Disconnect Phone from PC
On Phone: Power Down then Remove SIM Card (so it doesn't trigger another PIE Update after installing Oreo?)
On PC: Extract the firmware file downloaded in step #1. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
On Phone: Boot Phone into Download Mode: Power Down; Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode.
Connect Phone to PC with USB Cable:
connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
On PC: Run Patched ODIN vB:
Install Firmware without HOME_CSC!!! (this will wipe it clean) (the "HOME_CSC" causes boot loop problems?)
Add each file to it's respective field in Odin v3.13.1.
Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
BUT NOTE AGAIN: do NOT use the HOME_CSC option as it may/will cause boot loop problems
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
Click the start button, wait for Odin to say 'PASS' in a GREEN box.
Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
On Phone: After installation of Oreo, Enable Developer Mode (Settings/AboutPhone/SoftwareInformation: Click Build Number 4 times until Developer Mode is Enabled)
On Phone: Turn off Software Updates (to prevent PIE from updating automatically again): Settings/DeveloperMode/"Auto Update System"=Disabled
On PC: Run Smart Switch, restore everything EXCEPT settings (i.e. old Pie settings won't translate to Oreo properly)?
[*]Use ADB to disable System Updates: See below "STEPS TO DISABLE SYSTEM UPDATES USING ADB" or post See steps here to disable Software Update
On Phone: Insert SIM Card
STEPS TO DISABLE SYSTEM UPDATES USING ADB:
As mentioned in the other post, there are two System Apps named "Software Update":
1) Software update (with a green icon) (underlying com.sec.android.soagent)
2) Software update (with a blue icon) (underlying com.wssyncmldm)
I only disabled com.wssyncmldm.
I did this on four Note 9 US Unlocked and none have since received the PIE update notice since March 22nd, 2019.
Here are the steps I used:
Installed ADB on Windows 10 Computer: Great Overview Here on ADB
Phone: Settings/DeveloperOptions/USB Debugging: ON
Connect USB Cable (watch for prompts)
Computer: Open a Command Prompt; Type in: c:\adb; adb devices; adb shell
Computer: pm disable-user --user 0 com.wssyncmldm
THAT disables the Second/BLUE "Software Update" (com.wssyncmldm)
Phone: Turn USB Debugging: OFF
Confirm it is Disabled:
Phone: Settings/Apps/Menu/ShowSystemApps,
Scroll Down to Software Updates
Blue should indicate "disabled"
Reboot; Confirm
Click to expand...
Click to collapse
Hi.
This post was very useful.
I have a Galaxy Note 9, Spain, Unlocked, exynos
Model Number: SM-N960F
Updated to Pie,with security update April, and another security update in May.
Following this post I was able to succesfully downgrade to oreo.
In my case, I used non-patched odin (I think is not needed for exynos?)
Downgrade to Android 8.1.0, Spain PHE, N960FXXS2ARL3 was ok
yonokomolomo said:
Hi.
This post was very useful.
I have a Galaxy Note 9, Spain, Unlocked, exynos
Model Number: SM-N960F
Updated to Pie,with security update April, and another security update in May.
Following this post I was able to succesfully downgrade to oreo.
In my case, I used non-patched odin (I think is not needed for exynos?)
Downgrade to Android 8.1.0, Spain PHE, N960FXXS2ARL3 was ok
Click to expand...
Click to collapse
Glad to hear it worked for you!
If any of the steps were confusing, wrong, or could use more info, please let me know and I'll update the original post.
Thanks!
JohnNadeau said:
Glad to hear it worked for you!
If any of the steps were confusing, wrong, or could use more info, please let me know and I'll update the original post.
Thanks!
Click to expand...
Click to collapse
Hi
Apart from odin version, i remember only one change.
step9: On Phone: Boot Phone into Download Mode: Power Down; Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode
This combination of buttons did not work for me.
Instead, I had to press+hold "VolDown+Bixby" and plug the USB cable (connected to the PC) without releasing the buttons.
For the rest of steps, i do not remember any change
yonokomolomo said:
Hi
Apart from odin version, i remember only one change.
step9: On Phone: Boot Phone into Download Mode: Power Down; Press+Hold "VolDown+Bixby+Power" release when first Samsung Logo appears. Follow screen directions to place in Download Mode
This combination of buttons did not work for me.
Instead, I had to press+hold "VolDown+Bixby" and plug the USB cable (connected to the PC) without releasing the buttons.
For the rest of steps, i do not remember any change
Click to expand...
Click to collapse
Hi... thanks for the feedback. I just tested on my phone and it did go into Download Mode without attaching a USB cable . But based upon your input, I edited step #9 in the original post to clarify that the phone first had to be powered down, then Press+Hold etc...
I'm considering buying a Verizon Note 9 SM-N960UZKAXAA (Black 128GB) with Oreo, new or used. What is preventing me, is I need to be able to record both sides of calls, including Wi-Fi calls, as I can now. The phone would become unusable to me if Verizon were to update it to Pie because the update destroys or severely limits that capability. My question is, if I buy the Verizon Note 9 with Oreo, can I perform the steps toward the end of the procedure to prevent it from being upgraded to Pie?
Thanks!