Hey, after yesterday's security update, the phone is stuck on powered by android screen. The only thing I can do is go into fastboot. It does not boot into recovery (gets stuck on powered by android screen once again). I don't have an unlocked bootloader, so I cannot really flash directly from fastboot. Any ideas what could be done?
Hi,
I had the same Problem.
When my phone has booted, I could choose between "Start", "Fastboot" and "Recovery". I choose recovery, but everytime it booted to where I can choose between the options. After a few times (5 or so) it booted to TWRP. Then I Flashed Back to the January Update (OTA ZIP-File downloaden from the Essential Website). Then my phone booted normaly to Android.
Maybe if you Don't have TWRP, you can follow the instructions on the Website from Essential.
No issues here but I'm stock and unrooted
I had issues as well. The problem is anytime i try to boot into TWRP when i apply it to the current kernel. Magisk is fine, but TWRP, when applied to the current kernel doesn't seem to load.
1. After feb install, i put TWRP (with jan kernel) in slot B and i was not able to boot to it (it came right back to the fastboot screen). I could boot into A which was the new stock kernal but B was a no-go.
2. I then put the december kernel with twrp into slot b and that did the same thing! i was not able to boot into slot b.
3. Then i put the original TWRP mata file into B and then was now able to boot into twrp.
4. now in TWRP, in slot b, i ran the TWRP installer and it patched slot A and B. Upon reboot, slot a just bootlooped!
4. i then just copied the feb kernel with magisk into A and the phone boots.
5. i now have feb w/magisk on slot a and mata TWRP in slot b. I have not found a way to have twrp working in slot A!
JD
Well, in my case, the phone is fully stock. At this point, I think I am limited to fastboot as it's not booting in recovery. Is there anything that can be done within fastboot without unlocked bootloader?
update on "no booting with feb": i cannot get into twrp at all now. It doesn't matter if i use the original mata twrp kernel or any new or old kernels with TWRP; they all fail and boot to fastboot.
I reflashed jan and now twrp works just fine. Can someone confirm if feb does indeed work with twrp?
Thanks,
JD
Apparently the old version of TWRP isn't compatible with the February OTA update from essential, maybe all the future monthly OTA's as well.. but, a user has created and posted a February img for TWRP compatible with this month's OTA. I think the zip for that February version of TWRP is coming soon as well... Currently running February OTA with the February TWRP image on slot b.. I'm not flashing anything else until the zip for the new TWRP comes out
RoyalOrigin said:
Apparently the old version of TWRP isn't compatible with the February OTA update from essential, maybe all the future monthly OTA's as well.. but, a user has created and posted a February img for TWRP compatible with this month's OTA. I think the zip for that February version of TWRP is coming soon as well... Currently running February OTA with the February TWRP image on slot b.. I'm not flashing anything else until the zip for the new TWRP comes out
Click to expand...
Click to collapse
do you have a link for this twrp compatible with this months ota? i am not able to find it here on xda.
Thanks,
JD
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
RimvydasT said:
Is there anything that can be done within fastboot without unlocked bootloader?
Click to expand...
Click to collapse
Don't think so... You definitely can't flash anything with a locked BL.
RoyalOrigin said:
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
https://drive.google.com/file/d/11YtZTqgbDRgws10RpMwIGTSy_X_2A9re/view?usp=drivesdk
I will try that.
Thank you very much.
kt-Froggy said:
Don't think so... You definitely can't flash anything with a locked BL.
Click to expand...
Click to collapse
yeah.. it doesn't look good. I wonder what Essential reps will have to say about their update bricking the phone, but as it's out of warranty, I doubt there will be any positive outcome here.
RoyalOrigin said:
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Very nice find! Thank you for posting this information.
JD
Related
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app
With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk
cas239 said:
With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.
tech_head said:
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.
Click to expand...
Click to collapse
I flashed TWRP Recovery when I rooted the phone
Bump
Sent from my PH-1 using Tapatalk
I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.
bjs339 said:
I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.
Click to expand...
Click to collapse
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.
tech_head said:
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.
Click to expand...
Click to collapse
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?
bjs339 said:
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?
Click to expand...
Click to collapse
No.
I was just talking about back to stock.
You would need to flash Oreo B3 separately.
You could just connect to a computer and flash Oreo B3 without going back to stock.
The fastboot flashable ROM is in the ROM section of the forum.
I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.
bjs339 said:
I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.
Click to expand...
Click to collapse
TWRP has a screen image offset.
Look very carefully at the passcode as you enter it.
I have a failure rate of about 50% due to the misalignment.
I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!
How did you "return to stock"? Using what method and files? From what are you returning?
drumrjoe said:
I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!
Click to expand...
Click to collapse
Which version of the stock ROM?
It originally came with 7.1.1 NMJ32f/436.. which upgraded to the latest version of pie... 9 something.. I have tried using the .bat file on both stock files, NMJ32F_back_to_stock and PPR1.180610.091_BACK_TO_STOCK_OTAFILE with the same result.. see vid please ... https://photos.app.goo.gl/XRUScdV9UYDnx5dn9
Thanks in advance for any help.
DJ
So I've had the idea and its probably been discussed to death because I'm slow. But say now I have pie running on partition a, what stops me from swapping to slot b in fastboot and installing a stock oreo or say custom rom? I've already bricked one essential so I'm gunshy to do anything. But luckily it worked out because I'm sure the one I had before was a sprint "unlocked" one everyone is having issues with.
The January updates are up.
OTA is live too. Just 50.8 MB for 1st Gen XL.
ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now
ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.
Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
Does anyone have the January pre-rooted boot.img?
BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
^^^
This is a 1st.........never seen anyone ask for it........LoL
BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...
crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work
- There are no Pixel security patches in the February 2019 Pixel Update Bulletin.
-Functional patches
All Pixel devices running Android 9 will receive an Android 9 update as part of the February OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and
supported Pixel devices.
Now it is installing. I still don't know what is changed. The Update is 111.6MB.
https://source.android.com/security/bulletin/pixel/2019-02-01.html
Security patch levels of 2019-02-05 or later address all issues associated with the 2019-02-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Pixel update schedule.
Has anyone had issues updating to FEB then applying Magisk?
Thanks
I'm having issues flashing the factory image without "-w," gives me the "Your device is corrupt and cannot be trusted" screen. Anyone else?
EDIT: flashing the Jan update fixes this and allows my device to boot again
So, I found this little egg by tapping, then pressing on device number. Is this new?
Paint.apk ?
N3V3RS3TTL3 said:
So, I found this little egg by tapping, then pressing on device number. Is this new?
Click to expand...
Click to collapse
Nope, it's been there before.
The only visual change I have noticed on my Pixel 2 XL so far is a slightly different color on the About Phone section in Settings.
N3V3RS3TTL3 said:
Paint.apk ?
Click to expand...
Click to collapse
And where is that? Can we open it someway?
Sent from my Pixel 2 XL using Tapatalk
vagkoun83 said:
And where is that? Can we open it someway?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's the Easter egg:
"The new Easter Egg can be found by going to ‘System’ > ‘About phone’ > ‘Android version’ > and tapping the nine multiple times, then the old P Easter egg will appear on a Pixel 3. If you keep taping the ‘P’ a few more times, the drawing UI appears."
The about phone option is no more in the system section.
docluv01 said:
Has anyone had issues updating to FEB then applying Magisk?
Thanks
Click to expand...
Click to collapse
I had issues with the update in general, but it was my fault. Everything worked out in the end. I think more than a little of it was because of the changes under the hood that Google applied.
Updated perfectly. Downloaded OTA, flashed in TWRP with TWRP zip, reboot to recovery to flash kernel then magisk. No issues whatsoever.
February feels much better, although could just be a placebo ?
I flashed with Duece script at usual. I'm no longer able to fastboot flash TWRP because it just hangs at the initial TWRP screen. Then I have to flash the ota or stock boot.img for the phone to boot. The old process to root doesn't work for me on the February update. I still was able and flash a magical patched stock boot image. So now I'm rooted with no recovery to flash a custom kernel.
mookiexl said:
I flashed with Duece script at usual. I'm no longer able to fastboot flash TWRP because it just hangs at the initial TWRP screen. Then I have to flash the ota or stock boot.img for the phone to boot. The old process to root doesn't work for me on the February update. I still was able and flash a magical patched stock boot image. So now I'm rooted with no recovery to flash a custom kernel.
Click to expand...
Click to collapse
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
jd1639 said:
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
Click to expand...
Click to collapse
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
mookiexl said:
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
Click to expand...
Click to collapse
I'm not sure what state your device is in so I'd flash the feb factory image using the flash all batch file with the -w removed. That'll return your device to stock without wiping it. Then fastboot twrp, then install twrp, if you want it, then install magisk.
mookiexl said:
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
Click to expand...
Click to collapse
USB cables, ports, and platform-tools up to date?
Badger50 said:
USB cables, ports, and platform-tools up to date?
Click to expand...
Click to collapse
Neither of those are the issue because I was able to fastboot flash the magisk patched kernel image. I'm kinda leaning towards TWRP issue. If I go back to January update I can then fastboot flash TWRP . I'm actually shocked no one else is having this issue.
mookiexl said:
Neither of those are the issue because I was able to fastboot flash the magisk patched kernel image. I'm kinda leaning towards TWRP issue. If I go back to January update I can then fastboot flash TWRP . I'm actually shocked no one else is having this issue.
Click to expand...
Click to collapse
Meh...I've had the same twrp file for months, and it's worked with all the updates. But hey, this is the P2XL...so anything's possible :good:
jd1639 said:
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
Click to expand...
Click to collapse
Not sure if I'd consider Deuces flash script a toolkit per se...
New Rising said:
Not sure if I'd consider Deuces flash script a toolkit per se...
Click to expand...
Click to collapse
It's a toolkit. Toolkits generally simplify processes and hide output that advanced users can use to achieve the same results without the toolkit.
Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.
thanks for this.. i was looking everywhere for boot extraction tools
Hi. I am looking for some method to flash a recovery or rooted boot for Razer 2 since the USB port on it is messed up.
Not sure if it is the software or the hardware, but the only way I can charge it at all (slowly) if I use an USB A to C cable and the device is off (well, not really since it flashes the logo, vibrates, and now complains about the unlocked boot-loader)
The stock recovery has the option "apply update from SD card" Are there any signed images in update.zip form I could just throw on the sd card?
By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.
There isn't one. Once booted you can use ADB over WiFi. But Fastboot only works with USB.
You're far better off updating to the newest firmware and patching via magisk than ever using downloaded pre-patched boot images
That would be true if we could get Magisk to patch a un-rooted phone. All I've done here is extract the latest stock firmware and patch it with Magisk so others can flash it. I believe the first time you boot after, it askes you to updated to the latest version.
hackthis02 said:
Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.
Click to expand...
Click to collapse
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.
kylster said:
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.
Click to expand...
Click to collapse
Take the patched one and flash it like you would any boot.img
Flash w/ Fastboot
pensive said:
By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.
Click to expand...
Click to collapse
not sure if i can paste here, but here we go...
Spoiler
https://www.reddit.com/r/razerphone/comments/iyb47z
im not sure why in razer webpage is incorrect, but is the same server AWS
P-SMR7-RC003-RZR 210107.3225Security Maintenance Release / Over The Air (OTA) UpgradeGlobal (Aura)9.0 Pie2021 February 05
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3225-user-full.zip
Hey I recognize that post