Related
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
AronR said:
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I did this a week ago, and what a carry on I had, I thought i bust my tablet
I downgraded to .370 version using official firmware with flashtool, then I rooted using DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit (this is the easy part)
Then I used .109 version firmware (stripped ftf and flashable zip) - this is where it went wrong as I got into a boot loop
http://forum.xda-developers.com/showthread.php?t=2671276
I used both DE versions (German) for the flash/install - still works on UK tablet
I think there is a specific order to install busybox before or after dual recovery - this might be where it went wrong for me.
I also used an older version of dual recovery, (TabZ-lockeddualrecovery2.7.94-BETA.installer) and have yet to flash to the latest version
Sorry this is a bit muddled.
I just got my tab a couple days ago I guess I screwed up upgrading from 370 to 109. Following along closely to this thread
Sent from my SGP311 using Tapatalk
This is a guide that I wrote to enable root on Android version 4.3, build number 10.4.1.B.0.109 for SGP311. Follow at your own risk. I will not be responsible for damage to your Xperia Tablet Z! I am going by memory and XDA posts I have re-read.
Please read this first then follow the steps!!
1. Firstly you need to ensure you have the drivers installed for your tablet, so you could install Sony PC Companion http://www.sonymobile.com/gb/tools/pc-companion/
2. On your tablet make sure that Developer options is enabled (if not, press About tablet in the tablet settings menu several times), USB debugging is ticked and Verify apps over USB. Also turn on Unknown sources in Security settings
3. Assuming that the tablet is running version 10.4.1.B.0.109 you need to downgrade to version.370
4. Download and install Flashtool by @Androxyde http://www.flashtool.net/download.php - install this to your C: drive
5. Download the official .370 (I used SGP311_10.1.C.0.370 DE_Unbranded.ftf) firmware from here http://forum.xda-developers.com/showthread.php?t=2402863 thanks to @DevMark. This file should be placed inside the firmwares folder of Flashtool and thanks to @ donedos for his initial suggestion
6. Download the rooting kit from http://forum.xda-developers.com/showthread.php?t=2333566. Thanks to @DooMLoRD
7. It is suggested that a backup is carried out on the tablet as this flash/root will wipe the data from it – I never did this, as I was quite happy to install apps/.apk again, and I had a lot of crap on my tablet anyway
8. Open up Flashtool, power off the tablet, and plug the usb cable into the tablet.
9. With the tablet still turned off press the volume down button, and plug the usb cable into your PC, this should get your tablet into flash mode
10. There is a lightning bolt symbol on top left corner of Flashtool, click this, and two options should pop up. I think you click the top one; if so, you will be prompted to locate the .ftf file, select the .370 file. If this file is not visible, you probably need to select the second option that popped up!
11. The tablet should be flashing now, and takes a few minutes or so. Instructions will appear in Flashtool to unplug and power on your device.
12. It will take a while for your tablet to turn back on; when it does you might need to carry out the actions again in 2. above. Just make sure you are running firmware .370 now instead of .109
13. Now connect you tablet again to USB, device drivers might install again. Open up/extract DooMLoRD_Easy-Rooting-Toolkit_v17 and click the runme_win.bat file and follow the instructions – your tablet should now be rooted. Check for the Super SU app in your app list, or if it’s not there install from Play Store.
14. Download the file Xperia Tablet Z (SGP311) 10.4.1.B.0.109 VMo De from here http://forum.xda-developers.com/showthread.php?t=2671276, thanks goes to @bernddi . Extract the file so there are two files (SGP311_10.4.1.B.0.109_VMo De_stripped.ftf and SGP311_10.4.1.B.0.109_VMo De.zip)
15. Download and use this file http://www.winmd5.com/ to verify the md5 checksum matches the .109 files you downloaded.
16. If everything is okay, place the large zip file onto the root of your external memory card, and the .ftf file into the firmwares folder of Flashtool (later on don’t mix this file up with the .370 file)
17. Download the correct version of XZDualRecovery file for your tablet, – thanks to @[NUT]. I first tried the most recent version, but had problems with flash and root, so then I tried the older version TabZ-lockeddualrecovery2.7.86-BETA.installer. Files are linked from here http://forum.xda-developers.com/showthread.php?t=2261606.
18. Download and Install BusyBox from the Playstore, and run the app, then install again to your Tablet (using default options I believe) – this install failed first time for me, if same happends with you try again until it works
19. Connect your .370 rooted tablet to your PC, and run the DualRecovery file by clicking on install.bat – this will install the recovery to your tablet
20. Your tablet should power back on, or you’ll need to turn it on yourself. Make sure stuff works fine, you might need to carry out No. 2 again, I’m not sure
21. You should also have a file called NDR Utils on your tablet, if not install from the PlayStore, and run this. The option to boot into Philz Touch Recovery should be visible, select this option and reboot. You can reboot by pressing power up, while the tablet is turning on, but I have problems getting this to work. NDR makes it much easier
This is where it might get risky. It appears that the older version of DualRecovery does not have the option to verify the md5 checksum, but if the file winmd5free said the numbers match you should be okay
22. In recovery you need to select Install Zip, then select install zip from storage/sdcard1, then go to the zip file, and press it. The flashing of version .109 should begin – it takes a while
23. After the flash you must power off the device, DO NOT reboot
I believe this is where I got into a boot loop, and I am not certain how I got out of it. This link might help http://forum.xda-developers.com/showthread.php?t=2703882. Thanks to @Cat McGowan. When I finally got out of the boot loop, I started all over again from step No.8!
24. Open up Flashtool again, and flash the stripped ftf file like you did in No. 9 and No. 10
25. Follow the instructions to disconnect and power on your tablet, you should now have version .109 and still be rooted after the initial setting up of the tablet.
Please let this work!
If there is anyone reading this that spots an error or omission please post it
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
cirovi said:
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
Some root apps and recovery need it.
Sent from my SGP311 using Tapatalk
cirovi said:
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
actually it is already integrated in recovery package (/xbin/busybox), so there is no need to install it manually.
Well my tab went tits up a little while back, and I followed my guide and it worked
worked perfect for me... thank you very much
Help Needed
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
CentinelX said:
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Ok I managed to get out and install 370 again. But where did I go wrong?
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Hello guys, any ideas? Thanks!
jakeortega said:
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Click to expand...
Click to collapse
Hello guys, any ideas? Thanks!
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
es0tericcha0s said:
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
Click to expand...
Click to collapse
Thank you es0tericcha0s for this information.
What I'm trying to do right now is updating my SHV-e160s from 4.0.4 to 4.1.2 using Kies v2.6. Unfortunately, I'm getting this error "Failed to run firmware upgrade: unknown error.". Until now, I'm afraid to update my firmware manually as I don't have much knowledge to do that.
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Alright, I'll try these steps immediately and will comeback for the result. Thanks again.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Hello, sorry I forgot to ask, will this root my device? I'm afraid I might bricked it.
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
es0tericcha0s said:
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
Click to expand...
Click to collapse
Hello again es0tericcha0s, I haven't tried the instructions that you gave me yesterday as I'm still downloading the firmware, last night I encountered an issue after enabling my Bluetooth, something like "NFC Service has stopped." just keeps on popping up. So I turned off the bluetooth then restarted my phone, it went well for a while.
After that, I enabled my 3G Cellular Data to check what was NFC service error is, after a few minutes, I lost my signal, phone turned to No Service, then in Settings -> About Phone, I got an Unknown Baseband.
EDIT
I got No Service since last night up until now.
EDIT Oct. 13, 2015 9:49 AM +08:00 Manila Time
I manage to update my phone from ICS 4.0.4 to JB 4.1.2. But still, my baseband is Unknown and I have no signal.
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
es0tericcha0s said:
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
Click to expand...
Click to collapse
I also though of that, hopefully not.
When I first got the phone, my gf sent me our pictures via bluetooth , no issues occured. After a while, I noticed that there are so many photos of the previous owner (around 1000+) and mp3s (around 1000+ also). So I connected the phone via usb to my pc and deleted all those pictures and mp3s inside the My Computer -> SHV-E160S -> Phone (Computer\SHV-E160S\Phone). After doing so, I started to encouter some issues, when enabling the bluetooth, the phone hangs and reboots then the error 'NFC service has stopped' keeps on popping up, until it went Unknown Baseband.
Now, the phone keeps on rebooting similar to the symptoms that it gets when baseband version is unknown.
I'm looking for solutions to fix the unknown baseband and saw the Back up and Restore EFS, I just need to root the device to try this fix. Maybe I'll post an update whether if I manage to solve this problem or not, if it didn't fix the issue then maybe the problem is the baseband chip. what a crap!
This is my reference for the EFS Fix
http://techbeasts.com/2014/07/13/fix-samsung-galaxy-unknown-baseband-version-guide/
Thanks!
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
es0tericcha0s said:
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
Click to expand...
Click to collapse
So I need to install TWRP first before rooting the device? Also I'm planning to use a rooted stock firmware which is 4.1.2, I just don't know the difference between UH24 and MH2, I've read that UH24 is already old and it's better to use a MH2 build and what is the Recovery UH24/MH2?
EDIT:
I forgot, I cannot check my current Baseband since it is still unknown.
EDIT: 12:30PM +8:00
I managed to get my Build#, it is MH2, I'm currently looking for a rooted 4.1.2 MH2 download link.
Way faster and easier to use the method I outlined, but either way should work.
es0tericcha0s said:
Way faster and easier to use the method I outlined, but either way should work.
Click to expand...
Click to collapse
Sorry, I'm really a root virgin here. While following your advise, I'm also currently looking at this guide -> http://forum.xda-developers.com/showthread.php?t=1924535. I'm done downloading Tegrak for MH2, a small problem I encountered here is I don't have a folder named 'sdcard' in my phone, so I created one and copied the 'Kernel' .zip, also I copied it to usbStorage folder.
I'm about to flash the 'Recovery' .tar to my phone. Hoping a success result
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
es0tericcha0s said:
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
Click to expand...
Click to collapse
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
jakeortega said:
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
Click to expand...
Click to collapse
Finally! I'm done rooting my phone, though I encountered another issues again. My Menu Button and Back Button does not work.
UPDATE: 4:08PM +8:00GMT
I think I found the problem as to why my Menu button and Back button doesn't work. I'v check my Baseband and it is -> E160SKSJMH1 and my Build # is -> JZO54K.E160SKSJMH2. Am I using a wrong FW as supposed to what I should be using? Which build should I install, the MH1 or the MH2?
Also, the Tegrak Kernel I've used is Build 48 for SHV-E160S MH2. I've also tried factory resetting the phone but the issue still exists.
Thanks!
UPDATE: 4:41PM +8:00GMT
Managed to fixed the issue by updating my Touch Firmware. Cool!
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
discussion?
Chaosruler said:
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
Click to expand...
Click to collapse
Interesting, was this an issue with the WW-5.17.44.68 update or has this been an ongoing issue? I didn't bother with the previous one because it didn't seem to do a whole lot, but never noticed this issue.
Chaosruler said:
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
Click to expand...
Click to collapse
I hate doing this juggle. Big part of why I don't try to update unless it's significant :/
Chaosruler said:
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
Click to expand...
Click to collapse
Thanks for the heads up on this. I check the release thread often in hopes of Oreo, but they don't bother putting this information on their small updates. I think I'll update just because of that really, although Oreo would have been nice too :silly:
Chaosruler said:
discussion?
Click to expand...
Click to collapse
I feel like there's probably only 2 or 3 people who check these forums often nowadays, which is a shame because the phone is quite nice, and even has the bootloader unlocked as well. But ASUS seems to have too many phones that need updates and we're left in the dust waiting. Both XDA and Zentalk forums have people complaining and talking about this being their last device, which is reasonable and align with my thoughts as well. Really though, I want to go and make my own ROM for this phone, but don't really have the time, resources, or experience to tackle it just yet. Maybe I can use it in the future for practice
Update Impressions
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10 but any computer with fastboot installed will work really) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. /u/Ryder. has pointed out the Zentalk forum has the latest recoveries available, so check there first. At the time of writing, I was pushed to login to view that forum, so instead I just grabbed the latest available from AndroidFileHost, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.2.1* from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img). *3.2.1 is available in the Mega. At the time of writing, I only checked the AndroidFileHost link and didn't check to see if there was an updated build for it. It is Oreo compatible, so when they finally get around to giving us Oreo, you'll have a suitable recovery to go along with it. Thanks to /u/Ryder. for the heads up.
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Error when I try to download.
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
asianflipboy said:
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. I just grabbed the latest available, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.1.1 from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img).
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Click to expand...
Click to collapse
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Chaosruler said:
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Click to expand...
Click to collapse
You're right about that. I've updated my post to reflect it.
Chaosruler said:
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Click to expand...
Click to collapse
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Ryder. said:
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Click to expand...
Click to collapse
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
indiana99 said:
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
Click to expand...
Click to collapse
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
asianflipboy said:
You're right about that. I've updated my post to reflect it.
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
asianflipboy said:
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
No. Thank you very much for asking. I downloaded from a different location.
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Good to hear.
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Hmm, I think I'll do that. I'll make some small zip files for each.
---------- Post added at 09:56 PM ---------- Previous post was at 09:16 PM ----------
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Ryder. said:
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
Click to expand...
Click to collapse
Sorry for re-quoting all of you, but do you guys see the update anymore? It might have been why /u/indiana99 couldn't find it. I went to check while making the zip packs and it's not there... Maybe there was some issue with the build? It's got me a bit shook that it's suddenly not on the website.
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Chaosruler said:
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Chaosruler said:
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
indiana99 said:
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Click to expand...
Click to collapse
That's weird to me though. I just checked again and both variants are missing the current update, 5.17.44.87. Did they pull it for some reason? As far as I can tell, my phone is behaving pretty normally. Anyone that's updated notice anything weird?
I've removed the link. This article claims that we're finally getting the update by the end of March!
https://www.phonearena.com/news/Asu...-ZenFone-3-Deluxe-receive-Oreo-March_id103395
Finally!
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Julio2019 said:
Hello, Thanks for the information. I have bought this phone in November last year, and i like it. I bought it from Sunsky, i have the global version zui 5.0.066 st. Could you post or send me a video in how to do this please. I'm new in flashing phones. I only have flashes a Lenovo K5 note in the past (the 2016) version, it was easy because lenovo post the firmware and the instructions, i did it to upgrade the phone from Lollipop to Marshmallow. But i didn't root it. The K5 note is my father's phone.
I see how the Chinnese firmware looks, could i install the chinese firmware to my phone without any compatibility issues?, also i saw that the chinnese firmware has been updated to zui 5.0.163 st, with improvements and sound stability. And in the Lenovo Chinnese official club also there is a similar steps for rooting the device. Could you help me please to confirm these, and teach me how to do it, please?
Also, i have both firmwares, the CN lastest version; i downloaded it from the lenovo's chinnese official club (zui 5.0.163 st). And I also have the ROW version i don't remember where i downloaded it but this is the name of the file: L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225.rar
I have downloaded the QPFIL tool and lenovo drivers too. So i'm ready to learn. It would be great if you can make a video, please if you could. I only have install global versions, in the K5 note i install the global version. I could install the CN version in my K5 Pro without any issues? Thanks in advanced.
Click to expand...
Click to collapse
Sorry, I don't really have the time or the facilities to make a tutorial video, but the Chinese instructions follow the same process, only breaking up the process into a few more steps. Both achieve the same result. My thinking is that you might be able to install the Chinese firmware, but some forum discussions suggest that you will have some modem and IMEI issues if you do. There are ways to back these up using QPSTs software download application. My guess is that it'll probably work, but that it won't work flawlessly. Let me know how it turns out if you try it.
If you want to update your software without rooting, simply follow the process from step 5, using the new L38041_ROW ROM without swapping the boot.img. The link below shows the flashing process pretty well, but you'll need the later versions of QPST since you'll be using .elf programming paths and not .mbn. Once again, that will wipe your phone entirely.
"https://www.youtube.com/watch?v=W9Cz4LwAzLg"
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Julio2019 said:
Hello! Don't worry i'm going to follow your steps. By the way, about the CN firmware, would there be a way to back up my rom, my actual ROM with the modem and imei configuration? Is to prevent in bric the phone. I have read the warnings about the issues you talked about, and apparently these setteings are store in the nvram. There is a way to do a recovery image or ROM of my current firmware?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
And what version is your ZUI now? When i bought the phone, i tried to convince the provider to not install the custom global firmware, but he told me that lenovo technician said that they have to intall that global firmware. So, i accepted to buy the phone with the global version. I was trying to avoid all the gapps that the majority of phones have.
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Could you tell me how to uninstall the gapps, please?. I only want to have running the only and minimal google processes. And the other reason is because i like the clock widget with weather that the CN version have. There are other things that the CN have that the global version doesn't have.
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
Another question, do you know what enshrine is? Is in the wallpaper submenu but it doesn't do anything in my case. And theres a folder with images that i think are the wallpapers of the CN firmware. Thanks in advance
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
If I flash i need to install gapps or the gapps installs themeselve?
Click to expand...
Click to collapse
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
rlb596 said:
There probably is a way of completely backing up your current stock ROM, and I see tutorials on here about how to do it, but I couldn't figure out how to backup mine. I already had both Chinese and ROW roms, so I wasn't too worried. You CAN use QFIL to backup your IMEI, Modem, etc, however. It's in the tools drawer as "QCN backup restore"
I'm using 5.0.117 from FirmwareX ("https://firmwarex.net/lenovo-k5-pro-l38041-android-8-1-official-firmware/"). Honestly I'm unsure what release I was using before the flash. The new ROW rom will have a full google suite, but once you obtain root you can remove whichever apps you don't like. There's a whole host of information on xda and other forums about removing system apps on a rooted phone. Hell, there are even apps that do it for you. Magisk has a module as well which uses terminal commands. A quick and dirty method is to use a root explorer like Mixplorer and delete the /system/app/xxxx folder that you don't want.
I have no idea what enshrine is. My wallpaper menu just has static, dynamic, and album selections, with an option for HD desktop.
My thinking is that the Chinese version won't have gapps, in which you could potentially flash open gapps using an app like flashify. I'm not sure, as I've only used the ROW 5.0.117. Remember that this device as yet has no TWRP and prevents boot of an unauthorized recovery, so any sort of flashing has to be done via qualcomm flashing, or in system after gaining root access.
Click to expand...
Click to collapse
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Julio2019 said:
Hello, thank for your patience and teachings. Here are the image of the Enshrine Menu i talked about:
("https://drive.google.com/open?id=1FFgx5pmM6mIQUhrOLN2cjgyfOvFTV83s")
and here is when i select this option:
("https://drive.google.com/open?id=1L34tjYpiPmjAU443sjHCcM8TM8JyOY-o")
Oh, and also i want to ask you what does this application call AppDaily from Lenovo, i don't understand how to use it, here the image:
("https://drive.google.com/open?id=1z6swpSxTPw4JeodwZ-OvkKUav9FWEOsZ")
Hearing all you teach me, then i think it would be safe for the moment to only upgrade my system with the zui 5.0.117. It would be safe to make this upgrade. Do you recommend me to root after the upgrade?. Or wait more time for other solution. I think that first it would be better to upgrade with the ROW firmware. How do you feel the last ROW update. Although is strange because i have only see zui 5.0.066 and zui 5.0.088 global versions. Maybe only few phones receive the update. What do you think about?, What do you recommend? If only i upgrade the phone with the ROW there wouldn't be any modem and imei issues? Thanks in advance.
Click to expand...
Click to collapse
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
rlb596 said:
Remember, I'm just telling you how I did it. Your experiences might vary, but I've had no problems with this latest ROW in any aspect. It runs well, is pretty intuitive, and I notice very little change from the previous stock rom. If you want to try out either ROM before rooting, I'd suggest that you not customize your phone very much, or have any personal files on the built in storage, as these will be lost will each qualcomm flash. I'd recommend that if you're going to update, you might as well try rooting now to save yourself those issues. If you're uneasy about rooting and aren't having any issues with your current ROM, I'd suggest you wait until you have some pressing issue, as many of the included apps on this phone can be disabled or uninstalled. My purpose for rooting was that I became used to root-requiring apps like AdAway and some magisk extensions. The apps you're talking about are included with this system as well, but I never used them. Before the root, I disabled them. After the root, I deleted them.
This is a very new phone, so I wouldn't be surprised if there's more development 6 months in the future. Keep an eye on 4pda and club.lenovo's discussion forum for this device, as I anticipate their being the forerunners.
Click to expand...
Click to collapse
Agree. Hope they focus more in the subject we are talking. By the way, i have checked the club.lenovo's, and they got another new update with more improvements and a fix for their wechat app. , Now they are on zui 5.0.188 st. Could you show me images of the zui 5.0.117 interface, if you could. If not, don't worry i'm going to google it. But leaving this aside, i'm satisfy with the phone, in my opinion, is a great phone!, I like it, has excellent performance, a cool design, is slim, have a nice display, and good cameras. Have a nice day, hope we could talk again soon. If i get any more news, be sure i'm going to share it. Here in xda, i think we are the only ones who are talking about this phone. Hope more people and xda developers join us. Thanks. God blessed you.
Latest .188 st ZUI's interface changes a lot, but is the chinesse variant of the ROM, it comes with chinesse apps and only english and chinesse languages installed. Deleting the chinesse bloatware is easy, there is a folder named "preloaded" or preinstalled (something like that) in /system/ get root rights and delete the entire directory.
please create forum
rlb596 said:
As far as I know the bootloader for this phone is unlockable, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet. Just google it).
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX.
d. ADB and Fastboot tools.
This method uses Qualcomm flashing, so if you've never heard of that, read as much as you can before you try this.
Steps
1. Download and extract the ROM to your PC.
2. Attach your adb enabled device via usb and copy the boot.img file from the extracted folder to your device storage.
3. Install and open magisk manager on your device, then install magisk via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Once completed, take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with rooting your K5 Pro
edit: There is a way to unlock the bootloader! User KiiKeEp has posted a guide on the method, which also contains a usable TWRP for the global rom. Here's a more streamlined version adapted from his tutorial. Make sure you have oem unlocking enabled in developer options.
1. Go to "zui.com/iunlock" and fill in the boxes.
a. First input your IMEI1 which can be found by dialing *#06# or going to the "about phone" section in the settings.
b. Second, input your phone's serial number. You can find this by enabling debugging in your developer options menu, then using the adb command "adb reboot bootloader"
c. Input your email into the third box.
d. Type the displayed 4 digit number into the 4th box and then submit.
2. You'll receive an email containing a download link for an unlock .img called "sn.img". Download it.
3. Flash the unlock image in fastboot. Use the command "fastboot flash unlock", drag and drop the sn.img into the command window, hit enter, then follow the onscreen command.
4. If this is done correctly, you can flash the twrp.img that KiiKeEp included in his post. "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
Greetings Mr rl596!
So, what order do you recommend, i have downloaded KiiKeEp files, and successfully have receive my unlock image from lenovo, but in with order do i need do thinks. Is the following order correct?
1.- unlock bootloader
2.- Install zui 5.0.117 st ROM
3.- Install TWRP image
4.- Root device
Is this order correct?, I have the CN ROM in hand too, tha latest one is .188 st. But i need to make an EFS backup with the QPST tool, just in case. I have ask KiiKeEp, i'm waiting for his answer too. I want to make a video tutorial, so more K5 pro users could get benefit of this, and use all the potential this phone has. But what benefits does a unlock bootloader have?, Oh, and I almost forgot, for the QPST tool, do i have to install the driver that shows in the Device Manager as L38041 or the one that shows as QUALCOMM?
. Thanks in advanced.
Hi.
Thank you very much for the instruction - I successfully got root on my phone.
The only difference is I didn't use ADB, I just entered Download mode via the buttons: hold the volume + and - and power down until the logo flash.
:good:
Hi guys,
I tried but i have an error "Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable"
log :
13: E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf
00:25:31: Requested ID 13, file: "E:\Téléchargements\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\[TuserHp.com]_L38041_ROW_OPEN_USER_Q00020.0_O_ZUI_5.0.117_ST_181225_qpst\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
00:25:32: 622900 bytes transferred in 0.203000 seconds (2.9263MBps)
00:25:32: File transferred successfully
00:25:32: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\denis\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Download Fail:FireHose Fail:FHLoader Fail:Le fichier spécifié est introuvable (The specified file is not found)
Finish Download
do you have any idea ?
thx in advance
I was wondering if there is a difference between CN version and global version regarding future update which device should i get for better support or root
Hi, I have unlokced the bootloader and install magisk via twrp. Is there custom roms for this phone
O meu lenovo apresentar "Qualcum crushdump mode" alguém com isso?
---------- Post added at 05:04 AM ---------- Previous post was at 04:54 AM ----------
O meu lenovo fica no final do processo com "Qualcum crushdump mode" alguém conseguiu resolver isso?
Help! I do the first process but now i can´t enter phone because tell from password on encryption screen.
EDIT: I enter to EDL mode (Press Vol- and Vol+ at the same time and conect to the usb) and flash with QFIL with the original boot.img and the phone turn on normally.
Lenovo K5 Pro ROM
Hi.
Are you have good working ROM for Lenovo K5 Pro?
This is an awesome, awesome phone. I rooted it with Magisk boot image patching on PC, without TWRP and even installed GCam on it to improve the camera massively - can now take photos with Night Sight. The specs of this phone are AMAZING for its price. And the best part is it is without any notches, holes, pop-up cameras and retains the traditional clean design.
I tried the unlock bootloader (official) way to root the device but got stuck here:
Code:
C:\minimal_adb_fastboot_v1.4.3>fastboot flash unlock sn.img
target didn't report max-download-size
sending 'unlock' (5 KB)...
then nothing happens (waited for like 10 minutes).
Tried to install QPST 2.7 (3 different versions, same error) but setup gives me the following message:
Code:
the installer was interrupted before QPST 2.7 could be installed
SOLUTION: Download QPST Portable
---------- Post added at 08:25 ---------- Previous post was at 07:57 ----------
Getting Sahara error but not because I've waited too long! Any solutions? Getting desperate now.