Hi,
just to share my experience on the problem I faced while moving to stock ( I know these are my mistakes and anyone can do this so wanted to share just to save other new users)
I was on one of the custom ROM yesterday but due to lag in camera and slight other bugs (or say due to my requirement), I wanted to go back to stock. I had all the files, TWRP backup but as TWRP doesnt work on Android 8.1 for V10 (except BKL-L04), it was much complicated.
While flashing my stock system.img, I didnt realize that I am on magisk and patched_boot.img rather stock (that was my mistake) and just flashed my system.img and then factory reset in stock recovery. My phone booted fine but then no service for SIM cards, checked in about phone and found that I have lost my IMEI. (no other bugs). My bootloader is still unlocked but FRP lock (I did factory reset remember and I had the google account on earlier custom ROM which I did not delete)..
If you come across this situation, you can boot few times but this will remain the same and factory reset will not help. I was unable to flash TWRP to restore my stock backup (android 8.0, TWRP works on this, right) as my FRP was locked. Even enabled google account and factory reset all but no luck. Then, I made another mistake of relocking the bootloader. Once re-locked, It was in bootloop and only fastboot and erecovery was accessible.
I had no other option but to only download the full file in erecovery and boot. It will be a different file which we do not get on firmware finder, in my case, it was BKL-L09C432B160- FULL file. It took me 4 hours to download the 3GB full file (was in office and was unable to connect to office Wi-Fi, no hotspot issue on iOS12 beta, no 4GB SD card or data card which I normally carry with in bag so burrowed a data card and used my sim and downloaded the 3GB file in 4 hours). Once file was downloaded and flashed, all were fine with IMEI and everything stock.
Just wanted to share this experience so that any other noob or new user do not repeat this and get into all these trouble ( I knew that I will be able to revive anyhow as I am familiar with Huawei/honor phones but it may not be the case all the time with you- its just we need patience with this).
You can share your experience if you come across such so that it will be helpful for others.
I will create a guide as well to get back to stock ROM from custom ROM based on my experience (will skip the dload method as it is already covered and I have not tested that on EMUI 8 - have done it more than 100 times on EMUI 3,4,5) .
Thanks for reading.
I don't think you can download full package from erecovery for Indian model.. it gave me some kind of failure error whenever I tried to download
Rommco05 said:
Im curious how u lost IMEI and FRP lock? I flash couple times system.img and then factory reset in stock recovery without issues. Google account doesnt lock FRP no different if u signed in account or not. It is related to OEM in Developer section. I never delete my account, (when I sell my View10 I also dont delete my account just make FR and another person sign in and have FRP unlocked). Sometimes after flashing/Factory reset switch OEM to disabled
Click to expand...
Click to collapse
I did flash system.img on magisk ramdisk that may be the issue here for imei lost or may be i was on b160 before RR but flashed b130 image, anything. When downloaded b160-full in erecovery, all fixed.
Narasimha12 said:
I don't think you can download full package from erecovery for Indian model.. it gave me some kind of failure error whenever I tried to download
Click to expand...
Click to collapse
If firmware is not available then possibly the error. But this should have it and error may be due to anything else corrupted, just a thought
Rommco05 said:
U use some tool/service for send fw to erecovery?
Click to expand...
Click to collapse
Nope. Via erecovery, it automatically downloals the latest one
Rommco05 said:
Interesting, just only Chines models was able install/download fw over erecovery. This is new! Huawei make some changes I think
Click to expand...
Click to collapse
Nope. I ahd the same behavior on my BLN-L22 Honor 6X. Initially it was China variant but post debranding, It was BLN-L22 and I was able to download the firmware via erecovery. Thats the purpose of erecovery, rescue tool
Rommco05 said:
Hmmm, for me never work erecovery maybe I do something wrong. After 6 yeats I swich from Huawei to OnePlus and life so easy
Click to expand...
Click to collapse
I never got updates on my Honor 5C in 2 years. Yesterday afetr trying for 12-14 hours of all trial, I was able to update to Nougat and 3-4 OTA updates together. It was tedious task.
Just did it. Debranded from EU version to India with VOLTE. will post a detailed guide soon. as usual, noob friendly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only bug till now is - I can not unlock my bootloader.
remote: check password failed
shashank1320 said:
Just did it. Debranded from EU version to India with VOLTE. will post a detailed guide soon. as usual, noob friendly.
Click to expand...
Click to collapse
Can the Indian variant be rebranded to the US model?
mondalakash said:
Can the Indian variant be rebranded to the US model?
Click to expand...
Click to collapse
Yes. Need oeminfo and custom bin file. Someone on US version need to share both. I will rest.
shashank1320 said:
Yes. Need oeminfo and custom bin file. Someone on US version need to share both. I will rest.
Click to expand...
Click to collapse
OK waiting for your guide.... So anyone with an US model and twrp can share the required files?
mondalakash said:
OK waiting for your guide.... So anyone with an US model and twrp can share the required files?
Click to expand...
Click to collapse
Yes. I will post that as well.
mondalakash said:
OK waiting for your guide.... So anyone with an US model and twrp can share the required files?
Click to expand...
Click to collapse
Any issue with Indian variant or specific reason if i may ask.
shashank1320 said:
Any issue with Indian variant or specific reason if i may ask.
Click to expand...
Click to collapse
Can't flash roms majority roms support only bkl l04
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
And I don't use volte
mondalakash said:
Can't flash roms majority roms support only bkl l04
Click to expand...
Click to collapse
No thats not true. As far as i seen, official twrp support Android 8.1 and that's for L04 only. But do support other devices with Android 8.
Openkirin ROMs does not support twrp. Which ROM are you trying
shashank1320 said:
No thats not true. As far as i seen, official twrp support Android 8.1 and that's for L04 only. But do support other devices with Android 8.
Openkirin ROMs does not support twrp. Which ROM are you trying
Click to expand...
Click to collapse
Omni du aoscp
Oeminfo can be backed up in twrp or manually copy the file and custom bin under /data to be backed up manually.
Related
I've seen a few questions about downgrading from 6.0.1 to 5.1.1 and that odin won't allow it.
It's because of secure bootloader, that won't allow downgrade of binary version.
I've made a flashable zip for twrp of the latest 5.1.1 released with csc NEE. (because thats my region)
This will leave your current bootloader version and baseband version, compared to the odin file.
I just did some very light debloating of some microsoft crap as far as I can remember. Maybe some google app as well, like hangout.
No root added, no tweaks, just pretty much stock. Edit: Forgot to mention it's deodexed and zipaligned.
Thought I could share it if anyone needs it.
DOWNLOAD AFH:A310F_5.1.1_NEE.zip
MEGA MIRROR:A310F_5.1.1_NEE.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice work! Can you do the same for 6.0.1? Since 7 came out I'm stuck there and can't downgrade.
mcpossity said:
Nice work! Can you do the same for 6.0.1? Since 7 came out I'm stuck there and can't downgrade.
Click to expand...
Click to collapse
Hi, thanks.
Since the last MM update, our bootloader got upgraded to binary 3. Same as Nougat.
It should be possible to downgrade with odin using one of the latest released MM firmwares. One that starts with A310FXXU3.
Don't forget to back up data and factory reset before you do, otherwise you'll probably end up in a bootloop problem.
tys0n said:
Since the last MM update, our bootloader got upgraded to binary 3. Same as Nougat.
It should be possible to downgrade with odin using one of the latest released MM firmwares. One that starts with A310FXXU3.
Click to expand...
Click to collapse
Yeah, I know, but I want to downgrade to an earlier version of 6.0.1 which has still the old bootloader with binary 2...
mcpossity said:
Yeah, I know, but I want to downgrade to an earlier version of 6.0.1 which has still the old bootloader with binary 2...
Click to expand...
Click to collapse
Not possible unless you modify the .tar.md5 by removing the .bin files in it, then tar it up and flash in odin.
The secure bootloader (sboot.bin) won't allow the downgrade of itself. Needs to be left at U3.
Modem (modem.bin) must also be left at U3, because downgrade modem to U2 while keeping the U3 bootloader will leave you with unknown network or IMEI loss untill upgraded again.
Same with cm.bin. It needs to be left at U3 afaik.
tys0n said:
Not possible unless you modify the .tar.md5 by removing the .bin files in it, then tar it up and flash in odin.
Click to expand...
Click to collapse
Thank you, that worked!! I'm surprised myself because I had tried it before with only sboot.bin removed and it had failed. Now the flash went through seamlessly.
tys0n said:
I've seen a few questions about downgrading from 6.0.1 to 5.1.1 and that odin won't allow it.
It's because of secure bootloader, that won't allow downgrade of binary version.
I've made a flashable zip for twrp of the latest 5.1.1 released with csc NEE. (because thats my region)
This will leave your current bootloader version and baseband version, compared to the odin file.
I just did some very light debloating of some microsoft crap as far as I can remember. Maybe some google app as well, like hangout.
No root added, no tweaks, just pretty much stock. Edit: Forgot to mention it's deodexed and zipaligned.
Thought I could share it if anyone needs it.
DOWNLOAD:A310F_5.1.1_NEE.zip
View attachment 4166300View attachment 4166301View attachment 4166302
Click to expand...
Click to collapse
Can you do this for A510F? Please?
Help in A7 (SM-A720F ZTO)
tys0n said:
Not possible unless you modify the .tar.md5 by removing the .bin files in it, then tar it up and flash in odin.
The secure bootloader (sboot.bin) won't allow the downgrade of itself. Needs to be left at U3.
Modem (modem.bin) must also be left at U3, because downgrade modem to U2 while keeping the U3 bootloader will leave you with unknown network or IMEI loss untill upgraded again.
Same with cm.bin. It needs to be left at U3 afaik.
Click to expand...
Click to collapse
I need to do this on an SM-A720F, but I do not know. Could someone do it for me? I am willing to even make a donation through Paypal. :good:
To go by Odin.
In this firmware:
ammobile.com/firmwares /galaxy-a7/SM-A720F/ZTO/download /A720FXXU1APLI/123200/
msoaresantos said:
I need to do this on an SM-A720F, but I do not know. Could someone do it for me? I am willing to even make a donation through Paypal. :good:
To go by Odin.
In this firmware:
ammobile.com/firmwares /galaxy-a7/SM-A720F/ZTO/download /A720FXXU1APLI/123200/
Click to expand...
Click to collapse
Hi. Do you need specificly that firmware or you just want to downgrade from Nougat?
If you need to downgrade from N, here's also a newer 6.0.1 for ZTO, A720FXXU2AQFA which I think should work for downgrade.
http://updato.com/firmware-archive-select-model?record=161D5BBD669011E7963AFA163EE8F90B
tys0n said:
Hi. Do you need specificly that firmware or you just want to downgrade from Nougat?
If you need to downgrade from N, here's also a newer 6.0.1 for ZTO, A720FXXU2AQFA which I think should work for downgrade.
I really need the A720FXXU1APLI firmware!
Thanks !
Click to expand...
Click to collapse
can't flash xposed-v86.1-sdk22-arm64 on my A310F, "ROM A310F_5.1.1_NEE"
please help
qazqaz1970 said:
please help
Click to expand...
Click to collapse
Use arm instead of arm64, and use xposed for samsung by wanam :good:
tys0n said:
Use arm instead of arm64, and use xposed for samsung by wanam :good:
Click to expand...
Click to collapse
xposed-v81.0-sdk22-arm-custom-build-by-wanam work perfect
thank's.
tys0n said:
I've seen a few questions about downgrading from 6.0.1 to 5.1.1 and that odin won't allow it.
It's because of secure bootloader, that won't allow downgrade of binary version.
I've made a flashable zip for twrp of the latest 5.1.1 released with csc NEE. (because thats my region)
This will leave your current bootloader version and baseband version, compared to the odin file.
I just did some very light debloating of some microsoft crap as far as I can remember. Maybe some google app as well, like hangout.
No root added, no tweaks, just pretty much stock. Edit: Forgot to mention it's deodexed and zipaligned.
Thought I could share it if anyone needs it.
DOWNLOAD:A310F_5.1.1_NEE.zip
View attachment 4166300View attachment 4166301View attachment 4166302
Click to expand...
Click to collapse
Many thanks for sharing! I've tested this one as I wanted just to take a deeper look at 5.1.1 on A3 2016 (My phone when unboxed immediately started upgrade to 6.0.1 so I did not have much time to play around with 5.1.1). I am quite surprised with the performance. The 5.1.1 is surely a beastie. Unfortunately I've got used to some Nougat features (reply from notifications, centered lockscreen "big" clock, quite powerful doze mode saving a lot of juice from the battery) and decided to go back to 7 which I use currently as a daily driver.
link update
hi guys please link update 50kb/s :crying: :crying: please plase emergency
French ?
A big thank you for your post and your work. If I put in place your NEE file, would I have the firm in French? It's good with TWRP that we put in place?
I do not understand a word of English and have to go through a translator.
Thanks again
menuisier3 said:
A big thank you for your post and your work. If I put in place your NEE file, would I have the firm in French? It's good with TWRP that we put in place?
I do not understand a word of English and have to go through a translator.
Thanks again
Click to expand...
Click to collapse
Hi. Yes, flash it with twrp. French language should be included.
Added mega mirror. AFH seem to have problems lately.
Hi!
Thanks a lot for this stock rom!
The battery life and speed it's better than nougat.
But I have a question, can you make the same stock rom based on 6.0.1?
I don't have a PC to extract a rom from firmware, and I searched a lot a flashable stock 6.0.1.
Sorry for my bad english and thanks again!
help!! help!!
Can you do for the A710f? Please??
Hi In this Guide I am going to show a way to update Emui 8.x to Emui 9.x using Firmware Finder
It can be used on locked and unlocked Bootloader.
Data mostly wont be erased but will be erased in some cases where stock system is tampered earlier.
It may or may not lock your Bootloader.
For this you need to install Firmware Finder app ( https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder ) on your device , original thread for the app ( https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/ )
Note 1:
This method requires latest EMUI 8.X available for your device. If you are not on the latest update repeat the below steps to install latest EMUI 8.x for your device.
Note 2: This process is safe to proceed if you have selected correct firmware for your device , If you try to flash wrong firmware and bricked your device I wont be responsible for it.
Steps to Update :
1. Install Firmware Finder App ( https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder)
2. Select your Device in the App
3. Check the list of available firmwares
4. If you are not on the latest EMUI 8.x firmware then you need to install it
5. Select the next update iteration for your device
6. Check whether the update is approved your IMEI or not if check step 11 below
7. If the update is approved Get an update through eRecovery (Note that for this method you have to change DNS in your Router)
8. Click On Next and copy DNS address from the App
9. Change DNS in the Router and reboot your Router (Check whether DNS is configured properly or not by clicking this URL http://query.hicloud.com/checkConnect.action if you get 404 then its not configured properly)
10. Now click on the check availablitiy if not yet approved check next step
11. There is a option for Register update in the screen now click on register update and click next here your IP will be registered for sending the update
12. Now connect your device to charger and reboot into eRecovery by pressing Volume+ button
13. Once its rebooted cleck on the option Download latest version and recovery
14. On Next step Download and recovery
15. It will search for WiFi and will list the available WiFi , select the WiFi which you used to register your IP in step 11
16. It will proceed to download the select firmware once it done it will Reboot.
https://imgur.com/a/r28YKbx
https://imgur.com/a/MyL4Gew
Screenshots for the steps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Repeat the process till you are on the latest version of EMUI 8.x once its done you can Install EMUI 9.x
If it helps Donate to Huawei Firmware Finder (Team MT) and Thank them.
If this steps are helpful thank and rate this thread.
Thanks for the guide Unfortunately i am already on EMUI 9.0 beta for view 10. So won't be able to switch to EMUI 9.0 stable which appears on Firmware Finder through the method. But looks like a neat trick. <Thumbs up>.
Btw, totally out of topic question (answer if anyone knows) - if i select the option 'download latest version and recovery' under eRecovery; will it wipe my data? I know wipe data/factory reset option will do that. But will this option do the same? just curious.
kavee.gauravjoshi said:
Thanks for the guide Unfortunately i am already on EMUI 9.0 beta for view 10. So won't be able to switch to EMUI 9.0 stable which appears on Firmware Finder through the method. But looks like a neat trick. <Thumbs up>.
Btw, totally out of topic question (answer if anyone knows) - if i select the option 'download latest version and recovery' under eRecovery; will it wipe my data? I know wipe data/factory reset option will do that. But will this option do the same? just curious.
Click to expand...
Click to collapse
Depends upon the package downloaded if its a downgrade package it will wipe the data if its the same installed package it mostly wont but we cant guarantee what happens depends on the amount of modifications you made to your device.
miststudent2011 said:
Depends upon the package downloaded if its a downgrade package it will wipe the data if its the same installed package it mostly wont but we cant guarantee what happens depends on the amount of modifications you made to your device.
Click to expand...
Click to collapse
Thanks. Will experiment with it once i take backup. Cheers
kavee.gauravjoshi said:
Thanks for the guide Unfortunately i am already on EMUI 9.0 beta for view 10. So won't be able to switch to EMUI 9.0 stable which appears on Firmware Finder through the method. But looks like a neat trick. <Thumbs up>.
Click to expand...
Click to collapse
Is your phone model BKL-L09 (C432)? If so, you can use this to update from EMUI 9 beta to non-beta.
Smaehtin said:
Is your phone model BKL-L09 (C432)? If so, you can use this to update from EMUI 9 beta to non-beta.
Click to expand...
Click to collapse
I have already checked your post. But unfortunately I have BKL-L09 (C675) Indian one
But correct me if I am wrong, won't your method work for C675 too? I mean EU version = Global version, isn't it?
kavee.gauravjoshi said:
I have already checked your post. But unfortunately I have BKL-L09 (C675) Indian one
But correct me if I am wrong, won't your method work for C675 too? I mean EU version = Global version, isn't it?
Click to expand...
Click to collapse
It will probably work fine, but I don't think it's a good idea since it will rebrand your phone to the C432 variant, I believe. But if you check my thread, I've posted a version that should work for the Indian C675 version, feel free to give it a try
Oh. I couldn't find a version for Indian C675 in your thread. all the versions were for EU version. may be i am going blind. Haha. Anyway, i will check on desktop tonight. Currently accessing XDA on mobile. Thanks mate
kavee.gauravjoshi said:
Oh. I couldn't find a version for Indian C675 in your thread. all the versions were for EU version. may be i am going blind. Haha. Anyway, i will check on desktop tonight. Currently accessing XDA on mobile. Thanks mate
Click to expand...
Click to collapse
Second post, I added it just after you mentioned you were using the C675 variant, https://forum.xda-developers.com/showpost.php?p=78557687&postcount=2
kavee.gauravjoshi said:
Oh. I couldn't find a version for Indian C675 in your thread. all the versions were for EU version. may be i am going blind. Haha. Anyway, i will check on desktop tonight. Currently accessing XDA on mobile. Thanks mate
Click to expand...
Click to collapse
Bro,
Did u update the mobile using this method and successful?. please enlighten us how to install 9.0
Followed the guide from Firmware Finder yesterday. Updated from Oreo B157 to Pie B161 on a Mate 10 Pro BLA-L09. Worked like a charm. Just make sure you selected the correct update package.
atf2m4 said:
Bro,
Did u update the mobile using this method and successful?. please enlighten us how to install 9.0
Click to expand...
Click to collapse
The Firmware Finder solution doesn't work for me, because i am already on EMUI 9.0 Pie Beta. Even though i tried it. it showed the firmware might be removed from server. So didn't go ahead. Other method didn't work for me, might be because of the same reason.
kavee.gauravjoshi said:
The Firmware Finder solution doesn't work for me, because i am already on EMUI 9.0 Pie Beta. Even though i tried it. it showed the firmware might be removed from server. So didn't go ahead. Other method didn't work for me, might be because of the same reason.
Click to expand...
Click to collapse
I think I got a work around for you, just use hisuite in desktop and downgrade your version to EMUI8.x and then try this method but do note that downgrade will format your phone and data will be lost.
miststudent2011 said:
I think I got a work around for you, just use hisuite in desktop and downgrade your version to EMUI8.x and then try this method but do note that downgrade will format your phone and data will be lost.
Click to expand...
Click to collapse
Thanks for the reply. Ya i gave it a thought. But since i am not rooted, can't use Titanium Backup. will have to set up everything from scratch. Don't have that much time. Will wait for few more days for stable release. And if my patience wears off by then, will downgrade and follow this method
kavee.gauravjoshi said:
Thanks for the reply. Ya i gave it a thought. But since i am not rooted, can't use Titanium Backup. will have to set up everything from scratch. Don't have that much time. Will wait for few more days for stable release. And if my patience wears off by then, will downgrade and follow this method
Click to expand...
Click to collapse
No need for TB you can use native Huawei Backup it will even backup app data to.
miststudent2011 said:
No need for TB you can use native Huawei Backup it will even backup app data to.
Click to expand...
Click to collapse
Oh yeah. I saw that option. Sure, will try that. Hopefully i will be able to downgrade to 8.0. last time i couldn't find that option in HiSuit. Will check thoroughly now.
kavee.gauravjoshi said:
Oh yeah. I saw that option. Sure, will try that. Hopefully i will be able to downgrade to 8.0. last time i couldn't find that option in HiSuit. Will check thoroughly now.
Click to expand...
Click to collapse
In latest versions you cant find Downgrade option directly you should keep on trying but there is one older version where there is a direct option.
"Getting Update info failed.. "
Changed DNS and checked hicloud url .. it showed connected to team MT server.
But in recovery it shows above error..
I'm on pie beta and my Friend on V174 Oreo ..
Both showed same error.
What to do.. mean while your second method worked for V174 build. thank you
MidhunUnni said:
"Getting Update info failed.. "
Changed DNS and checked hicloud url .. it showed connected to team MT server.
But in recovery it shows above error..
I'm on pie beta and my Friend on V174 Oreo ..
Both showed same error.
What to do.. mean while your second method worked for V174 build. thank you
Click to expand...
Click to collapse
Firmware finder method only works on emui 8.x it won't work on Emui 9.x
I own the Indian variant of the Honor View 10. I tried the methods as mentioned in your post but everytime it downloads and installs a package which is the same package which i received as an OTA this month. Any helps?\
Thank You.
I have Flashed I4213 Android 10 rom into my I4293 device and this what happened.
Many of you may know that the fact Sony recently released Android 10 official firmware (53.1.A.2.2) for both Xperia 10 and 10 plus. but not all of the devices. I've been using Xperia 10 Plus I4293 Hong Kong variant for few months now. Even though official firmware released my device still haven't got the new update. Last night I've done a little bit experiment. I've downloaded 53.1.A.2.2 (Customized South Africa) firmware from XperiFirm and then done few changes inside the firmware folder. then using Androxyde flashtool created a new bundle for my Xperia 10 Plus I4293. I've renamed it Customized AU - 53.1.A.2.2. To this point I had no idea what's gonna happen next. But I still wanted to flashed it to my device and try it out. And guess what, it's actually worked. As I said before I've used South African firmware for my device. But after I put my sim card it's automatically detected as Australia. Surprisingly there's no country lock in that firmware. But in settings phone model shown as I4213 instead of I4293. Because after I flashed I4213 firmware into my device it's automatically converted it's model number. But as I know I4213 is the 4GB ram variant of the Xperia 10 plus. But in android system it's detect the 6GB ram. And the great thing is all the original Sony apps seems working perfectly, including Album, Camera pretty much everything.
And there was a common screen freeze or non responsive bug in these devices before. And now it's all gone. From my experience so far touch screen and touch responsive much better than before. Even the finger print sensor. seems like they actually fixed the previous bug with this update. I think that's a huge improvement for all these devices. I really want to flash actual Hong Kong version of the firmware to my device. but after couple weeks releasing the firmware for only for few regions, Sony still failing to provide the update for all the models of the same device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[update:25/05/20 Actually the screen freeze issue still not completely gone. I'm still experiencing some of those issues as before as well as occupational ghost touches. But it's a really few amount compared to Android 9. I have no idea what causes that problem. I've even flashed LineageOS before. And yet problem arrived after few days.]
How to do it:
1. Download the I4213 - 53.1.A.2.2 firmware using the Flashtool by Androxye.
2. And also, add this flash script into the firmware folder before you create the bundle.
3. And then close the XperiFirm and click tools-->bundles-->create.
4. On that window, select the downloaded firmware folder, then select the device model you wanted to flash. So you need to select Xperia 10 (I4293) not I4213. [even though you've downloaded I4293 firmware you need to select I4293. Because we're flashing a I4293 device.]
5. On the branding and version tabs just type anything you want. And then select all the firmware files in folder list and click [->] button to add all those files to firmware content section. And click create button. I'll take some time to create the bundle.
6. And then click flash device icon and select flashmode option. you could see your firmware file on flashmode section, under I4293 . And That's pretty much it. And then you can flash the firmware into your device.
*Please be aware the fact that, after flashing this firmware into your device. It'll automatically convert into a I4213 device. But the android software will detect your 6GB ram without any problem. even the IMEI doesn't change. everything will be fine.
** And if Sony releases the firmware for I4293, you can flash those firmware file into your device and convert back to the original model number. And for that just follow the same steps. But for that you need to download I4293 firmware and create a bundle for I4213 and flash it to your device.
***And also as always, please make some backups before doing this.
------------------------------------------------------------------------------------
[update:07/06/20 It's about a month Sony first released their 53.1.A.2.2 firmware for Xperia 10 plus 4GB ram [I4213] version. They included March 2020 android security patch even though, now it's few months older. When you check the security settings on your device you can see it's already outdated. And the irony is I4293 model still haven't got single android 10 update yet. And their security patch already outdated. Honestly Sony has the worst update delivery system ever. But luckily in Android 10 we can install more updated play store security patch.
Someone received the official update on reddit and complained that he can not hear through the earpiece after the update to android 10,only through speaker during a call. Can you confirm that you can make and receive calls?
mathiosn said:
Someone received the official update on reddit and complained that he can not hear through the earpiece after the update to android 10,only through speaker during a call. Can you confirm that you can make and receive calls?
Click to expand...
Click to collapse
No. everything working for me. even ear proximity sensor works just fine. And I just found out that Sony released I4293 China version of the firmware. It's called Customized CN (53.1.A.3.8)
Hi. Me too i want to flash android 10 but still no update for my xperia 10 i4193 hk. I already flashed tw taiwan firmware as it is more updated but still no android 10 update. Im thinking of trying what you did with your 10 plus. But you said on your post you change something in the firmware? Can you confirm that? Is that something like porting the firmware from different region to your i4293? And by the just now there is an update for your device but for china region i4293. The build number is quite different 53.1.a.3.8.
solismartin96 said:
Hi. Me too i want to flash android 10 but still no update for my xperia 10 i4193 hk. I already flashed tw taiwan firmware as it is more updated but still no android 10 update. Im thinking of trying what you did with your 10 plus. But you said on your post you change something in the firmware? Can you confirm that? Is that something like porting the firmware from different region to your i4293? And by the just now there is an update for your device but for china region i4293. The build number is quite different 53.1.a.3.8.
Click to expand...
Click to collapse
I can actually provide you the firmware file I've used to flash. And yes, right now there's 53.1.A.3.8 Which is indeed Chinese market version. We can actually flash that to our device without doing any changes because model number is the same. I'm actually thinking about re-flashing 53.1.A.3.8 version into my device. But I'm still wondering what's different between 53.1.A.3.8 and 53.1.A.2.2.
XOBOT.V2 said:
I can actually provide you the firmware file I've used to flash. And yes, right now there's 53.1.A.3.8 Which is indeed Chinese market version. We can actually flash that to our device without doing any changes because model number is the same. I'm actually thinking about re-flashing 53.1.A.3.8 version into my device. But I'm still wondering what's different between 53.1.A.3.8 and 53.1.A.2.2.
Click to expand...
Click to collapse
yes im also wondering whats the difference. I tried googling but didn't find anything. However for my xperia 10, not 10 plus. I4193 doesnt have china only hk and tw. And still nothing even the 53.1.a.3.8
---------- Post added at 04:57 AM ---------- Previous post was at 04:17 AM ----------
XOBOT.V2 said:
I can actually provide you the firmware file I've used to flash. And yes, right now there's 53.1.A.3.8 Which is indeed Chinese market version. We can actually flash that to our device without doing any changes because model number is the same. I'm actually thinking about re-flashing 53.1.A.3.8 version into my device. But I'm still wondering what's different between 53.1.A.3.8 and 53.1.A.2.2.
Click to expand...
Click to collapse
can you walk me through with the process. I believe its customized za right but in my case it'll be for i4113 to my i4193. What are the tools needed and the instructions. I might flash it if i can no longer wait for hk or tw update. TIA.
solismartin96 said:
yes im also wondering whats the difference. I tried googling but didn't find anything. However for my xperia 10, not 10 plus. I4193 doesnt have china only hk and tw. And still nothing even the 53.1.a.3.8
---------- Post added at 04:57 AM ---------- Previous post was at 04:17 AM ----------
can you walk me through with the process. I believe its customized za right but in my case it'll be for i4113 to my i4193. What are the tools needed and the instructions. I might flash it if i can no longer wait for hk or tw update. TIA.
Click to expand...
Click to collapse
You don't have to change pretty much anything. Just download the firmware using the Flashtool by Androxye. In your case I4113 South African firmware. And then click tools-->bundles-->create. On that window, select the downloaded firmware folder, then select the device model you wanted to flash. So you need to select Xperia 10 (I4193) not I4113. On the branding and version tabs just type anything you want. And then select all the firmware files in folder list and click [->] button. And finally click create button. And then you could see your firmware file on flashmode section. And don't forget to add a flash script into the firmware folder before you create the bundle. That's pretty much it. And then you can flash the firmware into your device.
And also I've found about the 53.1.A.3.8 firmware. Just don't worry about it. It's also Android 10 without google services for china region. They using baidu network instead of google. There's no single google app in that firmware.
XOBOT.V2 said:
You don't have to change pretty much anything. Just download the firmware using the Flashtool by Androxye. In your case I4113 South African firmware. And then click tools-->bundles-->create. On that window, select the downloaded firmware folder, then select the device model you wanted to flash. So you need to select Xperia 10 (I4193) not I4113. On the branding and version tabs just type anything you want. And then select all the firmware files in folder list and click [->] button. And finally click create button. And then you could see your firmware file on flashmode section. And don't forget to add a flash script into the firmware folder before you create the bundle. That's pretty much it. And then you can flash the firmware into your device.
Click to expand...
Click to collapse
nice thank you! I dont know how to add a flash script can you also help me with that. This is flashing through PC right? If still no update I'll do it on weekend.
solismartin96 said:
nice thank you! I dont know how to add a flash script can you also help me with that. This is flashing through PC right? If still no update I'll do it on weekend.
Click to expand...
Click to collapse
Yeah I just checked still nothing. Use this View attachment 53.0.zip flash script. It'll work. just extract the extract the 53.0.fsc file and copy it to your downloaded firmware file before you create a bundle. And yes, this flashing with the PC.
XOBOT.V2 said:
Yeah I just checked still nothing. Use this View attachment 5023353 flash script. It'll work. just extract the extract the 53.0.fsc file and copy it to your downloaded firmware file before you create a bundle. And yes, this flashing with the PC.
Click to expand...
Click to collapse
it worked! I was able to flash android 10 53.1.a.2.2 of i4113 to my i4193 and it works fine. Thanks for your help. I would say this should have its own thread on xperia 10 thanks again!
Yeah no worries, man. If you wanna post a thread about it on Xperia 10 section just go ahead.
Hello, I also use I4293(CDA 1318-2077)
If flash to I4213(53.1.A.2.2), what file do I need to change?
Akizora980 said:
Hello, I also use I4293(CDA 1318-2077)
If flash to I4213(53.1.A.2.2), what file do I need to change?
Click to expand...
Click to collapse
Hey, I just added a step by step guide in to the original post. just refer it.
XOBOT.V2 said:
Hey, I just added a step by step guide in to the original post. just refer it.
Click to expand...
Click to collapse
thank you very much :fingers-crossed:
ありがサンキュー
Akizora980 said:
thank you very much :fingers-crossed:
ありがサンキュー
Click to expand...
Click to collapse
Yeah no worries, glad to help.
Ram Usage
Hello,there
Nicely done on flashing another rom to your phone! I've done this with newflasher (not recommended btw).
Can I ask, did you actually get to unlock 2G of Ram(like some PC Graphics cards with bios mods) or is it just written there because of the model?
Thanks!
XOBOT.V2 said:
Yeah no worries, glad to help.
Click to expand...
Click to collapse
I used newflasher keep the user data flashing
she very good
Akizora980 said:
I used newflasher keep the user data flashing
she very good
Click to expand...
Click to collapse
Awesome. have you got any issues after flashing?
JohnKaraz said:
Hello,there
Nicely done on flashing another rom to your phone! I've done this with newflasher (not recommended btw).
Can I ask, did you actually get to unlock 2G of Ram(like some PC Graphics cards with bios mods) or is it just written there because of the model?
Thanks!
Click to expand...
Click to collapse
Are you crazy? how that even possible in mobile phones? It's obviously because of the phone model. my device is I4293 HK 6GB ram version. that's why. my point is even though you've flashed different model, software recognize the full ram capacity.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP RECOVERY FOR REALME 6/7/Narzo 30
RUI 2.0 ANDROID 11
by albatron34000
Build Type: test - unofficial
Build notes:
- This release has been tested only on Realme7, Narzo 30
Install:
- Flash with fastboot (no vbmeta flash needed)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot recovery.
Credits :
- @HemanthJabalpuri, @dude_exe : for helping to build dt and build recovery.
- @pero_AF : for testing and reports.
for bugs : tell me.
Download : https://drive.google.com/file/d/1kRW11lYJJzSsOVNebf6eEb4c7rNuvtFo/view?usp=sharing
Link is borken, It says file expired
worked bro
This works too for RMX2151 - RUI 1.0 - A10?
Answer: Yes.
this is better TWRP unofficial build from Gofaraway. decryption works, not laggy
telegram link: https://t.me/realme_6_gofaraway/34782
immns said:
this is better TWRP unofficial build from Gofaraway. decryption works, not laggy
telegram link: https://t.me/realme_6_gofaraway/34782
Click to expand...
Click to collapse
when i try booting it, the phone just hangs and reboots into system after a while
jakaco said:
when i try booting it, the phone just hangs and reboots into system after a while
Click to expand...
Click to collapse
what device are u using? what method did u use for entering recovery? volume down + power won't work anymore on rui2 please use reboot recovery or some third party rebooter app on playstore. I can confirm that file is working on my Realme 7 rmx2151 runing RealmeUI 2.0 C.15 (see attachment, its fresh downloaded from xda, i guess it's not corrupted)
immns said:
what device are u using? what method did u use for entering recovery? volume down + power won't work anymore on rui2 please use reboot recovery or some third party rebooter app on playstore. I can confirm that file is working on my Realme 7 rmx2151 runing RealmeUI 2.0 C.15 (see attachment, its fresh downloaded from xda, i guess it's not corrupted)
Click to expand...
Click to collapse
ohh i thought it would work on rui 1.0 too, do i have to flash stock and update to rui 2.0?
jakaco said:
ohh i thought it would work on rui 1.0 too, do i have to flash stock and update to rui 2.0?
Click to expand...
Click to collapse
oh yes of course. then you can download twrp from it's website. there's official build for realme ui 1 good luck
immns said:
oh yes of course. then you can download twrp from it's website. there's official build for realme ui 1 good luck
Click to expand...
Click to collapse
i flashed rui 1.0 how do i update it to rui 2.0 theres no update in the settings
jakaco said:
i flashed rui 1.0 how do i update it to rui 2.0 theres no update in the settings
Click to expand...
Click to collapse
from my experience simply clear data and cache from com.oppo.ota or changing software region will fix that. but you have to use stock recovery for upgrade i believe
Open the phone app on your device and dial *#3954391#. Then dial *#391#. A screen should come up with a whole bunch of regions listed.... original thread
Click to expand...
Click to collapse
immns said:
from my experience simply clear data and cache from com.oppo.ota or changing software region will fix that. but you have to use stock recovery for upgrade i believe
Click to expand...
Click to collapse
which region should i set?
jakaco said:
which region should i set?
Click to expand...
Click to collapse
it depends. first try your own region then check whether it give you update or not. try india region if the first one fail
immns said:
it depends. first try your own region then check whether it give you update or not. try india region if the first one fail
Click to expand...
Click to collapse
im trying to update to a91 but the updater crashes really soon and doesnt update
jakaco said:
im trying to update to a91 but the updater crashes really soon and doesnt update
Click to expand...
Click to collapse
did u use stock recovery or twrp? i guess twrp on rui1 can't update ota, so you have to use stock recovery. there's also ofp file for a91 out there that you can decrypt and flash it with spflashtool.
immns said:
did u use stock recovery or twrp? i guess twrp on rui1 can't update ota, so you have to use stock recovery. there's also ofp file for a91 out there that you can decrypt and flash it with spflashtool.
Click to expand...
Click to collapse
i successfully updated to a91 but theres still no android 11 update, i also relocked my bootloader
jakaco said:
i successfully updated to a91 but theres still no android 11 update, i also relocked my bootloader
Click to expand...
Click to collapse
just wait for awhile. or change the region again. i think locked or unlocked wont affect software update on this phone, my phone bootloader unlocked since a.71 A10 and now updated to c.15 A11.
immns said:
just wait for awhile. or change the region again. i think locked or unlocked wont affect software update on this phone, my phone bootloader unlocked since a.71 A10 and now updated to c.15 A11.
Click to expand...
Click to collapse
i unlocked my bootloader and it seems like my phone changed back to rmx2155 with the bootloader unlocked, is this significant?, i also changed the region to signapore ex since people seemed to have success with it
jakaco said:
i unlocked my bootloader and it seems like my phone changed back to rmx2155 with the bootloader unlocked, is this significant?, i also changed the region to signapore ex since people seemed to have success with it
Click to expand...
Click to collapse
i believe rmx2155 are europe only, so canging to Singapore region will not work. try other region that still in Europe. or.... if everything seems fail. just flash your phone with spflashtool. here's link for rmx2155 A11 c.15
immns said:
i believe rmx2155 are europe only, so canging to Singapore region will not work. try other region that still in Europe. or.... if everything seems fail. just flash your phone with spflashtool. here's link for rmx2155 A11 c.15
Click to expand...
Click to collapse
i dont know what happened but my region is set to singapore (i even have the theme store) the bootloader is unlocked (which is not possible on rxm2155) im gonna try some stuff with spflashtool
Hello everyone.
I bought a japanese Xperia 1 III (Softbank version A101SO) with Android 12 and I've searched for the 13 update but it turns out Softbank didn't release Android 13 on this phone yet.
So I decided to flash the KDDI version to it (with newflasher) and it worked.
But the problem is I got a very weak signal, a battery drain and the 4G rarely appears (always H or H+)
I tried to come back to the old original firmware but the phone won't boot after the flashing process (rollback protection)
The phone has a locked bootloader and it says it can't be unlocked so I wonder if you have a solution for me because I lost all hope right know.
If I can just go back to its original firmware (Android 12 from Softbank) that's all that I need right know.
Thak you for your answers.
Unless you unlock your bootloader, otherwise, you cannot go back to Android 12 again. If your phone's config name 'Bootloader unlock allow' is No, then you have to stick around with KDDI Android 13 fw.
FiDra said:
Unless you unlock your bootloader, otherwise, you cannot go back to Android 12 again. If your phone's config name 'Bootloader unlock allow' is No, then you have to stick around with KDDI Android 13 fw.
Click to expand...
Click to collapse
Thanks for your reply! I'll have to stick with it then...
But can I flash the Softbank modem to it to have a better signal coverage?
I think cross flashing is okay but you need to do some search to make sure you flash all needed files to prevent boot loop.
FiDra said:
I think cross flashing is okay but you need to do some search to make sure you flash all needed files to prevent boot loop.
Click to expand...
Click to collapse
crossflashing works but the problem is the Signal and the battery drain.
is there a way to flash other modem files to the phone?
Try newflasher, you can search the forum for the guide.
FiDra said:
Try newflasher, you can search the forum for the guide.
Click to expand...
Click to collapse
Newflasher is the tool to flash the roms.
I know how to use it since I've crossflashed my Xperia 1 III with another region FW using it.
My question is: is there a way to flash different modem files (and other important files) to the phone with a different region rom to fix the signal and battery drain issues?
Samuël_Fab said:
Newflasher is the tool to flash the roms.
I know how to use it since I've crossflashed my Xperia 1 III with another region FW using it.
My question is: is there a way to flash different modem files (and other important files) to the phone with a different region rom to fix the signal and battery drain issues?
Click to expand...
Click to collapse
Yes just keep the .Sin files that you fish to flash and remove the rest from the rom folder. And make sure when prompted by Newflasher to "keep user data".
bentree said:
Yes just keep the .Sin files that you fish to flash and remove the rest from the rom folder. And make sure when prompted by Newflasher to "keep user data".
Click to expand...
Click to collapse
ohh! thanks for your tip!
I want to ask you:
do you know the name of the modem files that control the network?
Samuël_Fab said:
ohh! thanks for your tip!
I want to ask you:
do you know the name of the modem files that control the network?
Click to expand...
Click to collapse
Modem.Sin is the file you are after.
bentree said:
Modem.Sin is the file you are after.
Click to expand...
Click to collapse
So I've successfully flashed the modem sin file but there's a problem with the camera.
It refuses to launch and the Telephoto lenses are moving all the time (with the noise of the lens moving).
But the signal is back at 4G.
Samuël_Fab said:
So I've successfully flashed the modem sin file but there's a problem with the camera.
It refuses to launch and the Telephoto lenses are moving all the time (with the noise of the lens moving).
But the signal is back at 4G.
Click to expand...
Click to collapse
no idea with that one... sorry
bentree said:
no idea with that one... sorry
Click to expand...
Click to collapse
I guess flashing it with other modem sin files don't resolve the issue.
I need to wait for the Softbank Android 13 (if it will be released one day...)
Thanks to you and people on this post, I've been able to flash fw 61.1.E.5.215 into my A101SO and fix mobile connection and camera by flash .sin file from A101SO android 12 fw. If you still struggle with the camera, let me know. I've seen improvement with battery life and mobile signal, the only let down is netflix wont install from playstore nor playback at full fidelity if I install with apk
Samuël_Fab said:
I guess flashing it with other modem sin files don't resolve the issue.
I need to wait for the Softbank Android 13 (if it will be released one day...)
Click to expand...
Click to collapse
Bachtran24 said:
Thanks to you and people on this post, I've been able to flash fw 61.1.E.5.215 into my A101SO and fix mobile connection and camera by flash .sin file from A101SO android 12 fw. If you still struggle with the camera, let me know. I've seen improvement with battery life and mobile signal, the only let down is netflix wont install from playstore nor playback at full fidelity if I install with apk
Click to expand...
Click to collapse
what file did you flash for the Camera?
Ainz_Ooal_Gown said:
what file did you flash for the Camera?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I succesfully flashed a bootable fw (XQ-BC72_Customized SEA_61.2.A.0.447 for me), I flash these .sin files from A101SO_SoftBank JP_61.1.E.5.215 right after. The camera problem only rise if you also flash modem_X-FLASH-ALL-4BA8.sin
Bachtran24 said:
View attachment 5922171
After I succesfully flashed a bootable fw (XQ-BC72_Customized SEA_61.2.A.0.447 for me), I flash these .sin files from A101SO_SoftBank JP_61.1.E.5.215 right after. The camera problem only rise if you also flash modem_X-FLASH-ALL-4BA8.sin
Click to expand...
Click to collapse
Hi @Bachtran24 if i understood you correctly then you have installed a Dual XQ-BC72 to your single SIM A101so version and then flashed the modem files and it worked for you?.
Can you please exactly tell which modem files you flashed? in the ROM folder there are 3 modem files.sin.
When you flashed modem.sin filers which ROM folder did you use BC-72 or A101so.
I have the same issues i have updated to global Dual ROM and now my A101so is not getting any signals. looking for your help
crazycolor786 said:
Hi @Bachtran24 if i understood you correctly then you have installed a Dual XQ-BC72 to your single SIM A101so version and then flashed the modem files and it worked for you?.
Can you please exactly tell which modem files you flashed? in the ROM folder there are 3 modem files.sin.
When you flashed modem.sin filers which ROM folder did you use BC-72 or A101so.
I have the same issues i have updated to global Dual ROM and now my A101so is not getting any signals. looking for your help
Click to expand...
Click to collapse
Did you see the picture, just flash those 4 from A101SO_SoftBank JP_61.1.E.5.215 folder, delete other. Reply if you cant see the pic, i'll put it in context
Bachtran24 said:
Did you see the picture, just flash those 4 from A101SO_SoftBank JP_61.1.E.5.215 folder, delete other. Reply if you cant see the pic, i'll put it in context
Click to expand...
Click to collapse
thank you for your reply. i can see the picture and got the answer that i should use A101SO folder for secondary flashing. thanks!