Develop Bugs

One m8 t mobile lollipop ota captured

Got the update at 2am, posting it so maybe custom roms can get WiFi calling, feel free to mirror just asking you keep them in the thread.
https://docs.google.com/file/d/0B7lAMKoPVdWKU1VfSnRNZS10Zjg/edit?usp=docslist_api

would i be able to just flash this if i wanted to with twrp. just curious.

Android6190 said:
would i be able to just flash this if i wanted to with twrp. just curious.
Click to expand...
Click to collapse
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.

dang. okay

T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip

do we just flash in twrp? Thank you by the way

No it's a stock ota you have to use HTC recovery.

rubyman94 said:
do we just flash in twrp? Thank you by the way
Click to expand...
Click to collapse
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad

bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
Umm... your Firmware file is corrupted

Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.

bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
I mean it could be my computer but it keeps saying its corrupted when I download it.

Azuske said:
Umm... your Firmware file is corrupted
Click to expand...
Click to collapse
It's not, it's encrypted.

bradley_e_smith said:
really? it came directly from the OTA.zip file and I was able to extract recovery.img from it.
Click to expand...
Click to collapse
gamer765 said:
It's not, it's encrypted.
Click to expand...
Click to collapse
Oh, well it won't let me put it on my device because the computer thinks it's corrupted

Fenny said:
Twrp won't have the decryption keys or some of the HTC specific functions required to apply the OTA. You'll need a stock /system and a stock recovery.
Click to expand...
Click to collapse
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.

cyclonesworld said:
Would this explain the error that I'm getting?
Package expects build fingerprint of htc/tmous/htc_m8:4.4.4/KTU84P/396641.2:user/release-keys or htc/tmous/htc_m8:5.0.1/htc_m8: 5.0.1/LRX22C/464190.4:user/release-keys.; this device has htc/tmous/htc_m8:4.4.3/KTU84L/365360.5/user/release-keys.
I flashed stock recovery, but my phone is still root. Did a full wipe/restore, still getting same thing. The error looks like it's not happy about a missing update perhaps, if I'm reading that correctly. Best I know, I have the latest kitkat version. But, I've had twrp for awhile so maybe I missed an OTA update along the way.
Click to expand...
Click to collapse
If you're SOFF and supercid just flash the lollipop ruu T-Mobile just release. It doesn't matter what previous rom you're on. Then reflash custom recovery and rooted. I've done this alot of time already.

bradley_e_smith said:
Check out my TWRP of a stock no-root ROM (lollipop): https://mega.nz/#F!qsNkyITK!yGJVGKuWOZ_vyndIF8-Z0Q
There are also other files there as well, but remember that if you don't update your firmware you may have issues.
-brad
Click to expand...
Click to collapse
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?

rickpref said:
So the steps would be:
- Flash stock recovery via fastboot
- Flash firmware via fastboot
- Flash twrp via fastboot
- Flash Lollipop via twpr
Is this correct?
Click to expand...
Click to collapse
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad

bradley_e_smith said:
For me (I am s-on) I did it in this order:
- flashed twrp stock rom
- rebooted and made sure the rom worked
- flashed stock recovery via fastboot
- rebooted and downloaded and installed OTA.
If you are s-off I believe (someone correct me if I am wrong) you can use the RUU instead.
I did have a wifi issue which was solved by a factory wipe ( yes I had to re-install and setup the phone again).
-brad
Click to expand...
Click to collapse
Wow, that sounds much simpler, thanks...gonna try that now.

Radio
Any chance someone can please post a flashable zip with the new t-mo radio?

Where would I get the stock recovery for this fw and update. I want to root but keep my ota

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

[SOLVED] chinese variant to Global NEED HELP!!!

Hi!
i installed the global rom via TWRP recovery
now when i try to set up new device all i get is chinese region
Then i hit next and started looping for some reason and message showing "Find Device Automatically Closed"
After multiple loops it restarts and the TWRP is gone
i tried multiple Roms all the same
if anyone has a clue please help
The solution : use MiFlash not TWRP and careful just flash not flash and lock you might get into a bootloop if you made that mistake just like i did don't panic use Mi Unlock
After it reboots setup your device say goodbye to Chinese bloatware.
Thx @nhtnokia

