Related
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
boot part is not backup when using Backup / Restore.
Update 1 : Cache is mounted at start
Installation instructions :
Download : update.zip
- Copy the update.zip to a sdcard
- Follow the same procedure as explain in this post for the FolioMod
- Don't need to wipe.
- After reboot, enter recovery again to see the change
Click to expand...
Click to collapse
Usage :
- ( VOL + ) and ( VOL - ) key to highlight the menu
- ( HOME ) key to select
Click to expand...
Click to collapse
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
wolfx said:
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
partitions do not mount automatically at startup
boot part is not backup when using Backup / Restore.
Installation instructions :
Usage :
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
Click to expand...
Click to collapse
this will be so great, good joob and keep em comming. Next stop Gingerbread
Installed it just aminute ago worked great. I played around a bit, i formated system, data, cache and dalvik cache. I also tryed format boot but that was a no go. In the first clockwork 3 releases there was also this problem with boot. i cant remember if it was the same error, but its fixed now so that it works correct. I also flashed FolioMod from clockwork iwth out any problems. Really nice work
Great Job!! Now we just need some AOSP/CM7 love
Can I use it with stock rom too? Tnx
Great work thanks alot for taking the time to do this
girello71 said:
Can I use it with stock rom too? Tnx
Click to expand...
Click to collapse
I don't try backup / restore (nandroid) with stock rom maybe it work, but when i try to flash stock rom it skip the different part and don't write anything.
However, what could be interesting if backup / restore work is to make a backup of a fresh install stock rom with the last update include.
boqonx said:
Great Job!! Now we just need some AOSP/CM7 love
Click to expand...
Click to collapse
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Of course dude, take your time and slowly churn that tasty gingerbread dough
wolfx said:
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Click to expand...
Click to collapse
Finaly, one more rom builder. We need some options to choose from. Wish you the best of luck. And if you dont mind, maybe from time to time post progress on your work. If you need some beta testing, im there
Back to square 0
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
If you delete the update.zip for clockwork recovery you will have normal recovery. When installing clocwork you pu the zzip to root of exterenal sd card boot to recovery do system update, device reboots, now you have to do the system update again, your now in clockwork recovery
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
Not sure you bricked it, you can use the fastboot method to flash the recovery again, then you can use the recovery to flash a full rom.
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
boqonx said:
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
Click to expand...
Click to collapse
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
wolfx said:
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
Click to expand...
Click to collapse
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
wolfx said:
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
Click to expand...
Click to collapse
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
nickwarn said:
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
Click to expand...
Click to collapse
Rom manager don't work with this recovery for now, official support must be added by Koush in rom manager before. I will commit the source to him when recovery is finalized.
Butchi said:
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
Click to expand...
Click to collapse
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
- start your folio in fastboot mode and plug in. Win will not find the right driver to use
- Force driver installation : click update driver -> have disk -> point to "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Choose bootloader driver
After this you normally can use fastboot place in : <your-android-sdk-folder>/tools
For the recovery.img you can use the one include in the update.zip or one from FolioMod.
Hope it can help you
I am still not there...
Again thanks for all the help and support
OK I installed the SDK (and the JRE as it was also a requirement). But i did not find the USB driver so far (which is strange because i had connected the folio with the PC earlier).
While doing all that i discovered that somehow the ClockworkMod Recovery was installed correct. I could get the expanded ClockworkMod menu. (Using the power button and simulteaneous the Vol+ button within the 3 sec. And whatever i selected update or recovery, i got to the ClockworkMod menu.) This looked promissing.
So i put an update.zip on the sdcard (dextermod 1.3b).
In the menu i selected 'apply sdcard:update.zip'. After this i got the screen (white text) Confirm install? THIS CAN NOT BE UNDONE and (yellow text) 7 lines with '-No', one line with '-Yes - install /sdcard/update.zip' and 3 more lines with '-No'.
After selecting the 'Yes' line i got the following messages:
--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Strange enough, even after the update was aborted, the system started again after i selected to reboot in the ClockworkMod menu. Wow. Who knows what happened may explain this. But nice for me the system works again (till the next time).
Looking very nice. Just flashed it and made a backup
Edit: February 2012: please disregard ALL information below this red text. ROM Manager now supports the Huawei U8160, and will flash the official recovery build from the app. See the Getting Started with ROM Manager & ClockworkMod section in this post.
ClockworkMod Recovery for Vodafone Smart (Huawei U8160)
Current release - v0.1 - 12 September 2011 [CWM Ver. 4.0.1.5]
What is ClockworkMod Recovery? From AddictiveTips:
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
Click to expand...
Click to collapse
Installation - Fastboot Method:
Use this method if you have never installed a build of ClockworkMod before.
Download the Android SDK for your operating system [Windows users are recommended to download the .zip version].
Extract the fastboot / fastboot.exe file from the tools folder of the Android SDK zip file to a folder on your computer.
Download the latest zip release of ClockworkMod using the link(s) below.
Open the ClockworkMod .zip file and extract the recovery.img file to the same folder as the fastboot / fastboot.exe binary.
Reboot (or turn your phone one) whilst holding the power and volume down keys. Your phone will now be in "fastboot" mode.
Open a terminal or command prompt, and run the following commands:
Note: these are example instructions for a Windows user who has extracted the fastboot.exe and recovery.img to C:\VodafoneSmart. Adjust the folder path to wherever you extracted these files.
Code:
cd C:\VodafoneSmart
fastboot flash recovery recovery.img
fastboot reboot
Installation - ClockworkMod Method (zip):
Use this method if you already have ClockworkMod installed, and you wish to update the version that already exists on your phone.
Download the latest zip release using the link(s) below.
Transfer the .zip file to your SD card. Do not extract the .zip file - only copy it.
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes. Reboot and enjoy!
Usage:
To access ClockworkMod recovery, any one of the follow methods will work:
If you are running a build of CyanogenMod, choose the Recovery option from the reboot menu;
Run "adb shell reboot recovery" on any rooted ROM;
Reboot your device whilst holding the power and volume up keys.[/li]
Once you've entered ClockworkMod Recovery, you will be presented with several options (some familiar, some not). I won't try to explain all of the options, as there are better guides on the internet (example: the AddictiveTips site above). However, these are the ones you should really know about:
Wipe data/factory reset - same as before
Wipe cache partition - same as before
Install zip from sdcard -> choose zip from sdcard - this is the new method you will be using to flash ROMs and update packages
Backup & restore - this menu lets you perform a full backup or restore of your boot, /cache, /data/ & app2sd partition (which is compatible with mad2sd)
Mounts & storage -> mount USB storage - this lets you enable UMS mode to copy update packages (if you forgot to transfer before rebooting into recovery)
Advanced -> partition SD card - this lets you easily partition your SD card for use with mad2sd or any third-party app2sd solutions. It lets you select the size for the EXT4 partition as well as swap. MAKE SURE TO BACKUP ALL DATA ON YOUR CARD BEFORE USING THIS OPTION.
Changelog:
[CWM Ver. 4.0.1.5] v0.1 zip - 12 September 2011
First release.
Hi, I've been trying this guide and am having trouble with both methods.
Fastboot Method
I get into fastboot mode (where it's just at the hourglass screen), and type in "fastboot flash recovery recovery.img". The command prompt just says "Waiting for device", and never updates.
ClockworkMod Method
I installed the CWM I got off the Android Market, and then tried to reboot into recovery mode (both by rebooting through CWM and by pressing Volume+Up & Power). I just end up waiting at the hourglass screen like when it's in fastboot mode.
Any idea what I'm doing wrong?
for fastboot try without battery inside (only usb) works for me
if fastboot wont work try methode 3. http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
with extractet recovery.img from zip (http://forum.xda-developers.com/showthread.php?p=17496869)
jajajim said:
for fast boot try without battery inside (only usb) works for me
Click to expand...
Click to collapse
Tried that too; didn't work.
Thanks, worked for me with fastboot on u8180
zodac01 said:
Fastboot Method
I get into fastboot mode (where it's just at the hourglass screen), and type in "fastboot flash recovery recovery.img". The command prompt just says "Waiting for device", and never updates.
Click to expand...
Click to collapse
That happens to me too... I also noticed that in device manager is missing driver for Android 1.0? I don't know what to do next. Someone knows? Thanks
EDIT: It works ... download Pulse_Drivers_xp_w7_w764.zip from dc-unlocker (sry can't post link).
EDIT: It works ... download Pulse_Drivers_xp_w7_w764.zip from dc-unlocker (sry can't post link).
Click to expand...
Click to collapse
for linux users??
just a note, the U8160 has a different USB hardware ID when in fastboot mode, and so inside 70.android.rules you need to add "12d1" and "18d1"
18d1 is the fastboot USB id and 12d1 is the adb USB id
This is for linux btw.
i've two questions for subpsyke:
it's planned update to cwm recovery 5?
Why don't knowledge Rom Manager cwm recovery in your cyano release for U8160?
p.s
sorry for my bad english, i'm italian's users ...
thanks, needed this!
renegade_82 said:
i've two questions for subpsyke:
it's planned update to cwm recovery 5?
Why don't knowledge Rom Manager cwm recovery in your cyano release for U8160?
p.s
sorry for my bad english, i'm italian's users ...
Click to expand...
Click to collapse
Yea i got this problem too, in ROM manager, this recovery isnt detected, any ideas on how to get it?
EDIT: I flashed the IDEOS recovery through rom manager then flashed back this recovery, and now it works like it should.
EDIT: done, thanks a lot
for pulse driver, turn on phone, then press power + volume down, then plug usb, PC will search for a driver
fastboot is just: power button + volume down (and then it sticks on logo or hourglass) then open command prompt on pc
pulse driver:
http://www.mediafire.com/?l9zoonl8kygcejm
Hi there
Download the Android SDK for your operating system [Windows users are recommended to download the .zip version].
Extract the fastboot / fastboot.exe file from the tools folder of the Android SDK zip file to a folder on your computer.
Click to expand...
Click to collapse
I'm a windows user and i've downloaded the Sdk zip and there's no fastboot.exe on any of the folders... :|
Any suggestions?
Thanks in advance
jpcoke said:
I'm a windows user and i've downloaded the Sdk zip and there's no fastboot.exe on any of the folders... :|
Click to expand...
Click to collapse
Download android-sdk-windows-1.6_r1
The latest sdk doesn't have it
fastboot and recovery
http://www.wuala.com/freegroup/cyanogen/VodafoneSmart.zip/
u8160 cwm
iam havving problems around here
i need more instruction , i have the folder with recovery and fastbot ,but how to put tham on the phone ? i have rooted my device sucesfully iam stuck rebooting on recovery mode , i cant reboot as you show us , or enter in fastboot , please help me do it
aripelx said:
Download android-sdk-windows-1.6_r1
The latest sdk doesn't have it
Click to expand...
Click to collapse
cant seem to find this version of the sdk to download, anyone got a link?
thanks
I have a branded Vodafone Smart (U8160) and it stucks everytime at the hourglass screen. It won't get into recovery mode.
How do I fix this?
Edit: I haven't rooted it yet. Have I to do it before I could install CMW?
mcpossity said:
I have a branded Vodafone Smart (U8160) and it stucks everytime at the hourglass screen. It won't get into recovery mode.
How do I fix this?
Edit: I haven't rooted it yet. Have I to do it before I could install CMW?
Click to expand...
Click to collapse
for cwm it's power button+volume UP
fastboot power button+volume DOWN
it's easy to root with gingerbreak v1.2
---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------
asidhowz said:
cant seem to find this version of the sdk to download, anyone got a link?
thanks
Click to expand...
Click to collapse
man, I have posted the link just up
Thanks, worked like a charm
This guide, for the Lenovo Tab 3 8" (TB3-850F), has 3 purposes:
1. Unlocking your bootloader;
2. Installing TWRP custom recovery;
3. Attaining superuser privileges (root) of the stock OS.
NOTE:
I can attest & confirm that this method has worked 100% on at least 7 devices of my own. Please read and re-read the instructions carefully before proceeding. If you follow this tutorial exactly as delineated, you should have no adverse issues in unlocking your bootloader, flashing custom recovery, or achieving systemless root of the stock Android OS.
MENTIONS & THANKS:
Based on XDA Senior Member @Hemphiz's groundbreaking root and custom recovery for this device, I am now revising this thread wth improved step-by-step instructions based on members' feedback and experiences. Thanks @Hemphiz for your research, assimilation of necessary files, and for breaking ground on this tablet. Thanks also for your granting me ownership of the thread. Your contributions are greatly appreciated by many. Thanks to the great @Chainfire for his flashable systemless rooting script. Thanks to @jemmini for compiling TWRP for this tablet. Finally, thanks to the many members who have tested this guide and provided much needed input & user experience.
DISCLAIMER: As always, please be reminded of the risk involved with flashing a custom recovery and/or attempting to attain superuser privileges of your Android OS. I will not be held responsible for devices bricked or otherwise rendered inoperable as a result of this thread. You assume full responsibility for any good or bad which may result from proceeding any further. However, with that having been said, I will provide any and all support possible. Read and follow the foregoing steps thoroughly and carefully prior to proceeding. NOTE: THIS GUIDE IS INTENDED ONLY FOR THE LENOVO TAB 3 8"/TB3-850F.
REQUIREMENTS:
1. Minimal ADB & Fastboot v1.4 (or newer) Windows Installer;
2. Windows PC or laptop (Mac may be used; however this guide is intended for Windows 7 and newer operating systems);
3. Official Lenovo USB Device Driver v1.1.21;
4. TWRP v3.0.1 for the TB3-850F;
5. ADB Driver Installer for Windows;
6. SuperSU v2.82-SR5 flashable zip.
(All files, drivers & utilities for this process are available in the below download link)
DOWNLOAD LINK: https://drive.google.com/folderview?id=1l-YN5aXmjDF3O1bHxFHVIxLKuvd847Q9
INSTRUCTIONS:
1. First and foremost, unlocking the bootloader is necessary. Also, this step is a good place to make some requisite preparations. Power on your Tab 3 and select SETTINGS once booted up. Go to ABOUT DEVICE, find BUILD NUMBER, and tap it 7 or 8 times until DEVELOPER OPTIONS is enabled. In DEVELOPER OPTIONS, tick OEM UNLOCKING and USB DEBUGGING. On your PC, install the Minimal ADB & Fastboot utilities, the ADB Driver Installer, and the Lenovo USB Driver Installer. Connect your Tab 3 to your PC with the supplied (or quality equivalent) OEM charging/syncing cable. Open a command window in your ADB/Fastboot directory, by holding SHIFT and right clicking in the desired path. In the command window, type: adb devices & press RETURN. If your device is connected properly, the command window will display a string of numbers/letters, which represent your device's serial number. If your serial number does not appear in the window, try changing USB ports, change syncing cables, or try reinstalling the ADB Drivers. Once properly connected, type adb reboot bootloader & press RETURN. Your tablet should boot into Fastboot Mode, which will be displayed in white bold letters on your device's display once complete. Once in Fastboot Mode, type fastboot oem unlock & press RETURN. Your device will prompt you to press Volume Up to proceed with unlocking the bootloader, or Volume Down to cancel the process. WARNING: UNLOCKING THE BOOTLOADER AUTOMATICALLY INITIATES A FACTORY DATA RESET. YOU WILL LOSE ANY UNSAVED VIDEOS, MUSIC, PERSONAL FILES, ETC.
2. Now that your bootloader is unlocked, you are ready to flash TWRP. Download the twrp.img file from my link and save it to your PC in the ADB/Fastboot path/directory. Also, save a copy of the file on your device's internal storage or external micro SD card. Since your device underwent a factory data reset, you will again need to enable DEVELOPER OPTIONS & tick OEM UNLOCKING & USB DEBUGGING as you did in Step 1. When you have done this, again open a command window, ensure a proper connecion, & type adb reboot bootloader & press RETURN. Once in Fastboot Mode, type fastboot boot twrp.img & RETURN. EXTREMELY IMPORTANT NOTE: this device's boot image is secured with dm-verity. Leave the /system partition as read-only when prompted by TWRP. Mounting /system as read/write at this point will result in a boot loop. Flashing SuperSU, as outlined in Step 3, will patch dm-verity and fix this.
From the TWRP main menu, select INSTALL, select the image file option in the bottom right of the screen, navigate to the location where you saved twrp.img in device storage or external storage, and commence the installation. Be certain and correctly choose "recovery" when prompted by TWRP. Now select REBOOT, then RECOVERY. Your TWRP custom recovery should now be successfully installed on your device's /recovery partition.
3. Now, it is time to root this tablet. Download & save a copy of the SuperSU v2.82-SR5 zip file to the tablet's internal or external storage. In TWRP main menu, select INSTALL & navigate to the saved SuperSU zip. Commence with installation. Systemless root mode will unpack, modify, repack and flash the patched boot image. Once done, reboot system. Your Android OS should now have full systemless root, and the /system partition may now safely mount as read/write.
TROUBLESHOOTING:
In the event your device becomes stuck in a bootloop, or is otherwise failing to boot into the OS, the following is a link to my stock firmware images thread for this device. NOTE: the following link will be beneficial only if your device successfully boots into Recovery/Fastboot mode. This link provides stock partition images of /boot, /recovery, /logo & /system. Typically, flashing the stock boot & system images will get you up & running again, and will restore the Android OS to stock condition.
https://forum.xda-developers.com/an...o-tab-3-8-tb3-850f-android-6-0-t3593043/page5
In the unfortunate event that you encounter a brick (your device fails to boot into the OS or Recovery Mode), please visit @r&xp's thread on unbricking your device & restoring it to factory stock condition. Members using his thread be sure to thank @r&xp. His collection of necessary files & comprehensive instructions has saved many, many bricked tablets. https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
What is your software version?
Mine is TB3-850F_160412
i have a pending 51MB update ,do i complete all updates or ignore them and root?
Also whats the procedure to unroot if i want to get the updates later?
viv_jen said:
What is your software version?
Mine is TB3-850F_160412
i have a pending 51MB update ,do i complete all updates or ignore them and root?
Also whats the procedure to unroot if i want to get the updates later?
Click to expand...
Click to collapse
Look for build number. It's usally best to determine things. I'm on TB3-850F_S100030_161209_ROW
I took the latest OTA before flashing twrp else ota will fail due to the recovery being modified. For unroot there's an option in Superssu to unroot. I would personally create a full backup via twrp before rooting, so you can revert to it if you wish
this bricked my tablet
nox13666 said:
this bricked my tablet
Click to expand...
Click to collapse
Well you must've done something wrong. It's pretty much fool proof
Hemphiz said:
Well you must've done something wrong. It's pretty much fool proof
Click to expand...
Click to collapse
Great thread. OP's instructions & downloads work flawlessly. Thank you @Hemphiz
Thanks for the guide
Thanks for the guide!
Everything works but when I reboot into recovery I just get the dead android with no command under him..
I tried two times with same result Fastboot reports twrp flashes ok
Any ideas?
Thanks
Xecsc said:
Thanks for the guide!
Everything works but when I reboot into recovery I just get the dead android with no command under him..
I tried two times with same result Fastboot reports twrp flashes ok
Any ideas?
Thanks
Click to expand...
Click to collapse
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.
MotoJunkie01 said:
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.
Click to expand...
Click to collapse
I was running into the same issue after flashing twrp.img via fastboot, it kept coming up with no command when booting into recovery. Followed MotoJunkies advice and booted into twrp.img instead of flashing and installed it that way, now my device is rooted. Thank you Hemphiz and MotoJunkie.
MotoJunkie01 said:
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.
Click to expand...
Click to collapse
Thanks worked perfect!
this did not work for me. now my tablet is in boot loop. keeps going to team win. trying to trying to mount storage and then back to the regular boot. over and over.
figgenhoffer said:
this did not work for me. now my tablet is in boot loop. keeps going to team win. trying to trying to mount storage and then back to the regular boot. over and over.
Click to expand...
Click to collapse
Hmmm. Did you execute "fastboot oem unlock" first to unlock your bootloader? It sounds as though you are saying TWRP installed correct? When you try to boot into the OS, you are getting reverted back to TWRP?
i did that. i had teamwin recovery. then installed the superuser.zip and it keeps looping
figgenhoffer said:
i did that. i had teamwin recovery. then installed the superuser.zip and it keeps looping
Click to expand...
Click to collapse
I see. The superuser zip is likely the culprit. Which one did you use? Did you use the one in the link? Here is a link for the stock boot.img for this device. Install it in fastboot mode by typing "fastboot flash boot boot.img". Try booting after flashing the stock boot image and also try reinstalling the boot script.https://drive.google.com/file/d/0B7-zQU1VihD3ZGZBRzU1Nm1PYjA/view?usp=drivesdk
Note: you will need to rename the downloaded file to " boot.img"
Thanks for the guide. Tried to do this on the Lenovo TAB3 10 Business, but no success
I can connect using the tools and enter into fast boot
When I flash, it seems successful, but after shutdown, start with power, volume buttons, I don't see the TWRP, but instead a kind of test app
When i use the other method to boot into the twrp, the Lenovo, boots normal, not into TWRP
Any ideas?
smouge said:
Thanks for the guide. Tried to do this on the Lenovo TAB3 10 Business, but no success
I can connect using the tools and enter into fast boot
When I flash, it seems successful, but after shutdown, start with power, volume buttons, I don't see the TWRP, but instead a kind of test app
When i use the other method to boot into the twrp, the Lenovo, boots normal, not into TWRP
Any ideas?
Click to expand...
Click to collapse
When you initially connect your Tab3 to PC and open a command window, did you execute both recognition tests? "adb devices" and "fastboot devices"? I am just curious as to whether your device is being recognized by both the fastboot and the adb platforms. Please try this and let me know.
This i what I with Lenovo Tab3 10 business
>adb devices
List of devices attached
8HSKCMT4PJIZ9HDZ device
>adb reboot bootloader
>fastboot devices
8HSKCMT4PJIZ9HDZ fastboot
At this moment, on the Lenovo Android you only see a smaal line at the bottom: =>FASTBOOT mode...
The fastboot does nt deisplay errors, but after the following command, the tablet just boots in the normal Android. On the Android device I also saw quickly the message "USB transferring OK" before booting
>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.192s]
booting...
OKAY [ 0.073s]
finished. total time: 1.269s
---------- Post added at 09:20 AM ---------- Previous post was at 09:03 AM ----------
On the Lenovo TAB3 10 Business I can also do the following:
Holding Vol up + Power when off and then releasing power when you see the Lenovo logo will bring up the following menu:
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot] <<==
With the recovery mode I see the following:
Android Recovery
Lenovo/LenovoTB3-X70L/TB3-X70L
6.0/MRA58K/TB3-X70L_S000020_170209_ROW
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Backup user data
Restore user data
Root integrity check
Mount /system
View recovery logs
Power off
smouge said:
This i what I with Lenovo Tab3 10 business
>adb devices
List of devices attached
8HSKCMT4PJIZ9HDZ device
>adb reboot bootloader
>fastboot devices
8HSKCMT4PJIZ9HDZ fastboot
At this moment, on the Lenovo Android you only see a smaal line at the bottom: =>FASTBOOT mode...
The fastboot does nt deisplay errors, but after the following command, the tablet just boots in the normal Android. On the Android device I also saw quickly the message "USB transferring OK" before booting
>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.192s]
booting...
OKAY [ 0.073s]
finished. total time: 1.269s
---------- Post added at 09:20 AM ---------- Previous post was at 09:03 AM ----------
On the Lenovo TAB3 10 Business I can also do the following:
Holding Vol up + Power when off and then releasing power when you see the Lenovo logo will bring up the following menu:
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot] <<==
With the recovery mode I see the following:
Android Recovery
Lenovo/LenovoTB3-X70L/TB3-X70L
6.0/MRA58K/TB3-X70L_S000020_170209_ROW
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Backup user data
Restore user data
Root integrity check
Mount /system
View recovery logs
Power off
Click to expand...
Click to collapse
Chances are the twrp isn't compatible with your device. Although the hardware all looks the same. Problem is my knowledge with Android development isn't that great. I simply read in my spare time. The twrp I found for this device on a previous xda thread, but it was more of a Q&A so I made this guide to simplify things for people. I do know that the original twrp was made here http://4pda.ru/forum/index.php?showforum=583
Worked great for me thanks. Had a few problems off at first but managed to get it done. First boot did take a little while but after that all is great
Touch is Working Now. (Finally) with OTA Support only for zero5 indian varient
Join Telegram group for further development : https://telegram.me/infinixzero5
This is Ported TWRP Recovery from a same Mt6757 chipset model. which i used to port it for our Infinix X603.
Thanx @topjhonwu for magisk.
Thanx for @majorkid for making OTA supportable
TWRP for non indian and global version for necessary changes. (Need to test)
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Unlocking Bootloader
- Make sure your Bootloader is Unlocked. If already unlocked jump to how to flash.
Process to unlocking.
1. go to settings/about phone/build number (tap build no for 7 time now developer option available in settings)
2. go to developer option turn on usb debugging and OEM unlocking.
3. then go to pc download and extract and copy adb fastboot driver folder in Drive C. (or install form net.)
4. Go in fastboot folder which is copied to C. press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
5. Click it, A cmd or power shell window will open.
type "adb devices" - it show some no of your device just give permission from your phone screen)
type "adb reboot bootloader" your phone reboot in bootloader mode.
type "fastboot oem unlock" follow onscreen instruction on phone, press volume + to confirm. thats it but it will erase all your data.
Reboot phone by pressing power button for 10 sec. setup it as temporarily.
Flashing of TWRP
1. Download the Latest TWRP Recovery Image and extract it (Attached). Use correct version for your device for OTA support.
For India (Indian) For Global (Global)
(Insert a SD card in your phone to take stock boot.img backup it will required for OTA in Future.)
2. Go in adb fastboot folder which is copied to C. copy twrp_recovery.img here then press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
3. Click it, A cmd or power shell window will open.
4. Flash it via fastboot cmd (fastboot flash recovery Twrp_recovery.img) don’t use bracket.
It will flash recovery on your phone. Now type fastboot reboot in cmd window and press and hold vol+ button and hit enter.
Phone will reboot in twrp recovery.
Note : After flashing first time it will ask for password due to phone is encrypted.
a. just cancel it and allow to modify system by swiping arrow at down and select 2nd last option at right side then select globe icon on right and chose your language English.
(First take Boot.img backup Via backup option in TWRP in SD Card. (bcz internal storage shows 0 mb here at this movement.) It will use for OTA so save it.
b. then flash magisk manager.zip file attached here. (it will remove dm-verity and force encryption from boot.img) and give root access.
c. then go to Wipe and select format Data it will erase all data on your internal storage. remember it will erase your data in ext4 format so go to wipe advance select data and change file system to f2fs. Ext4 data not supported by kernel so you got loop to recovery so It must to repair data in f2fs.
d. Done Reboot to recovery and you got mounted storage.
Another Method.
- Flash it via SP flash tool. (use version 5.1744 recommended)
How to use SP flash tool :
Install Vcom media tek driver on your pc.
More detail and download available on following link
https://spflashtool.com/
IF ANYONE GOT LOOP IN BETWEEN TO RECOVERY MEANS PROCESS NOT FOLLOWED PROPERLY.NOT BOOTING PHONE JUST FLASH STOCK RECOVERY. YOUR PHONE WILL BOOT THEN DO PROCESS AGAIN.
OTA-
1. When ota available just download it. Don’t start flashing.
2. Location of OTA downloaded file in Root so use any root file explorer.
3. File can be found in :-
a. Root/cache/update.zip
b. Root/data/data/com.google.android.gms/app_download/update.zip
4. Copy file name is update.zip to your sd card or phone memory.
5. Reboot to recovery and flash first stock boot.img which you already taken backup and saved before when flashing twrp.
6. now flash update.zip via TWRP (dont reboot after flashing otherwise you will currept your system)
7. After flashing update.zip, first again take backup of your boot.img for future ota update.
8. After taking backup of boot.img flash magisk.zip and reboot. (If you did not flash magisk then your data again encrypted and u lose all data)
6. Done you are on latest version.
Note:- Always remember to flash magisk.zip at last before reboot.
OTA SUPPORTABLE TWRP Link for zero 5 global varient by @majorkid -
https://androidfilehost.com/?fid=890129502657578792
OTA SUPPORTABLE TWRP Link for zero 5 pro global varient by [MENTION=7078341]majorkid[/
https://androidfilehost.com/?fid=890129502657578807
Update: Last updated on 27/01/2018 (With almost all stock stuff with OTA support)
Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)
XDAdeveeloopers said:
Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)
Click to expand...
Click to collapse
flip screen was old but i updated it with working twrp. is it showing vernee mix 2 name on top?
can you send screen shot.
its working perfectly.
just match the zip size which you downloaded (if it is 13.23 mb then it is old)
download current version attached above is 15.31 mb in size.
Screen Shot is also updated
Let me know your success.............................
flipped screen fixed !
Ok, now it's not flipped but the touch is still disabled
again, thank you for your efforts. I've attached the screenshots. it tells me to enter the password but the touch is disabled and i couldn't type anything.
At this stage only cancle button will work. Dont type anything just press cancle button.
It shows next screen.
I chek if issue is there.
Cancle is not working too
XDAdeveeloopers said:
Cancle is not working too
Click to expand...
Click to collapse
just use it as temp. bcz after flash touch not working.
Touch is disabled in kernel for recovery partation by infinix.
for temp use cmd.
fastboot boot recovery.img
will update soon..........
when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?
XDAdeveeloopers said:
when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?
Click to expand...
Click to collapse
Read OP carefully. You need to format data partition completly first time and need to patch boot img via lazy flasher.
Showing 0mb bcz it is encrypted. You can use memory card.
If you want root then go for magisk root till recovery updated.
OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work (extracting ramdisk failure aborting) , isn't there any way to install supersu in order to get apps working correctly?
XDAdeveeloopers said:
OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work, isn't there any way to install supersu in order to get apps working correctly?
Click to expand...
Click to collapse
which busybox your trying and what error.
currently supersu have some error with new devices. which version you tried it should be 2.82 or above.
I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk
XDAdeveeloopers said:
I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk
Click to expand...
Click to collapse
Use busybox form playstore stericson.
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Finally the Touch is updated and working now.
I enabled touch in kernel which is disabled for recovery partition.
XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
System is encrypted.
Use magiskmanager beta 14.5 or flash lazyflasher via twrp then one time you need to wipe data partition.
Always remember when you flash orignal boot.img you need to flash lazyflasher or magisk otherwise your system will become encrypted again.
Thank you, now touch is working perfectly <3
XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
you can use ndk busybox from magisk app there is option download module.
But currently there is problem with module with this phone. the data partition is in F2FS format and its kernel is not handling f2fs properly.
TWO option for use magisk module.
1. wait for kernel update via infinix. or
2. format data partition as Ext4 from twrp.
Super su does not work correctly with f2fs currently.
But when I format data partition it resets my phone
XDAdeveeloopers said:
But when I format data partition it resets my phone
Click to expand...
Click to collapse
yes formatting data will reset it.
Hello,
I got a Xperia XZS SO-03J (Japan Docomo Variant). Anybody got any ideas to root this device and any custom roms. Already searched the forum but no avail. Thank you for your help.
Japanese cellular version usually unable to unlock bootloader.but still some phones can unlock. if you have twrp ,you can install some rooted ROMs modified from official ROM.(btw you have to find a ROM can install without unlock bootloader)
sinkoo1979 said:
Hello,
I got a Xperia XZS SO-03J (Japan Docomo Variant). Anybody got any ideas to root this device and any custom roms. Already searched the forum but no avail. Thank you for your help.
Click to expand...
Click to collapse
if you have docomo ubl yes you can patch kernel manual , because it's different from Au,Global,Softbank
I've tried with x compact docomo ubl yes
I think first of all need to check whether the bootloader is unlockable or not
if you can UNLOCK the Japanese Xzs then
you can use this TWRP
https://dl.twrp.me/kagura/twrp-3.2.3-0-kagura.img.html
there is a depate that you can cross flash XZ's Android 6 to extract DRM keys! but i am not going to go that, as soon as you UNLOCK you bootload, TA partition will be GONE..
what is your build number?
download your build from FLASHTOOL---> Xperfirm and send me KERNEL.sin and i will send you the modded kernel
rest PROCESS you can Read (carefully) at
https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
its for XZ but applies to XZs too!
YasuHamed said:
if you can UNLOCK the Japanese Xzs then
you can use this TWRP
https://dl.twrp.me/kagura/twrp-3.2.3-0-kagura.img.html
there is a depate that you can cross flash XZ's Android 6 to extract DRM keys! but i am not going to go that, as soon as you UNLOCK you bootload, TA partition will be GONE..
what is your build number?
download your build from FLASHTOOL---> Xperfirm and send me KERNEL.sin and i will send you the modded kernel
rest PROCESS you can Read (carefully) at
https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
its for XZ but applies to XZs too!
Click to expand...
Click to collapse
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Amirai17 said:
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Click to expand...
Click to collapse
requesting you please
send me also these three files
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
there will be system.sin in that ftf,
convert it using FLASHTOOL > tool > sineditor > selected system.sin and click extract data, it will make 6gb file SYSTEM.ext4, open it with 7zip and locate the above three file and add in the goodle drive PLZ
Amirai17 said:
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Click to expand...
Click to collapse
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
Thanks for the kernel mod, you mod it so fast that's so amazing
Anyway i will try it tomorrow, pray fo the kernel got stable
Before i use this kernel on this thread https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
And i got unstable performance. Trying use kernel auditor not effect it and i decide to flash it back to normal again.
Amirai17 said:
Thanks for the kernel mod, you mod it so fast that's so amazing
Anyway i will try it tomorrow, pray fo the kernel got stable
Before i use this kernel on this thread https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
And i got unstable performance. Trying use kernel auditor not effect it and i decide to flash it back to normal again.
Click to expand...
Click to collapse
I dont know about that thread
Seems like different process
Anways plz do try this and let me know
YasuHamed said:
I dont know about that thread
Seems like different process
Anways plz do try this and let me know
Click to expand...
Click to collapse
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
This is a good news! , good to know that you were able to Root it.
i am sure you will find good performance.
nighlight makes your screen TINT different (reduces blue) which makes it easier on eyes while you browsing in night or from bed. blue light hurts eyes and brain and increases sleeplessness.
a shortcut toggle button next to FLASHLIGHT will appear (if arent already in your build) and display setting will have NIGHLIGHT FEATURE ENABLED- you can control the INTENSITY of this filter according to your needs
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
I have the same phone xzs docomo so-03j on the same build, is it ok if i flash this too or will it brick my phone? thank you
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
How has it been? the performance? mine heats up akot when gaming and is even slower than my Softbank xperia xz I would like to root mine as well if it is good and if it is possible
other build number
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
why with different build number?
i have build number 41.3.B.1.113
or can i flash to global rom and what the side effect?
plz tell me how you root your xz. my xz 601so with allowed yes
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
Temporary root is now possible on the Xperia so-03j, I personally tested a few minutes ago.
Check this comment for instructions. And here instructions to create a launcher.
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
can i root my Xperia XZs AU version with these files that are attached in this post, or do i need different files ?
thank you @YasuHamed
5crypt said:
can i root my Xperia XZs AU version with these files that are attached in this post, or do i need different files ?
thank you @YasuHamed
Click to expand...
Click to collapse
Those files seem appropriate for stock rom release 41.3.B.1.140., so don't try unless you're running that specific version (quite outdated if you ask me).
But first make sure your bootloader can be unlocked. If that's the case, you may want to install a recent rom with root support, or check the guides for rooting stock rom. Be aware that with unofficial roms you might lose camera quality or have no cam support at all.
If you're stuck with an unlockable bootloader (like myself) your choices are much more limited. My current approach is having latest stock, disable bloatware apps, and use temporary root when needed.
thank you @dinosaur99 for your quick response, i got the one that cannot be unlocked, so i'm using the temp root method, but do you know how to gain temp root access without using adb (laptop or computer), and can i automate the temp root every after reboot ?
again thank you for your response, and looking forward from you
5crypt said:
thank you @dinosaur99 for your quick response, i got the one that cannot be unlocked, so i'm using the temp root method, but do you know how to gain temp root access without using adb (laptop or computer), and can i automate the temp root every after reboot ?
again thank you for your response, and looking forward from you
Click to expand...
Click to collapse
Good question! I wanted to create a launcher too!
So I just followed these instructions and it works fine. First you need to perform the following commands from computer (have a copy of the exploit file in working directory):
Bash:
adb push su98-memory-kallsyms /data/local/tmp/
adb shell
# Run this from inside the shell
chmod +x /data/local/tmp/su98-memory-kallsyms
/data/local/tmp/su98-memory-kallsyms
chcon u:object_r:system_file:s0 /data/local/tmp/su98-memory-kallsyms
Now reboot the phone, and the file /data/local/tmp/su98-memory-kallsyms should still be there. On your favourite console app, create a new terminal launcher/profile/whatever it's called and name it "Root terminal", then make it so it runs this command on shell login:
Bash:
/data/local/tmp/su98-memory-kallsyms
Note there's a trailing <Enter> key at the end of the command. I use Connectbot and it was necessary.
Cheers!
Edit:
By the way, the last line would be the equivalent to "sudo bash" in a computer. That means you can write a script with the root commands to be executed upon reboot. Example launcher:
Bash:
/data/local/tmp/su98-memory-kallsyms /data/local/tmp/my-script