Database Develop

CyanogenMod Problem

I flashed my phone with CyanogenMod13, completely not knowing what I was doing. I realized there were a few bugs on CM13 like my camera not working and things like that so I want to go back to stock Marshmallow 6.0.1 so I can have FOTA and a fully functioning phone. I know it was pretty silly of me to actually attempt this without consideration but could anyone help me out on getting back?
I have a Z5 Compact E5823.
Thanks.

Just download flashtool, stock firmware and flash it
btw. It's Xperia Z section, not Z5

Thanks man, sorry about the wrong section.
Will I be able to flash stock rom and receive OTA updates? My bootloader is currently unlocked.
I have already tried flashing before and I am getting random errors each time, with all drivers downloaded properly.
I flashed it with Emma last night and it took me to 5.1.1, and I cant receive any updates, so what am I doing wrong?
I want to go back to stock rom with OTA updates, although CyanogenMod13 was great.

MattyCurrann said:
Thanks man, sorry about the wrong section.
Will I be able to flash stock rom and receive OTA updates? My bootloader is currently unlocked.
I have already tried flashing before and I am getting random errors each time, with all drivers downloaded properly.
I flashed it with Emma last night and it took me to 5.1.1, and I cant receive any updates, so what am I doing wrong?
I want to go back to stock rom with OTA updates, although CyanogenMod13 was great.
Click to expand...
Click to collapse
Nope, OTA not working on unlocked bootloader, this can brick your phone

How can I lock my bootloader? Or do you think its recommended I keep the bootloader unlocked?
I just wanted to go back to stock rom for OTA updates thats all.
Many thanks.

MattyCurrann said:
How can I lock my bootloader? Or do you think its recommended I keep the bootloader unlocked?
I just wanted to go back to stock rom for OTA updates thats all.
Many thanks.
Click to expand...
Click to collapse
Do you have TA partition backup? If no, it's not posible to relock bootloader

Kuciak said:
Do you have TA partition backup? If no, it's not posible to relock bootloader
Click to expand...
Click to collapse
I don't even know what that is lol. I should've done research in advance before proceeding to unlock my bootloader. I did make a backup of everything though, I used a tutorial, I used TWRP to backup stuff, or something like that?
Also, is there no way to receive OTA updates now that my bootloader is unlocked? Will flashing stock rom not allow me to receive OTA updates?
Thanks for your ongoing support btw, really stressing me out lol.

Does the latest security patch update stay when you root?

I was wondering what sort of changes take place when you root the G5s Plus. I got several patch updates so far. Will the latest update stay once I root the device? I just want to root the device for now, not install any custom roms.

I received an OTA with an unlocked bootloader so I don't see any reason why you wouldn't with root. This only works with the stock recovery though, if you have TWRP installed I don't think it will work.

William1020000 said:
I received an OTA with an unlocked bootloader so I don't see any reason why you wouldn't with root. This only works with the stock recovery though, if you have TWRP installed I don't think it will work.
Click to expand...
Click to collapse
Rooting involves 3 steps. Unlock bootloader, install TWRP, and install Magisk patch. Just unlocked bootloader doesn't mean phone is rooted.

androidman2018 said:
Rooting involves 3 steps. Unlock bootloader, install TWRP, and install Magisk patch. Just unlocked bootloader doesn't mean phone is rooted.
Click to expand...
Click to collapse
Unlikely that the OTA will install if you have TWRP and Magisk... I wonder if we can still use Flashfire to flash the OTA and keep recovery and root?

Help with up to date guide to Root

Hi,
Can someone concisely give the most up to date instructions on how to root the P20 Pro
Confused because some people talk about debranding first? Is this necessary if you, like me, just have a generic non-network branded phone?
Also.. Does rooting require twrp?
A bit unclear on if I should use the offical or unofficial twrp methods.
And if so does twrp prevent OTA updates? I was lead to believe that any OTA updates would simply wipe any root and you just have to go through the steps again, but would twrp prevent an OTA update in the first place?
What are the best instructions to root the P20 Pro to keep the OTA updates going (even if you need to reroot after each update).
Thanks heaps in getting through the confusion!

Here you have manual to root in simple 4 steps. You need adb and fastboot on your computer, bootloader unlock code and Magisk from link in post
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326

Does any of the steps,
1/ unlocking the bootloader
2/ debranding
3/ installing TWRP
3/ rooting
Wipe the device?.. I'm assuming yes?
Also. What's the point of debranding?..
I think I'm on a generic P20 Pro that wasn't bought from a carrier - so is that step necessary for me.
Thanks heaps again for the advice - coming over from the Samsung world and maybe I'm so used to the rooting methods there

Also do any of those steps prevent OTA updates?
Or is there somehow to still use OTA updates but simply need to reapply root on every occasion there is ah update?

