Related
Hello,
I own the 32gb h791 nexus 5x and the phone is bootlooping after android 7.0 update.
so basicly the phone showing google logo and then reboot back..
My bootloader is unlocked, so I tried to flash marshmellow without any success.
I can not access the recovery.
I saw a thread about flashing tot but i read in the thread that It is re lock the bootloader.
I dont have efs backup..
Any help?
Thanks,
Nimrod
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
But that's a hardware bootlop no software
How many files had been flashed when you've tried to flash it? If any, have you done any modifications like root etc ?
If no, just lock bootloader and send RMA
If you can send to Google, you don't have to lock bootloader.
If your warranty expired, try to talk to Google may they will give you a replacement anyway, if not Google, you can try to LG because of 15mo warranty from production date
TypNguy said:
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
Click to expand...
Click to collapse
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
His problem is a hardware issue not software. Might get lucky and volte it back to life but I highly doubtful . LG notorious for certain models that infinite bootloop issue g4 was the worse.
Yes, the root toolkit worked for me. I still don't know how to flash correctly, so if you have the right driver's associated with your phone/laptop it should be a breeze. The best part is that there's a log, so you know what the toolkit is doing. For example, it may unroot your phone before it flashes the new stock image for you.
---------- Post added at 02:40 AM ---------- Previous post was at 02:36 AM ----------
Just found wugfresh's answer to your question I think.
Link
Address: http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Banan PL said:
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Click to expand...
Click to collapse
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Click to expand...
Click to collapse
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
There's a temporary workaround if you're a stock rooted user:
Here's a reddit link regarding a workaround:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
However, this isn't helpful if you're a regular custom rom user as you'll notice in the details.
As for DRM, I think so. I have been looking for confirmation about DRM being impacted by this "No RPMB" status. I've only seen one other person outright mention this. It's hard to find users who get this issue and even harder to get them to respond on my inquiry on whether they can use DRM apps. What issue are you seeing with Play Movies? Can you open the app? Or are you given an error message of any kind? I'm interested from the troubleshooting perspective so that I can help ID when others have the same issue. Also, can you confirm this affects other multimedia apps with DRM protection? I was thinking that Hulu, Netflix, HBO would be apps that utilize DRM if you have subscriptions.
Sent from my Nexus 5X using Tapatalk
I don't care much about custom OS, at least for now. I can open Play Movies browse feed and library, but it ain't play any video (Couldn't fetch license (error -1)). Unfortunately I don't have subscriptions in these services, but I used local TV streaming app that uses DRM and it showed error 203 (whatever that means). I tried also watch movies from Google's app on YouTube, no luck.
Sent from my Nexus 5X using XDA Labs
Hi there, same case, no rpmb after replacing motherboard, Netflix won't start (error 500 device failure). Tried with stock but now PureNexus rom.
Sent from my Nexus 5X using Tapatalk
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
tuningsea said:
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
Click to expand...
Click to collapse
Thanks for the advise, however I want to find a way to create this Rpmb at home, for users who warranty has gone, still looking..
Sent from my Nexus 5X using Tapatalk
Netflix norpmb
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
I confirm it's working. Has anybody found a different solution for no rpmb from the one posted on reddit?
Inviato dal mio Nexus 5X utilizzando Tapatalk
kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
Netflix app will crash few times, try to hide with Magisk Btw. Re open few times, like 10 and login. Then you will be redirected to the homepage.
Envoyé de mon Nexus 5X en utilisant Tapatalk
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
androidfreak11 said:
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
Click to expand...
Click to collapse
I'm also looking for a solution all the time
but I haven't found one yet
openyourmind said:
I'm also looking for a solution all the time
but I haven't found one yet
Click to expand...
Click to collapse
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
i was able to flash stock rom via fastbook (had to unlock bootloader 3 times, everytime it rebooted, but it worked tho)
only problem, when i install twrp and press reboot phone, it will only boot to twrp! and i have to type in a decription password or something, because i unlocked the bootloader and android should have deleted everything, but didn't cause i would have to reboot for that, but it will only boot in twrp .. so yeah, that's where i got stuck .. any idea?
otherwise i'll resell this thing and maybe get an htc 10 or a nexus 5x with stock mobo
Hi all,
I currently have stock 8.1 installed on my refurbished Nexus 5X with NO RPMB, and would like to install a custom ROM (Pixel2ROM from argraur).
If possible, I prefer NOT to get root. Maybe it helps passing safetynet.
As I understood, I should do following steps:
- Unlock bootloader
- Flash stock ROM. -> Is this step necessary since I already have stock 8.1 installed?
- Flash TWRP
- Reboot directly into TWRP
- Wipe data and cache
- Flash custom ROM
- Flash Magisk or superSU -> Without this step, would TWRP get replaced with stock recovery? Is Magisk or superSU better?
Can you please check if the steps are right, and answer the 3 questions.
Thanks!
EDIT: I tried without flashing the stock ROM nor root. Everything went fine and TWRP remains installed.
Hello I created a thread trying to help with this cases.. If someone with better knowledge see a better option, please say it there to update it..
NO RPMB (how to install TWRP, a new ROM and using Magisk)
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
ciorci said:
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
Click to expand...
Click to collapse
Without the magisk part its like you are using a normal rom with a normal boot image, just need to dirty flash the new rom..
With the magisk part it would need to make a new patched boot image..
So at least you will need to extract the new boot image of the new rom file, use it on magisk and patch it, after that I dont know... to my method work the first time it was needed a clean installation, but didn't tried it yet because the new update of my rom developer needed to be a clean installation due to many changes on the rom, so i didn't have opportunity to try update normally but when I do I will update my thread with what to do on that case and if it works..
It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks
Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.
Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.
Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).
relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.
ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.
The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.
Hi,
I have an XT1789-06, RETEU. I had it unlocked and rooted, but went back to stock without rom. However, bootloader is still unlocked. Got it somehow working to pas SafetyNet and run google pay while on Android 8, but now I OTA-updated to Android 9 (although first 10 attempts with OTA weirdly failed, number 11 finally worked ).
But now, with Pie, Google Pay is not working anymore and I receive two (instead of one at Android 8) error/warning messages while starting.
First one is still the "Your device has loaded a different Operating system" and the typical error screen.
But when booting up and showing the Motorola logo, theres a small hint saying "Verity mode is set to disabled"....
Please help!
No one here to help?
ElwynnEldoriath said:
No one here to help?
Click to expand...
Click to collapse
The Z2 Force doesn't quite have the support that it had in the early days. @Uzephi doesn't have the device anymore so he cannot do any building or testing anymore. The days of strong active development support has passed for this device. It sucks because I love the Z2 Force and it's my daily driver.
My understanding is that the text you see that says verity mode it set to disabled is there because the bootloader is unlocked. I'm not 100% sure about it though but I remember reading some other users posting about it.
If your device is fully stock on the Pie OTA, you can always relock the bootloader to see if that will allow you to use Google Pay and your banking apps.
My suggestion is to leave the bootloader unlocked because I'd you ever have any issues it will give you a couple more options to recover your device.
Sent from my Z2 Force using XDA Labs
Kidding...Figured I'd start off the banter on this topic. Excited to get mine and be on the bleeding edge but already anxious about loosing root for a while.
bacon612 said:
Kidding...Figured I'd start off the banter on this topic. Excited to get mine and be on the bleeding edge but already anxious about loosing root for a while.
Click to expand...
Click to collapse
Same! I do like to experience the phone exactly as it is out of the box for a little while first (otherwise how do I know what I want to mod?), but I hope root is available pretty quickly. It usually is with OnePlus devices, right?
haha, but the sooner the better!! cheers
My best guess is that root will be available upon receipt of the device. Magisk has already updated to patch the Samsung S21 Ultra (SD888) kernel, I'd imagine the kernel on the 9 Pro not to be that much different. TWRP on the other hand is probably no where close. Since the Chinese version of TWRP (LRTeam) stopped making recoveries before Android 11, I think a fully functional TWRP is a ways off. But we'll see... Mauronofrio has made TWRP work for many devices that weren't officially supported. There is also an app made by a kernel developer that can OC/UV the GPU. Haven't been able to use that just yet but hopefully soon!
EDIT: Looks like root is definitely good to go (dev thread with patched boot img for European and Indian versions).
Root should actually be available once u get the device. If there is an update, unlock bootloader first then get full OTA then extract the boot.img out of it and use magisk to patch then u can fastboot flash it.
Bradl79 said:
Root should actually be available once u get the device. If there is an update, unlock bootloader first then get full OTA then extract the boot.img out of it and use magisk to patch then u can fastboot flash it.
Click to expand...
Click to collapse
Yes. I had planned on doing this. Anyone seen a link to the full OTA? I'll extract and patch it for the US unlocked model. Nothing on oneplus.com support page yet
How do I unlock the bootloader?
My plan is to unlock bootloader as soon as I get the device than start using it, once Root / TWRP will become available I'll flash that.
Would it work? Or will I need to format before rooting?
Levi4cyber said:
How do I unlock the bootloader?
My plan is to unlock bootloader as soon as I get the device than start using it, once Root / TWRP will become available I'll flash that.
Would it work? Or will I need to format before rooting?
Click to expand...
Click to collapse
fastboot oem unlock? (to be confirmed)
It will format the data partition (if nothing has changed since my previous oneplus 3T).
Bradl79 said:
Root should actually be available once u get the device. If there is an update, unlock bootloader first then get full OTA then extract the boot.img out of it and use magisk to patch then u can fastboot flash it.
Click to expand...
Click to collapse
Can someone point me to an explanation of how to do this?
getting the full OTA (here on this forum, or on the oneplus website?)
extracting the boot.img (if it's more difficult than extracting it from a zip file?)
patching the boot with magisk (I've only applied magisk through recovery)
fastboot flash boot boot.img (that one I know )
Thanks.
clavelm80 said:
Can someone point me to an explanation of how to do this?
getting the full OTA (here on this forum, or on the oneplus website?)
extracting the boot.img (if it's more difficult than extracting it from a zip file?)
patching the boot with magisk (I've only applied magisk through recovery)
fastboot flash boot boot.img (that one I know )
Thanks.
Click to expand...
Click to collapse
Here is the guide I followed for my OnePlus 7 Pro. I assume it will be about the same.
[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro
Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk. Recommended to patch your own image read this Grab the latest Platform Tools HERE 1. Download a stock Oxygen OS ROM Zip from Here Or the general section of...
forum.xda-developers.com
I usually get the OTA from Oxygen Updater app, but it should also be on the OnePlus website.
There's a python script in the link above that extracts payload.bin in the OTA so that you can get to boot.img.
Install the latest Magisk app on your phone (previously Magisk Manager) and user it to patch boot.img: https://topjohnwu.github.io/Magisk/install.html
terlynn4 said:
Here is the guide I followed for my OnePlus 7 Pro. I assume it will be about the same.
[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro
Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk. Recommended to patch your own image read this Grab the latest Platform Tools HERE 1. Download a stock Oxygen OS ROM Zip from Here Or the general section of...
forum.xda-developers.com
I usually get the OTA from Oxygen Updater app, but it should also be on the OnePlus website.
There's a python script in the link above that extracts payload.bin in the OTA so that you can get to boot.img.
Install the latest Magisk app on your phone (previously Magisk Manager) and user it to patch boot.img: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Just need to get that system image so I can extract. Im on AA (international unlocked)
Same, I'm just here waiting for an AA system image. Impatient to get rooted and ensure L1 is working on this display!
Edit: It seems 9 Pro does NOT have hardware attestation which is great for those of us looking to root and keep our L1 certificate.
Can confirm,
fastboot oem unlock
worked to unlock bootloader like on past models. Waiting for that image now so we can actually do something.
Other variants already have root. We on AA (us unlocked) are still waiting for the image
It seems 9 Pro does NOT have hardware attestation which is great for those of us looking to root and keep our L1 certificate.
Nom Prophet said:
Can confirm,
fastboot oem unlock
worked to unlock bootloader like on past models. Waiting for that image now so we can actually do something.
Click to expand...
Click to collapse
Did you have to do anything special to get the fastboot command to work?
I went to developer options and enabled "OEM unlocking" and "USB debugging", then rebooted to fastboot mode and confirmed the device shows up, but when I run "fastboot oem unlock" I get this error:
FAILED (remote: Command not supported in default implementation)
Did I miss something?
terlynn4 said:
Did you have to do anything special to get the fastboot command to work?
I went to developer options and enabled "OEM unlocking" and "USB debugging", then rebooted to fastboot mode and confirmed the device shows up, but when I run "fastboot oem unlock" I get this error:
FAILED (remote: Command not supported in default implementation)
Did I miss something?
Click to expand...
Click to collapse
Make sure you have the latest fastboot and or latest Android developer suite installed
bacon612 said:
Make sure you have the latest fastboot and or latest Android developer suite installed
Click to expand...
Click to collapse
I just grabbed the latest platform-tools and tried again with the same results.
Actually I seem to be in Recovery Mode when I get that error. I started with the device booted and ran "adb reboot fastboot", and it took me to the menu where it shows the 3 languages (Recovery Mode, not Fastboot?). On that screen, "fastboot devices" shows the phone, but "fastboot oem unlock" gives an error.
From there, if I use the menu to boot to Fastboot Mode (where it says Fastboot Mode in red and says device state is locked), then "fastboot devices" doesn't show the phone anymore.
Fixed and unlocked now. I followed the following steps in the top answer here to install a different driver:
Android Fastboot devices not returning device
At the moment I would like to reinstall Android on my device(custom hardware device). I got the image files after building. But when I enter fastboot devices nothing returns. adb devices is worki...
stackoverflow.com
Odd that I didn't have this issue with my old phone since I was just flashing stuff with fastboot a few days ago. Older version or something, I guess.
terlynn4 said:
Fixed and unlocked now. I followed the following steps in the top answer here to install a different driver:
Android Fastboot devices not returning device
At the moment I would like to reinstall Android on my device(custom hardware device). I got the image files after building. But when I enter fastboot devices nothing returns. adb devices is worki...
stackoverflow.com
Odd that I didn't have this issue with my old phone since I was just flashing stuff with fastboot a few days ago. Older version or something, I guess.
Click to expand...
Click to collapse
Always gotta keep things up to date. I remember flashing a Motorola a while back that had me feeling frustrated and flummoxed only to find out that --while I had updated fastboot itself-- I had an out of date mfastboot, or whatever Motorola was using.