Flash cust.img or use MiFlash to flash stock ROM.

nhtnokia said:
Flash cust.img or use MiFlash to flash stock ROM.
Click to expand...
Click to collapse
I cant find firmware .img i only found Tgz file type
i have done a backup before flashing i get file types .win001.sha2

faroukxda said:
I cant find firmware .img i only found Tgz file type
i have done a backup before flashing i get file types .win001.sha2
Click to expand...
Click to collapse
I think you should use MiFlash to change from CHINA to the GLOBAL version.

nhtnokia said:
Flash cust.img or use MiFlash to flash stock ROM.
Click to expand...
Click to collapse
nhtnokia said:
I think you should use MiFlash to change from CHINA to the GLOBAL version.
Click to expand...
Click to collapse
i think i screwed up very bad. i flashed and locked with miflash now it goes directly to recovery
saying miui vesion isn't supported
is there any way that i can reflash a locked device to stock firmware " Hard Reset" ?

faroukxda said:
i think i screwed up very bad. i flashed and locked with miflash now it goes directly to recovery
saying miui vesion isn't supported
is there any way that i can reflash a locked device to stock firmware " Hard Reset" ?
Click to expand...
Click to collapse
If your bootloader is still unlocked. I can help you. Let's inbox me.

nhtnokia said:
If your bootloader is still unlocked. I can help you. Let's inbox me.
Click to expand...
Click to collapse
check DM

Question Going back to CN Rom from Global

hey guys, successfully flashed the global rom over my redmagic 6 pro CN version but decided to go back to the CN rom, but when I try to install it via local update it results in a recovery boot loop and the only option is to do a factory reset, but when I do a factory reset, for some reason it goes back to the Global Rom. Any tips on what I need to do? thanks

auerick said:
hey guys, successfully flashed the global rom over my redmagic 6 pro CN version but decided to go back to the CN rom, but when I try to install it via local update it results in a recovery boot loop and the only option is to do a factory reset, but when I do a factory reset, for some reason it goes back to the Global Rom. Any tips on what I need to do? thanks
Click to expand...
Click to collapse
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.

bob24260 said:
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.
Click to expand...
Click to collapse
I actually tried that but then it get's stuck on the Nubia logo, so something must have gone wrong somewhere, and one odd thing is if I try installing the latest V2.63 CN rom via local update it tells me that the package is not compatible with the phone. At least the Redmagic 5G had the local update option on its recovery. Nothing at all on the Redmagic 6 Pro. Isn't recovery.img included in the payload.bin? doesn't seem to be there when I dumped the payload

auerick said:
hey guys, successfully flashed the global rom over my redmagic 6 pro CN version but decided to go back to the CN rom, but when I try to install it via local update it results in a recovery boot loop and the only option is to do a factory reset, but when I do a factory reset, for some reason it goes back to the Global Rom. Any tips on what I need to do? thanks
Click to expand...
Click to collapse
Hi there, can you describe the whole steps to flash your RM6 pro from CN to global?
Which rom did you use? EU or non-EU?
Thanks for the reply.

cannon3025 said:
Hi there, can you describe the whole steps to flash your RM6 pro from CN to global?
Which rom did you use? EU or non-EU?
Thanks for the reply.
Click to expand...
Click to collapse
I installed both just to see if I cam go back to CN rom once I'm on either Rom
Basically just downloaded the Global ROM file from the Nubia website, put it on my phones root folder, then did a local update, using the system update local update setting

