Related
https://www.essential.com/developer/current-builds
Also, just received it on my phone this very moment.
Downloading now! Came to post this exact thing.
UPDATE
Screen shot for those interested
changelog?
mookiexl said:
changelog?
Click to expand...
Click to collapse
Check the screenshot one post right before your!
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
ziddey said:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
Click to expand...
Click to collapse
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
If I try to unroot by restoring images it says "Stock backup does not exist!"
sruel3216 said:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
Click to expand...
Click to collapse
I believe you'd fail the OTA if you have an altered boot, but you can try.
oracleoftruth said:
If I try to unroot by restoring images it says "Stock backup does not exist!"
Click to expand...
Click to collapse
I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing
You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.
Drop a shell.
Determine current boot slot: getprop |grep boot.slot
Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)
Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.
Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.
Nice...4 days in, and patched with the security update already.
ziddey said:
I believe you'd fail the OTA if you have an altered boot, but you can try.
Click to expand...
Click to collapse
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.
For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Just installed patch. Scrolling feels so much better, especially when scrolling slow.
gorm said:
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Click to expand...
Click to collapse
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!
I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to
get my screen back.
Really weird stuff.
EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/
I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.
Thanks!
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
jon_ybanez said:
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
Click to expand...
Click to collapse
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
beard805 said:
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
Click to expand...
Click to collapse
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Sadly, I don't know much about the SIM side of the issue
Hope someone with more knowledge can chime in!
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing
You can try to dd them:
Code:
dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2
Would be a good idea to backup your current images
from https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135
To avoid headache, if you flashed android 11 update. Don't flash the twrp. Don't be foolish like me thinking that the old twrp will work. Now my device is bricked
@blackhawk do you have twrp in android 10 installed. Can you provide me nvram backup cause mine was currupted
CrisTV said:
@blackhawk do you have twrp in android 10 installed. Can you provide me nvram backup cause mine was currupted
Click to expand...
Click to collapse
Sorry but I don't. I'm still using Pie on a stock Note 10+.
Which is why the sad face icon and no comment previously.
blackhawk said:
Sorry but I don't. I'm still using Pie on a stock Note 10+.
Which is why the sad face icon and no comment previ
Click to expand...
Click to collapse
its ok, thanks
Did you try flashing you phone in EDL mode? I think that might work even without a working boot.rom or recovery.rom.
Good day everyone. Can anyone share with me a link or files of the latest update for GM1915. I mistakenly bricked my oneplus 7 pro tmobile and cant seem to get past tmobile logo after reboot. I have formated but still no way. I have looked up every where online in search of the stock rom download so i can extrate boot.img or just flash the whole thing. Is there anyone to help with that? i will be extremely grateful. Thanks.
BlurAirll said:
Good day everyone. Can anyone share with me a link or files of the latest update for GM1915. I mistakenly bricked my oneplus 7 pro tmobile and cant seem to get past tmobile logo after reboot. I have formated but still no way. I have looked up every where online in search of the stock rom download so i can extrate boot.img or just flash the whole thing. Is there anyone to help with that? i will be extremely grateful. Thanks.
Click to expand...
Click to collapse
im
BlurAirll said:
Good day everyone. Can anyone share with me a link or files of the latest update for GM1915. I mistakenly bricked my oneplus 7 pro tmobile and cant seem to get past tmobile logo after reboot. I have formated but still no way. I have looked up every where online in search of the stock rom download so i can extrate boot.img or just flash the whole thing. Is there anyone to help with that? i will be extremely grateful. Thanks.
Click to expand...
Click to collapse
im in the same boat here, exactly your problem. let me know if someone helps and gets our phones back
Raahim.v said:
im
im in the same boat here, exactly your problem. let me know if someone helps and gets our phones back
Click to expand...
Click to collapse
I actually found a solution to it. I will share with you the link on how i did get past the problem.
jlwoolf said:
I have GM1915 that I converted to international and had some weird graphical issues, but I did find a solution (sort of). First I used MSM to flash OOS 9. Starting from there I used oxygen updater to get the OOS 10 version and then again to get the OOS 11.0.3.1.GM21AA. Now I still had graphical issues (not as severe as what you described, but some scaling problems nonetheless). I didn't like the fix of FHD 60hz cause at that point the phone just felt slow, so I used adb to force 90hz and then disabled battery saver to force QHD. Also, I installed an "updated" linux kernel. IDK if it helped, but so far my phone has worked well.
I made a little guide and am uploading files to this folder right now (its about 9gb of downloading so its gonna be a sec). Hopefully this makes your phone work in Android 11.
Click to expand...
Click to collapse
Here. Follow this guild. It will help u convert to international rom. That's how i get past the problem.
Converted T-Mobile rom to international rom.
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
my POCO X3 PRO was in the ArrowOS A13 ROM, I modified some things like the Adreno Drivers to version 615 worked perfect, the next day I updated via OTA with OrangeFox and everything was still 100% after 2 days I was editing a video and it crashed It got stuck and didn't respond, then when it restarted it didn't start the ROM (it stayed in the POCO logo)... It goes into recovery but it takes at least 30 seconds to go in, I saw that I got 3 new partitions that weren't there (System_EXT, Product, ODM,) does not recognize the storage (the Micro SD does) the VAYU has dynamic partition, but my VAYU says that it has not tried to recover by My flash. it flashed ok but it didn't work. gives an error called (Block device required)
linuxinho said:
my POCO X3 PRO was in the ArrowOS A13 ROM, I modified some things like the Adreno Drivers to version 615 worked perfect, the next day I updated via OTA with OrangeFox and everything was still 100% after 2 days I was editing a video and it crashed It got stuck and didn't respond, then when it restarted it didn't start the ROM (it stayed in the POCO logo)... It goes into recovery but it takes at least 30 seconds to go in, I saw that I got 3 new partitions that weren't there (System_EXT, Product, ODM,) does not recognize the storage (the Micro SD does) the VAYU has dynamic partition, but my VAYU says that it has not tried to recover by My flash. it flashed ok but it didn't work. gives an error called (Block device required)
Click to expand...
Click to collapse
Other recovery like twrp, relocked bootloader? Block device required? You use Google? There are many threads about this error
joke19 said:
Other recovery like twrp, relocked bootloader? Block device required? You use Google? There are many threads about this error
Click to expand...
Click to collapse
I already tried different recoveries, and nothing, I can't find information about the problem, I don't know if it's a hardware problem or if it has to be repaired, I didn't expect that, I had been with the VAYU for 9 months and I've changed everything and nothing had happened to me. my bootloader is unlocked
Flash stock fw with fastboot
cuynu said:
Flash stock fw with fastboot
Click to expand...
Click to collapse
I already tried it, with my flash
linuxinho said:
I already tried it, with my flash
Click to expand...
Click to collapse
You use Google? In the morning I had read something over flash stock recovery and sideload... XDA and the net have many threads
joke19 said:
You use Google? In the morning I had read something over flash stock recovery and sideload... XDA and the net have many threads
Click to expand...
Click to collapse
I don't use google, I use the rom clean without gapps, I never use google services
Search for your error with Google
linuxinho said:
I don't use google, I use the rom clean without gapps, I never use google services
Click to expand...
Click to collapse
joke19 said:
Search for your error with Google
Click to expand...
Click to collapse
there is no information about the error, on the internet
linuxinho said:
there is no information about the error, on the internet
Click to expand...
Click to collapse
Okay
joke19 said:
Okay
Click to expand...
Click to collapse
I think I'll have to take it to a specialized technician
Use original fastboot rom from xiaomi. That's fixed my issues.
eliasnico said:
Use original fastboot rom from xiaomi. That's fixed my issues.
Click to expand...
Click to collapse
did you have the same error as mine?
A similar issue happened to me on stock ROM as well. I'm wondering if the boot partition is just dead and requires service?
linuxinho said:
my POCO X3 PRO was in the ArrowOS A13 ROM
Click to expand...
Click to collapse
Ok, although I don't understand why would you even use 13... but ok...
linuxinho said:
modified some things like the Adreno Drivers to version 615 worked perfect,
Click to expand...
Click to collapse
First mistake. You THOUGHT it worked perfect. Can you confirm that with dmesg and logcat? Absolutely no errors or crashes related to the gpu? Come on, man!
linuxinho said:
after 2 days I was editing a video and it crashed It got stuck and didn't respond,
Click to expand...
Click to collapse
How come, since it works perfectly?! I often encode, recode, cut and edit video on my unmodded ArrowOS 11 Poco X3 Pro, and have no issues. Unbelievable!
99 percent of Poco bricks on this forum are caused by inept people tinkering with parts of firmware they should not tinker with. Well, besides indian Poco versions, those were abysmal.
I had this issue also, i fixed it by flashing xiaomi.eu fastboot rom, used batch file (present in rom zip) for clean install.
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/xiaomi.eu_multi_POCOX3Pro_V13.0.4.0.SJUMIXM_v13-12-fastboot.zip/download
<Moderator Edit>: Deleted quote since I deleted the quoted post.
One can express such things in a different, non hurting way, remaining objective and not senseless aggressive. Finaly we all have made +/- stupid things in the past und hoped to get help from experts
<Moderator Note>: Thread cleaned.
Everyone, please always follow XDA Developers Forum Rules , especially in this instance, Rule 2.3:
2.3 Flaming / Lack of respect: XDA is about sharing, and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Whenever anyone breaks any of our rules, please use the Report button in the lower right corner of their post and let us know so that we may address it, and at the same time please don't respond to the posts that break our rules - only report them. Thank you!