[Q] help after downgrade(solved) - Sony Xperia T, TL, TX, V

I downgraded to 303 uk to root, but after OTA I get stuck on a recovery screen with a toolbox and warning triangle on.
I have tried leaving it it just continually reboots.
phone was on uk EE 195 fw, it is bootloader locked, and not allowed.
PCCompanion does not fix it or flashing the ftf made of my original 195 update, seems the ee fw didn't allow OTA.
Any Ideas before my battery dies?
wowser it took 35 for the ota to complete.......
all sorted now

Related

[Q] .257 OTA upgrade fails

Hi everyone,
Today, the 14.1.G.2.257 OTA update was finally available here in France. However, when I try to install it, after a short moment with Budroid and a progress bar that doesn't reach the end, the phone reboots and a message saying the update failed appears.
There is ROM available that suits me, so I want to make this work.
I'm running a stock 14.1.G.1.534 for C6903, rooted with vRoot, and debloated a little. I also have the dual recovery, and my bootloader is still locked.
Thanks for reading !
had the same today was on ee 534 in the uk & had ota update note and fail. so flashed generic uk 534 in flashtool & unticked wipe options except cache then re-rooted with kingo & then got update via ota again & now have 257 with root. onlt takes about 20 minutes. hope this helps
Tested and approuved with generic Fr 534.
Thanks a lot !

Do I need to upgrade to 23.4.A.1.232 to be able to upgrade to 264?

So, I'm on 23.4.A.1.200 firmware (non rooted, bought outright from Optus in Australia).
I currently have a notification to upgrade to 23.4.A.1.232 (have had it for a little while actually).
Do I need to upgrade my phone to 232 firmware first to then receive the notification to upgrade to 264 firmware? Or will I eventually receive a notification to upgrade to 264 if I just wait a while?
You need to upgrade to 232 and then 264 - unless you do it from the computer / flashtool

How do I reflash stock firmware?

I'm on L09C09B361 (unlocked bootloader). I've went back to stock recovery and I'm trying to flash update_data_full_p4_pl.zip via dload; it flashes in few seconds (goes from 5% to 99% and it's done), but I still don't have the apps.
How do I reflash the stock ROM (I have both update.zip and update_data.zip).
Thanks.
Anyone? :/
I have tried Huawei Updater 2.0 and Firmware Finder DNS, doesn't work.
Locked bootloader, unlocked bootloader - doesn't matter.
HiSuite complains about internet connection when using any of these.
Hello,
A few days ago I managed to change the rom on my Huawei P9 from c150b367 (Telekom Hungary) to c432b386 (general European). I could find the oeminfoc432.zip on the internet.
If I wanted to go back to c150 (telekom), where can I fownload the oeminfo c150.zip file from?
Thanks in advance for your help.

[Q] LOCK BOOTLOADER on OREO (not relock)

Hello,
I was on B360 Oreo.
I unlocked bootloader, flashed TWRP, used MAGISK (16) to modify boot(ramdisk) partition, flashed it and got ROOT.
Then I flashed HYPER KERNEL.
Now i realised that custom kernel gives me nothing special in term of battery life (after 7 days) so i flashed back all stock partitions (BOOT, RECOVERY, KERNEL).
Now I am on stock, but with bootloader unlocked.
So i can get updates, but no ANDROID PAY.
The TASK is: How to lock bootloader. I mean LOCK not RELOCK.
ON nougat when i used the HWOTA to debrand my device the device was automatically locked after the change.
Now on HWOTA8 i flashed all three parts of the B360 full ota to get the bootloader locked, but still unlocked.
I think to erase and flash OEMINFO again, but i am afraid to brick the device by that.
Does anybody know how to make forced update that the bootloader will lock?
@Blackball maybe?
Actually the only way i discover to do this is, go Back to nougat, and the update vía firmware Finder vía proxy while you had your bootloader locked after rebranding again, Cheers brother
will try to update via firmware finder from b360 to b365 full firmware. Will see.
How this went for You?

Mate 10 Pro Unable to update firmware OTA or using eRecovery / FunkyHuawei

