Enchilada Partition Resizer for OnePlus 6!
What does this tool do? And what are the benefits? Well. This tool will resize Your system partition size to 6GB allowing You to flash any sGSI (some of them are huge) and my future roms that will require more than 3GB (2850mb roughly) system size. It's pretty problematic for many roms and I just delay them because of this.
DO NOT use it on 7 Pro, OP7 or anything else. (6T Tested and works)
I also added a backup feature of Your stock partition table just in case. Might be useful for some people.
Known Issues
You might get stuck in fastboot until You flash a ROM
How to Use:
MAKE SURE TO BACKUP EFS, DATA AND PERSIST (if possible) BEFORE USING IT!
Also make sure You're not currently using EPR! (If You already used 1.0 and Your system is still 6GB, no need for 2.0)
Boot into TWRP (Tested on BluSpark)
Flash EPR zip that matches Your storage
Reboot to bootloader (fastboot menu)
Run any force wipe flasher of a rom that You want to use.
Wait till it finishes flashing and done!
If You want to go back, simply flash EPR Remover and Format data + wipe system.
Download:
Enchilada Partition Resizer 2.0.1 TWRP Flashable
If You have any other problems, just ask here on XDA or for the fastest support PM me or ask someone in my group on Telegram
Join my group!
If You want to motivate me to work more, buy me a coffee!
https://www.paypal.me/protodevnano
Credits:
Alternative415 for testing 2.0 all day! :highfive:
Amir and Geci for testing and providing 256 and 64GB sizes!
Manan Gupta for Initial Windows version.
Adarsh for testing Windows version and having to use EDL 7 times
CosmicDan for original guide that helped me a lot!
OnePlus for creating OP6!
My friend Dylan for always supporting me
If I forgot anyone, just PM me on Telegram!
XDA:DevDB Information
Enchilada Partition Resizer, Tool/Utility for the OnePlus 6
Contributors
ProtoDeVNan0
Version Information
Status: Stable
Created 2019-09-01
Last Updated 2019-09-01
Changelog:
02.09.19 - Added Windows Support
22.03.20 - Corrected guide in EPR 2.
Added windows batch compatibility. Haven't tested on an android device but seems to work.
https://drive.google.com/file/d/1IS8cfD59okX9qwaXUKxxVQedNzmpHhmt/view?usp=sharing
its not working for me on windows. but thanks anywya
Can't get into TWRP after resizing (Windows) ?? Always reboot to bootloader.
EDIT ; Maybe doing wrong.. Will edit again soon.
WrathChild08 said:
Can't get into TWRP after resizing (Windows) ?? Always reboot to bootloader.
EDIT ; Maybe doing wrong.. Will edit again soon.
Click to expand...
Click to collapse
same for me. now im tring to unbrick my phone.
WrathChild08 said:
Can't get into TWRP after resizing (Windows) ?? Always reboot to bootloader.
EDIT ; Maybe doing wrong.. Will edit again soon.
Click to expand...
Click to collapse
synk48 said:
same for me. now im tring to unbrick my phone.
Click to expand...
Click to collapse
When You're in a fastboot lock, You have to check what partition is active and then set it as active again.
So on windows if You resize A. And end up in fastboot lock.
You should use
fastboot --set-active=
(It will show You current slot)
and then
fastboot --set-active=a
If Your slot is a.
I have no idea why this happens but oh well. One day we will have 3 slots so let's appreciate 2 :silly:
Gonna try this to install OP7 Android 10 Rom Port, thanks. I Was on it all night long wondering why I couldn't make it working.
EDIT : Still stuck in fastboot mode even after typing fastboot --set-active=a (I resized a, yep), can't go to recovery. But maybe it's related to Android Q ? was on Q DP3 before resizing. Or Maybe it's because the OP7 ROm Port is hard to install aha. After cheking, system is 6Gb size so I guess your software is okay.
WrathChild08 said:
Gonna try this to install OP7 Android 10 Rom Port, thanks. I Was on it all night long wondering why I couldn't make it working.
EDIT : Still stuck in fastboot mode even after typing fastboot --set-active=a (I resized a, yep), can't go to recovery. But maybe it's related to Android Q ? was on Q DP3 before resizing. Or Maybe it's because the OP7 ROm Port is hard to install aha. After cheking, system is 6Gb size so I guess your software is okay.
Click to expand...
Click to collapse
follow this steps
if you are stuck in bootloader bootloop do this
1. msm download tool than back to OOS 5.1.11
2. unlock bootloader
3. manual update to OOS Q DP3
4. install patched boot to get magisk without root there you can find partched boot.img https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
4. this step is because android Q dont let you boot to TWRP by bootloader
5. install TWRP Zip with magisk
6. boot to recovery and open ERP Script to resize your partition and chose partition a
7. in bootloader put fastboot set_active b and then boot to recovery
8. select partition a
9. do a factory reset, wipe data
10. boot to bootloader
11. open OP7 Android 10 Port scrip
12. in bootloader put fastboot set_active a
13. done
if you phone still doesnt boot go to bootloader set_active b go to recovery, chose partition a in twrp and do a factory reset and wipe data again and reinstall OP7 port.
is the only way its worked for me. i hope it works for you.
sorry about my english.
The command window just vanishes after typing in the partition and hitting enter. Have tried entering both `a` and `b` and even tried running the batch file as an administrator. Anyone else facing this issue on Windows?
you forgot to type 'system'
sahu.prashant said:
The command window just vanishes after typing in the partition and hitting enter. Have tried entering both `a` and `b` and even tried running the batch file as an administrator. Anyone else facing this issue on Windows?
Click to expand...
Click to collapse
you wrote system first and next the partition letter?
synk48 said:
you wrote system first and next the partition letter?
Click to expand...
Click to collapse
LMAO I feel stupid. I just typed in the letter. :silly:
synk48 said:
follow this steps
if you are stuck in bootloader bootloop do this
1. msm download tool than back to OOS 5.1.11
2. unlock bootloader
3. manual update to OOS Q DP3
4. install patched boot to get magisk without root there you can find partched boot.img https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
4. this step is because android Q dont let you boot to TWRP by bootloader
5. install TWRP Zip with magisk
6. boot to recovery and open ERP Script to resize your partition and chose partition a
7. in bootloader put fastboot set_active b and then boot to recovery
8. select partition a
9. do a factory reset, wipe data
10. boot to bootloader
11. open OP7 Android 10 Port scrip
12. in bootloader put fastboot set_active a
13. done
if you phone still doesnt boot go to bootloader set_active b go to recovery, chose partition a in twrp and do a factory reset and wipe data again and reinstall OP7 port.
is the only way its worked for me. i hope it works for you.
sorry about my english.
Click to expand...
Click to collapse
after step 3 fastboot commands dont work, flashing twrp fails
Makhosi Mayisa said:
after step 3 fastboot commands dont work, flashing twrp fails
Click to expand...
Click to collapse
i sent you a PM...
synk48 said:
i sent you a PM...
Click to expand...
Click to collapse
Can you share?
Rishwan said:
Can you share?
Click to expand...
Click to collapse
what do you need?
synk48 said:
what do you need?
Click to expand...
Click to collapse
Same as above. I get the same error. Can't make EPR work, I end up in bootloader bootloop.
Rishwan said:
Same as above. I get the same error. Can't make EPR work, I end up in bootloader bootloop.
Click to expand...
Click to collapse
tell me what are you doing? step by step
synk48 said:
tell me what are you doing? step by step
Click to expand...
Click to collapse
tried a lot of ways.
1) MSM to go to 9.0.8
2) unlock bootloader and install twrp
3) boot twrp (with 9.0.8)
4) install dp 3 + twrp, reboot to recovery and repeat for both slots
5) on slot A, run EPR
6) at fastboot with no other way except to use msm because no command (such as set_active) makes it boot. at this point, i can't even go to recovery/bokt recovery (as Q doesn't support boot command)
method 2)
repeat the same except i ran EPR with 9.0.8 same issue. goes to bootloader always
Related
Hello everyone,
I've been tinkering around with Generic System Images since the Oreo Developer Preview 1 came out for the Razer Phone. I'm glad to say I got it to work, with lots of help from @MishaalRahman, @P4Block and indirect help of @phhusson and @TheCrazyLex.
What's working as of right now:
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
What needs further testing:
- 4G/LTE FIXED check out post #77!
- Once the above is confirmed to work => VoLTE on any carrier, and also testing on certain carriers like 3 UK (since they sold a version with different software).
What's broken:
- Audio in phone calls (works properly in VoIP/3rd party apps) FIXED check out post #48!
What ROMs can be booted with this (as of 30-03-2018):
AOSP 8.1
Lineage OS 15.1
Resurrection Remix
More to come...
Setting up your device:
You'll need:
Code:
To [URL="https://forum.xda-developers.com/razer-phone/how-to/guide-to-unlocking-bootloader-t3706462"]fully unlock your bootloader[/URL] and [URL="https://forum.xda-developers.com/showpost.php?p=74607352&postcount=8"]unlock flashing capabilities[/URL] on your device.
[URL="https://eu.dl.twrp.me/cheryl/twrp-3.2.1-0-cheryl.img.html"]TWRP image[/URL] + [URL="https://eu.dl.twrp.me/cheryl/twrp-installer-3.2.1-0-cheryl.zip.html"]TWRP injector[/URL]
[URL="http://tiny.cc/latestmagisk"]Magisk flashable zip[/URL]
A GSI of your preference from the ones listed [URL="https://forum.xda-developers.com/project-treble/trebleenabled-device-development"]here[/URL]. PS: Use the Gapps+SU one if you choose AOSP ;)
0. Make sure you're running the Android O DP1 from Razer, or any future update to it.
THIS WON'T WORK ON NOUGAT
1. Properly install TWRP on your device: (I'll be using @Dees_Troy's guide with a few modifications to make very sure everything will work as intended)
- fastboot flash the twrp image as explained by him, in your currently active boot partition. PS: After flashing the Android O DP1, it will always be A.
Dees_Troy said:
Once you have adb working, run this command: adb shell getprop ro.boot.slot_suffix
It should say: [ro.boot.slot_suffix]: [_a] Or: [ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this: fastboot --set-active=_b Or on slot B type this: fastboot --set-active=_a
You should see something like this: Setting current slot to 'a'... OKAY [ 0.042s] finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this: fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Click to expand...
Click to collapse
2. Once you're in TWRP, DO NOT SLIDE to allow modifications, but tap on Mount as Read Only. Plug in your USB cable, and adb push the boot image from the Android O DP1 factory image to your sdcard, as well as the TWRP injector and the Magisk zip. That can be done with the following commands:
Code:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
Code:
adb push path/to/the/factoryimage/boot.img /sdcard
Code:
adb push Magisk-16.0.zip /sdcard
3. Go into Reboot, then make sure you're on partition A. Else, tap on the button to set A as the active partition.
Now go back, tap Install, then tap on 'Install Image' then choose the boot.img you just pushed, and flash it as boot image.
Now go back, into Reboot, and move to partition B and repeat the step above.
Once you're sure both partitions only contain the unmodified boot images, set the partition A as active, go into Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
Once it finishes, do the same with the Magisk zip file.
4. Go into Reboot, press on Bootloader.
5. Connect the usb cable, and flash the GSI system image onto your system_a partition through fastboot from your pc. This can be done with the command:
Code:
fastboot flash system_a system-arm64-ab.img
5.b If you wish, you can install a different GSI onto your system_b partition, and that can be done with the following commands:
Code:
fastboot set_active b
Code:
fastboot flash system_b system-arm64-ab-gapps-su.img
5.c If you wish to go back to the system_a partition, you can execute:
Code:
fastboot set_active a
6. Reboot and enjoy.Prebuilt boot image:
If doing the steps from 1-4 seems messy or you don't get it to work properly, I've published the image I made following them with the latest Magisk and TWRP versions available as of April 20th 2018.
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
Code:
fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
SHA-2: 2f0c7348ac906f2f81fa39df7b24b69392783bd2379d5da357777be444c67d97
Old version (from ODP1 - may experience the bootloader issues):
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180330_cheryl_odp1.img
Code:
fastboot flash boot_b boot_linuxct_20180330_cheryl_odp1.img
SHA-2: 8f763162415167b2e919a450654f9a46f69b81f6853013bcabf362dfeb2a115e
Many thanks to everyone that helped me today to get this to work properly!
Want some screenshots?
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
PupPupG said:
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
Click to expand...
Click to collapse
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
This is awesome!!!
I'd love to have a fully working resurrection remix build working on my cheryl!!!!! =D <3
KEEP UP THIS AWESOME WORK!!!!!!!!!
linuxct said:
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
Click to expand...
Click to collapse
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
PupPupG said:
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
Click to expand...
Click to collapse
Flash the Oreo DP1 image and start over.
linuxct said:
Flash the Oreo DP1 image and start over.
Click to expand...
Click to collapse
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Flashing the Oreo DP1 image actually flashes an empty, non-encrypted userdata image. That's why I requested to start over.
That can also be another solution, bit messier than starting over but it's good.
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
M1cky said:
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
Click to expand...
Click to collapse
I do. Try installing the latest beta of Magisk and then, if that didn't solve it, try setting a new Build fingerprint with a tool like MagiskHide Props Config (PS. Just to be sure, set the Google Pixel 2 XL one since that's the only 8.1.0 build fingerprint provided by that tool).
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Happy to see people making use of Treble on Razer Phone this quickly.
Good job! @linuxct
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
RUNNERX said:
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
Click to expand...
Click to collapse
Yes, it happens sometimes. Let me explain this briefly:
1. This bootloader seems to forget what the active partition was when it was told to reboot the device instead of turning itself off, and I don't know why yet. It happens 1/5 times I press on "Reboot", more or less.
2. You need to re-set the active partition to the one you were using, in my case A, so with a cable and my pc I run
Code:
fastboot set_active a && fastboot reboot
Tired of typing, I made myself a script named razer in my /usr/bin
Code:
#!/bin/zsh
fastboot set_active a && fastboot reboot
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
el4nimal said:
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Click to expand...
Click to collapse
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
linuxct said:
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
Click to expand...
Click to collapse
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Resurrection Remix Intensifies
el4nimal said:
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Click to expand...
Click to collapse
Unless you have overwritten it, boot to download mode and use fastboot to switch to the other slot which will allow you to boot into TWRP and install Magisk. If you have overwritten TWRP, flash it on the other slot (for example if you have LOS installed in A, flash TWRP into B).
linuxct said:
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
Click to expand...
Click to collapse
It has happened after a power off also, would putting the same rom in a&b slot stop it? system_other is not bootable so the phone enters download mode? I don't understand the working of the a/b system.
And THANK YOU so much for working on this, so nice to be back on custom roms!
Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27
So we can flash either through TWRP or Fastboot right?
Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%
Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.
Thank you very much.
Is there any userdata.img available?
alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.
sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found
I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?
Thanks. Both methods work fine. Don't ask how I found out.....
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1
Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it
Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?
Does Nokia 1 support DT2W?
Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance
Can any please repost the firmware , the link isn't working
How to Install TWRP Recovery & Root Essential PH-1 (Windows/Mac/Linux)
This is an alternate method on how install TWRP. This one might give you a better understanding of slots.
Another method can be found at below link. Use whatever is easier for you.
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Warning 1: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 2: You might loose all your data. Make sure to backup your data.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pre-Requisites
Make sure you have unlocked the bootloader.
Download and Install drivers (Windows) :- https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Make sure to remove pin/password/pattern etc. Even though TWRP support decryption I personally suggest you remove it and can add it back later.
Make sure you are stock. If you are rooted, please install stock boot.img.
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Steps
1. Download all the files listed in downloads section and place them inside one folder say ph-1.
2. Unzip fastboot and adb zip file (platform-tools). Rename twrp image file to twrp-mata.img. move twrp img file to platform-tools folder.
3. Connect phone to computer and copy below files to internal memory.
* TWRP Installer Zip
* Magisk Zip
Reboot device into bootloader mode.
4. Using command prompt/terminal navigate to folder where fastboot is.
Command Prompt
Code:
fastboot devices
Mac/Linux/Powershell
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
5. Find current slot. Note this down some where.
Command Prompt
Code:
fastboot getvar current-slot
Mac/Linux/Powershell
Code:
./fastboot getvar current-slot
6. If you get current slot as
* A - we will flash twrp to slot B
* B - we will flash twrp to slot A
7. Flash TWRP to slot opposite of what we found out in Step 5.
Command Prompt
Code:
fastboot flash boot_slot twrp-mata.img
Mac/Linux/Powershell
Code:
./fastboot flash boot_slot twrp-mata.img
So, if your current slot was a, you will use boot_b above. If current slot was b, you will use boot_a above.
8. Set slot where we flashed TWRP as active.
Command Prompt
Code:
fastboot --set-active=slot
Mac/Linux/Powershell
Code:
./fastboot --set-active=slot
So, if your current slot was a, you will use --set-active=b above. If current slot was b, you will use --set-active=a above.
9. Use volume rockers till you see recovery option. Then press power button to select. You should now boot into TWRP.
If the touchscreen doesn't function, skip to instructions in post 2 below.
Now, flash TWRP installer zip file.
Once zip is flashed and has patched both slots. Go back to home screen.
Reboot.
On this screen select the slot which we had noted down in step 5.
Then reboot into system. You should now boot into Android.
10. To root. Boot back into bootloader mode. Go into TWRP recovery. Flash magisk zip. reboot.
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Video Guide
Downloads :
Latest ADB & Fastboot Zip File :- https://developer.android.com/studio/releases/platform-tools
TWRP for Essential Phone (need both .img and zip file) :- https://forum.xda-developers.com/es...official-twrp-3-2-3-0-essential-ph-1-t3840931
Magisk :- https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Going Back to Stock :- https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
If you flashed September Android 9.0 Pie Back to Stock (BTS) it flashes to both slots. In that case, if touch is not working please refer post 2.
Credits
@Dees_Troy for TWRP
@aer0zer0 for back to stock (BTS)
@topjohnwu for Magisk
@munchy_cool for this guide
reserved
Common Issues
Thanks to @starcms for helping with the instructions.
No touch in TWRP in Step 9.
Keep your phone connected to computer. Open command prompt/terminal/powershell.
Now we are going to install TWRP installer zip.
Command Pormpt
Code:
adb shell twrp install path/to/zip
So, let's say you have twrp installer zip (named
twrp-installer-mata-3.2.3-0.zip) in root of internal memory.
Code:
adb shell twrp install /sdcard/
twrp-installer-mata-3.2.3-0.zip
This should flash TWRP to both slots. Now, you can reboot using
Code:
adb reboot bootloader
and go back into TWRP. Check if touch is working and then set your slot to one noted in step 5.
If touch is not working use fastboot (step 8) to change the slot to that noted in Step 5..
Now boot back into TWRP using volume rockers and proceed to Step 10 (flashing Magisk zip)
Terminal/Powershell users please add ./ before the adb.
reserved 002
reserved 002
Nice write-up. I would also maybe add (to your discretion ofc) that if you flash the latest P BTS, it flashes to both slots, making touch unusable in twrp and will need to follow your addendum.
aer0zer0 said:
Nice write-up. I would also maybe add (to your discretion ofc) that if you flash the latest P BTS, it flashes to both slots, making touch unusable in twrp and will need to follow your addendum.
Click to expand...
Click to collapse
Done. Thanks for the advice :highfive:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"
Is my stockboot file is incorrect?
YunolexDDP said:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"
Is my stockboot file is incorrect?
Click to expand...
Click to collapse
recovery is part of boot image. if you flash stock boot, twrp is removed.
munchy_cool said:
recovery is part of boot image. if you flash stock boot, twrp is removed.
Click to expand...
Click to collapse
Yeah i know but now i wonder where goes wrong with my phone
Seem my English is not very good so....I dont know how to search the key word
So..I wonder if you have seem this situation before.
YunolexDDP said:
Yeah i know but now i wonder where goes wrong with my phone
Seem my English is not very good so....I dont know how to search the key word
So..I wonder if you have seem this situation before.
Click to expand...
Click to collapse
after installing twrp zip, if you instal stock boot or new kernel it will remove twrp.
you have to flash twrp zip after installing new kernel.
to root, boot into android once after instalinh twrp zip.
then boot back into twrp, and flash magisk zip.
munchy_cool said:
after installing twrp zip, if you instal stock boot or new kernel it will remove twrp.
you have to flash twrp zip after installing new kernel.
to root, boot into android once after instalinh twrp zip.
then boot back into twrp, and flash magisk zip.
Click to expand...
Click to collapse
I am pretty close it. Now i have my twrp install in one slot and the system can boot from another slot but uh..
do I need to flash stock boot before I flash magisk?
cus now I still cant boot the system from twrp..
the official website said "use the devices as normal" hmm..
I need to change the slot if i want to boot the system. Is that normal?
YunolexDDP said:
I am pretty close it. Now i have my twrp install in one slot and the system can boot from another slot but uh..
do I need to flash stock boot before I flash magisk?
cus now I still cant boot the system from twrp..
the official website said "use the devices as normal" hmm..
I need to change the slot if i want to boot the system. Is that normal?
Click to expand...
Click to collapse
NO you don't need to flash stock boot to instal Magisk.
yes, you need to change slot to boot system.
all of this is mentioned in first post.
i have a question, is there a way to just boot into TWRP to just flash magisk? without flashing TWRP itself? i want to recive OTAs still and all i want is just magisk installed, i tried the ,ethod of patching the boot.img but that was a huge fail please help!!!
DeimosPhobos said:
i have a question, is there a way to just boot into TWRP to just flash magisk? without flashing TWRP itself? i want to recive OTAs still and all i want is just magisk installed, i tried the ,ethod of patching the boot.img but that was a huge fail please help!!!
Click to expand...
Click to collapse
No.
We don't have fastboot boot
aer0zer0 said:
No.
We don't have fastboot boot
Click to expand...
Click to collapse
Ahhhh ok,
I figured out the patched boot image method, although when I tried to make my own patched boot IMG, it didn't work, I found a Reddit thread where someone had done it, I used theirs and it worked....although the command was supposed to be fastboot flash boot patched_boot.img and Everytime I did that it sent it to B, but failed on the write, they yelled at me saying that's the command and it should work lol, but I had to actually put fastboot flash boot_b patched_boot.img....the damn A/B partition stuff confuses me Alot lol
DeimosPhobos said:
Ahhhh ok,
I figured out the patched boot image method, although when I tried to make my own patched boot IMG, it didn't work, I found a Reddit thread where someone had done it, I used theirs and it worked....although the command was supposed to be fastboot flash boot patched_boot.img and Everytime I did that it sent it to B, but failed on the write, they yelled at me saying that's the command and it should work lol, but I had to actually put fastboot flash boot_b patched_boot.img....the damn A/B partition stuff confuses me Alot lol
Click to expand...
Click to collapse
sometimes older fastboot versions dont work well with Essential.
for ab slots, if you are want to flash magisk pre-rooted boot.img
just do
fastboot gervar current-slot (say you get a)
and then flash boot.img to current slot.
fastboot flash boot_a nameofboot.img
munchy_cool said:
sometimes older fastboot versions dont work well with Essential.
for ab slots, if you are want to flash magisk pre-rooted boot.img
just do
fastboot gervar current-slot (say you get a)
and then flash boot.img to current slot.
fastboot flash boot_a nameofboot.img
Click to expand...
Click to collapse
essential's driver package for windows doesnt require _a,_b unless you are being specific
fastboot flash boot whatever will work and flash to the current slot if your using essentials (which is an older version) if your using a newer version from google or minimal, it gives the __a or b error trying to append an extra underscore
aer0zer0 said:
essential's driver package for windows doesnt require _a,_b unless you are being specific
fastboot flash boot whatever will work and flash to the current slot if your using essentials (which is an older version) if your using a newer version from google or minimal, it gives the __a or b error trying to append an extra underscore
Click to expand...
Click to collapse
true, but not everyone is on Windows :highfive:
munchy_cool said:
true, but not everyone is on Windows :highfive:
Click to expand...
Click to collapse
Poor Linux folks ?
aer0zer0 said:
Poor Linux folks
Click to expand...
Click to collapse
lol.
Essential is the only phone to give me issues with fastboot though.
munchy_cool said:
lol.
Essential is the only phone to give me issues with fastboot though.
Click to expand...
Click to collapse
Tell me about it, lol.
---------- Post added at 12:00 PM ---------- Previous post was at 11:46 AM ----------
aer0zer0 said:
Tell me about it, lol.
Click to expand...
Click to collapse
Never seen a phone so finicky. I've also got the holy Grail cable that I don't let out of my sight. I've often wondered what makes it so finicky, and I come from a long line of HTC and motos
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
Hi sorry to hear that you got this problem and hopefully it gets fixed. I have another question: does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? Does that mean after installing, everything will be refreshed like a box opened phone?
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
h0l said:
Run this command in fastboot so you know which is the CURRENT active slot :
Run this command so you can flash the correct slot : replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
djsubterrain said:
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
Click to expand...
Click to collapse
Which is the default active slot? Is it okay to use either of the 2?
dmj0shu4 said:
Which is the default active slot? Is it okay to use either of the 2?
Click to expand...
Click to collapse
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
djsubterrain said:
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
Click to expand...
Click to collapse
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
dmjoshu4 said:
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
Click to expand...
Click to collapse
You are supposed to flash it in the one that IS the active one. Because you do want to root the slot that you'll be booting.
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
gh279760559 said:
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
Click to expand...
Click to collapse
not everything, just twrp and root will be gone if you restarted without installing magisk to the inactive slot
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
dude, thanks for this, i was banging my head against a wall trying to get root to work. I used your patched boot img and i had the version mismatch, but i local updated my android and it has root!
dmj0shu4 said:
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
Click to expand...
Click to collapse
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Hi guys.. can you post the steps in rooting android 10??
I've already had bootloader unlocked.
Do i need to.follow the steps intended for android 9??
Like
1. Install TWRP via fastboot.. (2files)
2. Reboot to twrp.
3. Flash magisk via twrp??
Is that it?? If so. Then after reading this thread.. some of. You mentioned about boot. Img?? Patched?? What's that supposed to mean?? Sir??
Thanks. Any advice is highly appreciated..
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
And by the way..
Im on Gm1910 model. Global rom. Gm21AA build.. if that info would matter.. i dont actually need the root on android 9. Coz parallel app is working.. but now in android 10. It isnt working.. so.i need to root to grant su to game guardian.. thanks..
MigbyPie said:
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Click to expand...
Click to collapse
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
E30Nova said:
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
Click to expand...
Click to collapse
Hopefully there will be a solution. I had tried to update from Pie to Q10 while staying rooted and it didn't work. So I had to wipe the whole device and decided to wait for a smoother root method for my device. If you have any other ideas about rooting Q10 let me know. Thank you
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
You saved my life! Thank you!
But how do we get twrp now? Is there any way?
Me too. Use tool all in one but it doesnt work. Stuck at "waiting twrp boots".
Any help, thanks.
Same here any Solution?
Sent from my GM1911 using Tapatalk
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Stuck at Fastboot booting when flashed img and also zip
Sent from my GM1911 using Tapatalk
I updated my phone to 10 last night, followed the same guide as I have for every other update but this time I lost root for some reason.
I still have TWRP recovery on there but it can't read internal storage so I can't flash Magisk.
I tried changing file system to ext 2 then back to 4 and then repairing it as I read elsewhere and this wiped the phone obviously but internal storage seemed to be working until I set the phone up again, downloaded Magisk, rebooted to recovery and I'm back where I started, internal storage showing as 0mb in TWRP.
Any ideas how to fix?
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide
Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.
no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system
I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching
Functionally on OOS 10.0.1 OP6 ?
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.
Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?
WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works
After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
As above. No wifi, no sound. What's going on?
Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...
ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!
loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes