Develop Bugs

Odin flashed firmware update re-lock my bootloader?

Okay so i went through the bootloader unlock process on my Note 4 without any major hickups, was running on CM13 ever since until i wanted to play with Gear VR which from what i could find required me to be on a stock based/touchwiz rom, first up was Omega which installed fine but would boot loop at welcome screen, so then i went with Evolution and almost same story, just boot loop. Figured it had to be a problem with the firmware version on my phone and without thinking i downloaded the CPF1 firmware and flashed with Odin. Flash went fine with no problems, booted into marshmallow just fine, enabled usb debugging and rebooted to flash TWRP for recovery and i get zilch. Every single TWRP and CWM recovery file i try to flash end in a failure. Can't even get Kingroot to give me root in MM so I think i'm stuck...dont even see the Unlock logo and Custom on the main screen after i hit the power button to turn on.
SO.........
Big question is, did i just re-lock my bootloader when i flashed firmware CPF1?

I think I did this same thing a while ago, were you on an older version of CM13 from May or so? Anyway, what I had to do was flash stock 5.1 in Odin with the up to date kernel, modem, etc and follow the guide to re-unlock your bootloader

Well got it re-flashed and unlocked again, gotta give a shout out to the great guys here on XDA.
Next question is do i need to flash a new bootloader or modem in odin/twrp before moving to a MM rom or is that stuff usually included in the rom? My experience in roms and stuff is from my old Razr Maxx HD and never jumped operating system version with it so i'm not sure on this one.

Is it possible to get back to stock ROM at this point?