Hi
I'm unable to change the firmware on my BLA-L29 C432 B142 May security patch (rebranded from C636 about 6 months ago).
Checking OTA just says 'no updates available' and if I try to update via FunkyHuawei using eRecovery it downloads but after 'verifying' it moves on to 'recovery system running' and then errors with the message 'recovery failed' when it gets to 1%.
I've tried quite a few things to try and get something to move on, but it seems like I'm stuck on an old version of firmware and no way to change it. I need a new plan.
I've tried (with lots of factory resets and wiping cache inbetween):
- OTA updates - always says no update available.
- Via FunkyHuawei:
- Reflash same firmware (eRecovery fails during 'recovery system running')
- Reflash newer or older firmare in same region (eRecovery fails during 'recovery system running')
- Change region, reflash newer or older firmware in same region (eRecovery fails during 'recovery system running')
- Use unbrick tool to flash same or different firmware in both same and different regions (unbrick tool completes but firmware version always stays the same in about phone, the android security patch date changes though, but eRecovery won't let me reflash anything afterwards as eRecovery fails during 'recovery system running')
- The last OTA update I got was C432 .137. When everyone else was getting .145 OTA I got Firmware Finder to move me from .137 to .142.
Has anyone got any ideas on what to do next? I don't want to be stuck on the same firmware version and security patch forever.
Other than the FunkyHuawei rebrand about 6 months ago from C636 to C432, the phone is standard (no attempt to unlock bootloader, root).
I was thinking of:
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
- Flash TWRP
- Flash a custom ROM
- Try and restore back to stock
- Possibly rebrand back to factory original C636 as there seem to be a few threads about rebranded phones not getting updates promptly, but I can't see anyone else who is getting eRecovery failing no matter what they do and no way to change firmware. I have already tried rebranding back to C636 via FH, but can't, as eRecovery fails at the same point when trying to flash the C636 firmware.
Funky should always work to update, check that DNS is correct when you enter that test site.
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
Click to expand...
Click to collapse
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
ante0 said:
Funky should always work to update, check that DNS is correct when you enter that test site.
Click to expand...
Click to collapse
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
ante0 said:
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
Click to expand...
Click to collapse
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Thasscas44 said:
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Click to expand...
Click to collapse
HuRUpdater can only handle same region updates as far as I know.
You can use HWOTA to rebrand, but mankindtw (original author) has since edited the thread as he thought his tool bricked devices. But it was firmware that caused it.
And I can't remember the exact steps... You have to flash twice though, first to rebrand (example C636) and then to update to the same rebranded (C636) firmware.
https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
You could use FHRebrand tool, but it will change your bootloader unlock code so you'd have to use HCU client (DC-unlocker) twice to get it.
Also, before flashing anything, check xloader with this tool: https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
For now, stay on XLOADER 01 firmware. We don't know if Huawei will change to 02. Going from 02 to 01 will end in a hard brick.
B142 is 01 so you're safe now
Thanks to your advice, I have a plan now. And good to know about the xloader stuff, that could have ruined my day.
I'm going to:
1. Get bootloader code [update: done using dc-unlocker, confirmed working on C432 .142]
2. Flash TWRP
3. Put same region and slightly downgraded version of firmware on to a USB and flash with HuRUpdater (assuming it needs to be put on a USB OTG stick as the M10Pro doesn't have an SD card). I intend to use the downgraded version so I can see the version successfully change in "about phone"
4. Rebrand using FH tool (if there's less chance of bricking than HWOTA) and keeping an older firmware
5. Hopefully it works, and [after getting the bootloader code again from dc-unlocker in case I need it in future] I will be able to update via OTA to latest official firmware
Hopefully starting again completely will overwrite whatever it is that's getting me stuck.
Thanks to @ante0 I got out of the hole I was in.
From what I've tested, there seems to be an inability to update OTA from a rebranded BLA-L29 432 running 137 or 142.
Here's what I did.
1. Unlocked bootloader, flashed twrp, flashed downgraded 137 version of C432 with hrupdater. Success. No offer of an OTA update though so still stuck on old version.
2. Ran FH rebrand tool to change region to the factory original C636. eRecovery failed at the same stage as before. Fail.
3. Kept region as C636, unlocked bootloader and flashed twrp again. Flashed April version of C636 firmware using hrupdater, twice. Success.
4. Immediately on boot up phone offered to update OTA to the latest version of C636 firmware. Success.
It seems that the phone wouldn't offer an update OTA if on rebranded C432 and running 137 or later, but did offer OTA when it was back on C636. I live in Europe, but will keep the 636 region if it means I get OTA, else I can't pass the phone on.
Now to relock the bootloader so banking apps work. Plan to use the fastboot relock command followed by dc unlocker relock tool. Hoping not to brick at the last stage!

Categories

Resources