Guide has been reworked to be more clear and based on comments.
[Part One]
Backup Data
Update phone to latest version
[Part Two]
Download the Firmware for the Zenfone 9 https://www.asus.com/mobile/phones/zenfone/zenfone-9/helpdesk_download/
Download Payload GUI. https://forum.xda-developers.com/attachments/payload-dumper-gui-v2-3-zip.5758127/ (Hermann2306 credit for mentioning)
Extract the Payload Dumper GUI zip file, as well as the UL-ASUS Firmware zip file
Run the Payload Dumper GUI program in the unzipped folder. A file explorer window will pop up; open the unzipped UL-ASUS Firmware folder and select the payload.bin file. Another file explorer window will pop up; select the UL-ASUS Firmware folder if not already selected, then click select folder in the bottom right.
Click Dump on the Payload Dumper GUI Application. The files will be output to the UL-ASUS Firmware folder.
[Part Three]
Download Magisk and install onto phone via APK. https://magiskmanager.com/downloading-magisk-manager/
Plug phone into computer and allow file transfer.
Within the UL-ASUS Firmware folder there will be a boot.img file. Move this file onto the phone.
Open the Magisk application and follow image below, select the boot.img to patch
{
"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"
}
A file will be output with magisk. Move this file back onto the PC, and rename to boot.img
[Part Four]
Unlock Zenfone 9 Bootloader. Asus provides a bootloader unlock tool on their website. Below is the link directly to the apk. https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Install the drivers listed below for the phones recovery mode https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip (Asus Driver Xanker commented. Thank you again)
[Part Five]
Download Minimal ADB and extract files https://androidfilehost.com/?fid=962187416754459552
Move Boot.img file into Minimal ADB extracted folder.
Put Zenfone into recovery mode and connect to PC. Recovery mode can be achieved by turning off the phone and then powering on whilst holding the volume up button. Release when the ASUS logo pops on screen.
Run cmd-here.exe in the Minimal ADB folder; a command window will open
As a test run the command listed below and it should output a device fastboot devices
If that test succeeded run the final command to flash, fastboot flash boot boot.img
The command prompt command didn't run. Said it was not recognized. Is there a specific place the .exe need to be in the directory?
NVM...got it.
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
bighit101 said:
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
Click to expand...
Click to collapse
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
The image version that I just downloaded seems to be at a higher version (WW-32.2030.2030.26 as opposed to WW-32.2004.2004.84 on my phone) and the phone doesn't have that version available (I haven't unlocked the bootloader yet). Should I update locally or download the earlier version of the image instead?
If your phone has the 2004 version installed extract the boot.img from the downloaded 2004 Payload.bin. Or you can update your phone and use the 2030 boot.img.
For me it works with the 2030 version. Root installed, everything ok (AdAway, Postbank (BankingApp)).
If you want to pass SafetyNet just install the magisk module from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1 and reboot.
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Hermann2306 said:
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Click to expand...
Click to collapse
Doesn't work, the guide asks for denying google system apps which doesn't work because they are always off deny list (this is intended behaviour)
For the record, every other payment apps I am using, even the ones that check for safetynet are working. YASNAC returns a both pass basic.
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Hermann2306 said:
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Click to expand...
Click to collapse
Wallet is configurable, it's just that when you save your card details and it starts contacting the bank it would jump to an error saying that the system is modified.
Maybe try this? (I think you have already read/tried it)
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
Does someone rooted a 16GB ram Zenfone 9? My software is 32.2004.2004.74.
Can not find this software at Asus website.
I have rooted the 16gb version (32.2030.2030.26).
Why dont make an update before root?
xanker said:
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
Click to expand...
Click to collapse
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
williamcll said:
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
Click to expand...
Click to collapse
Try this: https://github.com/kdrag0n/safetynet-fix
Veiranx said:
Try this: https://github.com/kdrag0n/safetynet-fix
Click to expand...
Click to collapse
Safetynet fix is running, it's just that it's not enough, still going through the prop fix.
bighit101 said:
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
Click to expand...
Click to collapse
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
xanker said:
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
Click to expand...
Click to collapse
Yeah coffee is life!
You're too nice. Will donate in you're name.
Thanks man!!!
Related
This is my first attempt at creating something for users on xda, so be gentle .
Eternityproject has released a fine script for rooting our Motorola RAZR phones on the 4.0.4 update. As a windows-user that used to use batch scripts for everything I could not help but want some more output than just the [rebooting] echo's that the script print on the screen. As a bonus I thought it would be nice to see how long the script will take before my phone is rooted. I have made these wishes into an application, and pedrotorresfilho kindly allowed me to use their script in my application.
So what does it do?
It roots your Motorola RAZR and shows you what the script originally did. It also calculates how long your phone takes to reboot, and shows you how much time you have to get a nice cup of [insert drink here]. Or soda if you prefer that. In theory it is possible to root multiple phones at the same time, which saves time if you have to root 10 RAZRs at once (LOL... as if).
How does one use it?
- Install the program using Microsoft's Awesome ClickOnce distibution system
- Install the Motorola Drivers (Download MotoHelper from here)
- Enable 'Unknown Sources' (on your phone: go to settings, go to security, tick the box next to 'Unknown Sources') (needed to install supersu.apk)
- Enable 'USB Debugging' (on your phone: go to settings, go to developer options, tick the box next to USB Debugging) (needed to communicate with your phone over USB)
- When connecting your phone, please set the USB Mode to 'Media Sync - MTP', to be sure that mounting points won't interfere with the rooting process.
When the application is opened all the connected Android devices will be selected. This means that as soon as you press the 'Root' button, they will be rooted.
In principle the application does nothing more or less than the script. You don't have to have extensive knowledge of adb or android internals, it's just an app that shows the connected devices and a root button . If you are already rooted, it's easy to unroot using SuperSU.
{
"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"
}
Download links:
Open ClickOnce Application (works only if you have .NET 4.0 installed!)
Download page (use this if the above link does not work/you do not have .NET 4.0)
You can update by opening the application. If there is an update, you will be prompted to download the latest version.
Required:
Windows (with .NET Framework 4.0 Client Profile installed)
Motorola RAZR running ICS (other phones might work, but you will get a warning)
I ask all of you kindly NOT to mirror or reshare the application without my permission. Please share the ClickOnce Application link. Is assures that you are running the latest version!
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
miloj - For finding the exploit binary to root the phone
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Chainfire - For creating and providing SuperSu and his su binary - http://forum.xda-developers.com/showthread.php?t=1538053
Changelog:
1.0.0.6:
Added more strings to the logging output
Fixed the blocking of the root button if there are no devices selected
Added a splash screen to indicate that the application is actually loading
Changed the location where the splash as well as the credits/welcome screen appear
1.0.0.5:
added credits for Chainfires SuperSU and su
Removed the message that rooting was not successful
Added a few more messages about the script itself (in the script output)
Updated SuperSU and binary to 0.94 (su binary still says it needs to be updated )
1.0.0.4:
The application now properly disposes of the AndroidLib instance, disabled the CheckedItem event on the DeviceList because it was a tad buggy. This won't harm anyone.
1.0.0.3:
Enabled Microsoft ClickOnce Update deployment. If I fix a bug, you are able to update to a less buggy version
DJFliX said:
This is my first attempt at creating something for users on xda, so be gentle .
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
minoj - For finding/creating the exploit binary to root the phone (please correct me if this is not correct)
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Click to expand...
Click to collapse
+1 congratulations for this work
thanks
My Razr is already rooted, but I can test.
nespresso33 said:
My Razr is already rooted, but I can test.
Click to expand...
Click to collapse
I have sent you a dm .
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
whirleyes said:
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
Click to expand...
Click to collapse
Hmm... I will have a look at this. What are your reasons for using this except that it's simple? It's just a matter of preference, right?
pedrotorresfilho said:
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
Click to expand...
Click to collapse
Thanks man! Much appreciated!
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
Yeah, the installer should be extra user friendly. I should probably just advice users to use the .application link. But the link will only work if .NET client profile is already installed. I'll adjust the message about root, It seems that the library that I use does not query root status from the phone, but rather from it's cache. Maybe I have to update the phone data before querying for root. Thanks for your feedback!
Edit: I am now uploading version 1.0.0.5, I added credits for Chainfires SuperSU, removed the message about the rooting. Too bad my connection is bad (3G in the mountains in La Palma) so bear with me while the updated version is uploaded. Should be up within about 10 minutes, users that already have the application installed will asked to update to the latest version.
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
pedrotorresfilho said:
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
Click to expand...
Click to collapse
The refresh button is the button next to root . I'll put a tooltip on that button. Glad to hear all is fine. I'm uploading 1.0.0.5 to polish out the small annoyances and update SuperSU. Thank you so much for testing .
Edit: 1.0.0.5 is out . The download link is now public. Please leave suggestions and improvements in this topic or send me a DM. Thanks!
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro.
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Example screenshot:
jwoegerbauer said:
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
Click to expand...
Click to collapse
I tried to flash a custom script that use the
Code:
u_print()
function , but the signature verification fails i get an
Code:
errorr:21
jwoegerbauer said:
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro[/url].
Click to expand...
Click to collapse
Are you sure that I can flash an unsigned zip like superSu , with a stock recovery and locked bootloader ?
jwoegerbauer said:
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Click to expand...
Click to collapse
The TWRP is an open source project , all the source code is avaiable. But to have it works , you need the original kernel .
I tought , If I can unlock the bootloader I can read the image of the recvoery.img and from it extarct the kernel
Thanks for your answer.
@ element14
did you manage to make the device usebale?
Hello, i am also interested to reset\flash this device but I couldn't find any useful guide, did you manage to root it or flash it, I want to use it as android STB.
As long as you can establish an USB-connection ( read: ADB connection ) then you can root any device's Android OS, otherwise NOT.
Any updates on this topic? It would be great to know if someone was able to root it.
If this is the etisalat version of this box I have gotten APKs to work on it.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
What apk exactly?what you can do with this apk? And how you installed?
element14 said:
What apk exactly?what you can do with this apk? And how you installed?
Click to expand...
Click to collapse
I think it lets you install any APK on the device. Check https://emiratestel.github.io/website
There is only one port. Is there any other way? And how can i play videos from usb
xilogofficial said:
I think it lets you install any APK on the device. My method:
Going to apps list:
- insert usb
- click browse
- go up to internal storage, press ok, click Apps
part 1
- go to apps list, keep usb inserted
- scroll to Files, click it, click open
- if it opens skip to part 2
- else it will crash and show the first time boot
- go to apps list again while keeping usb inserted
- open files again
part 2
- connect a mouse to other USB port, navigate into the USB and into where you placed your APKs
- double click the apk to install it
- on first time install, it will show an error about unknown sources
- click settings on the prompt
- enable all sources shown
- continue installing the app
Click to expand...
Click to collapse
There is only one usb port. Is there any other way? And how can i play videos from usb
there's another on the bottom, or use a USB hub.
you can't play videos from USB without installing third party apps.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
Good Day! Appreciate your support . Dear Exactly Etisalat TV box model: DWI259S, but it is locked on Etisalat home page with their logo as I don't have Etisalat subscription any more, in that situation how possible to browse an APK file as you said in below steps? 2nd thing there is no standard Firmware available by Manufacturer (Technicolor), Please make a video or at least solve with help of photos and help us close this topic. Till date solution is not yet provided, Please help, Thanks and appreciate your support
.
element14 said:
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
Click to expand...
Click to collapse
Any Luck dear, Please advise as I want the same solution and receive same error 21.
engr.sys said:
Any Luck dear, Please advise as I want the same solution and receive same error 21.
Click to expand...
Click to collapse
Kindly Join our Discord Server Link :https://discord.gg/sbFnauNTWy
I can help u there
Hi
Can you please share the APK please ?
any update on this? did anyone managed to finally root this device or least sideload and apk?
b1acktiger said:
Hi
Can you please share the APK please ?
Click to expand...
Click to collapse
PM Me
Can you please share the APK please ?
Since there is no proper information about unlocking the bootloader for the newer versions of Oneplus Nord 2, this is how I got it to unlock and actually work.
For my system it did reset the device, clearing all the files and factory restoring the device, just make sure to make a backup before you do anything.
Just like any other post, no warranties or anything, this is all at your own risk.
1: Make sure to enable OEM unlocking and ADB Debugging in the developer options
1.1: To have these options, first go to About phone > Version
1.2: Keep tapping the "Build number" to unlock the developer options
1.3: Navigate back to settings and open Additional Settings. There you will find the Developer Options.
2: Install: Platform tools: https://androidfilehost.com/?fid=17248734326145690420
3: Install: MediaTek Preloader USB VCOM drivers: https://drive.google.com/file/d/1TPbW-v9-yOrzH15OaHmsPQad420mULeF/view
4: CMD to the root of the platform tools and use the command "adb reboot bootloader"
5: While in the weird tiny screen, validate that your device is there by typing "fastboot devices"
6: If so, type fastboot flashing unlock
7: Profit.
Hope this helps any other people searching for a proper way to do this.
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
meterpreter said:
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
Click to expand...
Click to collapse
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Eastw1ng said:
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Click to expand...
Click to collapse
I hope so too. I would really like to put lineage on this thing, probably the only os that can make a usable device out of this actually very good phone
Unlocking the bootloader requires two settings to be made in Android's Developer Options:
ADB Debugging
Allow OEM Unlock
@Eastw1ng, as obvious as this may be once you remember, unlocking the bootloader is something most people don't do very often - it might make sense to include that in the OP
@NetSoerfer, you're not wrong, quickly added it to the start.
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
CapnRene said:
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
Click to expand...
Click to collapse
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
HofaTheRipper said:
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
CapnRene said:
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
Click to expand...
Click to collapse
Can you tell me how to install these drivers I tried but still not detecting
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
X:\Users\XXX>where adb
X:\platform-tools\adb.exe
And system variables
{
"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"
}
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
pankspoo said:
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
Click to expand...
Click to collapse
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
pankspoo said:
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
Click to expand...
Click to collapse
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Eastw1ng said:
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
Click to expand...
Click to collapse
Yes installed
Eastw1ng said:
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Click to expand...
Click to collapse
V10 bootloader means boot.img? If you have that please send me
pankspoo said:
V10 bootloader means boot.img? If you have that please send me
Click to expand...
Click to collapse
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
pankspoo said:
Yes installed
Click to expand...
Click to collapse
Alright, well just put it into fastboot mode and check your device manager, does it show any devices that are not properly installed? If so, try to resolve it from there
Eastw1ng said:
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
Click to expand...
Click to collapse
Thanks
I am perfom this Sorry for my english, I am from Ukraine
Download archive!
We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer.
In the smart, turn on the developers menu, in it - "Allow OEM unlock" and "USB debugging" and connect the smart to the computer.
We drop valuable photo data from the smart to the computer for any, and, without disconnecting the smart from the PC, run the script (with the phone connected to the PC and loaded into the android phone. Reboot_to_fastboot_getvar current-slot.bat (not from the admin, just click twice).
Smart will look like this:
{
"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"
}
we allow - put a daw, ok. We are waiting for the smart to reboot into fastboot, when the barcode appears on the smart screen, before that we do not press anything in the script
I did the scripts step by step, after each operation in the script window, press enter to continue, and so on until each script is closed
We look at our current slot in the window and remember the letter - a or b:
In the script, press enter so that the smart reboots and the script closes.
Run flash_tool.exe, go to this tab and check the boxes, as in the screenshot:
So we consider the necessary versions of orig. files, so as not to download and sew a specific firmware version for this instruction.
(And best of all, all the checkboxes, except for system, vendor, userdata - they are not critical, if they are not removed, it will take up a lot of space on the computer up to +74 gb, but I did not put these checkboxes, there must be some risk and passion )
We press "Read Back" and only then we connect the switched off smart to the PC, we wait, at the end we disconnect the bodies, do not touch it: sveta:
Go to this tab, remove all checkboxes! And we only put on lk_ with the letter of a non-your slot that we looked at, for example, you had slot "a" - so we put a check on lk_b and vice versa :
Click "Download" and connect the switched off smart to the PC (it was already turned off: sveta
As it flashes, we close the USB flash drive window, disconnect and turn on the smart, after loading, we connect it to the PC again, we already run the script
Unlock_Moto_E6S.bat, wait until the body reboots into a fastboot (to the barcode on the screen) and only then press the input step by step to continue in the script until it is completely closed.
Everything, the bodies are unlocked. Now you can get an excellent and fast root from Magisk, try other firmware, unsubscribe which one is buggy, which one flies. I haven't tried yet. Now I will write how to flash orig. kernel with magisk root (attached magisk boot for xt2053-1 4/64 fw RETEU 288-60-6-29 https://mirrors.lolinet.com/firmware/moto/fiji/official/RETEU/
Additionally, there is a script in the folder to delete the message when loading that the bootloader is unlocked, it does not interfere much, but I deleted it. Since this is not important, I separated it from the main script, since I did not test it on different versions of the firmware, in theory it should work on all versions, you can try after unlock. Or throw off ROM_45 from your firmware, I'll remove it from it. I now have the latest firmware flashed, it is on the server, but for some reason it did not fly through the air. If you flash it, then you can safely delete the message from the bootloader with my script, there is a file from it)
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
severagent007 said:
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
Click to expand...
Click to collapse
dude!! followed all your steps and i now have a bootloader unlocked and rooted device. how did you figure out the lk and signature to unlock that??
proof attached below
Слава Украине!!!
can the mods move this to the moto e6s forum so we can spread the news?
luridphantom said:
can the mods move this to the moto e6s forum so we can spread the news?
Click to expand...
Click to collapse
I took the first firmware I got to try from here: https://4pda.to/forum/index.php?showtopic=892755
but the firmware itself is everywhere, for example here:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
DeveloperLuke Roms - Browse /GSIs at SourceForge.net
sourceforge.net
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You can try to sew any GSI arm64 a/b from anywhere you find and choose the one you like, because smart supports Project Treble.
If you like one and will look cool and work firmware, post links here!
Tested it and it worked! Thanks a lot!
Now looking for delevoping some roms to this device
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
refrigerador67 said:
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
Click to expand...
Click to collapse
did you use the auth file that comes with sp flash tool? without that your device wont boot properly
Yes, i used the correct download agent and auth file
interesting, i followed all his steps and had no problem rooting it. try backtracking with his scripts again?
Solved it, also me and a developer are working on a new, more simple and automated script. Still haven't figured out how to flash the lk via script.
When is done i will post a complete guide in the moto e6s forums on how to do it, i think it might work well, but i would have to test in a non-unlocked device
Can someone please make a video with explanation, I didn't understand very well what is done, so I won't touch anything, but I thank those who record a video explaining it to me (I'm Brazilian)
Here you have a more straight forward guide, note that is still in testing
[GUIDE] How to unlock bootloader on E6s
Hello, in this guide i will show you how to unlock the bootloader on Moto E6s ;) (Sadly for now this guide is Windows only) CAUTION You are doing this AT YOUR OWN RISK! I will NOT take responsibility if you brick your device! Also, remember to...
forum.xda-developers.com
Excuse my ignorance, do you think it is compatible for the XT2053-5 model?
cannot use fastboot flash boot magiskboot.img
sign failed
partition flash is not allowed
hey is the moto e6+ twrp work on e6s