Sorry in advance if this has been covered elsewhere.
-followed the steps to install a custom rom. unlocked the boot loader, installed twrp, cleared dalvik/data/etc.
-ROM eventually booted up ok, however, I could not connect to project fi with it. (unfortunately, your project fi service can't be activated right now-code t120).
-So, my intention was, ok, I will go ahead and go back to the latest stock. however, booting to recovery it appears to have reverted back to the stock recovery, and adb will not detect the device(fastboot will, but, when trying to run anything, be it to repush twrp, it just hangs. If I try and do the flash-all.bat off of the stock rom zip, it tells me flashing is not allowed for critical partitions, even though it is in fact unlocked. To be safe, I tried both fastboot flashing unlock, and unlock_critical.. both went to a '...' and sat there).
It still boots up and loads fine, I just cannot activate Fi, and cant seem to get anywhere with it otherwise. Any suggestions?
One final question- since i cannot get it to install stock rom via fastboot- if i drop the taimen-opm zip onto the phone directly, can i install it that way? Or am I S.O.L. because i do not have the custom recovery on there anymore?

Okay, what you're going to have to do is.
1. Go into fastboot mode and fastboot boot twrp.img and then flash another rom after doing a factory reset in custom recovery
2. Go into fastboot and flash factory image by downloading it from the google site.

mr.notsotech said:
Okay, what you're going to have to do is.
1. Go into fastboot mode and fastboot boot twrp.img and then flash another rom after doing a factory reset in custom recovery
2. Go into fastboot and flash factory image by downloading it from the google site.
Click to expand...
Click to collapse
Unfortunately that won't work for me. I tried fastboot boot recovery.img (its what I had renamed the twrp img file) and it fails with a data xfer failure, too many links.

otownmarine said:
Unfortunately that won't work for me. I tried fastboot boot recovery.img (its what I had renamed the twrp img file) and it fails with a data xfer failure, too many links.
Click to expand...
Click to collapse
Scratch that. Took some major screwing around (changing usb ports, multiple attempts at getting twrp to stick) but I was finally able to get it to apply the stock ROM and everything seems functional. Thanks.

Use this tool next time, it should help you out. It's worked 100% of the time for myself and I ended up staying on stock after countless minor annoyances with being rooted or using custom roms.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

otownmarine said:
Scratch that. Took some major screwing around (changing usb ports, multiple attempts at getting twrp to stick) but I was finally able to get it to apply the stock ROM and everything seems functional. Thanks.
Click to expand...
Click to collapse
Very sad to see we are still having so many USB related issues. We really need to come up with a definitive FAQ me thinks. Glad you got it done! ?

otownmarine said:
Scratch that. Took some major screwing around (changing usb ports, multiple attempts at getting twrp to stick) but I was finally able to get it to apply the stock ROM and everything seems functional. Thanks.
Click to expand...
Click to collapse
Yeah I keep forgetting that twrp is super finicky on this device because of the boot slots (a,b). I'm so happy you got it working. your adb has to be up to date as well.
I learned all of that the hard way as well. I just don't have a good memory of the steps I did. lol. I found that for my usage after trying multiple roms on this device that, stock rom is the best for my battery life and smoothness. I did root though and flashed a custom kernel. But that is only because I love thinking that my kernel is helping my battery life somewhat as well.

Just a heads up the reason you cant use project fi on a custom ROMs is because your probably using the e-sim. The software process behind the e-sim hasn't been worked out for custom ROMs and probably never will (not a big demand for it). You can always order a Sim card from project fi and put it into your phone and that will work with a custom ROMs; I have used project fi on every custom ROMs for Pixel 2 xl there is and no issues.

Did factory reset rooted XT 1799-2, now phone only boots into recovery mode

Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six

sixtheninth said:
Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
Click to expand...
Click to collapse
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files

jvfigueredo said:
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
Click to expand...
Click to collapse
Thanks senor, but how do I flash it via fastboot? Can't I use TWRP instead?

jvfigueredo said:
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
Click to expand...
Click to collapse
Ok I was able the Stock rom, but it is Chinese, not the global one wihout Gapps and lots of bloatware. Do you know if there is also a GLOBAL stock ROM I can get? Conversely, is there perhaps a custom ROM like Lineage OS or others that is compatible with this device? Cheers

sixtheninth said:
Ok I was able the Stock rom, but it is Chinese, not the global one wihout Gapps and lots of bloatware. Do you know if there is also a GLOBAL stock ROM I can get? Conversely, is there perhaps a custom ROM like Lineage OS or others that is compatible with this device? Cheers
Click to expand...
Click to collapse
Sorry this is the stock rom of montana_retcn, to install the playstore by the store that comes in it, and it has the English language.
The rom that you were supposed to be a shop rom of the store that you bought, mine came with one of this but unfortunately I do not know where it has to download ...

jvfigueredo said:
Sorry this is the stock rom of montana_retcn, to install the playstore by the store that comes in it, and it has the English language.
The rom that you were supposed to be a shop rom of the store that you bought, mine came with one of this but unfortunately I do not know where it has to download ...
Click to expand...
Click to collapse
Ok I guess there is nothing more to be done here. Any custom ROMs are also probably not lying around too I guess :/

sixtheninth said:
Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
Click to expand...
Click to collapse
Turn off the device, boot into Fastboot Flash Mode using vol down + power, using volume keys scroll and select factory mode and device will turn on. the next time you boot up the device, it won't go into TWRP directly. I have faced this issue many times. Hope this helps.

rizwan.mahai said:
Turn off the device, boot into Fastboot Flash Mode using vol down + power, using volume keys scroll and select factory mode and device will turn on. the next time you boot up the device, it won't go into TWRP directly. I have faced this issue many times. Hope this helps.
Click to expand...
Click to collapse
Not in this case. What Factory Mode did was that it got stuck in loading loop playing the Moto logo endlessly for over 5 minutes. Anyway, the phone is now hard bricked so I am facing even larger issue )

sixtheninth said:
Not in this case. What Factory Mode did was that it got stuck in loading loop playing the Moto logo endlessly for over 5 minutes. Anyway, the phone is now hard bricked so I am facing even larger issue )
Click to expand...
Click to collapse

I'm having the same problem with my wifes g5s.
I have found that from twrp>restart>bootloader (phone then enters bootloader) I can the immediately choose "start" to boot the phone.
But that is a hassle I'd prefer my wife not having to go through...