auerick said:
I actually tried that but then it get's stuck on the Nubia logo, so something must have gone wrong somewhere, and one odd thing is if I try installing the latest V2.63 CN rom via local update it tells me that the package is not compatible with the phone. At least the Redmagic 5G had the local update option on its recovery. Nothing at all on the Redmagic 6 Pro. Isn't recovery.img included in the payload.bin? doesn't seem to be there when I dumped the payload
Click to expand...
Click to collapse
I believe the recovery is part of the boot image now. I've dumped the payload too and I'll have a quick look and see if it's present. I have all the files for the US, global version. It's 4.1.2 I believe. I'll be happy to help any way I can. I just had a bad experience today... I've had my 6 Pro a week and already the cord has quit working. Not a good sign. I'm starting to regret my purchase.

auerick said:
I actually tried that but then it get's stuck on the Nubia logo, so something must have gone wrong somewhere, and one odd thing is if I try installing the latest V2.63 CN rom via local update it tells me that the package is not compatible with the phone. At least the Redmagic 5G had the local update option on its recovery. Nothing at all on the Redmagic 6 Pro. Isn't recovery.img included in the payload.bin? doesn't seem to be there when I dumped the payload
Click to expand...
Click to collapse
I checked and sure enough no recovery image. Pretty sure it's baked into the boot image. Perhaps try the 4.1.2 boot image? That may boot it. Seems like you've rebranded it global version by flashing the global rom. That's a possibility anyways

bob24260 said:
I checked and sure enough no recovery image. Pretty sure it's baked into the boot image. Perhaps try the 4.1.2 boot image? That may boot it. Seems like you've rebranded it global version by flashing the global rom. That's a possibility anyways
Click to expand...
Click to collapse
ok I'll try to play around with it, won't flashing the 4.1.2 boot.img cause a brick?

auerick said:
ok I'll try to play around with it, won't flashing the 4.1.2 boot.img cause a brick?
Click to expand...
Click to collapse
Shouldn't cause a brick. If you've already flashed global before there shouldn't be any problem. But to be sure instead of flashing just fastboot boot the image.
Fastboot boot boot.img
This will allow you the luxury of trying it without actually flashing it. If it hangs up simply reboot by holding power.

bob24260 said:
Shouldn't cause a brick. If you've already flashed global before there shouldn't be any problem. But to be sure instead of flashing just fastboot boot the image.
Fastboot boot boot.img
This will allow you the luxury of trying it without actually flashing it. If it hangs up simply reboot by holding power.
Click to expand...
Click to collapse
cool didn't know I could do that, thanks for the tip

bob24260 said:
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.
Click to expand...
Click to collapse
i tried this and it work but i forgot to wipe ..now i cant save images, files etc. but it doesnt matter.. anyway can you plese tell me how to relock my bootloader? some commands i think? im not familiar with relocking ..only unlocking xD this is my first time relocking bootloader

kittyshik said:
i tried this and it work but i forgot to wipe ..now i cant save images, files etc. but it doesnt matter.. anyway can you plese tell me how to relock my bootloader? some commands i think? im not familiar with relocking ..only unlocking xD this is my first time relocking bootloader
Click to expand...
Click to collapse
fastboot flashing lock
though this will prompt another factory reset

auerick said:
fastboot flashing lock
though this will prompt another factory reset
Click to expand...
Click to collapse
thanks man appreciated!

where did you get the CN rom? can you share here?

here bro https://ui.nubia.cn/rom/detail/68

kittyshik said:
here bro https://ui.nubia.cn/rom/detail/68
Click to expand...
Click to collapse
thanks

Hello what are the steps and commands to go back to the CN rom? I cannot get it from all your comments here :'(

bob24260 said:
Personally what I would do is extract the boot image from the CN rom zip and fastboot flash it after you flash the CN rom via local update. You will have to be bootloader unlocked of course. You can always relock after you've got the CN rom up and running.
Click to expand...
Click to collapse
hmm i tried this method, it seems like my phone just went back to global rom even after cn boot image flashed

China rom is faster than global

Question Locked bootloader while in download mode boot loop

Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks

Am i doomed?

cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country

BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.

cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL

cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...

BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.

cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.

BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch

BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.

cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.

BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened

cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.

BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO

cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces

BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated

Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.

cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.