Hey yall, attached is the magisk rooted boot.img for dp3. I am still having a lot of stability issues with the dp3 but they do not seem to be related to root because the problems were present before rooting. I figured I would just throw this up for those who are adventurous. I PROVIDE NO SUPPORT. I do not provide a how-to either to stop from people complaining about stability issues. This is provided as-is for those that know what to do with it.
cheers.
https://www.androidfilehost.com/?fid=6006931924117919427
Mine. ALso seem that my stability problems are related to at&t sim
So far there are 2 issues that I've run into, first, auto brightness seems to be all over the place, also work profile is not working either, when I press on the work profile app, nothing happens.
None of this is a deal breaker for me, but a bug is a bug.
eqbirvin said:
Hey yall, attached is the magisk rooted boot.img for dp3. I am still having a lot of stability issues with the dp3 but they do not seem to be related to root because the problems were present before rooting. I figured I would just throw this up for those who are adventurous. I PROVIDE NO SUPPORT. I do not provide a how-to either to stop from people complaining about stability issues. This is provided as-is for those that know what to do with it.
cheers.
https://www.androidfilehost.com/?fid=6006931924117919427
Click to expand...
Click to collapse
What specific issues?
ram4ufriends said:
What specific issues?
Click to expand...
Click to collapse
Again my problems are related to At&t sim. Once it is in the device, SystemUI FCs and locks up the device.
eqbirvin said:
Hey yall, attached is the magisk rooted boot.img for dp3. I am still having a lot of stability issues with the dp3 but they do not seem to be related to root because the problems were present before rooting. I figured I would just throw this up for those who are adventurous. I PROVIDE NO SUPPORT. I do not provide a how-to either to stop from people complaining about stability issues. This is provided as-is for those that know what to do with it.
cheers.
https://www.androidfilehost.com/?fid=6006931924117919427
Click to expand...
Click to collapse
Just use below?? On both slots?
fastboot flash boot patched.img
ram4ufriends said:
Just use below?? On both slots?
fastboot flash boot patched.img
Click to expand...
Click to collapse
Flash on both slots.
eqbirvin said:
Flash on both slots.
Click to expand...
Click to collapse
In fastboot how to flash in both slots
freakzapster said:
In fastboot how to flash in both slots
Click to expand...
Click to collapse
I'm sorry but I'm not providing a how-at at this moment. There are how-to's/explanations of the different fastboot & adb commands all over XDA by much more informed people than myself and I do not want to risk someone else's device because I do not provide a correct how-to. Nothing against anyone, I just cannot use the dp3 right now because at&t nor Verizon sims currently work with this Developer Preview. Because of this, I wouldn't be able to give a fleshed-out or comprehensive guide and I don't want anyone to soft brick their device. Once DP3 is fixed for at&t, I will write a full how-to.
freakzapster said:
In fastboot how to flash in both slots
Click to expand...
Click to collapse
You can just flash on active slot alone...
freakzapster said:
In fastboot how to flash in both slots
Click to expand...
Click to collapse
Why would you want to flash it to both slots. For one, there will be bugs in DP3. You may need to switch to a working ROM to get back to original. If you are asking how to flash in both slots, probably shouldn't be messing with an unofficial build. You see all the time people with bricked phones and 95% it was due flashing mistakes by the user. I'm not putting you down, the same goes with people flashing the same ROM, then immediately flashing it again to the other slot without rebooting between flashes. What if it doesn't boot and now you can't switch to the other slot because it is bad as well.
magisk and Twrp are working for DP3 apart from your boot image??
innocentwoolf said:
magisk and Twrp are working for DP3 apart from your boot image??
Click to expand...
Click to collapse
Yes.. but you can't mount data in twrp.. so you can't flash zips from internal storage in twrp...
ram4ufriends said:
Yes.. but you can't mount data in twrp.. so you can't flash zips from internal storage in twrp...
Click to expand...
Click to collapse
u mean data or storage??
so can we use otg for that? and can we simply flash magisk from it?
I pulled a logcat and found the fatal error with the SIM problems. It is related to the status bar I believe. Attached is the entire logcat and just the fatal error. Maybe someone more experience than me can take a look and see if they can get more information from it!
Code:
[07-19 19:42:03.079 2311:2550 E/AndroidRuntime]
FATAL EXCEPTION: SysUiBg
Process: com.android.systemui, PID: 2311
java.lang.ArrayIndexOutOfBoundsException: length=5; index=5
at com.android.systemui.statusbar.policy.MobileSignalController.getCurrentIconId(MobileSignalController.java:659)
at com.android.systemui.statusbar.policy.MobileSignalController.notifyListeners(MobileSignalController.java:788)
at com.android.systemui.statusbar.policy.SignalController.notifyListeners(SignalController.java:204)
at com.android.systemui.statusbar.policy.SignalController.notifyListenersIfNecessary(SignalController.java:162)
at com.android.systemui.statusbar.policy.MobileSignalController.updateTelephony(MobileSignalController.java:1166)
at com.android.systemui.statusbar.policy.MobileSignalController.access$100(MobileSignalController.java:76)
at com.android.systemui.statusbar.policy.MobileSignalController$MobilePhoneStateListener.updateDataNetType(MobileSignalController.java:1452)
at com.android.systemui.statusbar.policy.MobileSignalController$MobilePhoneStateListener.onServiceStateChanged(MobileSignalController.java:1408)
at android.telephony.PhoneStateListener$IPhoneStateListenerStub.lambda$onServiceStateChanged$0(PhoneStateListener.java:1015)
at android.telephony.-$$Lambda$PhoneStateListener$IPhoneStateListenerStub$nrGqSRBJrc3_EwotCDNwfKeizIo.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)
View attachment fatal_error.txt
View attachment logcat_07-19-2019_19-44-56.zip
freakzapster said:
In fastboot how to flash in both slots
Click to expand...
Click to collapse
I rename the boot img to "patched_boot.img and then these cmds.
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Related
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
steam374 said:
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
Click to expand...
Click to collapse
What is required for root work?
Root adds a binary file and some scripts to the /system partition
What happens when you flash a system.img?
Everything in the /system partition is wiped and replaced with the contents of the system.img
So, basically as long as I flash super su in twrp I'll be good to go?
steam374 said:
So, basically as long as I flash super su in twrp I'll be good to go?
Click to expand...
Click to collapse
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
danarama said:
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
Click to expand...
Click to collapse
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
steam374 said:
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
Click to expand...
Click to collapse
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
danarama said:
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
Click to expand...
Click to collapse
Okay! Thank you very much! This is the help I needed.
steam374 said:
Okay! Thank you very much! This is the help I needed.
Click to expand...
Click to collapse
No probs
danarama said:
No probs
Click to expand...
Click to collapse
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
steam374 said:
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
Click to expand...
Click to collapse
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
danarama said:
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
Click to expand...
Click to collapse
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
steam374 said:
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
Click to expand...
Click to collapse
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
danarama said:
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
Click to expand...
Click to collapse
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
steam374 said:
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
Click to expand...
Click to collapse
Hey, don't worry. We prefer "noob" questions to "noob-help-me-i-screwed-up" requests
Most custom ROMs for the OnePlus 5 are now supporting encrypted devices only. However, some users choose to keep their device in a decrypted state for MultiROM support and for other reasons. If you follow the steps below, you can flash any encrypted ROM on your decrypted device (without losing data) and your device will remain decrypted! I found this information in one of the many threads I've read (I don't remember which one) and thought I'd post it here to help others and for easy reference. Enjoy!
Follow These Steps:
1. Boot into TWRP
2. Wipe caches, data, and system partitions
3. Flash encrypted ROM
4. Flash GApps
5. Flash Magisk
6. Flash no-verity-op5.zip (not created by me)
7. Reboot
8. Enjoy!
If you closely follow the instructions above, you can enjoy any ROM on your decrypted OnePlus 5 and have the best of both worlds! :highfive:
Note 1: If device gets stuck at OnePlus boot animation after following all of the steps above, hold the power button for 10 seconds to turn off device. Power the device back on and it will boot successfully into the ROM.
Note 2: Some ROMs are not compatible with MultiROM without the inclusion of additional commits by ROM developer.
After wipes, its Flash ROM.. Flash optional Kernel.. Flash Gapps.. Flash No-verity.. Flash optional root (magisk or SuperSU).. Flash optional Viper4Arise?
Is this confirmed working? Has anyone actually tried the process and confirmed that any data on the phone's internal storage is there?
Ph0enix_216 said:
Is this confirmed working? Has anyone actually tried the process and confirmed that any data on the phone's internal storage is there?
Click to expand...
Click to collapse
Tested it yesterday with aosip and all data are on internal storage. Flashed validus today without no-verity-op5.zip and it worked too. Didn't lose data on internal storage...
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
Ph0enix_216 said:
Is this confirmed working? Has anyone actually tried the process and confirmed that any data on the phone's internal storage is there?
Click to expand...
Click to collapse
Yes, I have followed these steps to flash MANY encrypted ROMs on my decrypted device.
Confirmed to work successfully! :good:
Creeper36 said:
After wipes, its Flash ROM.. Flash optional Kernel.. Flash Gapps.. Flash No-verity.. Flash optional root (magisk or SuperSU).. Flash optional Viper4Arise?
Click to expand...
Click to collapse
I've found that flashing SuperSU (instead of Magisk) on encrypted ROMs often ends in a bootloop on my decrypted device. Flashing Magisk seems to be a requirement.
Not working for me. Tried with AICP release from 9/11. Wiped caches, system, data. Flashed rom. flashed gapps (tried stock/full/micro). Flashed magisk (also tried without). -> Bootloop
//edit
sorry i think i misunderstood the post. i thought i can flash decrypted roms on encrypted device xD is that possible too?
nico2195x said:
sorry i think i misunderstood the post. i thought i can flash decrypted roms on encrypted device xD is that possible too?
Click to expand...
Click to collapse
No, I believe your device must be decrypted to flash decrypted ROMs.
Thanks for this! Do you know who we should thank for the zip? If there's an original thread for it?
DunamisMaximus said:
Thanks for this! Do you know who we should thank for the zip? If there's an original thread for it?
Click to expand...
Click to collapse
You are very welcome! Unfortunately, I do not know who originally created the verity zip. It has been passed around on XDA by many people.
DunamisMaximus said:
Thanks for this! Do you know who we should thank for the zip? If there's an original thread for it?
Click to expand...
Click to collapse
sjamie said:
You are very welcome! Unfortunately, I do not know who originally created the verity zip. It has been passed around on XDA by many people.
Click to expand...
Click to collapse
The original zip was modified for making FBE optional by @snowwolf725. Click here to visit his original thread.
I have a quick question. I just unlocked the Bootloader on my Plus 5 and installed TWRP 3.1.1-1 and Magisk 14.0 on it. The firmware is 4.5.0 as I didn't let it update at all and did all this to the device upon first bootup. I did not decrypt.
I've tried installing latest RR release (final for N cheeseburger) and the install stops with errors. I tried a different rom in the same Android version (7.1.2) and get same results. MD5 checks out on both downloads.
Do I have to flash the latest OnePlus 5 update (full OTA 4.5.10) before flashing a 7.1.2 rom? And should I decrypt my device for easier flashing?
If no one answers, I completely understand and will search some more but this seems to be a cloudy subject that gets many different answers and I thought I would post it here. Thank you all in advance.
Sent from my Nexus 6 using XDA Premium HD app
shadowstep said:
The original zip was modified for making FBE optional by @snowwolf725. Click here to visit his original thread.
Click to expand...
Click to collapse
And there's a thread I started for using FDE.
It works with most ROMs...
https://forum.xda-developers.com/oneplus-5/development/op5-disk-encryption-enabler-op5-t3672477
glockman4519 said:
I have a quick question. I just unlocked the Bootloader on my Plus 5 and installed TWRP 3.1.1-1 and Magisk 14.0 on it. The firmware is 4.5.0 as I didn't let it update at all and did all this to the device upon first bootup. I did not decrypt.
I've tried installing latest RR release (final for N cheeseburger) and the install stops with errors. I tried a different rom in the same Android version (7.1.2) and get same results. MD5 checks out on both downloads.
Do I have to flash the latest OnePlus 5 update (full OTA 4.5.10) before flashing a 7.1.2 rom? And should I decrypt my device for easier flashing?
If no one answers, I completely understand and will search some more but this seems to be a cloudy subject that gets many different answers and I thought I would post it here. Thank you all in advance.
Click to expand...
Click to collapse
Yes.. U need to flash the latest firmware and then flash roms.. There's a thread for firmware.. Flash the whole zip would again give you stock recovery and you have to re do the fastboot stuff so makes no sense..
arjunarora said:
Yes.. U need to flash the latest firmware and then flash roms.. There's a thread for firmware.. Flash the whole zip would again give you stock recovery and you have to re do the fastboot stuff so makes no sense..
Click to expand...
Click to collapse
In addition to what is stated here, if you flash Magisk immediately after flashing the full firmware zip (no rebooting between steps), TWRP won't get replaced with the stock recovery. This is a great time saver!
Any method to get oxygen os as a secondary ROM with multirom?
dakotah2468 said:
Any method to get oxygen os as a secondary ROM with multirom?
Click to expand...
Click to collapse
Yes, I've read that is possible. No, I don't know how to do it. :laugh:
sjamie said:
Yes, I've read that is possible. No, I don't know how to do it. :laugh:
Click to expand...
Click to collapse
Darn, well thanks for the reply
I just wanted to thank you for this thread. All of the information you provided helped me immensely. I was struggling with this device and flashing roms at first but one I unencrypted it, with your guide, everything worked great. I was going to leave it encrypted for easier flashing since most all the roms for this device are encrypted only. But I was having more issues than ever. And many, of the posts in here have also answered quite a few questions I had. This should be a pinned tread.
Anyways thank you again. Your thread is a must read for anyone with an Opo5.
"Chance Favors the Prepared"
dakotah2468 said:
Any method to get oxygen os as a secondary ROM with multirom?
Click to expand...
Click to collapse
Have you tried flashing OxygenOS, the no-verity zip and Magisk?
glockman4519 said:
I just wanted to thank you for this thread. All of the information you provided helped me immensely. I was struggling with this device and flashing roms at first but one I unencrypted it, with your guide, everything worked great. I was going to leave it encrypted for easier flashing since most all the roms for this device are encrypted only. But I was having more issues than ever. And many, of the posts in here have also answered quite a few questions I had. This should be a pinned tread.
Anyways thank you again. Your thread is a must read for anyone with an Opo5.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
Thanks for the feedback and I'm glad this thread could provide you the guidance you needed.
How is Huawei handling root? Is it suspected to work or will this be a problem?
I guess the rooting process may be a bit similar to the Mate 20s. It took a while before root became available for Mate and the process relies on a somewhat compilicated procedure involving FunkeyHuawei and buying credits. If you really want to have root then probably better to wait or to buy a phone which is easier to root.
Hi,
Somewhat agree. Root might take time.
What I can confirm is that oem unlock is not greyed out.
P30 Pro dev options https://imgur.com/a/unJy0ZX
So do you think that someone will cook TWRP and magisk?
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Hope that someone will find a solution, maybe on chinese forums. I can't buy a non-rootable phone.
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
kilroystyx said:
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
Click to expand...
Click to collapse
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
JazonX said:
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
Click to expand...
Click to collapse
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
My p30 pro arrive today and i thought i can root it with this tutorial
https://myphoneupdate.com/root-huawei-p30-pro-unlock-bootloader-install-twrp-recovery/
And now i read here that its not possible? That is very Bad if this is so :/
Sorry for Bad English
Edit: oh... Yes now i See no Service sells this Codes at the Moment..
kilroystyx said:
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
:crying::crying::crying:
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
Unfortunately this means that Magisk is not ready to patch EMUI9.1
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
JazonX said:
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
Click to expand...
Click to collapse
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
kilroystyx said:
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
Click to expand...
Click to collapse
I have uploaded it here.
JazonX said:
I have uploaded it here.
Click to expand...
Click to collapse
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
kilroystyx said:
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
Click to expand...
Click to collapse
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Puksom said:
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Click to expand...
Click to collapse
Yes, to flash you need bootloader unlocked.
Don't waste your money yet, let's first JazonX test the recovery_ramdisk.img patched by me.
JazonX, have you tried? I hope it works
What about Treble support on this device? Is TWRP (or another custom recovery) avialiable? What wouldn't work in GSI?
This device is both treble and seamless update compatible/supported.
So how to run GSI firmwares on this device?
How to create /vendor, flash it and etc?
aaa.bbb111222 said:
So how to run GSI firmwares on this device?
How to create /vendor, flash it and etc?
Click to expand...
Click to collapse
Try out the official instructions from the XDA Treble thread, and report back. If it works, I'm sure we can get together a few people here and try to tweak the development further.
I had pixel experience running on it. Worked pretty well, except no aod, and vibrator didn't work.
suzook said:
I had pixel experience running on it. Worked pretty well, except no aod, and vibrator didn't work.
Click to expand...
Click to collapse
Could you give the steps on how you did it? is it just fastboot flash img? do we have to disable verity or something
suzook said:
I had pixel experience running on it. Worked pretty well, except no aod, and vibrator didn't work.
Click to expand...
Click to collapse
hi, may i know did you try phh aosp recent build? i try before and it bootloop.
atoyu said:
hi, may i know did you try phh aosp recent build? i try before and it bootloop.
Click to expand...
Click to collapse
1) You need a vbmeta.img from fastboot ROM.
2) Flash the vbmeta.img using the command, fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, this is done to disable dm-verity to let the GSI boot.
3) Download the latest A/B GSI
4) Extract and flash the GSI using the command, fastboot flash system filename.img, replace filename with the name of the image.
suzook said:
1) You need a vbmeta.img from fastboot ROM.
2) Flash the vbmeta.img using the command, fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, this is done to disable dm-verity to let the GSI boot.
3) Download the latest A/B GSI
4) Extract and flash the GSI using the command, fastboot flash system filename.img, replace filename with the name of the image.
Click to expand...
Click to collapse
Wow nice!
We should try to make a step by step thread in the ROMS forums to get more people to try out custom roms.
stealthj said:
Wow nice!
We should try to make a step by step thread in the ROMS forums to get more people to try out custom roms.
Click to expand...
Click to collapse
Just copy and paste my instructions.
I wish we had multi rom
---------- Post added at 06:57 PM ---------- Previous post was at 06:40 PM ----------
suzook said:
Just copy and paste my instructions.
Click to expand...
Click to collapse
Sounds good! I'll give credit where its due. Let me go ahead and try it out later on this week first.
So how was the rom running? Was it at full 120hz? Battery was ok?
stealthj said:
I wish we had multi rom
---------- Post added at 06:57 PM ---------- Previous post was at 06:40 PM ----------
Sounds good! I'll give credit where its due. Let me go ahead and try it out later on this week first.
So how was the rom running? Was it at full 120hz? Battery was ok?
Click to expand...
Click to collapse
Did it / does it work well? Any help going from full stock WW model to gsi?
I assume the unlock tool on https://www.asus.com/tw/Phone/ROG-Phone-II/HelpDesk_Download/ is universal WW/CN?
Please advise in eli5 detail.
@suzook
Thanks in advance
All sorted I will post a tutorial now
MANICX100 said:
All sorted I will post a tutorial now
Click to expand...
Click to collapse
Looking forward to this.
On a second note.
1. Does the official unlocking tool need internet to work i.e will forward IMEI and other identifiers to Asus.
2. Is there a way we can figure out how to unlock the bootloader without using the Asus official tool?
gorgorven said:
Looking forward to this.
On a second note.
1. Does the official unlocking tool need internet to work i.e will forward IMEI and other identifiers to Asus.
2. Is there a way we can figure out how to unlock the bootloader without using the Asus official tool?
Click to expand...
Click to collapse
1.) Yes, Internet is needed and yes it transmits the IMEI
2.) Not at this time
3.) My tutorial is live here: https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133
MANICX100 said:
1.) Yes, Internet is needed and yes it transmits the IMEI
2.) Not at this time
3.) My tutorial is live here: https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133
Click to expand...
Click to collapse
I checked out the link. Thanks for the guide and this reply.
If anyone knows of a forum thread trying to unlock without the official tool (haven't found a thread dedicated to this as of yet) or any resource threads which can help me learn and try it myself, please do point me in that direction.
Thanks again.
gorgorven said:
unlock without the official tool
Click to expand...
Click to collapse
I think that it's possible to reverse engineer way tool works using Something like apktool (if code is Java) or disassembler (if it's C/C++/etc).
Also, what about change IMEI to your old phone's one before using the tool and changing it back after that? (Any ID codes that device maybe are needed to be changed too)
aaa.bbb111222 said:
I think that it's possible to reverse engineer way tool works using Something like apktool (if code is Java) or disassembler (if it's C/C++/etc).
Also, what about change IMEI to your old phone's one before using the tool and changing it back after that? (Any ID codes that device maybe are needed to be changed too)
Click to expand...
Click to collapse
Even I believe that we should be able to do something, however my experience in this is modest at best. I am a nweeb.
Though the way I believe the official tool would work is.... And please correct me if am wrong...
1. It should send the IMEI no to the server.
2. The server sends a code to unlock the bootloader.
3. The tool unlocks the boot loader.
Now steps one and three can be reverse engineered. But unless step two is something like a MD5 hash of the IMEI etc, we might need to figure a way to do the unlocking in a new way.
I don't know if we even can change the IMEI without access to the root folder. I never had a phone since my Galaxy S2 which wasn't unlocked and rooted. I will do some research.
If anyone has any idea.... Kindly let us know.
Just curious - anyone here who tried GSI's stayed with them? I wonder how many bugs are there out of the box. There are some annoying bugs with recent WW ASUS software (like some SMS not being saved, but delivered to my wristband, touchscreen getting freezed with fingerprint unlock on after some phone locks) that really makes me wanna change that soft.
I do not care about gaming functions missing (like 60+Hz refresh rate, back LEDs).
Maczuga said:
Just curious - anyone here who tried GSI's stayed with them? I wonder how many bugs are there out of the box. There are some annoying bugs with recent WW ASUS software (like some SMS not being saved, but delivered to my wristband, touchscreen getting freezed with fingerprint unlock on after some phone locks) that really makes me wanna change that soft.
I do not care about gaming functions missing (like 60+Hz refresh rate, back LEDs).
Click to expand...
Click to collapse
I have stayed with phhussons GSI. As you say no 90/120Hz or back LED. Only other quirk is that apps think the fingerprint scanner is on the back , not in the screen. The fingerprint scanner still works, but makes it awkward to press 0 on your pin pad.
FYI: If you use the gapps build you can flash over an earlier months without losing any data!