Greetings community I have a big problem with my Z5 Compact E5803.
A couple of months ago I unlocked the Bootloader, I rooted it and never had any problem (I did all this in the version of Android 6.0.1) until I decided to update it by Flashtool to the latest existing version of Nougat (I downloaded the firmware E5803_32. 4.A.1.54_Generic LAM, through XperiFirm).
The fact is that by mistake I included these options in the firmware flash:
{
"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"
}
Now the problem is that I can not flash any kernel to root my phone, since I always get the same message in both Flashtool and Fastboot mode; "FAILED (remote: command not allowed)", I can not unblock or block the bootloader again, my cell phone does not recognize the nano SIM, and the screen freezes when I enter the camera application.
I made several attempts to flash again the firmware I had before flashing Nougat, Marshmallow (32.2.A.0.224_R7C_Latin America Generic_1299-2789.ftf), I tried to block the bootloader by Flashtool and unlock it again, according to the program all right but when reviewing the phone keeps appearing "Rooting status: unknown".
Community, I do not know what else to do, I would be very grateful for a definitive solution, thank you :crying:
PD.: I had posted this before, but I think I did it in the wrong place
I will be attentive to your comments and suggestions community and if the photos are not published in the post I will gladly pass the link :good: where you can see them. Sorry for my bad english
I do not know what you can do now
but I know where you were wrong , you did not have to tick SIMLOCK
Flash lollipop?
mlleemiles said:
Flash lollipop?
Click to expand...
Click to collapse
Yesterday I tried and unfortunately it did not work
Well, flashtool should backup your previous TAs. Find them at C:/user/.flashTool/registeredDevices/serial number/rawta/date.fta
Backup
do not back up with Flashtool but I have a backup made with this tool:
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
I have the file:
TA_E5803_XXXXXXXXXX_xxxxxxxx-xxx.img :victory:
perhaps this helps:
Restoring TA to factory state
https://forum.xda-developers.com/showpost.php?p=74041813&postcount=217
I cannot give any further advice, as I am not aware what the "Misc TA" options actually do. good luck
Related
I have tried both the methods to root my phone...that would be "Root MANY ANDROID"
{
"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"
}
as well as flashtool tutorial of "noob-proof root via Flashtool".
However I still receive error regarding to either driver failure or unable to hack...I have followed all the steps correctly and made sure the drivers are insalled too... you can see that in the attached images...
Suddenly I feel sony made my phone un-hackable or what??
Please advise me...I am sure I am performing some mistake somewhere...I have been watching different threads on this forum for past 2-3 days and still I don't have a solution to this...Please HELP!!!
the images are not clear .... try to flash ur mobile again with stock rom build 6.1.1.B.75 and then try the method of Root Many Android Devices
Thanks for your suggestion
Waledac said:
the images are not clear .... try to flash ur mobile again with stock rom build 6.1.1.B.75 and then try the method of Root Many Android Devices
Click to expand...
Click to collapse
Thanks for your suggestion...however I knew that windows 8 will make some nuissance...so rooted my phone using windows 7 on a virtual pc...however I have a entire different question for you where you can definitely help me understand the method of choosing a custom ROM, Kernel and Bootloader...could you please tell me how the cocktail for this different hardware/software works...I have read the entire description on different threads of what their job is and how they work...however I am still confused with how to mix a ROM, Kernel and a Bootloader..??
I have succesfully rooted my phone right now and would like to know about the next step!!
cyanogen mod roms and the roms based on cm requires unlocked bootloader ; unlocking bootloader will void ur warranty and u will loose drm keys forever
Sent from my Xperia P using xda premium
I held off updating my XZU to 4.3 until root was found, as I don't want to live without it (because of: Titanium backup, VPN software, full linux install on uSD card).
My XZU has an unlocked bootloader, too, as well as being rooted. I'd also modified /system/build.props too.
When I saw the OTA, I tried it and it failed without giving a reason, so I booted up Windows and used Sony PC Companion, and it too failed:
{
"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"
}
I've looked at many XZU update threads and none seem to mention this specific issue.
When the tool runs, it takes a minute to "prepare" (it seems to have kept stuff it downloaded the first time). The phone does stuff, screen goes blank. Then the update fails giving the above message. The phone is then dead, and I have to unplug the USB before I can turn it on.
I restored the standard build.props from a backup copy. Do I need to relock the bootloader? Remove SuperSU and unroot?
Laptop computer has lots of free disk space, and is running standard win7pro-x64, nothing special installed.
thanks for any ideas.
I think that it is the unlocked bootloader?
I just flashed the ce 290 ftf when I had some error in pcc. Might have been the same one.
Rooting is easy on 290 if you have an unlocked bootloader
it's not root, because I unrooted device, so I am guessing its the unlocked bootloader. I've never managed to get Barclays Bank mobile app to work as it complains about phone being rooted, still doesn't work, so it must be detecting the system modified flag (this is using the older version of the app which was happy to run on a fully p0wned Galaxy Note 2).
OK, it was the unlocked bootloader. OTA update now working.
thanks!
Hi everyone, I have the Ulefone Armor X5 2020 version (android 10)with the mt6762 mediatek processor ( description of the seller, the ticket on the box and Ulefone description) this is very confuse why the stock rom for this device is for mt6765 and I read mt6765 with sp flash software.
My problem is what this was bricked from factory, its work unstable and rebooting ramdomly.
I try many things like factory reset, wipe the cache, (when wipe the cache the display show E: Fota installation aborted, E:: No such file or diretory) reflash the stock firmware, reflash preloader and recovery separately, but the problem persist.
And one of the first messages i read was system corrupted.
{
"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"
}
Help me please!!!
Aha! Same fone as mine... Now here's your problem, same as mine, quite simply, android 9 says mt6762, but an upgrade to android 10_q shows mt6765, I now have mine on 10 pro, and it shows mt6762. Now to get out of where you are, you need to grab the firmware for your fone, have adb/fastboot setup, and get ready to restore fone, the fact you can see recovery means it aint that bad... did you fix it?
Pachacouti said:
Aha! Same fone as mine... Now here's your problem, same as mine, quite simply, android 9 says mt6762, but an upgrade to android 10_q shows mt6765, I now have mine on 10 pro, and it shows mt6762. Now to get out of where you are, you need to grab the firmware for your fone, have adb/fastboot setup, and get ready to restore fone, the fact you can see recovery means it aint that bad... did you fix it?
Click to expand...
Click to collapse
Hello, thanks for answering, could you tell me the download link of the firmware that you used to be able to test and see if my phone revives please.
Let me start by saying I am not rooted no twrp just plain stock , with locked bootloader. Also EU version.(V12.0.8.0.QJGEUXM)
A few months ago I downloaded the Android 11 Rom V12.0.6.0.RJGEUXM through the phone even though I am not on any trial program.
It installed easily on my phone , some people have had to use other methods...so I read.
Anyhow , I thought it was way too buggy and needed to downgrade.( Even after the the 2 other upgrades to V12.0.7.0.RJGEUXM. This is what I did to rollback if someone else is in the same boat.
I had to wait 3 days to unlock my bootloader,
Then I used the MiTool to select the ROM I wanted.
The problem then is the bootloader is still unlocked after you flash the new ROM, you need to use ADB command " OEM lock" to relock then phone , it should erase everything then go back stock. I am still learning with this Xiaomi device so I had to learn this from different sources and hope it helps somebody else out.
Soz if this is common knowledge or wrong part of forum!
thanks for the info but why did you downgrade did android 11 lags the phone or what
aymen peter said:
thanks for the info but why did you downgrade did android 11 lags the phone or what
Click to expand...
Click to collapse
1) WiFi issues and random reboots, when the phone booted (on its own accord) on reboot the wi fi took quite a few minutes ( over 5 minutes sometimes longer) to get back online.
2) The speaker volume seemed too quiet for video and calls.(on at full volume most of the time).
3) Not so polished, sometimes would be a bit laggy other times not.
At the minute Android 11 for the Poco is still Beta, I am sure these problems will get resolved. The moral of story ... Wait for OTA instead of forcing updates.
i used xiaomi flash tool to flash fastboot rom and selected this to keep unlocked bootloader
{
"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"
}
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"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"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.