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!
Related
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
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Same problem here. Already tried to boot every version of TWRP without success.
abrahammurciano said:
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
But there's no button to flash, I open the app, select flash recovery, select device, but theres no button to flash it.
See screenshot
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Denkai said:
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Click to expand...
Click to collapse
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
super odd. maybe your boot image is corrupt? still doesn't explain why fastboot boot isn't working though... Try bluSpark's TWRP image. it's a solid build and I am not having issues with it.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page17
or you can also try swapping to the other partition by typing 'fastboot --set-active=_a' (or fastboot --set-active=_b) and booting to that recovery.
if that doesn't work for ya, try and restore stock via fastboot is my only suggestion:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
[/COLOR]
abrahammurciano said:
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
Click to expand...
Click to collapse
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Does it work for Android 10?
oneplus 6 running oxygen os beta 30 with magisk 20.1 without twrp
Borat38 said:
[/COLOR]
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Click to expand...
Click to collapse
Please I need TWRP for Blackview BV9600 pro please share with me if you have a link to a webpage I may find it
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
Hello I'm having magisk root access and official TWRP app but can't use it for NAndroid backup, how can I use the app for backup and fishing custom ROM?
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
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
What should I make of
Code:
$fastboot erase recovery
erasing 'recovery'...
FAILED (remote: Check device console.)
iconoclasthero said:
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
Click to expand...
Click to collapse
What rom was installed last before all this began.
MrSteelX said:
What rom was installed last before all this began.
Click to expand...
Click to collapse
Havoc OS (Havoc-OS-v3.1-20200120-enchilada-Official.zip). The problem was that somehow my pin got corrupted/changed after my first couple of boots into Havoc. That precipitated a big mess.
That said, I switched to my desktop (also running Ubuntu 18.04) and got a new version of the SDK directly from android.com, and replaced the files that came from the repo. That was able to do the formatting and install the stock image so now I just need to go through the procedure again...
I wish I'd had a better sense of what was going on with the partition table/fstab/blkid because I was able to get in with adb shell and I theoretically could have manually formatted...
iconoclasthero said:
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
Click to expand...
Click to collapse
It looks like you had android 10 and you flashed official twrp, which is android 9 only, which happened to me before. I could recommend using this to flash OOS through fastboot.
[email protected] said:
It looks like you had android 10 and you flashed official twrp, which is android 9 only, which happened to me before. I could recommend using this to flash OOS through fastboot.
Click to expand...
Click to collapse
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
iconoclasthero said:
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 ?
iconoclasthero said:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 ?
Click to expand...
Click to collapse
iconoclasthero said:
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
Click to expand...
Click to collapse
I was looking around but I could not find what is going on with Havoc OS. I would probably recommended choosing a better maintained ROM with up to date instructions and support. Maybe Pixen or something. I was only able to find this old thread. Maybe you have better luck.
But if you really want Havoc, figure out first if it is androdi 9 or 10. If it is 10, use malfuriono unofficial twrp. If it is 9, you have to downgrade to OOS 9.0.9 first. Also, dirty flashes tend to cause problems, I would not recommended doing that. Make sure you wipe appropriate partitions
Welcome to my latest Thread. Today for the Official Pixel Expierence Builds from the Official Website. This Guide does include the Installation of a custom Recovery which allows Factory Resets and flashing Updates/ROMs. Enjoy!
1. Download and prepare everything
First of all visit: https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
And download the latest Software Binaries from Sony which You will need to flash together with the Boot Image (Kernel).
After that download the ROM File from here: https://download.pixelexperience.org/ and also download the "Recovery Image" which is a Kernel/Boot Image
Get the Magisk Manager Apk from here: https://github.com/topjohnwu/Magisk
Extract the Software Binaries to get the .img File from it.
2. Flash using Fastboot
After getting the Kernel/Boot Image do a patch with the Magisk Manager App (Your Phone doesn't needs to be rooted for that) (The Output File will get called magisk_patched,img from now)
Flash the Software Binaries from SONY with:
Code:
fastboot flash oem_a SW_binaries_for_Xperia_Android...............img
Repeat that step with:
Code:
fastboot flash oem_b SW_binaries_for_Xperia_Android...............img
Now flash the Kernel You got from the Magisk Manager with:
Code:
fastboot flash boot_a magisk_patched.img
And repeat that again for the Second Slot:
Code:
fastboot flash boot_b magisk_patched.img
3. Install using a SD Card or ADB
After flashing the Kernel. Turn Off Your Device and hold the Volume- (Lower) Button together with the Power Button until You see the SONY Logo. Release both Buttons and wait for the Recovery coming up.
Search now for the Apply Update Option and select based on Your preference the ADB or SD Card Method to flash the ROM. Connect Your Xperia to Your PC again and enter:
Code:
adb sideload filename.zip
(In case of using the ADB Method)
Your Device should now flash the selected ZIP File (In our case the Pixel Expierence ROM).
4. Profit
Wipe Your Device now using the Factory Reset of the Recovery. Install the Magisk Patched Kernel Image again using the commands of the second Step of this Guide to keep Magisk functional. Connect Your Phone to a Charger and install the latest Magisk Manager to Your Phone. That's it! Enjoy
What Works:
VoLTE
Wifi Calls
Video Calls over Carrier
Camera Button (Does not start Camera Apps)
Everything!?
Bugs:
None!?
Urnyx latest Google Camera Mod works well with this ROM now. Enjoy GCAM 7.x
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette
Any takers? How is the fingerprint sensor?
Updated the Guide. FP sucks still hard... Can't use it at all here. Same as Stock for Me.
Still some delay on unlocking the Device but the battery drain is fixed with the latest October Builds. Runs flawless in daily use! Never had such a good running AOSP ROM on any Xperia after the Z Series started. Awesome!
Can someone please make a YouTube guide for the less tech savvy of us?
I'm suffering from getting device is corrupt message after flash both oem_a/b and boot_a/b.
What is wrong?
azumanagi said:
I'm suffering from getting device is corrupt message after flash both oem_a/b and boot_a/b.
What is wrong?
Click to expand...
Click to collapse
Try flashing with fastboot dtbo_a dtbo.img and same for dtbo_b with the attached image and let me know if it fixes Your Problem
Miustone said:
Try flashing with fastboot dtbo_a dtbo.img and same for dtbo_b with the attached image and let me know if it fixes Your Problem
Click to expand...
Click to collapse
Thanks a lot !
It works, and now I'm in system.
Btw I want to know what the problem is?
Now I'm facing two problem.
1, SIM card can be detected, but can't work.
2, When I use GCam Mod, if I switch to night mode, the image shows upside down, but the photos taken are normal.
Just flashed this but for some reason my sim is not detected and my wifi wont turn on. Would love some help. followed the steps. Everything else works fine.
EDIT: fixed it. used different install method