Database Develop

Unbricking "Service Required Code Corrupt"

If you use "xFSTK-SoC-Driver-Setup" and "unbrick.bat" to "Unbrick your phone, and you got the "Service code corrupt" error..., This method is untested but i think it is the problem...​You need This:
Original ICS FIRMWARE that come with your phone.
xFSTK-SoC-Driver-Setup Installed (read How Install "xFSTK-SoC-Driver-Setup")
Unbrick.bat and respective folders.
Motorola Handset USB Drivers (x86 or x64).
ADB/ FASTBOOT or SDK.
Steps to revive:
Extract Unbrick.zip in "C:\atomSOC"
Go to unbrick folder. "C:\atomSOC\unbrick"
Go to your firmware folder and copy this files (dnx; ifwi)
Replace this files in "C:\atomSOC\unbrick".
Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
Run unbrick.bat in "C:\atomSOC"
How Install "xFSTK-SoC-Driver-Setup":
Run Setup
When Say "Intel Soc Is about to begin" Click OK
When Say "In Order to Complete (...) Will a device be attached (...)" Press Yes.
When Say "Step 1 (...)" Plug In your USB Cable to the pc. and click ok
When Say "Step 2 (...)" Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
¿How know if my phone go to the medfield flash method?
release the camera button, your phone will stay in a black screen with the green led.
And your pc says "New hardware recognized"
Name of hardware: MEDFIELD
Before the driver install:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads:
Unbrick.bat + xFSTK-SoC-Driver-Setup Download
If it works.. please, let me know​

Nope.
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen

1994deano said:
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen
Click to expand...
Click to collapse
Try again, your phone is not going to medfield flash mode correctly

I did not get the part - Go to your firmware folder and copy this files (dnx; ifwi)
How to go to firmware folder?,
I do not understand how to copy

i just re tried it and its got rid of the service required screen but now the screen is just black with the green led on

Me too samething, any sugestion?

gmpdri said:
Me too samething, any sugestion?
Click to expand...
Click to collapse
csn you boot to bootloader?? (power+vol.down)?

Nope
pangyaaaaaa said:
csn you boot to bootloader?? (power+vol.down)?
Click to expand...
Click to collapse
no that is why we are trying to use the medfield flash, as the bootloader is screwed up

1994deano said:
no that is why we are trying to use the medfield flash, as the bootloader is screwed up
Click to expand...
Click to collapse
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...

Boss442 said:
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...
Click to expand...
Click to collapse
ooh nice, let us know how you get on with it

S***, REALLY GOOD NEWS.....
RDS recognizes your phone on Medfield Mode...
Someone try to flash a firmware
Flashing Firmware dont work... ¿Maybe a custom XML Work?

HELP
For that ADB / Fastboot or SDK.?
Copying pro firmware?

saiko.sensei said:
For that ADB / Fastboot or SDK.?
Copying pro firmware?
Click to expand...
Click to collapse
if i found a way for bypass the "service required" error.. maybe you need fastboot... I am working with a lenovo pad (Intel SoC) maybe can use his flash tool to work (need fastboot). But dont recognize my phone, ¿Maybe need a custom driver? i am working in that

Yes, RSD lite recognises bricked phones, but it tries to enter fastboot mode to flash anything, so we're stuck...
Good luck!

Bricked while flashing JB Radio to ICS
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.

Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.

mercurio. said:
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.
Click to expand...
Click to collapse
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
SharpnShiny said:
Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.
Is your phone bricked in this condition right now? If it is, feel free to PM me.
Click to expand...
Click to collapse
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.

Boss442 said:
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.
Click to expand...
Click to collapse
I found out that the tool I ment is the xFSTK-Downloader ( rghost.net/44421368 ) that was alreaddy linked here at xda by U1138 in: http://forum.xda-developers.com/showthread.php?t=2184877
And yes, i suppose the black screen only and the service required brick are the same. they probably are due to a not working combination of firmware (ifwi & dnx) and flashed OS (i suppose the fastboot, no idea how where to get the dnx file needed for flashing it). you can try different ifwi and dnx files and get different results (so far i think there are only two types, the ones for JB fw and the others for ICS).
If you flash your rom with RSD going from JB to ICS you also flash the ifwi & dnx files, but not the bootloader. Therefore you end up with a non working combination of firmware (ifwi) and OS (fastboot) => nothing starts at all.
This problem was easy to fix for me flashing the appropriate JB firmware.
Then I did the mistake of flashing the JB radio before flashing a JB rom. This lead to a situation where neither the JB (leads to service required warning) nor the ICS (black screen, green led on) firmware works anymore and I have no idea how i could change the situation.
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?

mercurio. said:
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?
Click to expand...
Click to collapse
+ 1
Everything else I was try with U 1138`s help - without result

St.Noigel said:
+ 1
Everything else I was try with U 1138`s help - without result
Click to expand...
Click to collapse
I read more than 120 pages in forums, and... NOTHING!
But i'm triyng to port a "flash tool" from lenovo pad... :silly:

[FAQ] Frequently Asked Questions For Moto G (2nd Gen) [UPDATED-05/10]

Frequently Asked Questions
Motorola Moto G(2nd Gen)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Hello Guys this is a FAQ for Moto G(2nd Gen). Please read this here before posting it in the developmental section or creating a thread anywhere.
I am sure it will help.
Thank You
A big thanks goes to @matmutant for providing FAQ templates and his own FAQ from I have copied some things.Here is the original guide

[SIZE=+1]Q1: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.​
[SIZE=+1]Q2: How to unlock Bootloader?[/SIZE]Boot to Fastboot and follow my guide
or Motorola guide on Motorola's website​
[SIZE=+1]Q2: How to relock Bootloader?[/SIZE]Boot to Fastboot and give the command "fastboot oem lock"​
[SIZE=+1]Q3: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q4: How to flash Stock Firmware?[/SIZE]Please Follow this Guidehere.​
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide
[/URL]
​
[SIZE=+1]Q6: Where can i find a Custom recovery ?[/SIZE]TWRP 2.7.1.1​
[SIZE=+1]Q7: How to access bootloader?[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
[SIZE=+1]Q8: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
[SIZE=+1]Q9: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q10: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q11: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
For Indian customers, The warranty is void if you unlock/root your device. Motorola also reserves the right to maintain the records of unlocked bootloader devices. So you may not even get the warranty by relocking the device
[source]​
[SIZE=+1]Q12: What to do if my battery is fully discharged and not re-charging?[/SIZE][source]​
[SIZE=+1]Q13: Lost IMEI ? : How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img​
To restore in the event of corruption or loss:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds​(assuming you've pushed pds.img to internal SDcard storage first)
If for some reason this doesn't work, maybe your IMEI isn't destroyed but only not "readable" by system (file system issue? misread cluster reading frame ? no idea), in that case you may read the following story : http://forum.xda-developers.com/showthread.php?p=52648789
​
[SIZE=+1]Q14: How to disable/enable auto On/Off screen with Flip Shell?[/SIZE]
for stock rom : (disabling, since it's enabled by default)
install Xposed framework (and reboot)
install and enable MotoMagnetOff (and reboot)
Follow this FAQ​
[SIZE=+1]Q15: How to remove the 'unlocked warning' message?[/SIZE]Follow this method and default Motorola logo will be back .​
[SIZE=+1]Q16: How to reboot into 'safe mode'?[/SIZE]
Press power button, on the pop up, either keep pressing 'shut down' [stock] or 'reboot' [AOSP based]
more infos about this feature​
[SIZE=+1]Q17: What are the Moto G(2nd Gen) tech specs[/SIZE]
XT1068 (Dual Sim)
[SIZE=+1]Q18: How to get OTA updates even after Rooting and Flashing a custom Recovery[/SIZE]
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before
[SIZE=+1]Q1: How to Unlock Advanced Camera Settings?[/SIZE]
Refer to this thread​

Reserved--- 2

Reserved-----3

Last One

Please post your suggestions, queries and request in the thread

I was about to build an RC-FAQ for this new device ,
but that doesn't matter as long as you follow the RC-FAQs templates properly (like you did for Moto E)
Good luck !
if you need any help, just PM me!
[email protected]

matmutant said:
I was about to build an RC-FAQ for this new device ,
but that doesn't matter as long as you follow the RC-FAQs templates properly (like you did for Moto E)
Good luck !
if you need any help, just PM me!
[email protected]
Click to expand...
Click to collapse
Thank you for allowing me to do so.

Falcon G said:
Thank you for allowing me to do so.
Click to expand...
Click to collapse
Bro i tried to relock the bootloader
I tried "fastboot oem lock" command ,that didnt seem to work,cmd says to begin with "fastboot oem lock begin"
Then i tried again fastboot oem lock, on cmd it says cant relock bootloader sst failure
On phone it says failed to validate system image,whats the problem here ,could anyone explain me thanks

haytham.kenway said:
Bro i tried to relock the bootloader
I tried "fastboot oem lock" command ,that didnt seem to work,cmd says to begin with "fastboot oem lock begin"
Then i tried again fastboot oem lock, on cmd it says cant relock bootloader sst failure
On phone it says failed to validate system image,whats the problem here ,could anyone explain me thanks
Click to expand...
Click to collapse
Hmm I see that you use windows 8, a lot of times it worked when users tried on their windows 7 pc.
And why do you want to lock your bootlader you won't get your warranty back

Can i get latest OTA updates on unlocked bootloader?

haytham.kenway said:
Can i get latest OTA updates on unlocked bootloader?
Click to expand...
Click to collapse
Yes you can

i am willing to purchase the 2nd gen moto g and i want to know which variant is more development-friendly if there is such a thing. i mean what variant is more easily rooted, customized, and will have more custom roms and generally more developer attention? the single sim XT1063 or the dual sim XT1068?

Zheen said:
i am willing to purchase the 2nd gen moto g and i want to know which variant is more development-friendly if there is such a thing. i mean what variant is more easily rooted, customized, and will have more custom roms and generally more developer attention? the single sim XT1063 or the dual sim XT1068?
Click to expand...
Click to collapse
The single sim is actually more easy to build roms for. However the dual sim will be supported in the same way as you can convert the dual sim into a single sim variant.
So buy whichever version that suits you.
I am expecting to receive my single sim variant very soon

iS kERNEL sOURCE IS OUT YET ??

Did anyone notice any lag or freeze while playing 720p videos on the new moto g? Sometimes i see that video freezes and only audio continues to play.
Sent from my XT1068 using XDA Free mobile app

@ srprashant91 : I have been watching 720p video on my XT1068 using MX Player without any lag or stuttering. I have these saved on my 32gb Class 10 Micro SD. Are you streaming the video( wifi/3g), or playing it from internal memory, otg or SD? Also, which app are you using to watch the video? And have you tried using Software and Hardware based decoders if your app has them?

Aileach XDA said:
@ srprashant91 : I have been watching 720p video on my XT1068 using MX Player without any lag or stuttering. I have these saved on my 32gb Class 10 Micro SD. Are you streaming the video( wifi/3g), or playing it from internal memory, otg or SD? Also, which app are you using to watch the video? And have you tried using Software and Hardware based decoders if your app has them?
Click to expand...
Click to collapse
I am trying to play 720p videos via the youtube app using wifi. I notice this stutter, freeze or lag
Sent from my XT1068 using XDA Free mobile app

Global Version On AT&T
I was thinking about picking one of these up to use on AT&T (in the USA/California). The US GSM model is sold out. Will the Global GSM version work? And will it work good? Or will there be complications? Thanks for any help (I have been comparing bands and trying to search - but not really finding any concrete answers).

Another question relating to un-rooting in order to go ahead with the OTA update. Super SU has a built in function to 'Full unroot', can those of us who have rooted use this and then apply the OTA update, then root again after the update?
Is there any need to flash stock firmware just to get the latest OTA? The firmware for GB phones isn't available to download yet (well to date I'm unable to find retgb).

Confirm These Steps to Downgrade US Unlocked SM-N960U1 from Pie to Oreo

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!

Lenovo Smart Clock (Bootloader/AVB unlock, Firmware, Region Changer, Kernel Source)

How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB A cable (Example here)
2. You will need fastboot drivers on your PC
3. Unplug your clock
4. Plug the USB A to A cable into your computer and clock
5. Hold the volume + button and plug in the power cord
6. Keep holding volume + for about 20-30 seconds (It is slow to boot to fastboot)
7. On your computer in a terminal run, fastboot flashing unlock
Part 1 of unlocking is now done
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Normally doing this on an Android Things device is not possible due to their Private key unlock system. But due to a leak, the private key for the Lenovo Smart Clock is available. Word of warning doing this causes the stock android things not to boot only the factory firmware located on Slot A will boot. Consistently if you don't AVB unlock the factory firmware on Slot A doesn't boot If you have already set up your device once the factory firmware is deleted and currently there is not a way to get it back (Hopefully will change soon).
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB Unlock zip
2. Run this command in terminal
Code:
at_auth_unlock.exe cube_unlock_credentials_v2.zip
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command:
Code:
fastboot oem at-lock-vboot!
Downloads:
Stock Shipping fastboot firmware:
Here
AVB Unlock tool:
Here
Factory partition changer (Locale changer):
Here
Google released kernel source:
https://github.com/deadman96385/android_kernel_lenovo_mt8167s
Dump of stock partitions for easy viewing:
https://github.com/deadman96385/things_mt8167s_som_dump
Credit to @deletescape for the leak of the AVB Unlock Key, Stock firmware, region changer

Screenshots of the stock android things on Slot A if you don't setup the device :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP (Coming Soon)

Excited to see what you manage to do with this!

This is great! I have one of these and it felt way too restrictive, looking forward to seeing what comes out of this.

You can also unlock the boot loader simply with what's below... device does boot with this btw
fastboot flashing unlock
Although I've been messing with the device quite a bit. Plug in a usb keyboard, and you can get a web browser to recognize it and go to websites and such using the touch screen as a cursor, but you can't download APK files and install them and such. I've NEVER had the device recognized by ADB, so I can't pass commands from there either.

KaptinBoxxi said:
You can also unlock the boot loader simply with what's below... device does boot with this btw
fastboot flashing unlock
Although I've been messing with the device quite a bit. Plug in a usb keyboard, and you can get a web browser to recognize it and go to websites and such using the touch screen as a cursor, but you can't download APK files and install them and such. I've NEVER had the device recognized by ADB, so I can't pass commands from there either.
Click to expand...
Click to collapse
Just doing step one does not actually get you anything because if you flash something that isn't stock on the verified partitions it will not boot until you flash back the stock one. I have gotten adb to show up but not properly so it is offline. Still hacking away at it trying to get it to go so i can more easily debug TWRP and make edits to the system.

deadman96385 said:
Just doing step one does not actually get you anything because if you flash something that isn't stock on the verified partitions it will not boot until you flash back the stock one. I have gotten adb to show up but not properly so it is offline. Still hacking away at it trying to get it to go so i can more easily debug TWRP and make edits to the system.
Click to expand...
Click to collapse
Ahhhhh got it. I couldn't find anything when I was messing with it like you've found with those commands. I'm kinda new to all this myself at something with nearly zero support, although I have a ton of experience with phones. Had to find my own exploit with my HTC One M7 because the version of android on the phone was the final supported update when I got it, and everyone said "nothing is possible with this android version" as far as rooting... so I figured out my own way lol
I'll continue trying myself though for sure

I also own one of these clocks, so if anyone has anything that I could test out, please share!

I think I'm bit late to party. Anyone who has a backup for those lenovo products, maybe it's a good idea to torrent them.

Honami754 said:
I think I'm bit late to party. Anyone who has a backup for those lenovo products, maybe it's a good idea to torrent them.
Click to expand...
Click to collapse
I don't have the time to test this stuff out for at least a few weeks, but if when I get to it, I'll try to upload my Backups somewhere before I tinker with the system. I'll update this comment when I do.

[/COLOR]
CiriousJoker said:
I don't have the time to test this stuff out for at least a few weeks, but if when I get to it, I'll try to upload my Backups somewhere before I tinker with the system. I'll update this comment when I do.
Click to expand...
Click to collapse
That's not really what I mean... I was referring to some interesting documents from lenovo. Have a few of those hardware but unfortunately didn't grab those files. Anyone also interested in these can PM me maybe we can do something about it.

when will twrp be avable

Interesting as there has a been a few of these turn up to auction of late .
I have gone with the 10' for main room and 8' for bedroom.. love them..
Got the oldies the little 7'
Great for streaming too..

The one I wish it did was announce the time by voice when the internet was down and we said "Hey Google". I am blind without my glasses and often when I am in bed, the internet is down in my area for maintenance period. The clock becomes useless when the internet goes down.

How are people getting the web browser to appear? I'm able to unlock the bootloader but can not boot with the AVB unlocked (well...technically it boots but still shows the spinning circle even though it will let you go to settings). I tried flashing the stock fastboot img and booting with avb unlocked and still get spinning circle. Not trying to get too fancy with this...just want to be able to point to a status page that I can leave it on.

Does anyone try to build a new firmware image and install this instead of stock?
Maybe compiling Android Things from source is possible, but looks like Google has stopped the development. The Lenovo Smart Frame seems to have the same MT8167S and runs on Android 10. Maybe it's possible to compile a LineageOS version?
lenovo.com/us/en/coming-soon/Lenovo-CD-3L501/p/ZZISZSDCD04
Another option might be fuchsia that contains a mt8167s board ref.
fuchsia.googlesource.com/fuchsia/+/master/boards/mt8167s_ref.gni
Googles Coral announced a Dev Board Mini based on MT8167s, maybe they port the Debian-based Mendel Linux to it.
coral.ai/products/dev-board-mini

hugo987 said:
Does anyone try to build a new firmware image and install this instead of stock?
Maybe compiling Android Things from source is possible, but looks like Google has stopped the development. The Lenovo Smart Frame seems to have the same MT8167S and runs on Android 10. Maybe it's possible to compile a LineageOS version?
lenovo.com/us/en/coming-soon/Lenovo-CD-3L501/p/ZZISZSDCD04
Another option might be fuchsia that contains a mt8167s board ref.
fuchsia.googlesource.com/fuchsia/+/master/boards/mt8167s_ref.gni
Googles Coral announced a Dev Board Mini based on MT8167s, maybe they port the Debian-based Mendel Linux to it.
coral.ai/products/dev-board-mini
Click to expand...
Click to collapse
I suppose the smart frame is running android things as well. Compiling android things does make much sense except to prove the drivers are sort of working, this is not designed to let users have fun (ie installing apps).
Google *really* loves mt8167s for some reason. I'd say there's a good chance of we having full android on it but everyone's busy.

They are throwing these things at our head now. 35/40 USD during black fridays.
I don't think you can order the components for that price
Anybody still working on it ? Lenovo claims it's still working on the sound bug - hxxps :// forums.lenovo.com/t5/Lenovo-Smart-Display-Lenovo-Smart-Clock-with-Google-Assistant/Smart-clock-alarm-volume-too-loud-at-first/m-p/5040962?page=4 (latest reply 2020-13-11 from Lenovo) and they did some unanounced pretty good updates in september 2020 - hxxps :// 9to5google.com/2020/09/21/lenovo-smart-clock-night-light/
They also claim the source is on their website hxxps :// smartsupport.lenovo.com/us/en/products/smart/smart-home/smart-clock/za4r/downloads/ds539701
So is this dead ?

deadman96385 said:
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB A cable (Example here)
2. You will need fastboot drivers on your PC
3. Unplug your clock
4. Plug the USB A to A cable into your computer and clock
5. Hold the volume + button and plug in the power cord
6. Keep holding volume + for about 20-30 seconds (It is slow to boot to fastboot)
7. On your computer in a terminal run, fastboot flashing unlock
Part 1 of unlocking is now done
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Normally doing this on an Android Things device is not possible due to their Private key unlock system. But due to a leak, the private key for the Lenovo Smart Clock is available. Word of warning doing this causes the stock android things not to boot only the factory firmware located on Slot A will boot. Consistently if you don't AVB unlock the factory firmware on Slot A doesn't boot If you have already set up your device once the factory firmware is deleted and currently there is not a way to get it back (Hopefully will change soon).
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB Unlock zip
2. Run this command in terminal
Code:
at_auth_unlock.exe cube_unlock_credentials_v2.zip
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command:
Code:
fastboot oem at-lock-vboot!
Locale changer instructions:
Coming soon (Need to figure it out)
Downloads:
Stock Shipping fastboot firmware:
Here
AVB Unlock tool:
Here
Factory partition changer (Locale changer):
Here
Google released kernel source:
https://github.com/deadman96385/android_kernel_lenovo_mt8167s
Dump of stock partitions for easy viewing:
https://github.com/deadman96385/things_mt8167s_som_dump
Credit to @deletescape for the leak of the AVB Unlock Key, Stock firmware, region changer
Click to expand...
Click to collapse
how about smart display ,the same way?

jasonzhang1987 said:
how about smart display ,the same way?
Click to expand...
Click to collapse
We do not have the AVB unlock files for the smart displays sadly.

[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)

Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.​
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -​Just for example - the script would be located in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"​And the firmware files would be in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"​4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P

Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.

Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post

amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.

bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work

Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!

los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"

bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.

Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0

los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.

bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?

los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.

bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.

los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!

bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.

los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.

bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com

los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.

Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!

los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.

.