dgoncalves81 said:
Also do any of those steps prevent OTA updates?
Or is there somehow to still use OTA updates but simply need to reapply root on every occasion there is ah update?
Click to expand...
Click to collapse
Unlocking the bootloader will wipe your device. The other steps won't.
You need to have TWRP installed in order to be able to flash Magisk (for Root), and no you don't have to rebrand if you don't want to. You'll still be able to receive and download OTAs but if TWRP remains installed on your phone it won't be able to install unless you change back to the stock recovery. However there is methods to update with TWRP and you'll be able to get and install updates quicker than waiting for them to be pushed to you phone. That's the main reason people rebrand because generic European models are getting updates the fastest.
What's your device model and current firmware version from 'About Phone' in settings?

..

danifilth4king said:
Unlocking the bootloader will wipe your device. The other steps won't.
You need to have TWRP installed in order to be able to flash Magisk (for Root), and no you don't have to rebrand if you don't want to. You'll still be able to receive and download OTAs but if TWRP remains installed on your phone it won't be able to install unless you change back to the stock recovery. However there is methods to update with TWRP and you'll be able to get and install updates quicker than waiting for them to be pushed to you phone. That's the main reason people rebrand because generic European models are getting updates the fastest.
What's your device model and current firmware version from 'About Phone' in settings?
Click to expand...
Click to collapse
Thanks heaps for the advice - makes sense now!
I'm using the model CLT-L29 on C636 which I think is the Asia Pacific model.. And incidentally just received a OTA upgrade to the 128 firmware
.. So in order to receive OTA updates you simply have to change back to the stock recovery after using TWRP to install magisk and root?
But I imagine every time the OTA update occurs it wipes root?.. Which would mean reinstalling TWRP to regain root and doing the whole process again every time?

dgoncalves81 said:
Thanks heaps for the advice - makes sense now!
I'm using the model CLT-L29 on C636 which I think is the Asia Pacific model.. And incidentally just received a OTA upgrade to the 128 firmware
.. So in order to receive OTA updates you simply have to change back to the stock recovery after using TWRP to install magisk and root?
But I imagine every time the OTA update occurs it wipes root?.. Which would mean reinstalling TWRP to regain root and doing the whole process again every time?
Click to expand...
Click to collapse
Yep you got it in one lol
The other option so that you don't have to flash TWRP then back to stock recovery each time is when you receive an OTA is download the same firmware (Full-OTA version) from Firmware Finder - you would just need the update.zip - then using Huawei update extractor you can extract the ramdisk.img Then copy the ramdisk.img to your phone, use Magisk manager to patch it then copy it back to your PC and flash it via fastboot. But I think this is more work than flashing between TWRP & stock recoveries haha

january ota

Hello
I decided to try custom roms because dt2w, its very useful for me but i couldnt get it work on All roms that i tried, so i back to stock rom and locked bootloader..my question is xiaomi removed january Ota? Because before i try custom roms i had it..now after install stock rom it dont detect any Ota. I have only december secury Patch..or i have Ota broken? I flashed stock rom with Xiaomi flash edl mode

luisfontes01 said:
Hello
I decided to try custom roms because dt2w, its very useful for me but i couldnt get it work on All roms that i tried, so i back to stock rom and locked bootloader..my question is xiaomi removed january Ota? Because before i try custom roms i had it..now after install stock rom it dont detect any Ota. I have only december secury Patch..or i have Ota broken? I flashed stock rom with Xiaomi flash edl mode
Click to expand...
Click to collapse
January ota had a serious bug, it caused bootloops on many devices with locked bootloader so they pulled it.
Just wait for february patch and my advice would be to unlock your bootloader now and keep always unlocked

Ok thanks for your advice..i just relock because that annoing message everytime i reboot phone..anywayto remove that warning with bootloader unlocked?

Abrilabr said:
January ota had a serious bug, it caused bootloops on many devices with locked bootloader so they pulled it.
Just wait for february patch and my advice would be to unlock your bootloader now and keep always unlocked
Click to expand...
Click to collapse
I can get ota updates even with the bootloader unlocked? I use stock rom with no root.

luisfontes01 said:
Ok thanks for your advice..i just relock because that annoing message everytime i reboot phone..anywayto remove that warning with bootloader unlocked?
Click to expand...
Click to collapse
No, there is no way to remove that warning.
MartinGJorge said:
I can get ota updates even with the bootloader unlocked? I use stock rom with no root.
Click to expand...
Click to collapse
Yea, ull get ota normally, just dont root and dont touch kernel/system in any way

Prepare to EMUI 10

Comming soon.. maybe this year

il3gal said:
Comming soon.. maybe this year
Click to expand...
Click to collapse
That's old, there's already a B140 build. xD

Pretoriano80 said:
That's old, there's already a B140 build. xD
Click to expand...
Click to collapse
FF is always behind a bit I think, but if it's there it means its coming soon.

Pretoriano80 said:
That's old, there's already a B140 build. xD
Click to expand...
Click to collapse
Looking forward for an update solution from you and ante0.

