THIS THREAD IS NO LONGER UNDER DEVELOPMENT, FOR FUTURE UPDATES PLEASE HEAD HERE.
Flashing TWRP and Rooting the Asus Zenpad 10 (Z300M)
CREDIT: Diplomatic, JustShaun, and Flukester69 all made this possible. But really if anybody needs an applause, it's Diplomatic. If you wish to thank him you can do so here.
IMPORTANT! READ BEFORE CONTINUING!
Nobody here is responsible if you mess up your tablet! This is your decision and yours alone! Yes, this will void your Warranty! The below is based on the success of our own testing. We suggest reading this multiple times if necessary, before attempting. Ask questions if you are unsure, I'm sure someone will try and help.
Things you'll need:
- Windows computer / possibly Linux if you are savvy enough.
- Z300m with Android 7 (check if there's updates, if so, reboot tablet when done.)
- USB Cable (the one that came with it, or one you are sure works)
- MediaTek VCOM Preloader Drivers (I will explain further below) (Win10 installed drivers work too)
- Z300m Scatter File
- TWRP 3.1.1 image
- SP Flash Tool 5.1532
- SP Flash Tool 5.1548 or later (latest is 5.1720 at the time of this writing)
- Magisk Manager (Beta 13 works)
or
- TWRP 3.1.1 Recoveryasboot
Create a temp folder on your desktop and throw all the above downloads in there.
MTK Driver Install - Pre-Flashing Procedure:
Turn your tablet OFF and plug it in to your computer, Windows should recognize the device and download the drivers. You should be able to manually search through device manager (Turn on Hidden devices might be necessary). When the drivers have been downloaded feel free to unplug the tablet again.
You'll want to make sure the drivers are installed properly. A quick way to test,
Open Device Manager by either searching for it or running 'devmgmt.msc'
Turn on hidden devices.
Expand the 'Ports (COM & LPT) section
If the drivers are installed properly you should see 'MediaTek PreLoader USB VCOM Port (COM*)'
Good enough, if that worked. If not, check your device manager and figure out your driver issue.
Backing Up:
Open the SPFL (latest) dir and open option.ini in any text editor, you'll want to change "[ReadBack] ShowByScatter=false" from false to true and save your changes.
Load into flash_tool.exe.
Change the download-agent from MTK_AllInOne_DA.bin to DA_PL.bin - This is located under the SPFL dir.
Add the Scatter-loading file which should have been downloaded previously.
Head into the Readback tab and you should see 'Preloader, pgpt, proinfo ect...'. Check all of these boxes and click Read Back
Make sure the tablet is turned off and then plug it into your computer. Bar goes red, yellow and then done. Green Checkmark.
It's safe to unplug the USB from the tablet now and you can close the Flash Tool
Flashing TWRP:
It's up to you to backup your tablet. You should, but the tablet technically should reset if anything fails. Another choice that is up to you alone.
Again, Make sure your tablet is powered off and NO USB plugged in. This is basically the same procedure as backing up, except you're using the Download tab instead of Readback.
Extract SP-Flash-Tool-v5.1532.00 and Launch flash_tool.exe.
Change the download-agent from MTK_AllInOne_DA.bin to DA_PL.bin - This is located under the SP-Flash-Tool-v5.1532.00 dir.
Add the Scatter-loading file which should have been downloaded previously.
Look down the list you see Recovery line, click on the right side, point it to the TWRP.img you downloaded. (Make sure this line is only checked.)
Click the Download button and THEN plug in the USB cable to your tablet. Bar goes red, yellow and then done. Green Checkmark.
It's safe to unplug the USB from the tablet now and you can close the Flash Tool
Alternative method that does not require SP Flash Tool, scatter file, etc.
Unlock the bootloader: Download the Asus unlock tool for your tablet here and run it. (It's an APK from ASUS. When done you reboot tablet, you will see a message Your Device Cannot be Trusted..., you're unlocked.)
Download twrp-recoveryasboot-3.1.1-0-z300m.img.
Make sure you have fastboot/adb installed on your PC. Put your tablet in fastboot mode by holding Volume Up and Power, then selecting Fastboot Mode from the menu, and connect to PC.
Run this command to do a tethered boot of TWRP
fastboot boot twrp-recoveryasboot-3.1.1-0-z300m.img
This will boot but will not install TWRP. You may be able to do whatever you need in this environment. But it is recommended to install TWRP to your flash ROM, and proceed from there.
To flash TWRP from TWRP, go to Install -> Install Image. Select the twrp-3.1.1-0-z300m.img file you downloaded earlier (not the twrp-recoveryasboot*.img file). Select Recovery, then swipe to flash.
Reboot to Recovery
[TWRP first launch]
Now press and hold both the Volume Up and Power button at the same time. Tablet will show a list so let go of the buttons.
Use the Up volume now to select Recovery and press Down volume to select. Tablet should reboot into TWRP. (takes 10-15 seconds)
A dialogue will show in TWRP stating that there is a chance Recovery will be restored (the Asus one) so slide across to keep TWRP.
Mounting /system in read/write mode could be potentially hazardous, this is patched at your own risk.
***NOTE: You will need to boot into the recovery immediately after flashing, failing to do so will result in the Android OS reflashing its stock recovery. If you are concerned about which recovery is installed I would suggest using 'adb reboot recovery' to minimize risk.
[ROOTING]
Put the Magisk flash file on a working micro sdcard and pop it in your device. (this won't get deleted and can be accessed by TWRP)
Don't reboot yet, we need to flash Root (you should have Magisk img/zip on your micro sd inserted in tablet)
Assuming you are familiar with TWRP, Install the Magisk Manager.
When this is done, reboot your tablet to System with TWRP.
We've tried to make this guide as helpful as possible, read this thread and the Z380 thread as there may be new things learned, past experiences of others that could help you.
Enjoy your Rooted Tablet!
Thanks! Any chance of instructions for us using Linux?
Maybe we'll get LineageOS for this soon!
New TWRP Image March 4, 2018
Up to date precompiled kernel from firmware WW-5.3.19
Up to date TWRP/AOSP sources, including TWRP 3.2.1-0
Unified image that may be flashed to recovery or boot partitions, or be used for tethered boot
Guide and downloads on my new TWRP thread
Upgrade Installation
Copy the new image file to your tablet, then use your existing TWRP to Install->Install Image the .img file to Recovery. Then reboot to recovery.
Mandatory step: after trying this release out, you must come back here and post whether it works or not.
(Source code on my Z380M thread.)
Good job ! It's more than anyone else has managed to do so far
justshaun said:
In order to navigate through TWRP you will need to attach the OTG cable and mouse to your tablet, it doesn't currently have any touchscreen functionality. Reboot into the system and make sure to patch your OS.
Click to expand...
Click to collapse
After looking at kernel logs and old source code, it seems like the touchscreen driver is intentionally disabled from working in recovery mode. If we had updated kernel sources, this could be fixed easily.
QwertyChouskie said:
Thanks! Any chance of instructions for us using Linux?
Click to expand...
Click to collapse
Try the Linux flavor of SP Flash Tool?
Wow this is quite the process and twrp with no touch screen? Plz post your success to raise confidence of others like me. Last f'ng tablet I ever buy from Asus. Let's also not forget you will be stuck on this release forever afterwards.
Sent from my P00C using Tapatalk
how do you unroot tablet after this process?
Flukester69 said:
Wow this is quite the process and twrp with no touch screen? Plz post your success to raise confidence of others like me. Last f'ng tablet I ever buy from Asus. Let's also not forget you will be stuck on this release forever afterwards.
Click to expand...
Click to collapse
You can try the Asus unlock tool to be able to flash with fastboot and not worry about SP Flash Tool. At least one person got it work on the Z380M. And you can always unroot/restore original boot & system images to be able to upgrade the firmware. Also, it's kind of unfair to rate a company poorly for not supporting your hacks, especially since this tablet is basically unbrickable AFAIK.
MihaiA7X said:
how do you unroot tablet after this process?
Click to expand...
Click to collapse
Restore the original boot image if you only have systemless root. And also the system image if you've modified it.
diplomatic said:
You can try the Asus unlock tool to be able to flash with fastboot and not worry about SP Flash Tool. At least one person got it work on the Z380M. And you can always unroot/restore original boot & system images to be able to upgrade the firmware. Also, it's kind of unfair to rate a company poorly for not supporting your hacks, especially since this tablet is basically unbrickable AFAIK.
Click to expand...
Click to collapse
I'll give it a try at some point man, not sure about the unbrickable part, $hit happens. Do you have a reference for the guy with the 380 that flashed via fastboot? that would be the preferable method for me really.
---------- Post added at 10:20 PM ---------- Previous post was at 10:01 PM ----------
What is Magisk? Is it really needed? If TWRP is installed with the Flashtools can I not just flash SuperSU with TWRP? If you could clarify?
When I tried the command to flash recovery I got the following...
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13958 KB)...
OKAY [ 0.445s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.452s
What I meant by unbrickable was that you can use SP Flash Tool to talk directly with the SoC. That gives you low-level access to the flash ROM without depending on any software on it. So for example, if your bootloader or partition table is messed up, something that would brick most devices, you can flash those in without needing to get into the bootloader. I'm not 100% sure this is possible, but I'm pretty confident it is.
This is the post where the guy unlocked the bootloader. But I'm not sure he used fastboot to flash. TBH, FlashTool is not that complicated. Most of that stuff in the guide has to do with backing up your flash memory. If you wanna skip that part, that's up to you. You can just go ahead and use Flash Tool 5.1532 with the scatter file and the right download-agent to flash the recovery. BTW, you can follow that thread as well. Whatever applies to the Zenpad Z380M usually applies to the Z300M too.
Magisk is another root manager like SuperSU. SuperSU seems to have compatibility problems with this tablet. (I have not tried either.)
diplomatic said:
What I meant by unbrickable was that you can use SP Flash Tool to talk directly with the SoC. That gives you low-level access to the flash ROM without depending on any software on it. So for example, if your bootloader or partition table is messed up, something that would brick most devices, you can flash those in without needing to get into the bootloader. I'm not 100% sure this is possible, but I'm pretty confident it is.
This is the post where the guy unlocked the bootloader. But I'm not sure he used fastboot to flash. TBH, FlashTool is not that complicated. Most of that stuff in the guide has to do with backing up your flash memory. If you wanna skip that part, that's up to you. You can just go ahead and use Flash Tool 5.1532 with the scatter file and the right download-agent to flash the recovery. BTW, you can follow that thread as well. Whatever applies to the Zenpad Z380M usually applies to the Z300M too.
Magisk is another root manager like SuperSU. SuperSU seems to have compatibility problems with this tablet. (I have not tried either.)
Click to expand...
Click to collapse
Thanks for clearing that up... Ok I can use the 5.1532, I get that part but I don't get this part...
6. Make sure the tablet is turned off and then plug it into your computer
Click to expand...
Click to collapse
then
Click download at the top and plug in your tablet while it's still off. Assuming all goes well, the 'Download Flash' section at the bottom should be sitting on 100% and you should have a lovely green tick on your screen.
Click to expand...
Click to collapse
So when I press Download button in flash tool, the tablet needs to be OFF? Like powered off completely? Because nothing happens other than seeing the untrusted device (cuz it's unlocked) and the battery charging display.
Flukester69 said:
So when I press Download button in flash tool, the tablet needs to be OFF? Like powered off completely? Because nothing happens other than seeing the untrusted device (cuz it's unlocked) and the battery charging display.
Click to expand...
Click to collapse
Yeah, completely off. Have you installed the Mediatek USB port drivers? Where does it say untrusted device?
So after you unlocked it, have you tried fastboot flash? And you also don't need to use the 5.1532 version. I think the latest one will work too. The 1532 is just the NSA courtesy version.
diplomatic said:
Yeah, completely off. Have you installed the Mediatek USB port drivers? Where does it say untrusted device?
So after you unlocked it, have you tried fastboot flash? And you also don't need to use the 5.1532 version. I think the latest one will work too. The 1532 is just the NSA courtesy version.
Click to expand...
Click to collapse
Installed is whatever Win10 installed. I didn't try other drivers because adb / fastboot appear to work but I can try some other drivers.
Whenever I boot the tablet, it says untrusted device because the bootloader is unlocked. It says, booting in 5 seconds.
I do a fastboot reboot bootloader and I see it says fastboot ready at the bottom of the screen. When I type fastboot devices, it says my device in the list.
I tried fastboot flash recovery recovery.img if that's what you're asking (didn't work, so that's why I went with the software)
So just to be clear, you were getting 'FAILED (remote: download for partition 'recovery' is not allowed)' AFTER you've unlocked the bootloader?
If it's not being detected by SP Flash Tool, then something's wrong with your driver installation. Remember, those Mediatek USB drivers are not the same ones your ADB and/or Fastboot drivers. Check your Device Manger, under Ports, for a device called "MediaTek PreLoader USB VCOM (Android)". You have to check View->Show Hidden Devices to see it when your device is disconnected. You might have to right click and Update Driver Software to fix it.
diplomatic said:
So just to be clear, you were getting 'FAILED (remote: download for partition 'recovery' is not allowed)' AFTER you've unlocked the bootloader?
If it's not being detected by SP Flash Tool, then something's wrong with your driver installation. Remember, those Mediatek USB drivers are not the same ones your ADB and/or Fastboot drivers. Check your Device Manger, under Ports, for a device called "MediaTek PreLoader USB VCOM (Android)". You have to check View->Show Hidden Devices to see it when your device is disconnected. You might have to right click and Update Driver Software to fix it.
Click to expand...
Click to collapse
I got the failed with the fastboot command not the flash tool. I'll try and install the mediatek special drivers you are most likely right that they differ from the sdk provided ones. Reading other threads I understand the flash tool a bit more too. I'll do a bit more work on it and provide feedback. Thanks for your help diplomatic.
Sent from my P00C using Tapatalk
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
diplomatic said:
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
Click to expand...
Click to collapse
Well I ran the bootloader unlock tool I downloaded from Asus and ran it so I assumed it's unlocked. I tried to install drivers (latest I could find) but Windows 10 (64-bit) says I have latest installed. I checked device manager and when my tablet is off and I connect it I see the drivers(3) become active for a few seconds and then they turn off. Seems to me something is not working with this process. If you look below it seems to indicate to me the bootloader is unlocked.
Here is info
Code:
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
G7NPCV038358ANK device
C:\adb>fastboot devices
G7NPCV038358ANK fastboot
C:\adb>fastboot flash recovery c:\adb\twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13958 KB)...
OKAY [ 0.444s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.453s
C:\adb>fastboot getvar all
(bootloader) max-block-size: 0x80
(bootloader) check-fastboot-version: 1
(bootloader) sofia_support: 1
(bootloader) continuous: 1
(bootloader) flash-all-depart: 1
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:ADF: 2000000
(bootloader) partition-type:ADF: ext4
(bootloader) partition-size:APD: 6400000
(bootloader) partition-type:APD: ext4
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:asus_nvm: 100000
(bootloader) partition-type:asus_nvm: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: dfc00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: ff7000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: ff7000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: ff7000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 2000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: ASUS8163_EW_380
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.112s
C:\adb>
---------- Post added at 11:21 PM ---------- Previous post was at 10:33 PM ----------
diplomatic said:
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
Click to expand...
Click to collapse
LOL! OK. I figured $h.. out... The problem was this...
The device must be OFF and DISCONNECTED and ONLY connected when you hit the download button. The reason is, the driver shuts off if there is no data transferring. Very important detail. I am guessing this is what the issue was and why the flash tool was not working. Now I probably got old crap drivers by forcing them through Windows Troubleshooter to override signature verification. So anyway I tried flashing anyway and it failed. I suspect because I overrided good drivers with old ones. You can see what I got here.
https://ibb.co/mwkHFv
Whoa, that's kind of unexpected that fastboot would not let you flash even though it's unlocked. And the latest SPFT is not letting you download either. It says it's unlocked but it's acting like it's locked. But you're really close....
That S_SECURITY_SECURE... (6045) message is just the Flashtool's version of fastboot not allowed error (locked bootloader). So you still have to use 5.1532 to flash it. That's all.
I will post a signed image of TWRP to see if that will work for you.
diplomatic said:
Whoa, that's kind of unexpected that fastboot would not let you flash even though it's unlocked. And the latest SPFT is not letting you download either. It says it's unlocked but it's acting like it's locked. But you're really close....
That S_SECURITY_SECURE... (6045) message is just the Flashtool's version of fastboot not allowed error (locked bootloader). So you still have to use 5.1532 to flash it. That's all.
I will post a signed image of TWRP to see if that will work for you.
Click to expand...
Click to collapse
OK That worked with the 5.1532 and I booted to recovery and TWRP is there. Woohoo! Thanks for the continued help! I was getting frustrated. Not like the first device I flashed/rooted etc...
Disconnecting of the tablet until after Download button was one, the next the version of SP Flash.. cool. Making progress.
So you say SuperSU don't work... Magick one works though but installs crap, then you could use sysuninstaller to remove the crap...? Think I read that somewhere. Ok I'll read up anyway, kinda curious why SuperSU
wont work or has problems.
Also know that I removed all the MTK (older) drivers using USBDeview and then rebooting my tablet and going through all the modes, fastboot etc.. the drivers eventually all the Windows certified re-installed (the MS ones). So no need to download drivers either I guess.
Edit: this is a 1 time deal apparently. I had twrp installed but as I didn't have supersu 2.82 downloaded I rebooted out of recovery. Next attempt to go to recovery resulted in "Erasing" so I lost all my apps and had to setup my tablet all over again. Oh well, guess I know what to do now. Try again tomorrow.
All right, good job, man! :good: I'm sure our discussion will clarify the process for others...
As for root, someone else should help you out. I have not put root on my tablet. All my hacks and mods are done through TWRP.
I'm still surprised that the unlocked bootloader did not let you flash it.
---------- Post added at 12:02 AM ---------- Previous post was at 12:00 AM ----------
Flukester69 said:
Edit: this is a 1 time deal apparently. I had twrp installed but as I didn't have supersu 2.82 downloaded I rebooted out of recovery. Next attempt to go to recovery resulted in "Erasing" so I lost all my apps and had to setup my tablet all over again. Oh well, guess I know what to do now. Try again tomorrow.
Click to expand...
Click to collapse
Oh come on, how could you miss that big red text in the OP?
Related
Hi folks,
atm I feel like a complete newb because I cant manage to root my xoom according to http://forum.xda-developers.com/showthread.php?t=1074979 with fastboot. (Can't flash through cwm since the device is stock 3.2)
What I have:
Motorola Xoom EU 3G (MZ601)
Android Version 3.2
Kernel 2.6.36.3
Firmware GAS_EMEA_USAEVRSTUTMDE_P016
What doesn't work:
As soon as I try to flash recovery my almighty command line says:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (command write failed (Unknown error))
finished. total time: 1.103s
My xoom shows "Starting Fastboot protocol support" as if nothing happened.
When I try to issue the command again immediatly, the error changes to:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
FAILED (remote: (00120000))
finished. total time: 0.274s
The xoom is showing "Failed to process command error(0x120000)".
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan
jan_goose said:
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan
Click to expand...
Click to collapse
Have you tried to check the md5-checksum of the image file?
llama-power said:
Have you tried to check the md5-checksum of the image file?
Click to expand...
Click to collapse
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)
jan_goose said:
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)
Click to expand...
Click to collapse
well, they could but on my 64bit system everything worked out fine. You could try installing a 32 bit OS, as your computer is likely compatible to that. I don't, however, believe that would do any good as it looks like your computer is doing what it should, only your xoom isn't... (to me, it looks like your computer is sending the file just fine but the xoom just doesn't want to flash that file to memory)...
what does fastboot getvar all return?
llama-power said:
what does fastboot getvar all return?
Click to expand...
Click to collapse
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.
jan_goose said:
While charging, it says:
Click to expand...
Click to collapse
did you just omit the (bootloader) iswarrantyvoid: yes or did that really not appear? Apart from that, everything looks just like on my device... Thus, I am officially out of ideas... I'd offer to have a look at your device next week as I'll be in your location then but I currently don't see how that would do any good...
jan_goose said:
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
Click to expand...
Click to collapse
yeah, that distracted me at first too, but a friends MZ601 which is neither rooted nor unlocked, says the same, so I think thats fine...
Anyhow... sorry, no clue what's wrong with your device...:-(
can you flash a the recovery image from Motorola?
llama-power said:
can you flash a the recovery image from Motorola?
Click to expand...
Click to collapse
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.
wow
jan_goose said:
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.
Click to expand...
Click to collapse
i tried your method did not work i was also getting the error code what worked was using [Recovery] EOS recovery (R6) CWM Based and it pushed thru fastboot no problem just a heads up
Just to confirm...
jan_goose said:
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.
Click to expand...
Click to collapse
Did you verify if that information is correct? I get the same info from fastboot
Onedroidev said:
Did you verify if that information is correct? I get the same info from fastboot
Click to expand...
Click to collapse
I have no idea why the information seems to be wrong, but obviously it can be ignored, at least in my case.
As long as you've got a 3G module, it is not a MZ600, regardless what fastboot is saying.
I just got my new tablet today... it automatically did all it's updates while it was charging - I unlocked it following the tutorials and some strange issues started happening where the recovery ROMs I flashed couldn't see the system partitions. I tried a few different recovery ROMs (TWRP, CWM) but both did the same.
The problem, now when I try and flash anything using the bootloader, my command prompt claims it finished successfully, but my tablet's green flashing box stops flashing and does nothing until I hold on the power button to hard boot it.
Any ideas? Here's the information I've been able to gather:
Code:
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 0asdfghjklzxcvbnm
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 erase recovery
erasing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.238s
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 flash recovery openrecovery-twrp-2.4.3.0-tf300t-JB.blob
sending 'recovery' (7670 KB)...
OKAY [ 2.099s]
writing 'recovery'...
OKAY [ 2.694s]
finished. total time: 4.795s
PS C:\android-sdk\platform-tools>
I can erase and getvar all day, but flash makes it freeze up.
I forgot to include that once it locks up, the fastboot command does this:
Code:
PS C:\android-sdk\platform-tools> ./fastboot -i 0x0B05 devices
???????????? fastboot
PS C:\android-sdk\platform-tools> ./fastboot -i 0x0B05 getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.592s
PS C:\android-sdk\platform-tools>
kulm said:
I just got my new tablet today... it automatically did all it's updates while it was charging - I unlocked it following the tutorials and some strange issues started happening where the recovery ROMs I flashed couldn't see the system partitions. I tried a few different recovery ROMs (TWRP, CWM) but both did the same.
(bootloader) unlocked: no
Have you unlocked? Your posted information says no. If you are on 4.2 I can't say but previous firmware disallowed use of fastboot prior to unlocking.
Click to expand...
Click to collapse
tobdaryl said:
kulm said:
(bootloader) unlocked: no
Have you unlocked? Your posted information says no. If you are on 4.2 I can't say but previous firmware disallowed use of fastboot prior to unlocking.
Click to expand...
Click to collapse
I wondered the same thing - but I had TWRP working on it and it says on the top when I reboot "The device is unlocked"...
Click to expand...
Click to collapse
kulm said:
tobdaryl said:
I wondered the same thing - but I had TWRP working on it and it says on the top when I reboot "The device is unlocked"...
Click to expand...
Click to collapse
I have not seen this or read of this issue. Are you on the 4.2 version of software? If so you are in uncharted waters.
I didn't get the update and can't use the ota to install. I like many others are waiting for the asus firmware version.
I have read one reply where cwm didn't work on 4.2.
Something else I have never seen is the bootloader serial number displayed. You may wish to remove that line from your post. Just choose edit and delete that line, then save.
If on 4.2 this may indicate that cwm and twrp will require an update to work properly.
If you can use your tablet as is then I suggest doing so or flash stock JB firmware the most recent is 10.4.2.20 but for my use 10.4.2.18 has less lag and everything I need works properly.
I'll bookmark this thread and try to come back with some help after more research. Failing that maybe someone else will reply with a good suggestion.
Good Luck!
Please respond with your firmware version.
This is the standard method used to unlock the bootloader with fastboot. I can't use it since I'm not on 4.2 and won't suggest that you do; it is for information only at this point.
fastboot oem unlock
I suspect we would need to use the -i 0x0b05 as in fastboot -i 0x0b05 oem unlock.
Click to expand...
Click to collapse
tobdaryl said:
kulm said:
I have not seen this or read of this issue. Are you on the 4.2 version of software? If so you are in uncharted waters.
I didn't get the update and can't use the ota to install. I like many others are waiting for the asus firmware version.
I have read one reply where cwm didn't work on 4.2.
If on 4.2 this may indicate that cwm and twrp will require an update to work properly.
If you can use your tablet as is then I suggest doing so or flash stock JB firmware the most recent is 10.4.2.20 but for my use 10.4.2.18 has less lag and everything I need works properly.
I'll bookmark this thread and try to come back with some help after more research. Failing that maybe someone else will reply with a good suggestion.
Good Luck!
Please respond with your firmware version.
This is the standard method used to unlock the bootloader with fastboot. I can't use it since I'm not on 4.2 and won't suggest that you do; it is for information only at this point.
fastboot oem unlock
I suspect we would need to use the -i 0x0b05 as in fastboot -i 0x0b05 oem unlock.
Click to expand...
Click to collapse
Thanks for the response - the SN is bogus.So, when I boot without pushing vol up/down it goes to the "ASUS" logo screen with "device unlocked" at the top and it just sits... I can get into APX with vol up and fastboot with vol down.
With vol down this comes up at the top:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Then it has the typical RCK, Android and Wipe Data options.
When I choose RCK I get:
Code:
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000)
The device hangs until I power cycle from there.
Click to expand...
Click to collapse
kulm said:
tobdaryl said:
Thanks for the response - the SN is bogus.So, when I boot without pushing vol up/down it goes to the "ASUS" logo screen with "device unlocked" at the top and it just sits... I can get into APX with vol up and fastboot with vol down.
With vol down this comes up at the top:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-1.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Then it has the typical RCK, Android and Wipe Data options.
When I choose RCK I get:
Code:
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000)
The device hangs until I power cycle from there.
Click to expand...
Click to collapse
I am completely lost, if this is 4.2 that might be why. If you will give me your version I'll try to help you search and get an answer. Go to settings/about tablet/ and tell me what you have for build# and android version.
The serial# is not your tablet serial# but bootloader serial#. This may be in response to our recent petition to asus for the ability to unlock the bootloader in addition to the tablet unlock we now have.
If so this should allow nvflash for people on the JB bootloader.
Note: If you are on 4.2 you might look at settings and see if encryption is turned on, at least two have mentioned that it is on by default and it will cause various issues with fastboot and cwm or twrp.
Now that I think about it even on 4.1 encryption has caused some strange results.
Click to expand...
Click to collapse
tobdaryl said:
kulm said:
I am completely lost, if this is 4.2 that might be why. If you will give me your version I'll try to help you search and get an answer. Go to settings/about tablet/ and tell me what you have for build# and android version.
The serial# is not your tablet serial# but bootloader serial#. This may be in response to our recent petition to asus for the ability to unlock the bootloader in addition to the tablet unlock we now have.
If so this should allow nvflash for people on the JB bootloader.
Note: If you are on 4.2 you might look at settings and see if encryption is turned on, at least two have mentioned that it is on by default and it will cause various issues with fastboot and cwm or twrp.
Now that I think about it even on 4.1 encryption has caused some strange results.
Click to expand...
Click to collapse
I am on 4.2.1 and am having the same issue. I just checked and encryption is turned off on mine.
Click to expand...
Click to collapse
mistyv said:
tobdaryl said:
I am on 4.2.1 and am having the same issue. I just checked and encryption is turned off on mine.
Click to expand...
Click to collapse
Thanks for the update. I'll start searching also and report when I have some news.
Good Luck!
I'm finding several with fastboot issues as well as cwm and twrp issues but no resolutions yet.
I'll try to keep you posted if I get something positive.
Click to expand...
Click to collapse
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
ryuken11221 said:
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
That is what mine did and I thought it wasn't installing, but it actually did. Once I rebooted back into fastboot and selected RCK mine would boot into the recovery, but the internal and external sd card wouldn't mount. I tried TWRP and CWM, but no luck with either.
According to this thread http://forum.xda-developers.com/showthread.php?t=2180376 it is likely an encryption issue with 4.2.1 and we will have to wait till someone finds a fix. I was apparently wrong about the encryption on my earlier post.
ryuken11221 said:
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
I'm not finding answers to this problem; just questions.
I can't get 4.2 until Asus drops the file on their site.
At this point maybe everyone put this area on hold for a few days till we can get the full download and try to figure out what is happening and how to resolve these issues. Try to use your unit as it is for a few days and avoid possible bricks.
I have a full system dump of 4.2.1. Just extracting the bootloader and flashing it causes recovery to think it is encrypted. Custom recovery that is. Also I noticed that the 10.6.1.8 kernel doesn't like some updater-script commands. Finally there is a new file in /system/etc called recovery-resource.dat. I wonder if Asus has put some measures I in place to stop customising?
sbdags said:
I have a full system dump of 4.2.1. Just extracting the bootloader and flashing it causes recovery to think it is encrypted. Custom recovery that is. Also I noticed that the 10.6.1.8 kernel doesn't like some updater-script commands. Finally there is a new file in /system/etc called recovery-resource.dat. I wonder if Asus has put some measures I in place to stop customising?
Click to expand...
Click to collapse
Thanks for the good info. That explains a lot.
Were you using the update-binary from 10.6.1.8 or an earlier version?
Great catch. I just checked and we now have a different version of update-binary. Now I need to revisit my edify scripts.
Thanks!
Well I'm still running 4.1.1 I haven't be able to upgrade to 4.2 just as yet so I'm not sure what the issue with my device is I just restored it back to back to factory for work purposes and now I wanted to root it back and install recovery now this
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
tobdaryl said:
Thanks for the good info. That explains a lot.
Were you using the update-binary from 10.6.1.8 or an earlier version?
Great catch. I just checked and we now have a different version of update-binary. Now I need to revisit my edify scripts.
Thanks!
Click to expand...
Click to collapse
I haven't actually flashed all of it but tried to make it compatible with my TF700. I also tried 2 or 3 different updater binaries and they made no difference.
Specifically format now wanted 5 args where only needed 4 before. No idea what the 5th is. Package extract file didn't like me writing to /tmp but was OK with /data/media ..... Weird
Looks like a permissions thing?
sbdags said:
I haven't actually flashed all of it but tried to make it compatible with my TF700. I also tried 2 or 3 different updater binaries and they made no difference.
Specifically format now wanted 5 args where only needed 4 before. No idea what the 5th is. Package extract file didn't like me writing to /tmp but was OK with /data/media ..... Weird
Looks like a permissions thing?
Click to expand...
Click to collapse
Thanks for the help.
OK is this straying from what the topic is about just asking
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
ryuken11221 said:
OK is this straying from what the topic is about just asking
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
It is about the 4.2 rom and related issues; however I am done. Sorry for the interruption.
tobdaryl said:
It is about the 4.2 rom and related issues; however I am done. Sorry for the interruption.
Click to expand...
Click to collapse
Not a problem just wondering if I can get help with this just very very frustrating
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Hi all,
I've exhausted all my resources in trying to get this tablet to work. It might be hard bricked if that's even possible. Just a little back ground on what happened. The device was running very slow after 3yrs of using wingray (wifi MZ604?) [ROM][4.4.4] OmniROM - Wingray - bigPart. Anyway it's from Verizon and it only has wifi. But as I said, it was running very slow so I figured i'd flash back to stock ROM. The stock ROM flash fine and it was pretty responsive. Then this where everything went to sh!*.. I received an update notification, it updated, rebooted and the tablet is stuck on Dual Core M boot screen. I have tried to restore by flashing OmniROM - Wingray - bigPart and RDS back to stock ROM, both stuck on Dual Core M boot screen.
I spent over 48 man hours reading through the forums on how to unbrick this tablet. Unlocking the botloader and pushing twrp big part and flashing a custom ROM, to using One Click Tool made by XxLordxX to try to get it back to stock and installing Omni ROM. None of which seam to work. It always ends up stuck on Dual Core M boot screen until it runs out of battery charge. There is no way I can get into any type of recovery.
I have access to the following items:
- fastboot
- RDS
I don't have access to the following:
- bootloader
- ADB
- default or custom recovery
If anyone can assist, I would really appreciate it.
Edit: if it helps, this is what i extracted from the device in fastboot
Code:
(bootloader) version-bootloader: 1045
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x303:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: redacted
(bootloader) version-baseband: CDMA_N_03.1A.71P
(bootloader) version-baseband-2:
(bootloader) battery-status: 61%:7.729V:0.9731A:33.62C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
all: Done
Thanks
download twrp img file and use fastboot to upload the recovery? "fastboot flash recovery twrp-3.0.x.x-xxx.img" just gotta find which twrp you want. by the by, I just flashed the files from here and now I am getting a boot screen instead of stuck at bootloader like you ;
https://www.dropbox.com/sh/1fxrnv2ce8fyjyn/AABHGMZcGCYBYqtDSvMMpXC-a?dl=0
Which is from here - give the man props! https://forum.xda-developers.com/motorola-xoom/general/roms-motorola-xoom-t3602655
Unfortunately any twrp recovery I flash with fastboot doesn't allow me into recovery. Without recovery I can't flash those archives. Very annoying. But thanks for the heads up. I guess the main priority is to get a working recovery.
Sent from my iPhone using Tapatalk
Change the usb cable. I'm not joking, that might be the problem!
If that doesn't work, use RSD lite to flash the original ROM (the SBF file, you will find it on the internet). Make sure to flash the corresponding SBF to your tablet.
vlad_popescu47 said:
Change the usb cable. I'm not joking, that might be the problem!
If that doesn't work, use RSD lite to flash the original ROM (the SBF file, you will find it on the internet). Make sure to flash the corresponding SBF to your tablet.
Click to expand...
Click to collapse
Yea I believe you about the USB cable but unfortunately this was a hand me down and the original cable was lost.
I've tried all the SBF files I can get my hands on and it still gets stuck on the M logo screen and I can't get into recovery mode. I can list all the sbf files I've tried. They are still stored on my NAS.
Hello nomadman,
Check a zip from this thread according to your Xoom model version and area:
https://forum.xda-developers.com/showthread.php?t=1049485
Unzip the file. And do these commands to boot your rom:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Use this method to your own risk. I think it should work, but... I suppose it is your only chance to have stock rom again.
Thanks @Manuallama. I will give this a shot since I don't really have a choice. Before I flash I usually fastboot clear those boot, user, and system. We do this when I get home from work. Cheers
Sent from my iPhone using Tapatalk
Hello. Today, my wife's phone stopped responding to anything out of blue. I did a forced reboot (Vol down + power) and it rebooted and worked fine for a bit. Seeing as Android 10 was out, I dled fota file and flashed it via recovery from SD card, like I usually do. It flashed successfully and then rebooted. Once it booted, after a few seconds it hanged and became unresponsive again. Forced reboot once again, except this time it booted into a fastboot mode on its own and here lies there problem:
- going through an option to get into recovery mode doesn't help as it goes back into fastboot mode again
- rebooting through cmd doesn't help either
- pressing start just returns to fastboot mode
- shutting it down through an option in fastboot and then turning it on still yields the same result.
Basically, whenever phone turns on, it goes into a fastboot mode whether you want it or not.
Has this happened to anyone else? Any idea how to fix it?
Upd:
Code:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
Seems like update failed to flash into slot B and it's not bootable
Okay, so I fixed it.
I flashed service/raw fw through fastboot, commenting out userdata formatting part of the flashall_aft script (fastboot -w). After this, I was able to access recovery mode. In recovery mode, I flashed build 16.1220.1909.194 and then 17.1810.1910.63 from my SD card and phone came alive, while retaining all the data.
Perhaps, this information will help someone who will encounter the same situation.
can u provide links for service /raw fw and how did u flashed it.
My Asus ZS630KL is stuck at fastboot mode neither rebooting to recovery works nor flashing custom boot or stock boot works. how to flash back stock rom in fastboot mode.
DAMONDARK said:
can u provide links for service /raw fw and how did u flashed it.
My Asus ZS630KL is stuck at fastboot mode neither rebooting to recovery works nor flashing custom boot or stock boot works. how to flash back stock rom in fastboot mode.
Click to expand...
Click to collapse
Sure. You can get RAW one here. Unzip, cd to the folder and launch flashall_aft script in cmd. There a bash script in the folder in case you have a Unix system. Script will output "Download_PASS" when it's done. Do not disconnect your phone before then.
Note, by default, this will wipe your userdata partition. You can prevent that my commenting out/removing line 264 in the script. However, note, if you don't wipe userdata partition, until you upgrade to the firmware that you currently have, the phone won't boot.
If your final firmware is latest one, with Android 10 (build 17.1810.1910.63), you will have to first update to 16.1220.1909.194. Links to both are in my previous post. I advice to flash desired firmware through Recovery -> Install update from SD card, though adb sideload should work just as well.
I'm thinking that "service/raw fw" is what is called a "fastboot rom" with Xiaomi?
Asus does not provide these themselves somewhere?
Or only for internal use?
Now I don't have a problem with my Z6 currently, but like to be prepared, like a good Boy Scout.
DAMONDARK, I wrote a more detailed guide if you need it. Click
cobben, ASUS does not provide those RAW firmwares to the public themselves. My guess is they are distributed internally for the use by service centers and alike and some ASUS workers upload them for public use. It's basically a set of tools along with signed images of all partitions to flash a full firmware to a specific device.
Images being signed (unlike images extracted via payload_dumper), device will accept them even without unlocked bootloader.
Not sure what this kind of firmware is called for Xiaomi
Ok, that is basically the same as the fastboot ROM with Xiaomi.
Xiaomi provides these publicly for anyone to use.
They have a Windows tool for this.
Requires unlocked bootloader, but bootloader can be relocked with no consequences.
Then there are other traps with Xiaomi, ARB primarily.
An incremental upgrade to a new major Android version is bound to cause some problems for some users, at best.
There should be a publically available way to restore the device to a known state.
cobben said:
Ok, that is basically the same as the fastboot ROM with Xiaomi.
Xiaomi provides these publicly for anyone to use.
They have a Windows tool for this.
Requires unlocked bootloader, but bootloader can be relocked with no consequences.
Then there are other traps with Xiaomi, ARB primarily.
An incremental upgrade to a new major Android version is bound to cause some problems for some users, at best.
There should be a publically available way to restore the device to a known state.
Click to expand...
Click to collapse
They did provide a zip to go back to latest Android 9 build which is WW-16.1220.1909.194. It can be found here
In most cases, the above should be enough. If your bootloader is unlocked, you don't really need service fw, you can just flash images dumped by payload_dumper from any zip of a build from ASUS website.
Additionally, service firmware does provide a lock script, which supposedly locks the bootloader but erases userdata. I have not tested if it actually re-locks bootloader.
Device: 360 N6 Lite by QIKU, Snapdragon 630
Device is running stock ROM based on android 8.1,
Some good man tried to help me and created some TWRP version for me but when I flashed it my phone could not start: instead of booting it falls to fastboot mode.
Addtional info about my device which might be useful for knowledgeable person:
1. fastboot has limited functionality: it cannot flash any partiton, therefore the only way I can flash anything is by QFIL
2. I can install Magisk and patch stock boot.img, but when I flash patched boot phone goes to bootloop.
3. bootloader is unlocked:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3975
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x1F400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5EBBFBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xE0000000
(bootloader) secure:yes
(bootloader) serialno:********
(bootloader) product:QK1713-A01
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
4. some more info:
Z:\android\adb>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
Finished. Total time: 0.000s
Links related to my device:
TWRP version 1 which failed to load: https://disk.yandex.ru/d/XxzizBXtWnMcMg
TWRP version 2 which failed to load: https://disk.yandex.ru/d/4LBp0kkfgWZk7w
stock recovery: https://disk.yandex.ru/d/F4IHueroahPBhQ
stock boot: https://disk.yandex.ru/d/x_zcR0WDg9d4hg
stock ROM (very special CPB format!): V3.0.014 (8.1base version)
stock ROM (ZIP format!): V3.0.014 (8.1base version)
I wish somebody would take an interest in this difficult case and give it a try...
As an alternative, I could try to follow instructions if this would be more practical to buld TWRP.
Thank you!
vp1117 said:
Device: 360 N6 Lite by QIKU, Snapdragon 630
Device is running stock ROM based on android 8.1
Some good man tried to help me and created some TWRP version for me but when I flashed it my phone could not start: instead of booting it falls to fastboot.
Addtional info about my device which might be useful for knowledgeable person:
1. fastboot has limited functionality: it cannot flash any partiton, therefore the only way I can flash anything is by QFIL
2. I can install Magisk and patch stock boot.img, but when I flash patched boot phone goes to bootloop.
3. bootloader is unlocked:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3975
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x1F400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5EBBFBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xE0000000
(bootloader) secure:yes
(bootloader) serialno:********
(bootloader) product:QK1713-A01
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
4. some more info:
Z:\android\adb>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
Finished. Total time: 0.000s
Links related to my device:
TWRP version 1 which failed to load: https://disk.yandex.ru/d/XxzizBXtWnMcMg
TWRP version 2 which failed to load: https://disk.yandex.ru/d/4LBp0kkfgWZk7w
stock recovery: https://disk.yandex.ru/d/F4IHueroahPBhQ
stock boot: https://disk.yandex.ru/d/x_zcR0WDg9d4hg
I wish somebody would take an interest in this difficult case and give it a try...
As an alternative, I could try to follow instructions if this would be more practical to buld TWRP.
Thank you!
Click to expand...
Click to collapse
Here's the file TWRP for your device: 360_N6Lite_TWRP3.2.1_Recovery_9008.zip
The file is from 4pda forum with structions by bullik01: Acquiring TWRP
lopestom said:
Here's the file TWRP for your device: 360_N6Lite_TWRP3.2.1_Recovery_9008.zip
The file is from 4pda forum with structions by bullik01: Acquiring TWRP
Click to expand...
Click to collapse
lopestom said:
Here's the file TWRP for your device: 360_N6Lite_TWRP3.2.1_Recovery_9008.zip
The file is from 4pda forum with structions by bullik01: Acquiring TWRP
Click to expand...
Click to collapse
Thank you for taking your time and trying to help me!
I'm aware of this TWRP version. I know it was constructed somewhere in China and that bullik01 guy just copied it to 4pda forum.
My trouble is: 360_N6Lite_TWRP3.2.1_Recovery_9008.zip works only if phone runs android 7.1.2. If I try to install it with stock Oreo ROM, it crashes my phone as can be seen on attached pic. Error message translation into English:
Detected that the phone has been swiped into the non-officially certified ROM package! The phone will turn off in 5 seconds!
From this point of view, TWRP versions I referred to in my first message seem to me more ... advanced, I would say, as they do not crash my phone but just make it boot to fastboot mode.
vp1117 said:
Thank you for taking your time and trying to help me!
I'm aware of this TWRP version. I know it was constructed somewhere in China and that bullik01 guy just copied it to 4pda forum.
My trouble is: 360_N6Lite_TWRP3.2.1_Recovery_9008.zip works only if phone runs android 7.1.2. If I try to install it with stock Oreo ROM, it crashes my phone as can be seen on attached pic.
From this point of view, TWRP versions I referred to in my first message seem to me more ... advanced, I would say, as they do not crash my phone but just make it boot to fastboot mode.
Click to expand...
Click to collapse
Good to know. You can see other TWRP for same chipset and Oreo? If yes, attach your stock recovery.img; boot.img and TWRP file for Snap 630 - Oreo 8.1.
"You can see other TWRP for same chipset and Oreo?" - not sure what you mean. I never tried to flash TWRP built for any other devices. The only TWRP I tried - I posted links to them in my fist message and attached these files here. They are NOT working TWRPs. They were build locally by some guy who tried to help me out. Files names are 'ptwrp3.2.1-0.img' and 'ptwrp3.2.3-0.img', attached. They cause my device to boot into fastboot mode.
Also attached are my stock Oreo boot & recovery images.
I can provide you with any other file(s)/info if necessary.
Thank you!
vp1117 said:
"You can see other TWRP for same chipset and Oreo?" - not sure what you mean. I never tried to flash TWRP built for any other devices. The only TWRP I tried - I posted links to them in my fist message and attached these files here. They are NOT working TWRPs. They were build locally by some guy who tried to help me out. Files names are 'ptwrp3.2.1-0.img' and 'ptwrp3.2.3-0.img', attached. They cause my device to boot into fastboot mode.
Also attached are my stock Oreo boot & recovery images.
I can provide you with any other file(s)/info if necessary.
Thank you!
Click to expand...
Click to collapse
I know about the TWRP for D1 cannot flash in D2! Each device so each TWRP!!
I can compile TWRP but unfortunately my time is not good and I haven't A8.1 Source Code Team Win in my PC Linux now. That's need time and much size in the PC.
May be I can help PORTing. Wait patiently the file.
Thank you you are still with me!
Sure, if you need time then I'll wait. Just... minor concern from my side is as following: it appears that vendor (Qiku) have acivated DM-Verity in Oreo stock ROM for my device. My knowledge of android is almost zero but as far as I learnt, having DM-Verity activated would render all efforts of builing custom recovery useless since ABOOT will always prevent custom partition from booting... Am I not right?
Here is some info regarding my phone: https://github.com/search?q=qk1713
I'm not sure how valuable it is. I'm not even sure this info in trustworthy as I'm a complete newbie and cannot estimate value of anything related to linux/android world. Judging by the dates, the info might be related to android 7.1, not 8.1...
Also, I have PC with linux mint at my disposal and if I could obtain more detailed info about my phone using linux tools - I'll be more than happy to do so.
vp1117 said:
Here is some info regarding my phone: https://github.com/search?q=qk1713
I'm not sure how valuable it is. I'm not even sure this info in trustworthy as I'm a complete newbie and cannot estimate value of anything related to linux/android world. Judging by the dates, the info might be related to android 7.1, not 8.1...
Also, I have PC with linux mint at my disposal and if I could obtain more detailed info about my phone using linux tools - I'll be more than happy to do so.
Click to expand...
Click to collapse
Yes and not. We need look about files is from device/stock ROM. But if you really want know how compile TWRP read this about tools/instalation/commands:
GitHub - opticyclic/twrp-compile-guide at NX529J
A technical guide on how to compile TWRP for a new device. - GitHub - opticyclic/twrp-compile-guide at NX529J
github.com
GitHub - opticyclic/twrp-compile-guide at develop
A technical guide on how to compile TWRP for a new device. - GitHub - opticyclic/twrp-compile-guide at develop
github.com
Well guy, my time realy is not good now. But with minimal files I make 3 files for test. The problem maybe is DM_VERIFY from boot.img in your device. You can desactivate that with magisk?! You need know how install file.img in the recovery partition or test with: fastboot boot recovery.img
If you need something help about compile TWRP so contact me in my profile github.
Hi lopestom, I hope everything is OK with you.
THANK you for finding the time to build recoveries!
I don't use fastboot for flashing. Fastboot which is implemented in my phone prohibits flash command. Instead, I use QFIL, it works fine.
All 3 of recoveries you've buit led to same result: phone falls to fastboot mode.
Well, at least you somehow managed build recoveries which do not lead to red state!!
If, along with with your recovery I flash boot.img patched by Magisk, result is the same: phone boots into fastboot.
I wish I could build recoveries myself, but I somehow cannot get myself understand Linux. Everything is so... difficult and so... non-human in Linux. I only use Linux to edit system.img for my other phone. So, my knowledge is limited to how run caja as administrator and how to mount system.img for editing.
vp1117 said:
I wish I could build recoveries myself, but I somehow cannot get myself understand Linux. Everything is so... difficult and so... non-human in Linux. I only use Linux to edit system.img for my other phone. So, my knowledge is limited to how run caja as administrator and how to mount system.img for editing.
Click to expand...
Click to collapse
You read the links guide that I out before?
That's simple in first moment because only install tools to compile need. So you need github profile; sudo install xxxxx; repo; etc.....
The second is about device tree. But you have that so maybe good maybe not. Is need tests.
If not good you can search other same device tree to your Soc/Chipset/CPU in the github and modify informations from your device.
You can write me in my profile github and if I can so help more.
Hi lopestom, thank you for your explanations. From these explanations I understand the general idea. And, who knows, probably I'll give it a try some day. Another newbie will be trying to build a TWRP...
However, discussing my bad phone on different forums, I'm gradually coming to conclusion that probably my phone was built in such a way so any custom recoveries will always be rejected. There is a chance that any modified partition on my device needs to be signed by vendor's key.
So, it might be that those recoveries you kindly built for me few days ago are already good recoveries but we'll never know that because my phone just rejected them as not signed by this nasty QIKU vendor.
The task of fighting with boot/recovery signature is far above my knowledge. Most probably, I'll be defeated by it and will have to give up. As such, it will put an end to my endeavours in regards of TWRP...
I appreciate your help very much. I don't even know what makes you to spend your time helping newbies like me. THANK you!
Hello lopestom!
Just wanted to share with you some great news about those TWRP versions you so kindly build for my almost sunset phone.
They do work, all 3 of them!!
Somehow I got AVB disabled, not sure exactly what it was, so that now it is possible to avoid Red State / fastboot when flashing modified recovery.
So far I can see only one problem about these TWRPs: they fail to mount Vendor partition. But I do not want you to spend any of your time looking at this issue. I have now basic functionality with your TWRPs which I badly needed. I'm 100% happy with TWRPs.
Just to repeat: BIG thank you for your kind support!
Good day, can i also get this twrp works for me, i also have 360 n6 lite phone with android 7.1. i know the basic flashing of twrp but dont know the right files to flash, maybe you can help me pick the right files to install without error. My purpose of installing TWRP is for rooting my device and install magisk then install some app that can enable internal recording with any apps i use
Note: i also dint know to unlock bootloader of this
I wish you can help me and i really appreciate it,