Database Info

[GUIDE] How to Flash the Pixel Experience ROM on Nokia 7 Plus & Nokia 7

Hey guys i know the Pixel Experience rom has been released for a long time, more information about this Pixel Experience rom https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-pixel-experience-t3796011
but unfortunately we could not boot on nokia devices after we flashed this rom
Congratulations that bootloop problem has been solved right now, we are not tired to flash roms
DOWNLOAD TWRP https://drive.google.com/open?id=1-e7zNrXp_mi468h-Zu1X5gbwQtgE17I6
follow these steps
1: unlock your bootloader
thank for @hikari_calyx
2: erase data/factory reset
3: connect your computer with adb and flash any roms based on project preble ( AOSP or RR )(why this step ? my friend told me that this twrp has a bug which can't boot recovery on official firmware)
Code:
fastboot flash system system.img
4: flash this TWRP supported project treble with
Code:
fastboot flash boot_a TWRP.img
Code:
fastboot flash boot_b TWRP.img
5: boot into the twrp
6: extract rom image from PE zip and download Magisk-v16.6.zip, after that move them to Internal Storage
7: format data and flash the Pixel Experience image, choose "System image" Notice: Don't do a reboot before flash Magisk.zip
8: flash the magisk.zip
9: wipe all data and reboot. Done !
Notice: you may see Your Device Is Uncertified when you intend to login Google on this device
Just Do This
Download and install Device ID.apk
copy your Google Service Framework ID
fill your GSF ID on this web and Clink on REGISTER
reboot some times you will be able to use google apps
btw all project treble roms do not include Adaptive brightness and Ambient display
fix them at here https://forum.xda-developers.com/project-treble/trebleenabled-device-development/overlay-enable-night-light-adaptive-t3741965
I'm on this rom for three days and every things go fine unless fingerprint control bug (that means you can control your phone easily with fingerprint)
thanks for viewing, sorry for my english is poor but I've been improving it, I wrote this GUIDE without translate tool
thanks for every member which develop the project treble rom and TWRP and something else

some amazing screenshots

The image does not load

12345wxj said:
The image does not load
Click to expand...
Click to collapse
什么？哪一个镜像不加载？

1452686579 said:
什么？哪一个镜像不加载？
Click to expand...
Click to collapse
我這邊圖片一個都加載不出來

I have a Little problem at step one ._.
No way to unlock BL?

Why is the TWRP upload locked behind a google drive link that you need to request access for?

pitt93 said:
I have a Little problem at step one ._.
No way to unlock BL?
Click to expand...
Click to collapse
there is a way. but you need to pay.

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
Do they accept ETH/BTC?

shubham412302 said:
Do they accept ETH/BTC?
Click to expand...
Click to collapse
i have no idea. i don't think so, you need to ask them. it's 5 dollars, they for sure accept paypal

Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.

Doktaphex said:
Why is the TWRP upload locked behind a google drive link that you need to request access for?
Click to expand...
Click to collapse
I don't know why. ? Maybe it is shared right now

Doktaphex said:
Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.
Click to expand...
Click to collapse
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work

1452686579 said:
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work
Click to expand...
Click to collapse
It might take me a couple of days as I am quite busy at the moment.

Thank you for your development for the Nokia 7 plus. Really appreciated.

Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )

Doktaphex said:
Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )
Click to expand...
Click to collapse
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!

sublimeace said:
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!
Click to expand...
Click to collapse
I got my entire system back up and running using the July patched boot image flashed into boot a and b and then sideloaded rollback zip etc, etc....
In general I have found that when I get my self into these situations, if I actually have a back up it ends up failing anyway.
It's always more fun walking the tightrope.
Anyway, both SIM slots are fine on stock ROM rooted with magisk, xposed etc.
I won't be flashing any treble images until I hear more success stories in that respect, I feel that our twrp still has some kinks that need to be ironed out.

9: wipe all data and reboot. Done ! you mean factory reset?

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
so, no way

NV Backup Warning - Dynamic partition invalid. Quite the riddle.

UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.

Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.

Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.

So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?

Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work

yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.

vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?

yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.

Have you tried flashing QCN file?

yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?

Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.

Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.

Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!

yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.

I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...

vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me

yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?

vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option

yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it

Issue with OOS flashing in TWRP

Hello,
I did a factory reset of OnePlus 8, and I also wiped the system partition. Now the only thing left on my phone is TWRP. I'd like to flash OxygenOS, so I downloaded a signed flashable zip on this thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233
But when I flash it with TWRP, it says (in blue)
"flashing A/B zip to inactive slot : A"
Step 1/2
and it's been like this for quite some time now. I wonder if I've done something wrong ? Or should I wait ?
Thanks !

up

LucasDupuis32 said:
Hello,
I did a factory reset of OnePlus 8, and I also wiped the system partition. Now the only thing left on my phone is TWRP. I'd like to flash OxygenOS, so I downloaded a signed flashable zip on this thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233
But when I flash it with TWRP, it says (in blue)
"flashing A/B zip to inactive slot : A"
Step 1/2
and it's been like this for quite some time now. I wonder if I've done something wrong ? Or should I wait ?
Thanks !
Click to expand...
Click to collapse
It should take since time but I would say no more than ten to fifteen minutes to complete. Unfortunately I don't want you to stop the process now that it's started that could definitely render it inoperable.
If it does come out of it with an error then just try again but be careful and make sure your can MSM your phone to previous version. I did my TMO to Global flash through zip file with the run all bat. That was pretty damn easy. Happy modding!