badmania98 said:
Looking forward for an update solution from you and ante0.
Click to expand...
Click to collapse
All versions of EMUI10 that I've tested so far, force locks bootloader. So don't install if you don't want to get locked. I guess if you have beta access approved you can downgrade back to 9.1 using HiSuite.
I have to downgrade using testpoint
Fastboot will still say you're unlocked but the command fastboot oem lock-state info says it's locked. Downgrading back to 9.1 will give back the unlock status, apparently. I guess they just add something to lock even if you're technically still unlocked. And the command to unlock through fastboot is removed so no way to unlock it again. I hope it's just locking for the beta.

ante0 said:
All versions of EMUI10 that I've tested so far, force locks bootloader. So don't install if you don't want to get locked. I guess if you have beta access approved you can downgrade back to 9.1 using HiSuite.
I have to downgrade using testpoint
Fastboot will still say you're unlocked but the command fastboot oem lock-state info says it's locked. Downgrading back to 9.1 will give back the unlock status, apparently. I guess they just add something to lock even if you're technically still unlocked. And the command to unlock through fastboot is removed so no way to unlock it again. I hope it's just locking for the beta.
Click to expand...
Click to collapse
Maybe it is necessary to downgrade till EMUI 8.0?
I don't have beta access till now. But , as you know, I follow your and Pretoriano80 work very carefully.

badmania98 said:
Looking forward for an update solution from you and ante0.
Click to expand...
Click to collapse
Like @ante0 said in the previous post, we already have the links for the updates, but so far all of them will trigger the bootloader lock, so unless you don't care about it, you should refrain from flashing EMUI10.
If the final release won't change this behavior, then probably Huawei has decided to lock the bootloader for good.

Pretoriano80 said:
Like @ante0 said in the previous post, we already have the links for the updates, but so far all of them will trigger the bootloader lock, so unless you don't care about it, you should refrain from flashing EMUI10.
If the final release won't change this behavior, then probably Huawei has decided to lock the bootloader for good.
Click to expand...
Click to collapse
I prefer to wait. If you 2 will find a good solution to maintain boot-loader unlocked, I will follow it.

badmania98 said:
Maybe it is necessary to downgrade till EMUI 8.0?
I don't have beta access till now. But , as you know, I follow your and Pretoriano80 work very carefully.
Click to expand...
Click to collapse
Downgrade to EMUI 8?
Well, if you do like me you have to as I have to flash board when BL is locked.
If you mean to keep unlock it won't work. Update from Oreo to Q directly will cause problems, it did for me when going Oreo to 9.1 anyway, and system update actually forces you to flash the latest stable 9.0 (9.0.0.197) to update to 9.1.0.300 then to 9.1.0.306.
And it's not like it's using a function to lock BL like they do when you flash a dload firmware. It's probably still unlocked but something changes it to locked. Iirc you could unlock using TP before, but now it refuses as USERLOCK is changed to unlock as well when you use testpoint, so it will just say "Phone is already unlocked", before it only changed FBLOCK to unlock.
But we will see what happens

@ante0 @Pretoriano80 : just in case I would install this beta from FF. What install method I have to use?

badmania98 said:
@[email protected] : just in case I would install this beta from FF. What install method I have to use?
Click to expand...
Click to collapse
Installing with no-check recovery should work just fine, but you should also flash the new CUST and Preload.
If you really want to flash it, i can send you the link with the latest build (B140), but like i said, it will lock your bootloader.

Pretoriano80 said:
Installing with no-check recovery should work just fine, but you should also flash the new CUST and Preload.
If you really want to flash it, i can send you the link with the latest build (B140), but like i said, it will lock your bootloader.
Click to expand...
Click to collapse
Yes, thanks in advance. Also the link for the no-check recovery & tool.
LE. It is from somebody else.

badmania98 said:
Yes, thanks in advance. Also the link for the no-check recovery & tool.
LE. It is from somebody else.
Click to expand...
Click to collapse
It's a BLA-L29 C432 device?

Pretoriano80 said:
It's a BLA-L29 C432 device?
Click to expand...
Click to collapse
Yes.

badmania98 said:
Yes.
Click to expand...
Click to collapse
You can use the 3 files tool (skip the rooting part, of course) from here -> https://forum.xda-developers.com/mate-10/how-to/tool-emui-9-0-to-9-1-upgrade-tool-t3949867 <- and replace the nocheck.img with the one from here (tge no verification version) - > https://forum.xda-developers.com/mate-10/development/recovery-nocheck-pie-t3950037
Make sure that the downloaded firmwares are not corrupt, otherwise the installation may fail, because the no-check recovery will skip the integrity check.
I will send you the update files in PM.

i'd like to have a link for the update files aswell please, on firmware finder PC version there's only 10.0.139

vandal4e said:
i'd like to have a link for the update files aswell please, on firmware finder PC version there's only 10.0.139
Click to expand...
Click to collapse
It doesn't really matter. When you flash it you won't be able to flash any newer ones as you won't be unlocked anymore, and can't unlock again either without downgrading back to 9.1.
I would wait until official to see if forced locking remains or not.