Related
Before we start this post, I just wanted to say that I am new here (like today new) and XDA does not have this device listed in their website at all so I did not know where else to post this rather than the General Discussion, I do apologize for this annoyance and please forgive me. One last thing, I am not the developer of this, I am only the poster person........guy...... ;-; ....... the person who developed this custom recovery is @lopestom!! Please give him the credit he derserves, not me!! With this being said, let us move onto the post now!!
-----------------------------------------------------------------------------------------------------
*DO THIS AT YOUR OWN RISK!! I AM NOT RESPONSIBLE NOR IS THE DEVELOPER FOR ANY DAMAGE YOU CAUSE TO YOUR DEVICE!!*
-----------------------------------------------------------------------------------------------------
Greetings XDA Community and Blu Users!
Today I am Sharing this Custom Recovery that was made by @lopestom for the Blu Advance 5.0
Now before we get into this you will need to do the following first for the recovery to install.
You will need to install the MTK VCOM Drivers and the SP Flash Tool.
-How to install MTK VCOM Drivers for Windows 8: https://forum.xda-developers.com/showthread.php?t=2693906
-How to install MTK VCOM Drivers for Windows 10 64-bit/32-bit: https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
-Installation for SP Flash Tool: https://androidmtk.com/smart-phone-flash-tool
---------------------------------------------------------------------------------------------------
Now once you get this done, you will want to install the custom recovery files for which I am providing to you Blu Advance 5.0 Users from [B @lopestom[/B]. (download link at the very bottom)
Once you install the zip, follow these simple steps and you will have the recovery installed in no time!
1. Download zip file and then unzip to then where you will see two files: *recovery img and scatter file*
2. Open SPFT, and load the scatter file from that folder unzipped
3. Click the Download Tab, and edit the settings as follows:
A. Make sure 'Download Only' is selected
B. Only Recovery Partition box is checked
C. Make sure correct scatter is loaded
4. Double click in 'Location' field next to recovery partition and select recovery.img
5. Click "Download" Button
6. Power off phone
7. With "Download" button clicked in SPFT, connect phone to USB without powering on (VCOM DRIVERS MUST BE INSTALLED FOR THIS TO WORK)
8. Wait for SPFT to flash, popup with green check-mark will display when complete
9. Disconnect phone from USB, hold power + volume-up keys until boot into TWRP Recovery
10. Done!
11. You have successfully installed this custom recovery for your Blu Advance 5.0!!
As a perk, you can now root your device if you have not already with Super Su: https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip?retrieve_file=1
Downloads:
https://www.androidfilehost.com/?fid=745425885120706965
*ALL CREDIT GOES TO @lopestom*
When is TWRP installed?
Sorry, as a noob, I have no idea at what point TWRP needs to be installed, if at all. Andvance 5.0 isn't on the list in the official TWRP app, so installling that from Google Play Store doesn't help. Do I get blutwrp.img -and how do I install it? Do I flash twrp, too, or install it another way ? Should twrp come up automatically here? I'm totally confused with this guide.
thaaaaaaaaaaaaaanks
Androidfilehost link is out of mirrors
cuvtixo said:
Sorry, as a noob, I have no idea at what point TWRP needs to be installed, if at all. Andvance 5.0 isn't on the list in the official TWRP app, so installling that from Google Play Store doesn't help. Do I get blutwrp.img -and how do I install it? Do I flash twrp, too, or install it another way ? Should twrp come up automatically here? I'm totally confused with this guide.
Click to expand...
Click to collapse
This post looks pretty new. So I thought I'd drop by just in case you never figured out how to install TWRP. At the bottom of the guide there is this:
RonneyDude said:
Downloads:
https://www.androidfilehost.com/?fid=745425885120706965
Click to expand...
Click to collapse
That download URL is TWRP. If I were to guess, the download is an unofficial port of TWRP. Since TWRP doesn't have an official build for BLU Advance 5.0, you have to use the file provided by OP (I am not aware of any other unofficial ports of TWRP specifically for BLU Advance 5.0).
It has been a while since I rooted the BLU Advance 5.0 for my friend, but I believe it is not possible to directly flash a custom recovery onto the device. That's why you need to install SPFT which was also generously provided by OP:
RonneyDude said:
-Installation for SP Flash Tool: https://androidmtk.com/smart-phone-flash-tool
Click to expand...
Click to collapse
However, in order to use that tool, you must make sure you have the right drivers so your phone and computer can communicate:
RonneyDude said:
-How to install MTK VCOM Drivers for Windows 8: https://forum.xda-developers.com/showthread.php?t=2693906
-How to install MTK VCOM Drivers for Windows 10 64-bit/32-bit: https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
After you have installed the proper drivers for your computer and SPFT, you are all set to follow the steps OP provided. Any instance where it says "zip file" he is referring to the zip file you should have downloaded from androidfilehost.com (first link I quoted from OP).
As long as you know that, here are the steps 1 - 11 you should follow:
RonneyDude said:
1. Download zip file and then unzip to then where you will see two files: *recovery img and scatter file*
2. Open SPFT, and load the scatter file from that folder unzipped
3. Click the Download Tab, and edit the settings as follows:
A. Make sure 'Download Only' is selected
B. Only Recovery Partition box is checked
C. Make sure correct scatter is loaded
4. Double click in 'Location' field next to recovery partition and select recovery.img
5. Click "Download" Button
6. Power off phone
7. With "Download" button clicked in SPFT, connect phone to USB without powering on (VCOM DRIVERS MUST BE INSTALLED FOR THIS TO WORK)
8. Wait for SPFT to flash, popup with green check-mark will display when complete
9. Disconnect phone from USB, hold power + volume-up keys until boot into TWRP Recovery
10. Done!
11. You have successfully installed this custom recovery for your Blu Advance 5.0!!
Click to expand...
Click to collapse
cuvtixo said:
... I have no idea at what point TWRP needs to be installed, if at all.
Click to expand...
Click to collapse
I may be misreading this sentence, but incase I am not, I'll explain. The primary reason people install a custom recovery is so they can root their phones. In the case of BLU Advance 5.0, that phone only has an internal storage of 4GB, which I have recently learned is apparently taken up entirely by Messenger itself (if you download Facebook Messenger). What's the point of having a smartphone if you can't install apps on it? There is an app called Link2SD which can trick the phone into believing the external SD card space is internal (more or less). Link2SD needs root though.
After installing TWRP, now is when you can flash things the way I imagine you're moderately familiar with from your comment. The only thing you should need to flash via this method should be SuperSU, to give you the root privilege necessary for Link2SD. OP has also provided this:
RonneyDude said:
As a perk, you can now root your device if you have not already with Super Su: https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip?retrieve_file=1
Click to expand...
Click to collapse
If you followed all the steps properly, you should be able to power down your device, and boot into TWRP by holding the Power and Volume Up buttons until you see the white BLU boot screen. From there, you can flash SuperSU.
Hope this helped clear some things up for you!
weilunt0219 said:
This post looks pretty new. So I thought I'd drop by just in case you never figured out how to install TWRP. At the bottom of the guide there is this:
That download URL is TWRP. If I were to guess, the download is an unofficial port of TWRP. Since TWRP doesn't have an official build for BLU Advance 5.0, you have to use the file provided by OP (I am not aware of any other unofficial ports of TWRP specifically for BLU Advance 5.0).
It has been a while since I rooted the BLU Advance 5.0 for my friend, but I believe it is not possible to directly flash a custom recovery onto the device. That's why you need to install SPFT which was also generously provided by OP:
However, in order to use that tool, you must make sure you have the right drivers so your phone and computer can communicate:
After you have installed the proper drivers for your computer and SPFT, you are all set to follow the steps OP provided. Any instance where it says "zip file" he is referring to the zip file you should have downloaded from androidfilehost.com (first link I quoted from OP).
As long as you know that, here are the steps 1 - 11 you should follow:
I may be misreading this sentence, but incase I am not, I'll explain. The primary reason people install a custom recovery is so they can root their phones. In the case of BLU Advance 5.0, that phone only has an internal storage of 4GB, which I have recently learned is apparently taken up entirely by Messenger itself (if you download Facebook Messenger). What's the point of having a smartphone if you can't install apps on it? There is an app called Link2SD which can trick the phone into believing the external SD card space is internal (more or less). Link2SD needs root though.
After installing TWRP, now is when you can flash things the way I imagine you're moderately familiar with from your comment. The only thing you should need to flash via this method should be SuperSU, to give you the root privilege necessary for Link2SD. OP has also provided this:
If you followed all the steps properly, you should be able to power down your device, and boot into TWRP by holding the Power and Volume Up buttons until you see the white BLU boot screen. From there, you can flash SuperSU.
Hope this helped clear some things up for you!
Click to expand...
Click to collapse
While this helps, I've been doing this for months now... And now I am faced with the problem of the new OTA they just gave me, which blocks any and all root access that I had before. Now my problem is figuring out if I need to re-flash the previous version to my firmware or unlock the bootloader and just install a custom ROM, given that a universal ROM is compatible.
A way to unbrick?
So, I have one and bricked it when flashing a recovery I found when I searched blue advance 5.0 custom recovery on google
when I searched, I used the one I found at the blueroms dot info site
it is now in a boot loop, and I can't access anything except the menu between booting factory mode and recovery
is there a way I can fix it, and flash this?
Thanks!
Thanks for not only the instructions, but for accepting the possibility that I may have figured it out myself.
As a regular linux user, I'm not sure why the xda comunity depends on: SP Flash Tool, MTK VCOM Drivers for Windows and MTK VCOM Drivers for Windows 10 64-bit/32-bit. Especially at this point shouldn't there be some tools from Chrome OS? if not Linux itself? Sorry that's kind of off point, but your help is indeed appreciated.
Trying to Root
Hello everyone, I have been desperately trying to root a Blu Advance 5.0 HD that i just got. It runs Android Version 6.0 Kernal 3.18.19 Custom build BLU_A050U_V04_GENERIC 19-09-2016\
So The farthest i got was clicking download and plugging in the phone. It gives me an error and suggests i Format+download. Doing that semi bricks my phone and i have to flash a oem firmware. I even tried using the oem files and just replacing the recovery which did the trick in making it run, but did not install twrp. What am i doing wrong, Id rather not return the phone but i may if i cannot root it.
Thanks anyone who can assist me!
Nothing happened
Greetings,
I was able to install drivers on the PC and flash the recovery through SPFT and directly from fastboot but it didn't work. Although both methods gave me OK, when I boot into recovery I still get the stock recovery 3e version of the BLU. So, is there something that I'm missing?
Hi! I have done many ports in order to make TWRP work on this device although it doesn't work to it's full potential as it doesn't read the internal or external memory/partitions unless you format it. I'm also leaving the stock zip file and stock SP flashable zip file along with the scatter file so you can thinker around it. I have tried my best and this is the best I've come to for now. I tried porting custom roms but unfortunately to no avail I was left with no choice but to give out. If there's anyone that would like to fix the TWRP recovery or compile it to this device then feel free to conatct me The phone hangs at Alcatel Powered by Android boot screen and does nothing when eg flashing the stock zip or any custom rom I tried to test.
Tutorials
https://www.youtube.com/watch?v=5CxDF2pkdCQ
https://www.youtube.com/watch?v=05xO4vGKWIU
https://forum.xda-developers.com/android/software/guide-twrp-3-0-x-mediatek-devices-t3379681
I would like to say thanks to all the developers that I've ported their recoveries and best of all luck to all the XDA members trying to at least have android 7.1 o this phone. Keep in mind that this is the Alcatel U5 4G model and not the 3G model. The 5044 model and not the 4074 model. WIsh ye all luck :good:
-bb100dulski
Downloads
http://www.mediafire.com/folder/fd04tleav99h4/Alcatel_U5
Wow! Thanks for trying to port TWRP to our device. I'm going to wait until it's stable so I can have root!
user154 said:
In case you haven't rooted it already;
You can root this device without a custom recovery, if you get stock rom
You can take boot.img from the rom, use magisk manager to patch it, then flash the patched_boot.img to the device using SP tools
Click to expand...
Click to collapse
Hi! You can elaborate please? I really appreciate your help.
Thanks!
Thanks!
user154 said:
First you need to download the stock rom for this device, latest magisk manager apk, and if you havent already sp flash tools, and mtk vcom drivers.
Install vcom drivers, and extract sp tools.
Then take boot.img from stock rom and magisk manager apk and copy them to the device
Install magisk manager, then open it and click install, pick the patch boot image option. Direct it to the boot.img you copied to the device, this process will generate a patched_boot.img file, located in the download folder (I think, I cant 100% remember but i think its in download, if not look in top level of internal storage, and magisk manager folder)
Copy the patched_boot.img back to your computer, put it in the same folder as the stock rom (ie where you found the boot.img file you copied to the device)
Load up SP tools and load the android_scatter file from the stock rom, uncheck all boxes except boot, click the location field for boot and load the patched_boot.img you generated with magisk manager.
Remove the battery from your device and then reinsert,
plug usb cable into the computer but not your device
Click download on SP tools
While holing vol down plug the cable into your device, keep holding vol down till the bar across the bottom on SP tools goes yellow. When the flashing process is complete a box will come up saying download ok, you may now unplug your device and turn it on.
If you now load up magisk manager it should say magisk is installed and you will have root
Click to expand...
Click to collapse
Hi my friend, in first place thanks for your help and your time.
With your help i am happy with my rooted Alcatel U5 5044A. It is an after and before...
But was a nightmare, hehe.
I do everything step by step, and i rooted the phone but it was on sim lock screen and without chances of repair that.
After search, and try everything what i see, because of causality i download a firmware for the 5044D model and flash every again (with my modified boot.img) but using 2 parts of the 5044D firmare (simlock and secro).
Maybe i have an alien now, but with some magisk patches this phone is really very good for daily usage.
I am an iOS user on all my devices, and of course i jailbreak all them.
But that was a very cool adventure and now i get a very premium Alcatel U5 with:
- GPU Turbo Boost.
- Low-Ram Config+ for Magisk.
- S9 Emoji for Magisk (with Gboard).
- YouTube Vanced.
All credits to you!
Thanks for all and happy holidays.
PS: I take some images to show my result, but XDA says: To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
Reparar link
El link no sirve para descargar por favor reparar
This is tested file for FRP remove on Alcatel U5 5044D model. Flash it manully with SP tool
Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.
Extosis said:
Story:
I recently bought the, Ulefone Armor 6 Android phone. Didn't do much research into rooting before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Rooting procedure:
1. Get a local copy of the boot.img file from the Ulefone website (To make things simpler for you, Ulefone.com/index.html > Scroll down and click on "download" > Select your device model "Armor series" "Armor 6" > Scroll all the way down and click the download button for "The latest rom".)
2. Now you are at the google drive folder from Ulefone, with the files you need. Select EU if you have the EU version, or Non-EU for any other country.
3. Download the compressed file of your choice EU or Non-EU. (Ex. I downloaded the one for Non-EU which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
4. Open the file in your favorite archiver software, 7-zip, winrar, etc.... open the first folder in the archive, and extract "boot.img"
5. Download, "Magiskmanager.apk" from their Magisk Manager, and install it in your, Armor 6 phone.
7. Pass the, "boot.img" file from your computer to your cellphone. Preferably the "downloads" folder.
8. Open up Magisk manager, and click install 19.3 (or what ever is the current version) then click "Select and Patch a File".
9. Find your "boot.img" file and patch it with magisk manager.
10. After magisk manager has patched your file, pass the patched file, back onto your computer.
11. Now, in your Armor 6 phone, go to settings, scroll down to system and click it, click on about phone, and then tap the crap out of build number, until you become a developer.
12. Go back from about phone, click on developer options, and tick on "OEM unlocking".
13. Scroll down and tick on USB debugging.
14. Download your ADB tools with fastboot from android/google.
15. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
16. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
17. Once you have unlocked your bootloader, reboot the phone "fastboot reboot", wait till the phone boots up, go through the set up process, enable USB debugging again (Step 13), install magisk manager again, adb reboot bootloader in adb command prompt.
18. Once in fastboot mode again, flash the patched boot.img file.
fastboot flash boot boot.img
19. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense.
Click to expand...
Click to collapse
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
Upon doing a bit more research, the phone actually has TWRP & a TWRP fork.
How do we know we can trust you? I'm a nubee as I've said.
SteeleB89 said:
How do we know we can trust you? I'm a nubee as I've said.
Click to expand...
Click to collapse
Then this isnt for you and stick with stock... Stock honestly works just certain people want greater freedom with thier phones only issue is with that you yourself at greater risk of breaking something and wouldn't know how to fix it and in situations like that factory restores wouldn't even save you because the system partition doesn't go back to the way it was with a factory restore
Sent from my SM-J327P using Tapatalk
I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.
SteeleB89 said:
I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.
Click to expand...
Click to collapse
Well to start with, I didn't attach anything in this thread, only photos.
1. You bought the phone, a phone that is made from a Chinese company, odds are that it already has malware, backdoors, or things you don't want on the OS.
2. Like I said, I didn't attach anything for you to download, so I am not infecting you with anything. Fastboot even comes with Google SDK.
3. Magisk is a wide known group who release root for the public to download/install. Just like TWRP, clockworkmod, cynaogenmod, etc...
4. If you don't feel comfortable doing this process, then like stated above, you should probably feel safer staying with stock & no root.
As I am sure, everyone who mod their devices are fully aware of the consequences of exploiting their devices. Brinking, killing, or messing something up.
Cheers.
For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?
A.Fitz said:
For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?
Click to expand...
Click to collapse
I have literally used the "driver installer" from the Ulefone website. Install the MTK/VCOM Drivers.
Adb gets detected in TWRP & Fastboot is found on my computer just fine.
My suggestion would be to check if your anti-virus (if you have one) if it's blocking the drivers from being installed.
Ps: I have the latest Windows 10 1903 x64 Edu and the drivers work perfectly.
Will try at end of month and tell you guys the result later.
Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.
Stabys said:
Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.
Click to expand...
Click to collapse
Oh most definitely. I am actually going to add more detail to this tutorial once I have the free time to do so. This tutorial was mainly supposed to be like a rough idea on how to do it. However yes, I did a factory reset not to long ago and root was maintained.
Update:
Added more information and cleaned the thread up.
Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.
Stabys said:
Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.
Click to expand...
Click to collapse
Yeah, I think their new rom has a few security updates as well as other updates.
I haven't updated as of yet, because I fear I will lose root. However if I ever do, I'll update everyone if successful.
I understand you very well too.
Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.
Stabys said:
Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.
Click to expand...
Click to collapse
Hello it's been a while.
I have updated to the latest version by Ulefone for our Armor 6's.
Version: 2019.06.05.
I was able to root it again, using the same method in this thread.
As for the native apps, I haven't tried to remove them, however I am sure it is possible to.
HELP!
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Extosis said:
Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.
Click to expand...
Click to collapse
babyboy_legolas said:
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Click to expand...
Click to collapse
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?
babyboy_legolas said:
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?
Click to expand...
Click to collapse
To put the phone in manual fastboot mode, you have to power off your device first. By pressing both, "power button + volume down button" until you feel the phone vibrate.
Once the phone vibrates, quickly press, "Power button + volume up button" to view the fastboot/recovery/normal boot menu options. To select fastboot use the volume buttons.
Volume up = select
Volume down = move down through options.
Hi!
Oh I tried it once more now and managed to do it.
I did it with the ROM from Mega (20190605).
Thanks again!
Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** 1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!
Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto
kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.
Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.
kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!
Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...
Hi!
Xperia ZXP was running the official Firmware fine. Then, I just decided to root. I followed this video:
Got my phone properly rooted.
Now I keep getting notification of an update that I had before but cannot install it. Also, I cannot setup my company work profile as it detects root.
I mainly wanted to use Cheat Engine that why I rooted.
How do I apply latest update?
How do I hide root status?
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Is there a place/page here that lists all these tools?
Fix after root effects
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Here is how I'm going step by step:
Download Flashtool - Done
latest version of Xperifirm - Done
Find latest firmware with Xperifirm. Should end in .107 - Done
-- Download it - Done
-- decrypt it with Flashtool - Stuck
Download Newflasher - Done
-- Unzip Newflasher into the folder you have the decrypted files
Plug your phone into your computer
-- Make sure you have the correct driver - Done
-- Developer option and usb debugging enabled on your phone - Done
Put phone into flash mode and hit newflasher.exe
-- choose "n" for the first two choices and let it run
-- That will give you the latest and final update for this phone
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Doomer D. Great said:
Here is how I'm going step by step:
• Download Flashtool - Done
• latest version of Xperifirm - Done
• Find latest firmware with Xperifirm. Should end in .107 - Done
○ Download it - Done
○ decrypt it with Flashtool - Stuck
• Download Newflasher - Done
○ Unzip Newflasher into the folder you have the decrypted files
• Plug your phone into your computer
○ Make sure you have the correct driver - Done
○ Developer option and usb debugging enabled on your phone - Done
• Put phone into flash mode and hit newflasher.exe
○ choose "n" for the first two choices and let it run
○ That will give you the latest and final update for this phone.
• Now use twrp to install the latest Magisk version(search online)
○ also have Magisk manager app(Play Store) on your phone
• Once that's done and you've rebooted phone
• open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
• If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Click to expand...
Click to collapse
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
bobsright said:
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
Click to expand...
Click to collapse
The latets Xperifirm also extract right after downloading so the decrypt step is not needed.
I'm flashing a I write. I'll be dealing with the next part now:
Now use twrp to install the latest Magisk version(search online)
also have Magisk manager app(Play Store) on your phone
Once that's done and you've rebooted phone
open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything
TWRP has to be flashed or installed from store?
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
bobsright said:
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
Click to expand...
Click to collapse
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Doomer D. Great said:
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Click to expand...
Click to collapse
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
bobsright said:
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
Click to expand...
Click to collapse
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Doomer D. Great said:
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Click to expand...
Click to collapse
So Cheat Engine doesn't detect root with Magisk?
bobsright said:
So Cheat Engine doesn't detect root with Magisk?
Click to expand...
Click to collapse
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Doomer D. Great said:
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Click to expand...
Click to collapse
Oh well, at least you got it updated and working. Maybe it'll take some searching somewhere else to get that other stuff worked out.
Just a side note; I used to work for Sheikh Hamdan bin Rashid Al Maktoum at his Throughbred operation in Lexington.
Excuse me, does anyone know how to root xz premium docomo ubl no ??? Now on Android 9 Pie, please help.
I believe the Japan market version can't have the bootloader unlocked, thus, no root.