Related
Hi guys,
This is all about developing the Focus S, since we are on our own on this one I thought id start the ball moving but it would be great if others can help, my first target is to try and download as much of the device as possible
Can I promise anything at all? nope
Have I achieved anything yet? well id say 1 step above doing nothing at all, if you can call that progress then yes, there is progress
Is it even possible to do anything? i dunno
Could i brick my device? possibly, i honestly don't know
in short, this is me blindly wondering in the dark with absolutely no direction what so ever!
So what have i done, well, i managed to get the Focus S talking to Qualcomms diagnostic utility, QPST and RevSkills CDMA Workshop
I cant get QXDM to install on Win 8 x64 and im not sure we need that one anyway
it is possible to edit stuff on the phone at a very low level, NOT OS level, it should be possible to download the various images on the phone, but ive yet to have any luck with that, it keeps coming up with "Arm9 fatal error"
ive been able to download and backup various phone settings but this is still outside of the OS#
I can play about with the EFS but there are several folders that i cant get in to yet
So far,both the samsung download mode and the ARM9 (?) download mode IS visible and installes as a com port, but there is no response on that port, i can only get a response within windows when i enable USB diag mode....
i decided not to link to the various tools ive mentioned here, i dont know the legalities of it all so use google, they are all easy to find.
Samsung studio 3 drivers
http://downloadcenter.samsung.com/c...813082717640_Samsung_USB_Driver_Installer.exe
Install it with compability for windows vista.
Samsung Focus info (note that most of this doesn't work, its for the older focus but some does)
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
Handy Diagnostic codes
*#7284# - USB Path control (select to change how your phone communicates with your computer)
*#197328640# - The Root Menu (seriously, don't get too cocky, you could bugger up your device)
Samsung USB Download mode
Turn off Device
hold the camera button and the Volume UP
Whilst holding those two push and hold the power button until it vibrates
Samsung Device Hard reset
Turn off Device
hold the camera button and the Volume Down
Whilst holding those two push and hold the power button until it vibrates
Follow on screen instructions
Enable Diagnostic mode and Connect to QPST or other GSM/CDMA software
Download and install the Samsung drivers above
open the diagnostic app and dial code *#7284#
Select Modem,USB Diag
Reboot
When you plug the phone in you should see a COM port install and appear in device manager
load QPST configuration
Click on the Ports Tab then Click add new port
Select your Phone com port
Click OK then select the phone from the list, hit enable
Click on start clients then you can play with a bunch of options
Please note that this is a serious piece of kit, its designed for low level editing, what I mean by that is that it couldn't care less about if it works or not after you finish playing, a couple of other software options to play with are CDMA tools and RevTools both have the potential to paperweight your phone!
NOTE: Zune will not connect and whilst connected to PC you may lose all GSM connectivity whilst connected as well.
Enable FTM (Factory Test Mode)
open Diagnostic app and dial code*#197328640#
select 6 (common)
Select 1 (FTM)
Select 1 (on)
Click return save (it doesn't always persist unless you do)
Hit Back until you back to the main menu then win key to Windows
REBOOT to enable
NOTE: You will lose ability to connect to GSM with this enabled, a reboot is required to enable it after its set and to deactivate it, ive not found a noticeable difference with this on
If im not wrong, WP uses arm v7.
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
tayfelix said:
If im not wrong, WP uses arm v7.
Click to expand...
Click to collapse
yes your right, but that's what it says, it reboots in to some sort of QC download mode, QPST is the waiting for it to talk to it which it doesn't do, it just sits there with this error message.
I have been able to backup the Important bits that make the phone work, and I have access to the EFS, I can change all sorts at a very low level but any time I try and download some of the various "partitions" it reboots to this special download mode. because we don't have any form of ROM I thought the first priority should be to see if we can make a backup of it, outside of MS encrypted zune backup I mean
the software is old so perhaps it doenst work with newer hardware, but then it does with android soooo.....
LudoGris said:
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
Click to expand...
Click to collapse
don't hold your breath, I still don't really know what im doing, consider this playing.....in a mine field
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
tayfelix said:
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
Click to expand...
Click to collapse
That depends what you mean by work, will the focus flash connect to various diagnostic tools? yes probably, will it be possible to download the ROM? maybe, beyond that I haven't got a clue
starting to run out of ideas, I think either the download mode via QPST is disabled or, and more likely, the driver isn't correct, when it enters the arm9 fatal error screen it is still using same driver, the same driver samsungs download mode uses, but both won't talk to QPST unless I enable diagnostic mode within windows phone OS, the prob with that is that it won't then allow access to the file systemSent from my fake Lumia 900 using XDA Windows Phone 7 App
It also have diagnostic tools .
tayfelix said:
It also have diagnostic tools .
Click to expand...
Click to collapse
be careful, you can bugger up your device!i will write a more detailed guide later
First things first, you will need to make sure you have the samsung diagnostic tool install
bring up the phone dialer and dial
##634#
you will now see a diagnostic app on your app list, run it and type in
*#7284#that will enable you to change the USB connection mode,select
Modem USB diag
OPTIONAL - Typing in the following code will bring up the diagnostic root menu
#197328640#you can find a full list Here Many of the codes on that list just run functions found in the root menu
Bare in mind that pissing around with some of the things in there will bring about a swift crappy end to your day!
plugging in your your phone at this point will install a Samsung COM driver
next download and install QPST on your computer, run the config part of that, it will ask you to select your phone, you will need to add a com port, it should then list your phone to connect to it
you can then edit the EFS, service/phone settings, download settings
you will need to know your SPC number, mine was already 0000000, there are ways of working out your number if leaving it all at zeros doesnt work.
use the service editor to read the phone settings, it will ask for your SPC, once loaded,you can save those settings to a file, very important ifyou screw something up
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
tayfelix said:
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
Click to expand...
Click to collapse
as reported in windows phone about screen, note that the Focus S and Omnia 7, has a firmware update that will stop any interop unlocking, i had it installed but it killed my battery life and my phone reception so i took it off, id suspect the bootldt vs will be different between devices, even though they were released at the same time
bootldr 6.5.16.0
firmware 2103.11.10.1 (not the Samsung update that breaks interop)
diagnostic 0923 (not the Samsung update that breaks interop)
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
tayfelix said:
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
Click to expand...
Click to collapse
I made a backup before I installed it
I think we can get an xap of my version of the diagnostic tools, but the firmware update also changes drivers an a few other things, those cant be changed, if we could send custom cabs to the device we are laughing, but we cant, to cab send requires the cab to be signed, and the device would need to have that certificate, which cant be put on whilst its all in use
:S don't think so as diagnostic tool is based on firmware I think.
tayfelix said:
:S don't think so as diagnostic tool is based on firmware I think.
Click to expand...
Click to collapse
try this, remove your existing diagnostic app and install this xap
How can u install a xap..
Is your device still unlocked? The Samsung update will stop you applying the unlock but if you had it already installed it will still work, if it is unlocked then use an cap deployed, my link to the wee guide details how to do it, if it's interop unlocked but you can't install an xap deplorer the use the xap deplorer included with the WP SDK
Sent from my Lumia 900 using XDA Windows Phone 7 App
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
tayfelix said:
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
Click to expand...
Click to collapse
well there isn't anyone working on unlocking it as far as I know, so if its going to happen then we need to do it ourselves.
Ive exhausted just about every avenue I can think of getting access to the device, ive been able to dump parts of the RAM but still not the ROM,
EFS is writable but I cant get in to the secure folders. The only way I can think of for getting the ROM is to get it working in one of the two download modes, both will not talk to anything tho, perhaps if I had the commands to copy the ROM I could just send them in the hope it will reply but it sure as hell isn't saying anything to the commands I have sent.
Hmmm. Must there be a exploit? Zzz there's are very little/no hackers having a focus s or a focus flash/omnia w. they all have 1st gen devices I think.
Hello,
I had some problem while enabling the FS full access with my Samsung ATIV S (OS version 8.0.10211.204).
Here are the steps I followed:
1 - first dev unlock and then interop unlock the device
2- I installed the SamWP8 Tools and I turned on the Full FS access
3 - I followed the suggestions that can be found on the various forum's threads but still I can't get access to the phone's disk (the disk seems to be empty)
Just a side note: I'm working with a Windows 7 OS and I'm virtualizing a Windows 8.1 pro + WP8 SDK - this should be a problem, since I can sideload xaps without any error.
Can someone please assist me with the solution of the issue?
Thanks in advance.
Sandro.
** Update ** I solved the issue by upgrading the OS from GDR1 to GDR2, following @MauzaoFilho and @Randοm Hero's suggetions - the device first downloads and installs the GDR2 than, if you want, it will allows the uprade to the GDR3. Thanks for the help.
Try to update your system to version GDR2, I think this is a problem of incompatibility between the interop unlock with the GDR1 and FS.
Are you running software on the PC that interacts with the phone (eg windows media player syncs, etc.)? If yes, turn that program off.
Randοm Hero said:
Are you running software on the PC that interacts with the phone (eg windows media player syncs, etc.)? If yes, turn that program off.
Click to expand...
Click to collapse
No, everything is turned off.
My problem now is: can I directly update my device to GDR3 - now I have GDR1 - while preventing the interop-unlock ?
Thanks
sandro1900 said:
No, everything is turned off.
My problem now is: can I directly update my device to GDR3 - now I have GDR1 - while preventing the interop-unlock ?
Thanks
Click to expand...
Click to collapse
I think first you have to update to GDR2, then GDR3 (someone confirm this, please). If you Interop-unlock GDR2, then yes, you can indeed prevent your phone from unlocking, using the SamWP8 Tools & following the instructions in this thread
Hi everyone. It has been a very frustrating experience with this mode.l I am trying to root the
Rooting At&t Asus Memo Pad 7 LTE (ME375CL). I have tried of provided solutions, one on this forum. even looked at YT vids and nothing worked. I would certainly love input from someone who either has the same model or is familiar with that model. I even tried Zenfone root but it does not work for that particularity built. Desperately need help in rooting this one. Its a tough nut to crack. Need the special forces of techies on this one.
XavT
If it has lollipop there is currently no active root method.
johnkirchner said:
If it has lollipop there is currently no active root method.
Click to expand...
Click to collapse
its kitkat 4.4
here ya go
Download this file first to your PC- www-filedropper-com/attasusmemopadlteroot replace the dashes with periods
[Almost] Stupid proof directions for Windows users:
1) Turn on device and wait for it to be on the "desktop" / main area.
1a) Plug in device into computer. WAIT UNTIL IT IS DONE INSTALLING THE DRIVERS BEFORE CONTINUING.
2) After you get that green check mark for the driver installation, extract the file you just downloaded (this is referring to the original poster's zip file link).
3) Run "CheckBeforeAction.bat" on Admin mode (Right click, run as administrator; this file can be found in the FOLDER of the zip file you downloaded earlier.)
3a) Follow prompts on the window that opens.
3b) If you follow the prompts, it should have restarted your device and you should be in a black screen with some minor text (aka Fastboot).
*** WARNING: IF YOU ARE STILL ON THE DESKTOP, YOU WERE IMPATIENT LIKE ME, AND DID NOT WAIT FOR THE DRIVERS TO INSTALL. ***
4) Once in Fastboot / black screen with text only, run "Root.bat"
5) It should complete successfully.
6) Restart device and you're all set.
ok thanks I will try it and see
Can I use the at&t model outside USA and without a sim card?
You should be able to, it would obviously be WiFi only.
johnkirchner said:
You should be able to, it would obviously be WiFi only.
Click to expand...
Click to collapse
Hi I need help rooting my asus memo pad 7 LTE from AT&T I tried the steps but nothing I'm on android 4.4.4
can you send me the link
I've been trying to root my tablet, does anyone have the link so I can download it and root my tablet. I'd appreciate the help
dose any way to root (asus k00r) me572cl android 5.0.1 ?
Solved,
http://4pda[dot]ru/forum/index.php?showtopic=640814&st=3420#entry53047686
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
I recently have been purchased the LTE version of this device. Although I cannot try this out currently, I probably will in the future so please keep us updated about your experiments for reference!
avkjbl5bak said:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
Click to expand...
Click to collapse
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
howgies said:
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
Click to expand...
Click to collapse
I have my Mediapad M3 Lite rooted by magisk.
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
I download and installed latest magisk app.
I opened the magic app-> install -> install -> patch the boot image file which I then flashed through fastboot.
I then opened magisk -> install -> Direct install.
Everything works but like me you take a risk in not using the exact boot.img.
I tried and installed TWRP which worked but the volume keys would let me run the script I was trying to rebrand the phone. In the end it isn't necessary to root the phone.
sd26 said:
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
Click to expand...
Click to collapse
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
nicolap8 said:
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
Click to expand...
Click to collapse
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
sd26 said:
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
Click to expand...
Click to collapse
if my reply is too poor, report it to mods...
A post like your IS an advice because people read and follow it. What is wrong is not that you write or my opinion but people behaviour
I read the "risk" word but a lot of people would not. This is also the reason I don't wrote the dd command: search and learn! Most of the messages you read here are of people who have broken their own terminal because just followed a post like your, without knowing what are doing.
N
sd26 said:
Everything works but like me you take a risk in not using the exact boot.img.
Click to expand...
Click to collapse
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
#marcg# said:
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
Click to expand...
Click to collapse
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I have
avkjbl5bak said:
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
Click to expand...
Click to collapse
Did you ever get and answer to your question about cloning or getting the original factory images. I've been trying on and off for 9months. I have unlocked the bootloader and backed up using TWRP (from the 10inch model), but when I relocked the bootloader everything fell apart... unstable boot loops, etc. not sure if I had to wipe recovery I burned with TWRP or what. Also TWRP does not back-up the data partition I think due to encryption (from other posts I read). My goal was to rebrand a pile of the Chinese version tablets I have to US because we use them in our product, and the US are not available, so rebranding would give me more time before to find a replacement. Any clues would help!!!
sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I successfully rooted my CPN-L09 without loosing fp sensor, have a look here: https://forum.xda-developers.com/mediapad-m3/help/to-patch-boot-img-magisk-v17-3-t3938629
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
bigprat9 said:
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
Click to expand...
Click to collapse
You have to use the calculator in landscape mode (turn on auto-rotate) and then the bracket buttons will appear.
So I finally got around to installing this on my stock version. I found 16GB was too limiting and I was hoping to use the SD card to expand the space so I could use it for a few more years. I purchased the code from DC_unlocker.
A couple of things I noticed while following the guide. To enter fastboot mode, holding down the volume down and power button doesn't seem to work. What you to do is while it's off, hold down the volume down button and plug in the microusb cable, while continuing to hold it down. You could also enter fastboot using an ADB command.
Also I couldn't wipe anything before installing the new roms, I got error messages. I'm not sure what that means. Anyways after installing android 9, it seemed to take a very long time to first boot. The graphic animation is going, but I wasn't sure if it was working so I hard reset once, tried to boot again and then waited again, hard reset again and put it down thinking I would have to look into the error messages and when I came back it was up and running.
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
lawhec said:
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
Click to expand...
Click to collapse
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
surdu_petru said:
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
Click to expand...
Click to collapse
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
lawhec said:
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
Click to expand...
Click to collapse
Thank you very much too
Hello
I followed the steps here to unlock the bootloader with my btv-dl09, that worked fine even its not lite.. :fingers-crossed:
but now, any clues? may i ll try the way of lawhec with
lawhec said:
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
Click to expand...
Click to collapse
but cant find the TWRP 3.3.1-1?
may u Mean
[Recovery][Official] TWRP 3.3.1-10 [G97*0][Snap][3.Jan.20]
[Recovery][Official] TWRP 3.3.1-12 Snapdragon [N97x0][10.Nov.19]
[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J6+/J610F/FN/G/DS
???
if so, why u choose one of these? No Clue for me^^ plz let me know
greetz
ADD: just found
Developed By :letschky
twrp-3.1.1-1-next.img
Jul 13, 2017 | 03:32PM
maybe these? looks pretty old but still working? Oo
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!