Nathan.7118391 said:
It should take since time but I would say no more than ten to fifteen minutes to complete. Unfortunately I don't want you to stop the process now that it's started that could definitely render it inoperable.
If it does come out of it with an error then just try again but be careful and make sure your can MSM your phone to previous version. I did my TMO to Global flash through zip file with the run all bat. That was pretty damn easy. Happy modding!
Click to expand...
Click to collapse
Thanks for your reply.
I left it for more than an hour and it was still on step 1/2. So I stopped the process by rebooting with ADB. When I did that it wiped my /sdcard. I tried to flash OOS again but same result ... I've never heard of MSM before. I just googled it and I see that's it's an unbrick tool only available for Windows but I'm using a Mac. I can still use my brother's laptop which runs Windows 10 but I'd like to know if there's any alternative before doing that.
I really just want to get OOS back Not crossflashing or downgrading
Thanks !

I had a same problem few days ago.
I managed to save my phone with this restore tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
Now everything works fine.

miimaa said:
I had a same problem few days ago.
I managed to save my phone with this restore tool: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
Now everything works fine.
Click to expand...
Click to collapse
Thank you for your answer.
I'm trying to run MSM tool but I can't boot in EDL mode and the link for the Qualcomm drivers appears to be dead ...

LucasDupuis32 said:
Thank you for your answer.
I'm trying to run MSM tool but I can't boot in EDL mode and the link for the Qualcomm drivers appears to be dead ...
Click to expand...
Click to collapse
I followed this video and it helped me to solve the problem.
I had problems with EDL-mode too. Try the EDL-mode by just pressing the volume up button and use the phones own cable.
Here's link for drivers: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043

miimaa said:
I followed this video and it helped me to solve the problem.
I had problems with EDL-mode too. Try the EDL-mode by just pressing the volume up button and use the phones own cable.
Here's link for drivers: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
Click to expand...
Click to collapse
Could you also give me the link for the video ? Thanks !

LucasDupuis32 said:
Could you also give me the link for the video ? Thanks !
Click to expand...
Click to collapse
Oops, sorry, here's the link: https://www.youtube.com/watch?v=jtc7EhNsfPA

ADB and 8T

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

OnePlus 8 TMO Missing IMEI and can't unlock bootloader

Hey yall, I really need some help.
So some back story:
I started using a oneplus 8 TMO version and wanted to unlock the bootloader to get android 12 and root the phone. So I went through the process of getting an unlock token and when I finally got it, unlocked my bootloader, flashed the global version of oxygen os, and got it updated to android 12. Everything was working great. So then I wanted to root the phone so I downloaded twrp, booted into fastboot, and tried flashing it. The phone then booted into the system even though I told it to boot into recovery. After about a minute or so it froze and rebooted into a kernal panic. I unfortunately do not have what it said and cant repeat the process, but it booted into recovery and I clicked reason for boot and it said something about the kernal. So after a reboot it then went into crash dump mode. So I had to use the msm download tool (unfortunately I only had the tmo msm version and thought I could just repeat the process because I had slow internet and didnt want to download the global msm tool) to get the phone working again. So booted into edl mode, reflashed the phone, and it booted up. The problem now is that I do not have an IMEI number. I have a wifi address, bt address, and everything else that makes me assume that the efs partition is still ok (but I dont know enough to debate that) but it does not recognize my sim card. The phone also freezed and restarts approximately every 30 seconds.
And now my problem and what I have tried:
Because I have no IMEI I cannot enable oem unlocking in developer settings, cant flash anything in the bootloader - including the unlock token - and can barely do anything in the system because it only stays on for small amounts of time. I have tried many imei write tools such as qualcomm smartphone write imei, readnwrite tool, fastboot imei writer, miracle box, and I think some others but none of them recognize my phone. Ive also tried the oneplus debloat and oem unlock script to try and bypass the setting but it didnt do anything. I have dialed *#801# and was able to enable engineering mode and diag toggle but it still didnt do anything for me. So I really dont know what to do any more. When in the bootloader or recovery the phone does not reboot, so I can stay there as long as I need. Any help on this would be greatly, greatly, greatly appreciated.

Have you tried using the MSMTool again?

Xryphon said:
Have you tried using the MSMTool again?
Click to expand...
Click to collapse
Yeah unfortunately that hasn't worked... I've done it miltiple times with the T-Mobile one and can't use any other one because I don't have an unlocked bootloader... If I had a way to bypass the oem unlocking option in the settings then I might have a chance to fix it but don't know how to do that...

try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen

gingerboy92 said:
try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen
Click to expand...
Click to collapse
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.

shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out

gingerboy92 said:
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out
Click to expand...
Click to collapse
Yeah, OOS 12 messed up my phone for a bit until I was able to get OOS 11 back on both slots.

shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
which worked for you?