How will I root Android 13 OnePlus 8 pro
Nivu_s said:
How will I root Android 13 OnePlus 8 pro
Click to expand...
Click to collapse
How I always do it is extract the rom your on, then extract payload.bin with Payload Dumper. Then take the file boot.img and put it in your download folder on your phone. Then install the Magisk apk on your phone. Fire up Magisk and do any updates that it needs. Then open Magisk and hit install from the top Magisk section. Select "Select and Patch a File" and then select the Let's Go button. Navigate to your dowload folder and select the boot.img you put there and hit hit Lets Go again. Magisk will create a boot image that you can flash to get root.
Take this new image off your phone and stick it in your extracted folder with the rom. Open Power Shell by holding shift down and right clicking your mouse. Then flash your new file with the command Fastboot flash boot xxxxxxxx.img. (your file name) Reboot and you are rooted.
Of course this is a Windows only way to do it. You can do the same thing in Linux , but it is a bit more difficult.
Did it work for u
Nivu_s said:
Did it work for u
Click to expand...
Click to collapse
Yes, it works with any rom. I have rooted A11, A12, & A13 custom and stock roms this way.
I forgot to tell you that you have be in Fastboot mode to flash the boot file. The easyist way is to turn it off, then turn it on while holding Volup/Voldown/power all at the same time and this will put you in fastboot mode to flash your boot file.
Ok I'll try this
Make sure to always use this command first. If it boots and works properly then you can consider flashing it. the boot command attempts to boot the named image file. If it fails to boot it's as simple as rebooting to get back to normal. Also if you ever have an app that won't install with root you can run the following command with the stock boot.img and it will allow you to do what ever you need to do, after reboot you'll be back to normal with root and the app installed. I must do this when installing chase and using fingerprint login.
fastboot boot name_of_boot.img
Unable to unlock bootloader it says command not supported in default implementation.
android 13.
In2021
Can unlock bootloader on 10-11
wtf!!droid said:
Unable to unlock bootloader it says command not supported in default implementation.
android 13.
In2021
Can unlock bootloader on 10-11
Click to expand...
Click to collapse
You can MSM back to 11 fairly easy.
HolyHog said:
You can MSM back to 11 fairly easy.
Click to expand...
Click to collapse
Wym how can i update my phone with unlocked bootloader
wtf!!droid said:
Wym how can i update my phone with unlocked bootloader
Click to expand...
Click to collapse
MSM doesn't care what status your phone is in. It installs the rom it is associated rom under any circumstance. You will lose anything you don't have backed up but you will start with a fresh install of A11 which can be unlocked. Then you can upgrade back up to A13 with an unlocked bootloader. When you unlock the boot loader your phone will do another wipe so don't bother doing anything on the first boot. Just get to Developer settings to hit the unlock button, boot to fastboot to OEM unlock and you will be good to go.
A trick to use MSM is start the program and hit start so it will be sniffing for your phone. Then hook it up your computer while on and then hold down Vol UP/Vol Dn and power at the same time until MSM grabs it and starts installing. When it is done, do a reboot process before unlocking bootloader.
HolyHog said:
MSM doesn't care what status your phone is in. It installs the rom it is associated rom under any circumstance. You will lose anything you don't have backed up but you will start with a fresh install of A11 which can be unlocked. Then you can upgrade back up to A13 with an unlocked bootloader. When you unlock the boot loader your phone will do another wipe so don't bother doing anything on the first boot. Just get to Developer settings to hit the unlock button, boot to fastboot to OEM unlock and you will be good to go.
A trick to use MSM is start the program and hit start so it will be sniffing for your phone. Then hook it up your computer while on and then hold down Vol UP/Vol Dn and power at the same time until MSM grabs it and starts installing. When it is done, do a reboot process before unlocking bootloader.
Click to expand...
Click to collapse
It automatically locks the bootloader once the flash is complete.
Idk what you are talking about
I can revert back to 10-11-12 but my question is about bootloader unlock on android 13
wtf!!droid said:
It automatically locks the bootloader once the flash is complete.
Idk what you are talking about
I can revert back to 10-11-12 but my question is about bootloader unlock
Click to expand...
Click to collapse
Yes, MSM will completely put you back to stock with a locked bootloader. You will be able to unlock it after 1 boot up on A11.
@HolyHog He is saying that once he flashes whatever he is flashing to get to Android 13, once he is ON 13 and gets it all booted up n stuff... that the bootloader is at that point, re-locked.
wdarea51 said:
@HolyHog He is saying that once he flashes whatever he is flashing to get to Android 13, once he is ON 13 and gets it all booted up n stuff... that the bootloader is at that point, re-locked.
Click to expand...
Click to collapse
If your bootloader is unlocked, no OTA will lock it again. How are you upgading? I have OTA'ed a few times to A13 and my bootloader stayed unlocked through the process.
Related
This is FINAL working method.
First off you must unlock bootloader, and install twrp.
instructions for unlock bootloader are in this thread
http://forum.xda-developers.com/r1-...mazon-root-t3490882/post69387472#post69387472
I made many cycles between 6.6 and 6.1 and found that this set of files was minimum needed to maintain stable device. I started with only the preloader, and that left the phone able to connect to spft but the preloader was o longer in the "trusted zone" so it would not load the second step of power on (lk). replaceing the lk with spft after that allowed to boot to the boot menu, but would not trust the next step(boot.img). But with the preloader and lk I was able to fastboot, so was able to oem unlock.. this was the first method I was going to suggest. After more trials I decided it better to foll back all the bin files that the update replaced and also the secret bin so no more need to oem unlock after the roll back.
I got so comfortable moving between preloaders and version I got careless. My carelessness allowed me to mix up secure preloader and bin files with custom non secure recovery files and without realizing it I rebooted like that. I was left in a secure environment that was panicking because the recovery was not properly signed. (a terminal soft-brick)
My point is once you roll back DO NOT go back to locked and DO NOT blame me if you forget and restore some backup that does that to you down the road.
I do recomend that you roll back though. Because with the roll back, you are almost certain not able to brick because you can always use spft to to fix things.
THIS WILL ROLL BACK BOOT LOADER AND ALLOWS SPFT .
THIS HAS ONLY BEEN RUN WITH TWRP.
But the fastboot mode can also flash preloader if prefered. Just remember you may also need to oem unlock again after. This has not and will not be tested by me.
ONCE YOU HAVE UNLOCKED BOOTLOADER AND INSTALLED TWRP, return here and download "after_bootloader_roll_back_5.tar" unpack the tar and run the .bat file. It will adb push the recovery image to you phone and then install it.
It will rewrite :
1. preloader
2. lk (little kernel)
3. boot img
4. seccfg.bin
5. frp (to make sure bootloader remains unlockable)
6. trustzone (goes into both TEE1 and TEE2
7. secro.bin
All done.
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
jhonjahegu said:
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
Click to expand...
Click to collapse
Sounds like you need to do oem unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot oem unlock"
6. If need to do oem unlock you will also need to "fastboot format userdata"
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
digihaven said:
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
Click to expand...
Click to collapse
If it is looping into twrp then you must do step 6 from above.
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
clownkitty said:
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
Click to expand...
Click to collapse
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
mrmazak said:
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
Click to expand...
Click to collapse
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
clownkitty said:
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
Click to expand...
Click to collapse
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
mrmazak said:
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
Click to expand...
Click to collapse
I didn't realize you had to load straight into recovery mode after flashing it, I got it to work now, thank you so much!
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
tuespazio said:
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
Click to expand...
Click to collapse
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
mrmazak said:
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
Click to expand...
Click to collapse
Hi, dont worry now is fixed i return to 6.1 and then flash full 6.5 firmware.
Data is now working fine .
Thanks for your Support
sorry, wrong thread
ncy1 said:
Hi guys, sorry to bother you with this
I was on 6.0 rooted and without ads, i just tried to update my phone using the v17 and settings on this thread, when i went to cellphone info on settings it said i was still on 6.0. Did i miss something or this a normal thing? Anyway, i went back to recovery mode, did a wipe and tried to flash the 7.4.2 rom but it sent me an error, now the phone won't boot and gets stuck on the blu loadscreen.
Click to expand...
Click to collapse
Don't get me wrong, I feel bad for you that your phone is in this situation, but that has nothing to do with the thread you are posting in.
This thread is for rolling back the preloader.
And all the oem and Amazon Roms are 6.0
To get help you should post in the thread you got the ROM from.
And include the error you got.
mrmazak said:
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Click to expand...
Click to collapse
I think I just want to try this method, since I want to convert it to OEM and still keep OTA updates anyway. I'm blanking though as to how I need to go about this.
I have adb installed, and I have access. I assume this requires a fastboot command, but I don't know which.
Jessooca said:
Mrmazak... does this work on a new out of the box blu r1 that came with the 6.6 August update already installed?
I'm trying to help a friend, I surprisingly can't get the bootloader unlocked, dirtycow continually failed.
He doesn't care about updates etc... just wanted to flash the no ads firmware onto a prime version blu r1 hd
Click to expand...
Click to collapse
To the best of my knowledge it was.
Last time someone told me they were having trouble, they ran the codes manually one by one instead of using the script, and it worked. Apparently they had trouble pushing the files from the batch file. I had similar trouble when I wrote the script, that is why there are 3 second pauses ,that seemed to fix it for me. I will change them to 10 seconds and see if it helps.
I will update here when I change it then you candownload again and try, or you can make the changes yourself and let the me know
OK i updated the one-click.bat . you can download it again to see if that help. Also you said dirty-cow keeps failing, please let me know the fail message and also the comments displayed during the first part of the script. the part that is pushing files.
Also I have not been able to get feedback on the one-click.sh for linux. I don't normally use linux and did not test the shell. If you are using that one maybe the fail is my poorly written .sh
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
danbcooper said:
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
Click to expand...
Click to collapse
"oem" is not supposed to be capitalized
i went back and edited that original post too.
mrmazak said:
"oem" is not supposed to be capitalized
i went back and edited that original post too.
Click to expand...
Click to collapse
Now I ran "fastboot oem unlock" and it says FAILED (remote: unknown command). Do you know why?
Never mind.. Tried again and worked! Thanks for everything!
Hey all.
-Yesterday my phone updated from stock Android 6.1 (EMUI4.x I think) to stock Android 7 (EMUI5.0).
-Before the update, I had unrooted my phone, so I had an unlocked bootloader, and I also had installed TWRP Recovery.
-After the update, I realized that my device had become again unrooted and that the TWRP Recovery was gone.
Now, ofcourse my device has still an unlocked bootloader right? When I am in fastboot mode my device says "UNLOCKED" so I guess I have an unlocked bootloader.
I follow the steps to install TWRP Recovery:
1) I connect my phone (USB debugging ON etc) ("adb devices" -> is showing my device fine)
2) "adb reboot-bootloader"
3) "fastboot devices" (is showing my device fine)
4) "fastboot flash recovery twrp...img"
5) It says installation is ok
6) "fastboot reboot recovery"
7) Phone restarts and tries to boot into recovery but it's kept stuck there forever and says "Your phone is booting now...." So I just press Power off for a few seconds to escape and the phone boots normally to normal mode.
It seems that I can't install properly the recovery after the update.
Why is that?
Notes:
-When I turn on my phone (normally with the Power on button), a screen appears that offers me 3 options, one of them says "Press VolumeUp Key for a few seconds to boot into recovery", if I do that then my phone boots into stock recovery of EMUI.
-When my phone is off, and I press Power On + Volume Up then my phone tries to get immediately to recovery but it keeps stuck there forever ("Your device is booting now...") and I can escape only by pressing Power off for a few seconds (just like in step 7 above)
Thanks in advance.
The Bootloader is sometimes bugged after upgrade.
Try booting normally and go in and activate Developer Menu (if it's not active).
Find the OEM option in the menu and disable it.
Reboot.
Go in and enable it again.
Now try and install the recovery.
NOTE: I had to use the recovery called "twrp-3.1.0-2-hi6250.img".
Sidenote: I used SRKToolHuawei 2.0 to do the stuff. The guide below is for Windows pc's:
REMEMBER to get the correct recovery for Nougat if you try this (see above).
Rename it to "twrpp9litemm.img" and zip it.
Rename the zip file to "p9lite.zip".
Put it into the subfolder "..\recovery\p9lite", overwriting the original zip file.
Thanks for the reply.
The OEM option is already ON, but it won't allow me to move the switch in order to turn it off. What should I do?
greekoo1994 said:
Thanks for the reply.
The OEM option is already ON, but it won't allow me to move the switch in order to turn it off. What should I do?
Click to expand...
Click to collapse
Try resetting factory settings then redo all the steps
Which TWRP have you used?
i guess u have to unlock your bootloader again.
it wrongly shows the state of your bootloader. at least it was like this for me...and others here
Potato997 said:
Which TWRP have you used?
Click to expand...
Click to collapse
This https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
And this https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847
pimser said:
i guess u have to unlock your bootloader again.
it wrongly shows the state of your bootloader. at least it was like this for me...and others here
Click to expand...
Click to collapse
But I don't understand how it is possible for a bootloader to be locked after some software update? I mean the bootloader is at the bottom level of the phone (lower level than software).
greekoo1994 said:
This https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
And this https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847
But I don't understand how it is possible for a bootloader to be locked after some software update? I mean the bootloader is at the bottom level of the phone (lower level than software).
Click to expand...
Click to collapse
it can be locked by the firmware
greekoo1994 said:
This https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
And this https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847
But I don't understand how it is possible for a bootloader to be locked after some software update? I mean the bootloader is at the bottom level of the phone (lower level than software).
Click to expand...
Click to collapse
i dont know the process exactly but it does relock the bootloader after update. unfortunately it shows bootloader unlocked aldough it is locked. just unlock again with unlock code (attention phone will be reset afterwards, do backups) and flash twrp for root.
:good:
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.
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now
videodave1 said:
just trying to get back to stock now
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.
I have installed lineage os: https://forum.xda-developers.com/t/rom-official-instantnoodlep-11-lineageos-18-1.4192827/
Now I want to revert back to stock oxygen os. I have extracted payload.bin with contains lot of .img files
What are the fast boot commands to remove lineage os and re-install and install oxygen?
williamshockley said:
I have installed lineage os: https://forum.xda-developers.com/t/rom-official-instantnoodlep-11-lineageos-18-1.4192827/
Now I want to revert back to stock oxygen os. I have extracted payload.bin with contains lot of .img files
What are the fast boot commands to remove lineage os and re-install and install oxygen?
Click to expand...
Click to collapse
You're going to wipe anyway, just use the MSM tool. That's all I did.
Then re- unlock and you're done.
There could be a way to just flash singular images, but to avoid a dirty OS, I had used MSM, it's quick and it works.
dladz said:
You're going to wipe anyway, just use the MSM tool. That's all I did.
Then re- unlock and you're done.
There could be a way to just flash singular images, but to avoid a dirty OS, I had used MSM, it's quick and it works.
Click to expand...
Click to collapse
is it available for linux?
williamshockley said:
is it available for linux?
Click to expand...
Click to collapse
I don't think so mate, could ask in the forum..
Or you could just relock the bootloader, personally I'd go with the MSM but that's me.
Relocking is straight forward, kind of like reverse unlocking.
1. Reboot into Stock Recovery
2. Factory Reset the Device and Select Wipe All
3. Reboot into fastboot mode and connect to your pc
4. Use the command: factboot devices to check if your device is connected if it gives you the serial key
5. Use the command: fastboot oem lock and your device will give you the selection screen.
6. Select Lock Device from the volume rockers and use power button to confirm your selection.
7. Device will be locked and will boot into OOS
dladz said:
I don't think so mate, could ask in the forum..
Or you could just relock the bootloader, personally I'd go with the MSM but that's me.
Relocking is straight forward, kind of like reverse unlocking.
1. Reboot into Stock Recovery
2. Factory Reset the Device and Select Wipe All
3. Reboot into fastboot mode and connect to your pc
4. Use the command: factboot devices to check if your device is connected if it gives you the serial key
5. Use the command: fastboot oem lock and your device will give you the selection screen.
6. Select Lock Device from the volume rockers and use power button to confirm your selection.
7. Device will be locked and will boot into OOS
Click to expand...
Click to collapse
Should we use the relock method while in AOSP or after using the MSM tool? i have a macbook and i don't mind loosing data, just can't use MSM tool.
driss.sadok said:
Should we use the relock method while in AOSP or after using the MSM tool? i have a macbook and i don't mind loosing data, just can't use MSM tool.
Click to expand...
Click to collapse
MSM will relock the bootloader.
If you can't use MSM (not sure why that would be the case) then fastboot a stock ROM and then lock the bootloader, but as I said MSM would be a lot easier and risk free
dladz said:
MSM will relock the bootloader.
If you can't use MSM (not sure why that would be the case) then fastboot a stock ROM and then lock the bootloader, but as I said MSM would be a lot easier and risk free
Click to expand...
Click to collapse
I will try, thanks a lot
driss.sadok said:
I will try, thanks a lot
Click to expand...
Click to collapse
I made a video on YouTube, can be found in the 8 pro MSM thread on how to access edl mode, bare in mind you need to be quick from that point
dladz said:
I made a video on YouTube, can be found in the 8 pro MSM thread on how to access edl mode, bare in mind you need to be quick from that point
Click to expand...
Click to collapse
Actually i don't have windows, I'll wait till i find one to be sure in case flash fastboot will brick my phone.
And sorry for Liverpool's lost
driss.sadok said:
Actually i don't have windows, I'll wait till i find one to be sure in case flash fastboot will brick my phone.
And sorry for Liverpool's lost
Click to expand...
Click to collapse
Ah it is what it is. We played really bad..
Midfield yet again.
As for no windows, how were you planning to lock your bootloader or do anything else? If you meant you've got Linux or otherwise then pop win 10 on a dual boot.
dladz said:
Ah it is what it is. We played really bad..
Midfield yet again.
As for no windows, how were you planning to lock your bootloader or do anything else? If you meant you've got Linux or otherwise then pop win 10 on a dual boot.
Click to expand...
Click to collapse
no i said i have a macbook m1 which is not a native system for parallels desktop.... i usually flash my phones using terminal to flash or unlock etc. just like in windows powershell i just begin the command with the ./fastboot ....
driss.sadok said:
no i said i have a macbook m1 which is not a native system for parallels desktop.... i usually flash my phones using terminal to flash or unlock etc. just like in windows powershell i just begin the command with the ./fastboot ....
Click to expand...
Click to collapse
Ah ok sorry, I'm tired, missed it.
I've installed parallels on an M1 and if works perfectly fine mate.
I finally found a windows laptop, i did install oos 11 using MSM and it worked like charming. But the thing is, i have a EU phone and i choose to change it to INDIAN firmware version to have the chance test the colors os 13 beta. It did work too.
I didn't like Coloros in general so i did the same again, oos 11 with MSM indian firmware instead of europian's.
The problem is, after updating to oos 12 with air ota, i am stuck at version C60. And when i use oxygen updater app from playstore, i could download the C63 but it couldn't be installed with built in local updater neither with the OPlocal update.apk.
Should i revert back to EU to fix this ?
i tried to go back to oos 11 froom lineage os 20, ietting error param preload device not match image