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.
Good morning guys,
firstly i really have tried to read up on everything i can possibly before i posted this, i've been looking around trying to get as much info as i can
So from the start my HTC ONE SV is softbricked (i think) it tried to update a few months back and half way through the process something went wrong it shut down and rebooted, and it was just a black screen and battery icon (showing that it was charging still)
I then went to Hboot Recovery and started the process, what i found odd was that when it went to the recovery icon, the 2 swirling arrows over the device icon, it would show that for a couple of seconds then reboot itself it would repeat this process for about 5 minuets then finally boot up the phone into the HTC ONE screen, chime would play (but stutters) and then load me back to where i was in the first place a black screen with the battery icon, and time
So clearly something is corrupted either the restore portion or the os it'self, i decided that it would need to be re flashed.
i have gotten as far as Ulocking the bootloader and now i have what i belive is a compatible Rom for my phone,
so all that remains now is for me to actually do the process i've seen a lot of guides around but generally they all default to a ONE S not a ONE SV which either means no one has made a full guid for SV or the S and SV are compatible ?
anyway i was hoping someone here may have the time to help me out with how to do a flash back to stock
HTC ONE SV UK Orange / EE / same carrier no SD card (if that is needed let me know)
Whippyice said:
Good morning guys,
firstly i really have tried to read up on everything i can possibly before i posted this, i've been looking around trying to get as much info as i can
So from the start my HTC ONE SV is softbricked (i think) it tried to update a few months back and half way through the process something went wrong it shut down and rebooted, and it was just a black screen and battery icon (showing that it was charging still)
I then went to Hboot Recovery and started the process, what i found odd was that when it went to the recovery icon, the 2 swirling arrows over the device icon, it would show that for a couple of seconds then reboot itself it would repeat this process for about 5 minuets then finally boot up the phone into the HTC ONE screen, chime would play (but stutters) and then load me back to where i was in the first place a black screen with the battery icon, and time
So clearly something is corrupted either the restore portion or the os it'self, i decided that it would need to be re flashed.
i have gotten as far as Ulocking the bootloader and now i have what i belive is a compatible Rom for my phone,
so all that remains now is for me to actually do the process i've seen a lot of guides around but generally they all default to a ONE S not a ONE SV which either means no one has made a full guid for SV or the S and SV are compatible ?
anyway i was hoping someone here may have the time to help me out with how to do a flash back to stock
HTC ONE SV UK Orange / EE / same carrier no SD card (if that is needed let me know)
Click to expand...
Click to collapse
Update: just to add it's stock everything i've never hacked or modded this phone so it was on the last official os for HTC ONE SV what ever that was think MAYBE 4.2.2 and i have purchased a sd card just incase it was needed,
You can flash a custom recovery (TWRP) and flash back a working rom, if the bootloader is already unlocked.
old.splatterhand said:
You can flash a custom recovery (TWRP) and flash back a working rom, if the bootloader is already unlocked.
Click to expand...
Click to collapse
ok dude, sounds like a plan,
ummmmm how lmao i see your quite knowledgable on here i see you post quite a bit so thanks for paying attention to mine, i am trying to do exactly what you said but right now nothing seems to do what is explained on the web, i have the latest TWRP.img and i've tried to push it over from adb, i get an error saying "error cannot load "recovery.img" i've made sure it's in the same DIr as my adb
i've been trying to load it onto the sd card and get it to auto update from their no success either
halp
thanks again dude, i'm tryng to not be ignorant and still reading up at the same time but nice to have some help from a pro
I've heard "i have the latest TWRP" many times, but (without wanting to hurt you) this means nothing (latest from their web page? version number? for which model? so many things which can differ)!
You need to understand to provide proper information to us, so we can help better!
Not every recovery is working on 4.2.2, but this one should do.
Read the guide there how to install, you can't flash recovery with adb!
Then we need more information about your phone model, please! There are versions of One SV with or without LTE, carrier based... ...we don't know which one you own.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
ha ok that's fair enough i guess i know where your coming so yeah i can understand that, ok so i have the following
[Recovery] TWRP Recovery 2.7.0.x (recommended for 4.2.2
ADB
AdbWinApi.dll
fastboot
TWRP-2.7.0.1-k2_ul-k2u
in folder C:\android
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.61.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Hopefully that's everything
Ok, use the recovery and the how to install, to flash the recovery.
I'll attach here a dll file which you should also use/put in your adb folder (unzipped of course).
When you are in recovery you should do wipe system, data, cache & dalvik cache (unlocking bootloader did wipe your data anyway) and then you can proceed with flashing this rom.
Your info stated you have a k2ul (with LTE), so use the k2ul version. Or, you can also restore a TWRP backup, see this thread.
Or another option would be a custom rom, like this.
Good luck!
ok so i have added the dll to the adb folder in C;\android
i opend cmd (with admin)
typed
cd \android
typed
fastboot flash recovery recovery.img
and got
C:\Android>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
i am pretty sure it's me who is doing something wrong
sorry dude, i'm a total noob at this stuff, (blame my gf for breaking my phone lol)
Your recovery.img is also in this folder?
What is the output of fastboot devices?
Is your bootloader showing on the top "Unlocked" an "Tampered"?
ok so my folder now looks like this
abd
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
recovery.img
in C:\android
What is the output of fastboot devices = i'm not sure how to tell really ?
Is your bootloader showing on the top "Unlocked" an "Tampered"? = yes in fastboot usb mode with ***tampered*** & ***unlocked*** at the top
fastboot devices should show you your serial number (which you removed in getvar result).
Something 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"
}
i have currently showing
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd \android
C:\Android>fastboot devices
fastboot
C:\Android>
Ok, remove it from your post. Should be fine!
Your fastboot should be able to flash the recovery.img to your phone.
Now its time for me to go to bed.
old.splatterhand said:
Ok, remove it from your post. Should be fine!
Your fastboot should be able to flash the recovery.img to your phone.
Now its time for me to go to bed.
Click to expand...
Click to collapse
ok dude, i'll keep trying
thanks for your help
EDIT:
So i randomly managed to do it using one a all in one tool kit from Hasoon2000
one, (all varients kit) so i now have a working recovery manager,
now how do i get the flash os on their Via sd card ?
thanks
So i have managed to flash 2 roms now
1 stock rom which was provided too me, seemed to flash fine, however result is the same a black screen with battery and time with no single for data
2 team vipersv flashed fine tried various different ways of flashing it all seemed fine, boot up to same result black screen, battery icon, no reception for data
i belive that this is now not a rom issue it must be something relating to something else, 2 flashed roms with the exact same result dosn't make much sense that it would be them
i've seen a couple of other posts around is it worth re flashing a stock kernal again ? thanks
Did you flash the boot.img with fastboot?
old.splatterhand said:
Did you flash the boot.img with fastboot?
Click to expand...
Click to collapse
Hey,
i don;t think i have done that the following things have now been done
Bootloader was unlocked Via, HTCDEV code
WTRP flashed to recovery (working)
superUS flashed fine (working as far as i know)
stock kernel flashed VIA TWRP (flashed fine)
VierpSV flashed (flashed fine) same result)
Saturn III flashed (flashed fine) same result
stock flashed (flashed fine) same result,
they are the only things that have been flashed to the phone, if there is anything else that needs doing i haven;t done it as far as i know lol
EDIT;
i've just seen this in another thread i don't have my phone with me right now but assuming that my hboot is over mentioned version below could this be the problem ?
Quote:
Do I need to flash the boot.img manually in fastboot?:
No, if you're using TWRP and are on a Hboot-version lower than 1.13
Yes, if you're using any other recovery (like CWM)
Yes, if you're using TWRP and your ville has the Hboot-version 1.13 or hig
I have no flashed the boot.img (ViperSV) via fastboot so whats the difference between it being flash from twrp and from fastboot ? it seems to be still flashing the install from twrp
As you are S-On, you should definitely flash the boot.img with fastboot cmd.
Stock kernel for flashing in recovery is only for S-Off devices.
old.splatterhand said:
As you are S-On, you should definitely flash the boot.img with fastboot cmd.
Stock kernel for flashing in recovery is only for S-Off devices.
Click to expand...
Click to collapse
trying to figguer out if i am S-off or not,
is their any telltell signs that your S-off
?
EDIT
i am S-on, it says it right at the top lmao sorry
ok now i need to get S-off lmao. but i can't get into the os at pressent so i don't know if i can get S-off whitout being able to get to the os ?
No, you need a working os.
Did you flash boot.img with fastboot already?
And you can't boot into the os?
( Text below is just an explanation to my issues and why I need help! )
Hallo dear XDA forum people I ahve many times read posts and fixes about my cellphone here and managed to unlock, root and install Super SU on my HTC One S. It still has the stock rom, given it's now unlocked and rooted etc. Last weeks I've been having problems with calling out or receiving phone calls. Due to the cellphone hangs every time. So factory reset it to default. The problem persisted somewhat. It now just gets sluggish and I can't hear the other one speaking. Even though the cellphone actually made the connection. So thought about downloading a RUU or flash to another ROM to see if it's cleaner and more stable.
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/showthread.php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum
SOLVED flashed working ROM and fixed SD card mounting error.
After 3 weeks of frustration and trying I finally got my phone booting with a ROM. As I couldn't find any RUU.exe files for my phone and the RUU.zips didn't work either I had to go custom ROMing. I'll explain the whole process with steps I did so that others can read easily
1. Go into Bootloader, choose Fastboot and connect your phone with the USB cable. Open up CMD in your Fastboot/ADB folder by holding SHIFT+Right Click and type: ''Fastboot devices'' without the quotas, to see if your phone appear like SH32HW.... etc. You can also use the command: ''Fastboot getvar all'' to pull a few lines of comparable information.
2. Download the stock recovery file here: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img , place it in the Fastboot/ADB folder and open CMD again, if you haven't already, in the Fastboot/ADB folder and type ''Fastboot flash recovery ville_recovery_signed.img''
Let the file flash and when it's done type ''Fastboot reboot-bootloader''
3. After the short reboot choose Clear Storage. Your phone might try to boot after this. just hold the power button + volume down to restart it into bootloader again. Then choose Factory Reset from bootloader menu. The phone might try to boot again after this but restart it manually into bootloader if it gets stuck.
4. After clearing storage and factory resetting go into Fastboot USB mode again and use CMD in the Fastboot/ADB folder again to flash your custom recovery file. I used TWRP 2.8.7.0.zip. This TWRP recovery is signed for HTC One S S4. The guide for the Viper ROM recommends the TWRP2.6.3.0 for phones with HBoot 2.15, and TWRP2.6.1.0 for Hboot 2.16 phones.
The command for flashing this file is ''Fastboot flash recovery twrp-2.8.7.0-ville.img''
5. After flashing the custom recovery reboot bootloader with the command ''Fastboot reboot-bootloader''. Then after the short reboot go into recovery from bootloader.
6. At this time your SD card should work. Choose to mount USB from the ''Mount'' menu in TWRP. Attach the USB cable if you haven't already. Transfer your ROM.zip file to your SD card with this method.
( I used the Viper ROM found here: http://venomroms.com/htc-one-s/ )
7. After the transfer is complete choose ''install from zip'' in TWRP and choose the ROM.zip of your choice.
( I choose the Viper_One_S_3.2.0.zip file and chose the ''full wipe'' option, removing apps I didn't want etc. )
8. After installation let the phone work it's magic for like 10-15 minutes if necessary. It'll hopefully boot into the new system in time and you can complete the setup
---
The importance is that the stock recovery steps up til I flashed TWRP again fixed the SD card error. There's more fixes you could try if this didn't work and they can be found here: http://forum.xda-developers.com/showthread.php?t=2086156
I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...
Rapier said:
I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...
Click to expand...
Click to collapse
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked Thanks by the way ^^
HTC-One-User said:
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked [emoji14] Thanks by the way ^^
Click to expand...
Click to collapse
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...
Rapier said:
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hmm... My SD card actually got un-mountable and messed up after having stock ROM and just choosing to do a factory reset in the bootloader. That is when my problems started! But now after testing just this recovery and clearing storage, factory rest, flash new TWRP in exact that order fixd my issue. If I would factory reset before clearing storage and cache it would do nothing for me. It's weird but now it's ok and works ^^
Should have made a video of me restoring my phone to youtube so others can see to O.O
Edit: Made one here. it's not in awesome quality but it shows the whole process https://www.youtube.com/watch?v=_emclhywhlw
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?
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,