SvenHee said:
I'm having the same problem with my wifes g5s.
I have found that from twrp>restart>bootloader (phone then enters bootloader) I can the immediately choose "start" to boot the phone.
But that is a hassle I'd prefer my wife not having to go through...
Click to expand...
Click to collapse
Flash stock ROM via fastboot problem will be solved..
As far as people who need play store can flash gapps via TWRP as a same method we use for custom ROMs.
P.S. i will not suggest to buy XT1799-2 because this SKU is purely made for Chinese Market, if you need any custom ROM go to Weibo.com/diyroms and post a request to build a custom ROM for this device.
And there are some custom ROMs available that you can search via baidu.com ( Chinese Search Engine).
I will try to find any ROM and post for you guys and also post. Request to build for XT1799-2.
CHEERS

so have you find any global custom rom for this device ?

aamszia said:
so have you find any global custom rom for this device ?
Click to expand...
Click to collapse
Yes you can flash Viper Pie for Xt1792
Already tested at Xt1799

Question TWRP and the current version of OS as right now, both OEM and bootloader already unlocked

Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)

TWRP doesn't work with A12.

ffejy462 said:
TWRP doesn't work with A12.
Click to expand...
Click to collapse
This, decryption isn't supported AT ALL by any recovery running on A12. I've seen modified recoveries for A12 for other devices and it seems they try to disable forced encryption which is a BAD idea!
If you want to decrypt, would recommend either staying with OOS 11 or a custom ROM on A11. Bear in mind there have been numerous reported issues with TWRP hence why most custom ROMs for the OP9P choose to stick to LineageOS recovery.

cat139lyleb said:
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
Click to expand...
Click to collapse
It's because you flashed an incompatible TWRP (not compatible with Android 12 ROMS)

Okay, maybe TWRP is already aware of this problem with 12 ROMS, plus I already did tried a few times with OEM unlock in 11, but no luck. So that's why OEM unlocked in 12... very weird...
The bootloader won't unlock until OEM unlocks in any android versions. So first, that's why.

I have a question about that. Do you think it's why -> SECURE BOOT - YES?
Then how do we make it say NO?
Because we are aware that it is FULLY unlocked as DEVICE STATE - UNLOCKED, correct?

Question Revert back to Stock OOS

Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!

You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/

Salilsarkar said:
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Click to expand...
Click to collapse
Many thanks! I was having issues downloading the stock firmware files needed for the MSM tool. I do have the downgrade zip and ota signed zip for my model, but extracting with payload dumper gives me only 7 image files so I think it's incomplete, and I would still need to download the full firmware files to be able to flash via fastboot.

If you try using fastboot to downgrade, you're very likely going to brick and have to use the MSM anyway.

blitzkriegger said:
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
Click to expand...
Click to collapse
I was able to flash to oos11 using twrp. Well, I was on crdroid and there are custom ROMs that require oos12 before It will work. So I went crdroid 8.6 to oos11 to oos 12 and then lineage 19

Well it was a ride for me lol. Took me a few hours to realize I can gain fastboot access via long pressing power button+volume up and volume down altogether. I was then able to reflash the modded magisk boot image to regain access to AOSPA.
The fun part came after trying to flash back to stock via MSM. First I figured out that instead of using the "vol up+vol- button approach then connect usb" way of trying to get MSM tool to connect to the EDL mode of the phone, an easier method is to use "ADB reboot edl" command.
Now as I previously used global stock OOS, I mistakenly used the MSM tool for the global region. However, this got me in a SHA-256 mismatch in the flashing process, causing a flash error which got me back to getting stuck at the bootloader again. Turns out the global MSM tool does not work for LE2120 model.
So at this point I had 2 options - either find a MSM tool that works, or try flashing back to stock via fastboot. The fastboot way would have worked but I ran into a problem - you have to flash to .img files partly via fastboot, then partly via fastbootd. And when on fastbootd my phone is not recognized by the PC (this is why trying to flash back AOSPA also failed, it can't continue the fastbootd part of the install as for some reason my pc loses connection with the phone on fastbootd).
My saving grace was I found out that for LE2120, the EU version of the MSM tool works. So long-story short I got back to stock OOS 12 again. It was a fun yet nerve wracking experience, and I learned a lot.
So the lesson of the story is, for anyone tinkering with this device, to learn the basics, from knowing your correct model number, knowing the proper button combinations to boot to fastboot/edl/recovery, knowing which tools to use, to knowing how to setup/troubleshoot your pc to ensure the phone communicates properly at every step!