Related
Disclaimer: I have done these steps multiple times and haven't come across any issues, but before you continue please read this fully, and follow the steps completely. Any issues or damage to your phone that occurs while doing this I am not responsible.
That being said below will be everything you need to make sure this all goes smoothly:
Windows or Linux Laptop/PC
Atleast 50% battery on OP3T
Usb Cable for OP3T
Internet Access
Patience
Now to Begin the process to return to stock:
Step 1: Go to http://downloads.oneplus.net/devices/oneplus-3t/ , and download the 4.0.2 version. Again these are the steps I do so that I can make sure the process is done correctly and also that I can get rid of the annoying dm-verity warning. Don't worry at the end of this you will have the latest version for you're device.
Step 2: Go to your phone and reboot to twrp, once in twrp go to wipe>Advance Wipe> Tick everything but usb otg (I do this to make sure my phone starts out in a completely clean state>then swipe to wipe. Once it's finished press back twice to get back to the main screen for twrp.
Step 3: Please reboot device back to twrp. (I found the best way to do this without issues is on the main screen for twrp go to reboot>power off>when the unlocked bootloader warning comes on click the volume up button quickly>use the volume down button when another menu comes on and go to recovery. Again I did it this way because the with twrp version 3.0.4-1 gave me issues when trying to reboot twrp within twrp. Also you will get an No OS installed this is normal as you wiped the system completely. Don't worry just reboot back to twrp.)
Step 4: Once back to twrp you will get the screen where is says to allow modification. Please swipe to allow. Next please connect phone to pc/laptop, and transfer the 4.0.2 you downloaded to your phone. One completed go back to phone and click install and click on the file you just transferred and swipe to install. Once completed reboot device. (Warning: at this time you will get the Dm-verity warning, but dont be alarmed we will take care of that in the up-coming steps.
Step 5: Once the phone reboots and comes to the setup screen don't go through and add your accounts because we will be doing another reset. Quickly get to the home screen of your phone and go to settings>about phone>tap build number 7-10 times>back once>developer options>make sure oem unlocking is ticked, advance reboot is ticked, and usb debugging is ticked(If none of them are please tick them). Since your phone is connected to the pc/laptop after you turn on usb debugging a allow authorization box will show on your phone. Please allow that for this to work.
Step 6: Next go to this link: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.0.3/ , and go all the way to the bottom where it says download Oxygen Recovery (optional), and download that file, and place it on desktop.
Step 7: Now this is assuming you have adb/fastboot setup on you're pc/laptop. Please open up a Command prompt window with phone connected and type these commands in:
1) adb devices ( this will show your device ID Number). If it shows it please continue, if not there is an issue with adb/fastboot set up on your computer, or you typed that command in wrong. Once u get the issue resolved try the command again.
2) adb reboot bootloader (this will reboot your device to bootloader mode)
3) fastboot devices ( again this will show your device ID number as from before)
4) fastboot flash recovery [click and drag the recovery file you downloaded from oneplus website and saved to the desktop here, press enter, and once completed go to your phone and use either the volume up or down button till u see the word Start in green and then press the power button. This will reboot your device, and again you will still have the dm-verity warning on. We are almost done.
Step 8: Once your device is rebooted we need to get rid of all traces of twrp so go to your computer>file explorer>this PC tab>your device should be listed there since its still connected to pc> internal storage>locate twrp folder and delete. Now after you are done with this and you want to lock bootloader go to step 9, but if u don't want to relock the bootloader please just factory reset device, setup your device and then go back to oneplus.net and download the 4.03 version and adb sideload it, and dm verity is gone.
Step 9 Relocking bootloader is easy, and will reset your device. While on your phone go to settings>about phone>tap build number 7-10 times>back once>developer options> make sure that OEM unlocking is ticked, advance reboot is ticked, and usb debugging is ticked (again u may get the allow authorization pop up on your phone please allow). Go to command prompt for adb/fastboot and type in these commands:
1) adb devices ( this will show your device ID Number). If it shows it please continue, if not there is an issue with adb/fastboot set up on you're computer, or you typed that command in wrong. Once u get the issue resolved try the command again.
2) adb reboot bootloader (this will reboot your device to bootloader mode)
3) fastboot devices ( again this will show you're device ID number as from before)
4) fastboot oem lock; once you click enter go to your phone, and use your volume up or down buttons to click on lock bootloader. Let finish. This will reset your device again. Once this is all completed and reboot you have gotten rid of all the warning screens, and your device is like it was when you first got it. Set up device with your accounts and you will get a notification of a update. Download and install.
Congrats your phone is back to stock. If anyone has questions please pm me.
Again these steps are longer than what most of you may do. A few others including myself have done this multiple times to confirm. None of us had issues. It works
**Special Thanks**
The guys that tested this with me to confirm my steps are accurate
Google for well google
Oneplus for yet another awesome device and software.
***UPDATE***
Thanks to @ashokmor007 he made the video below on the steps.
https://www.youtube.com/shared?ci=xDFI-287K-Q
If there is anything else that someone may want a guide on how to do and there isn't one currently on xda. let me know and i can get a guide out. We are currently figuring out if this will work on the oneplus 3.
Very helpful tutorial
if anyone here has tried this please comment, and if u need help please pm me.
the_rooter said:
Thanks to @ashokmor007 he made the video below on the steps.
https://www.youtube.com/shared?ci=xDFI-287K-Q
Click to expand...
Click to collapse
If possible add to the main thread
ashokmor007 said:
If possible add to the main thread
Click to expand...
Click to collapse
done and finished thanks again for the video
TWRP - Mount Decrypt Data?
Good afternoon, the_rooter... Thanks for posting this. I'm trying to get back to stock and found this. I'll explain from the beginning...
My 3T will not boot now. Stuck on “Powered by Android” Screen. Here’s the sequence of events that led to this:
1. Flashed TWRP 3.1.0-1
2. Did a backup of phone (Orig OS… Just got phone a few days ago)
2. Flashed Sultan’s ROM
3. Installed Xposed.
At this point… Everything was working just fine… This morning I decided to install the Xprivacy Module and then I rebooted phone. When I did that, the phone just hung at the “blue android” start screen. I then did the following:
1. Held power button until shutdown
1. It took a while, but I was finally able to boot into TWRP.
2. Did a Wipe – The regular one
3. Restored my backup and rebooted. (Would not boot into the OS)
This is where I think I screwed it up even further… … Here’s what I did… I grabbed a shotgun and… LOL… No… but I was thinkin’ it… LOL… I did this:
1. Booted into TWRP
2. Did the Advanced Wipe and just wiped Everything(Internal Storage as well) except USB OTG
Also getting "Mount Decrypt Data" message when I boot to TWRP... Not sure why that's happening...
Now I can’t copy any files to the phone… Tried with Linux(Ubuntu) and a Windows system... Before all of this I could copy to the phone just fine. I tried disabling MTP in TWRP but that didn't work either. So I'm stuck on copying things to the phone at this point...
Can you set me straight?
Edit: Crisis over... Was able to load ADB drivers on a Windows Box and copy ROM back to phone... I'm back and smiling again.
Just use these tutorial for return 100% stock,it worked very good but the last dm verity message only dissappeard for me after step 9 updating to last 7.1.1 using adb sideload.
Thank You very much!!!!!
Is there a reason why you have to swipe to allow modifications? Can't you just keep TWRP read only and then the stock recovery will automatically be flashed so you don't have to do it manually? Also there will be no dm-verity warning.
Thanks for this guide, it worked great.
When you flash the downloaded 4.0.3, the ota of 4.1.0 will fail because somehow a partial ota is for some reason not possible. Anyway this is no problem because the phone will perform an automatic retry and downloads the full ota which worked for me and let the dm-verity warning disappear. I imagine future partial otas will work.
Therefore I think it is important to start with a version that is not the newest version (but e.g. with newest version - 1) or otherwise use some other way to get rid of the dm-verity warning.
Took the 4.0.3 update OTA but other than that followed exactly. Worked beautifully!
I didn't relock bootloader.
I also removed the default encryption.
I've followed all the steps, but dm-verity warning is still showing. I'm still on OOS 4.0.2 though. Someone with simmilar experience? How to get rid of that dm-verity warning?
Edit:
Manually upgraded to OOS 4.0.3 and dm-verity warning gone! Not sure why I was not receiving OTA update though.
What about returning to stock for 4.1.1??
I was coming from the beta channel, and after the initial wipe I was unable to boot into either recovery or the software. I had to reflash TWRP, and then I was able to install 4.02.
After unlocking, I was still getting the dm verity warning. The software attempted an OTA, but it failed. After this it downloaded the complete 4.1.3 via OTA, which worked and got rid of the dm verity warning.
Thanks for the guide!
Followed Tutorial 100% :/, Didn't get any error doing Flashing, Worked perfectly but still the DM-Verity warning.
That official TWRP 3.x is prone to cause dm-verify error and due to that I even has many files in /data lost! Better use TWRP 3.1 bluspark version. Though it's Unofficial its work best.. I also upgraded from 3.0 to 3.1 TWRP without getting the dm-verify error back..
arvindgr said:
That official TWRP 3.x is prone to cause dm-verify error and due to that I even has many files in /data lost! Better use TWRP 3.1 bluspark version. Though it's Unofficial its work best.. I also upgraded from 3.0 to 3.1 TWRP without getting the dm-verify error back..
Click to expand...
Click to collapse
How can I upgrade to the 3.1 version?
To return it to stock I just
1.flash the oneplus's Oxygen Recovery
2. full wipe in Oxygen Recovery
3. ADB sideload 4.0.3
4. lock oem in fastboot
and all the warning would disappear and every return to stock
diego97yey said:
How can I upgrade to the 3.1 version?
Click to expand...
Click to collapse
Just flash latest TWRP from recovery by clicking Install Image file or flash from fastboot...
x10000 said:
To return it to stock I just
1.flash the oneplus's Oxygen Recovery
2. full wipe in Oxygen Recovery
3. ADB sideload 4.0.3
4. lock oem in fastboot
and all the warning would disappear and every return to stock
Click to expand...
Click to collapse
Thanks bro ,, working Fine :good::good:
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
[UPDATE]: USE THIS ONLY FOR NOUGAT 7 OR 7.1! THERE IS A DIFFERENT GUIDE FOR ANDROID OREO!
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502 (Written by YasuHamed, not me!)
If you are not interested in android Oreo, or you want to go back to Nougat, this guide is still valid! [End of Update]
This is a guide for newbies or for people that are simply confused. If you have any questions, you can always ask me, and I will reply. but please make sure you haven't made mistakes and do not ask about things that are already stated here. Let's go!
BEFORE DOING ANYTHING, NOTES
-make sure you have installed ADB : https://forum.xda-developers.com/showthread.php?t=2588979
-make sure ADB can read your phone with the correct drivers installed. If you have trouble with that, read "DRIVERS" section
!It is absolutely necessary to install the drivers correctly!
-Backup your stuff if you have any, you will need to delete everything from the phone
-Enable USB debugging
-Note: some of these instructions apply to Windows OS only!
-Note: links to downloads have been shortcutted as much possible to make it easier for you!
-Find some stock roms here! https://forum.xda-developers.com/xperia-x/how-to/sonyx-f5121-downgrade-8-0-0-to-7-1-1-to-t3754986
(Credit: HEKER510)
-Warning: you will lose your warranty!
-I am not responsible for any damage done to your device.
BACKUP DRM KEYS (OR WORKAROUND)
You may want to unlock your bootloader. If you unlock it without backing up the DRM keys, you will lose them. I did that mistake and I regret it. If you already did, there is an alternative solution, skip to step 8.
1) If you are running android 7 nougat, you will need to downgrade to MM. If you are running MM, skip to step 7.
2) You will need to wipe everything before rolling back, so if you have any data back it up
3) Download any stock MM 6.0.1 firmware for the xperia X. You can find one here : https://mega.nz/#!1xRj2CYS Decryption key: !qBVi7yky8AL84eUF3bpTTGQ2YmN0ePCjc-eSDZGIZCI
Watch out: if you have the dual SIM model, F5122, you need to download accordingly!
For more firmwares, check "BEFORE DOING ANYTHING"
4) Download the latest flashtool: http://www.flashtool.net/downloads.php
Upon installation, tick on fastboot, flashmode drivers! If it didn't ask you, go to the installation folder and run Flashtool-drivers.exe. Please read "DRIVERS" section!
5) Flash the .tft file
How to flash?
0. Go to "C:\Users\[Your PC Name]\.flashTool\firmwares" , and put your firmware .ftf file in there!
1. Open Flashtool and click on the lightning bolt icon (first one from the left)
2. In the prompt, choose flashmode.
3. Under firmware, click on the version you put (It should probably only be one option)
4. Under wipe , tick everything. Under the others, do not make any changes.
5. Click "Flash"
6. When the popup appears, connect your device. It needs to be powered off, and connected while you are holding the
"volume down" button.
7. Wait for it to finish.
8. Done. Boot up the device, it might take some time to open so don't worry.
Click to expand...
Click to collapse
6)If your phone bootloops, try flashing again or a different firmware and make sure you followed the steps correctly.
7) Once your phone successfully boots android MM, use Dirtycow to get your DRM keys out: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
8) If you unlocked the bootloader before backing up your keys, you can use DRM kernel fix. You can get it here: https://forum.xda-developers.com/xperia-x/development/kernel-drm-fix-nougat-t3530849 Before using it check out the custom rom that includes this fix and other things.
UNLOCK BOOTLOADER
This is relatively easy and you can follow official sony instructions to do it.
1) Go to your phone settings, developer options, and enable OEM unlock
"But there is no developer options!" -Go to the bottom of your settings, system, about phone, and tap multile times on "Build Number", also at the bottom.
Click to expand...
Click to collapse
2) If you haven't already , install ADB fastboot and configure drivers (Link on top )
3) Follow the steps on the Sony website to get your unlock code: https://developer.sonymobile.com/unlockbootloader/email-verification/
4) After unlocking, a warning message on boot is normal!
INSTALL RECOVERY
Installing TWRP on your xperia X is very important, since you can flash zips and img files so easily, plus wipe, backup and other features.
1) Download the TWRP .img file: https://androidfilehost.com/?w=files&flid=197369 (Credit: eagleeyetom )
2) Make sure you have USB debugging enabled
3) Open your downloaded twrp folder
4) Run CMD in that folder (shift + right click inside the folder, Open CMD here )
5) Connect your Xperia X to your PC
6) Type these lines:
adb reboot bootloader
fastboot flash recovery recovery.img [where recovery.img is your twrp file name]
fastboot reboot
7) If no errors, twrp is now installed. Once your phone boots , turn it off,. To access TWRP recovery hold power button and volume down button until the TWRP menu appears.
STOCK ROM, ROOT
If you just want to root and not interested in additional features and tweaks, you can simply flash SU through TWRP to get your phone rooted.
Note: Current best stock ROM available: 7.1.1 (252) - better features than older ver, and good battery life.
0) Install your desired stock firmware using the exact same previous instructions, (under DRM section) with flashtool.
1) Download SuperSu
Or magisk, using YasuHamed guide mentioned on top, but I have not tested with anything other than Oreo 8.0
Use magisk if you want more stability / root features (like hide root from apps, modules )
2) copy it anywhere on your phone
3) Run TWRP
4) Tap on install
4) Flash the file
5) Reboot, you are now rooted
6) Insert your DRM keys if you have them
Custom ROMS
After unlocking the bootloader and installing TWRP this is the best way to go in order to get full root, tweaks.
https://forum.xda-developers.com/xperia-x/development/rom-xperia-x-pexorom-v1-0-0-f5122-f5121-t3590552
^ This is a very good custom ROM made by prmk74. You can see its features in his thread.
1) Download the rom and copy it to your phone
2) Run TWRP
note: It is recommended to wipe dalvik, cache, data ( your storage partition doesn't need to be wiped)
3) Tap install, find your downloaded file and execute
note: It is recommended to wipe dalvik, cache, data ( your storage partition doesn't need to be wiped)
4) Follow on-screen instructions, do not stop the booting after finishing the installation, it will take some time
5) Insert your DRM keys if you have them
6) For those who lost their keys: Now the functions like vivid image mode are working properly.
DRIVERS
For Windows 8/8.1/10 users, how to solve driver problems:
1) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers. Go to the flashtool install location and run the drivers.exe again, check fastboot and flashmode
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine
TO CONCLUDE:
This is what you may want to do to get the most out of your new xperia x:
1) Backup DRM
2) Unlock BL
3) Install TWRP
4) Flash Persian (or a different rom) through TWRP (And subscribe to the thread so you receive updates)
5) Restore DRM
Notes:
None of the links, tools are of my work, I'm just writing a guide for my fellow XX owners
^^ this guide is so really good :3. I post flash script for someone dont know how to find it ^^
unzip it in this position.
C:\Users\[user-name]\.flashTool\mydevices
max26292 said:
^^ this guide is so really good :3. I post flash script for someone dont know how to find it ^^
unzip it in this position.
C:\Users[user-name]\.flashTool\mydevices
Click to expand...
Click to collapse
Thanks!
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
brianx87 said:
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
Click to expand...
Click to collapse
These USB drivers are very annoying to work with. I got mine to finally work using a program called ADB driver installer. http://adbdriver.com/downloads/ Choose automated installation and try what I said. I believe it should fix your problem, after installing the drivers reboot and flash again.
Other than that, I have to ask are you 1000% sure you used the exact commands?
I saw another thread someone mistook
"flash recovery recovery.img" for "flash recovery.img"
"recovery" should be included before the recovery file name
brianx87 said:
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
Click to expand...
Click to collapse
Why didn't the sony guide work? It worked for me. Just so you know, the "device cant be trusted" message is appearing on everyones' phones after unlocking the bootloader, it's not a problem or something
the part of restoring DRM is skipped,
please xplain
YasuHamed said:
the part of restoring DRM is skipped,
please xplain
Click to expand...
Click to collapse
I know, as I said there is room for improvement. The reason I did not include it is because I never did it myself, so I don't want to write something wrong or something that could lead to problems. I write something only if I am 100% sure. If anyone of you is kind to offer that piece so the guide is complete I will be glad
FoxTheLegend said:
Why didn't the sony guide work? It worked for me. Just so you know, the "device cant be trusted" message is appearing on everyones' phones after unlocking the bootloader, it's not a problem or something
Click to expand...
Click to collapse
Ok I figured out what I did wrong and was able to amend another issue I edited out of this post.
brianx87 said:
Ok I figured outwhat I did wrong (able to boot into the os and warning message no longer an issue ) and the issue I am now facing is that twrp is hanging on the boot screen. Is this version of twrp built to a specific version of android?
Click to expand...
Click to collapse
What do you mean hanging? the twrp logo frozen?
FoxTheLegend said:
What do you mean hanging? the twrp logo frozen?
Click to expand...
Click to collapse
Working now, used a previous version of twrp by mistake. Using latest build works fine now, have to wait to get home from work to proceed with the rest, annoying procedures this stuff but your guide is great.
brianx87 said:
Working now, used a previous version of twrp by mistake. Using latest build works fine now, have to wait to get home from work to proceed with the rest, annoying procedures this stuff but your guide is great.
Click to expand...
Click to collapse
Thanks, Im glad to it works now
FoxTheLegend said:
I know, as I said there is room for improvement. The reason I did not include it is because I never did it myself, so I don't want to write something wrong or something that could lead to problems. I write something only if I am 100% sure. If anyone of you is kind to offer that piece so the guide is complete I will be glad
Click to expand...
Click to collapse
thank you for the answer sir
i am unable to find any twrp that work for my F5122, it always bricks and i have to reset.
is there any twrp recovery image that works correctly with f5122?
YasuHamed said:
thank you for the answer sir
i am unable to find any twrp that work for my F5122, it always bricks and i have to reset.
is there any twrp recovery image that works correctly with f5122?
Click to expand...
Click to collapse
Hmm.. Did you try the one from the poison thread? I myself have still the old version installed (not 3 or 3.1) if I find it on my pc I will share it with you
FoxTheLegend said:
Hmm.. Did you try the one from the poison thread? I myself have still the old version installed (not 3 or 3.1) if I find it on my pc I will share it with you
Click to expand...
Click to collapse
I have to modified kernel
all i want is to boot it via fastboot command
for example i have the rooted kernel SU installed (but battery drain is high) so i what wana do is flashing kernel with all securities OFF and then with twrp image i will do
Code:
fastboot boot twrp.img
i will boot the X in to twrp and i will flash SUPERSU via twrp.
thanks all
YasuHamed said:
I have to modified kernel
all i want is to boot it via fastboot command
for example i have the rooted kernel SU installed (but battery drain is high) so i what wana do is flashing kernel with all securities OFF and then with twrp image i will do
i will boot the X in to twrp and i will flash SUPERSU via twrp.
thanks all
Click to expand...
Click to collapse
I see, but don't you want to figure out why it's not working normally? Noone has reported a similar problem
FoxTheLegend said:
I see, but don't you want to figure out why it's not working normally? Noone has reported a similar problem
Click to expand...
Click to collapse
since there is no offcial twrp for X out yes and only DORA (XA) is available) even XA don't work for X
so either twrp 2.8, 3.0 or 3.1 any should just boot in order to let us flash superSU.
YasuHamed said:
since there is no offcial twrp for X out yes and only DORA (XA) is available) even XA don't work for X
so either twrp 2.8, 3.0 or 3.1 any should just boot in order to let us flash superSU.
Click to expand...
Click to collapse
=-= try to use this command fastboot flash recovery [your_recovery_name].img
I use f5122 and flash successfull twrp 3.0.2 and 3.1. with this, i flash some kernel and rom without any problem.
Everything is working good for me now, the only issue now is restoring the DRM keys, has anyone found a credible source for doing this on this device?
How can I be sure I have a full root? I can't seem to be able to uninstall some of the bloatware only disable it!
brianx87 said:
Everything is working good for me now, the only issue now is restoring the DRM keys, has anyone found a credible source for doing this on this device?
How can I be sure I have a full root? I can't seem to be able to uninstall some of the bloatware only disable it!
Click to expand...
Click to collapse
Well titanium backup can assure you but I don't see why you wouldn't have full root... You need an app uninstaller to uninstall bloatware, it can't be done through the settings you know that right
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
This is what I had - My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
Jazkade said:
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
Click to expand...
Click to collapse
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
brian117 said:
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
Click to expand...
Click to collapse
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
brian117 said:
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
Click to expand...
Click to collapse
Yes I did
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Can you give me a link pls?
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Flashing in progress.. please may this work..
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
EDIT: Seems you got it working. Congrats.
Jazkade said:
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
Click to expand...
Click to collapse
Choose an username... said:
Click to expand...
Click to collapse
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Jazkade said:
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Click to expand...
Click to collapse
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Choose an username... said:
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Click to expand...
Click to collapse
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Jazkade said:
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Click to expand...
Click to collapse
Enter fastboot and type the command "fastboot erase userdata
Choose an username... said:
Enter fastboot and type the command "fastboot erase userdata
Click to expand...
Click to collapse
adb reboot fastboot and it just reboots normally.
Jazkade said:
adb reboot fastboot and it just reboots normally.
Click to expand...
Click to collapse
Well whatever then just install TWRP. Use controllerboy's guide
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
idk how to downgrade to marshmellow.
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
downgraded, unlocked, twrp is up and running
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.