Hi,
some time ago I bought a used Sony Xperia Z5 Compact (E5823).
I am satisfied with the device. After reading the forum to check
thoughts and experiences using phone I realised that the phone
was probably modified.
Phone currently running smoothly without troubles.
The only thing I noticed is, that the updating of FW may not be working.
I don't know exactly how the updating system works. Checking for update
in different environments shows:
- Phone checking for updates
Your device is up to date!
- web page support sonymobile com /gb/xperiaz5compact/software
new update is available "New software update available! 32.2.A.0.224"
- Xperia Companion
Can not check for updates.
I also found that the phone has unlocked bootloader. It is likely that other
things are/were changed too (another rom or any other internal changes).
Now, I have some questions about phone:
- does the phone now have original SW (all of it)
- because of unlocked bootloader
- can I therefore expect any problems
- am I able to update android even to Android 7.0 when it will be available
- as I realized that DRM keys are lost - may this in the future causes any problems
Can anyone check, if currently installed software is regular/original? If it is not, how to
restore it to original state?
Below I enclose a status pages of the software on the phone.
Thank you for answers and explanations
***************
TYPE: PM-0880-BV
MODEL: E5823
Blobs: generic error!
HUK: generic error!
PRODID_AID: 0004
OTP_LOCK_CONFIG: 0155
OTP_LOCK_STATUS: LOCKED
AUTH_ENABLE: 07
FIDO_KEYS: Not provisioned, SUNTORY error
Factory reset reason: No device reset information found.
Phone Software Version: 1295-6639_32.1.A.1.185 GLOBAL-LTE2A - user
File System Version: GENERIC_32.1.A.1.185
S1 Boot Version: 1289-5620 S1_Boot_MSM8994_LA1.2.2_38
ETS Software version: 1295-0132_3
Costumization version: 1298-7782_R9C
Active Customization: 1298-7782_R9C
Memory card: No file found
LTA version: /lta-label/1299-9151_8-elabel-e5823-row.html
Content Version: PA5
Type Number: PM-0880-BV
Touch Firmware Version: 10
Fuel Gauge Firmware version: The phone doesn't support firmware version read
Current Modem Config: /system/etc/customization/modem/amss_fsg_suzuran_tar.mbn
Color ID: 1
Routing status:
Bootloader unlocked: Yes
HW Config rev: HWC_Kitakami_Com_010
Remote Lock State: UnLocked
Security Configuration: Live
Model number: E5823
Android version: 6.0
Android security patch level: 1. februar 2016
Baseband version: 8994-FAAAANAZQ-00033-25
Kernel version: 3.10.84-perf-g19d6d92 [email protected] #1 Mon Jan 25 22:47:42 2016
Build number: 32.1.A.1.185
I ran into the same problem that you have. I bought a Z5 Compact, not knowing that the bootloader was unlocked and the DRM keys were gone forever.
Generally, you can't upgrade the software using the OTA feature if your bootloader is unlocked, but you can very easily download the latest firmware (32.2.A.0.253) through Xperifirm and flash it with Flashtool. You don't even have to wipe data, so it will upgrade you very painlessly. After discovering that my phone's bootloader was unlocked, I used the tool on this page: http://forum.xda-developers.com/xper...el-dm-t3301605 to create a new boot image and kernel that bypasses all of the security settings and installs root. That got my phone right where I wanted it to be. I'll still have to manually upgrade the firmware when it comes out, but it's easy to do.
With flashtool I have relock bootloader. Then I try to upgrade
via Xperia companion and it works. Now it is android 6.0.1.
How it is possible? I didn't root phone or do anything else
just click on relock button.
Can be, that previously owner somehow restored drm
functionality without original drm keys? Can I verify that?
Related
Hello,
probably I did a failure in flashing ROM or Kernel (without SIM Card), and now GSM is not working (tested with two different SIMs / Eplus and t mobile). In Network search I see several provider (Eplus, O2, T-Mobile, Vodafone), but phone is not able to connect suitable provider. Both SIM-Cards work in other phone.
To repair I did following:
- PC Companion Repair - flashed Stock ROM
- SEUS flashed Stock Rom
- Flashing Stock-ROM with bootloader
- Bootloader unlock
- Root again
- Other Kernel /ROMs
All measure without success. Result in all cases were that phone can't log in.
I checked SIMlock Certificate by S1 Tool. Result was (at the moment 2.1.1.Clean.0.0 v6):
S1_EPROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
Model U20i
Software Version: 1235-3411_2.0.a.0.504
Custom Version: 1238-7168_R5B
Serial No. CB511L3PS6
SEMC SIMLOCK CERTIFICATE
Has somebody an idea ?
Regards Odiad
PS: Unfortunately I posted this question before in a wrong segment (Development). Maybe a moderator could be so kind to delete wrong post ? Sorry again..
Try these steps maybe
It includes relocking the bootloader, according to your output from S1tool it is still unlocked...
http://forum.xda-developers.com/showpost.php?p=25120412&postcount=7373
SmG67 said:
It includes relocking the bootloader, according to your output from S1tool it is still unlocked...
http://forum.xda-developers.com/showpost.php?p=25120412&postcount=7373
Click to expand...
Click to collapse
Hi SmG67,
the hint that my phone is still unlocked and the link was very helpful. I flashed Stock ROM again and additional I relocked the bootloader (first I had problems because S1tool version in XDA forum probably is old and had no Relock-button - but after googling I found current version of S1tool) - and thats great - phone works now - I can call again.
Thanks a lot - a phone without calling function is terrible...
Regards Odiad
glad it helped, enjoy your phone
I brought a ASUS Padfone Mini for my friend from Singapore so, I didn't break device pack until arrival to Sri Lanka. After coming to Sri Lanka, I could know it hasn't Google services. So, I try to solve that issue as instructions of many forums.
1. I tried to root it by Kingoroot, Kingroot, RootZenFone -1.4.6 & SuperOneClick etc. but I never root that device.
2. I tried to update WW firmware ( UL-ASUS_T00E-WW-6.5.36.0-user.zip) issued by official web site of ASUS by copying to SD card & SD Download option of Bootloader menu. Then there is a message
FASTBOOT CMD WAITING....
E: No detect /sdcard/ASUS_BUNDLE.zip file!
Installing demo content!!
No detect APD image file skip!
Error: Can't find image file
----------------------------------------------------
ERROR: Can't find image file
3. Also, I tried to upload firmware, CSC_PF400CG_all_TW_engT3.0.1.3.raw & official firmware by ASUS Flash Tool. Then there was a error message as "SKU version is incorrect".
My device details are as follows:
Model: ASUS_T00E
Android Version: 4.4.2
IA Firmware Version: 58.53
Baseband Version: 1446_1.3.47.0_1120
Kernel Version: 3.10.20
Build Number: KVT49L.CN_PadFone-V6.5.36-20141204
How can I solve above issue?
Hello,
I have an xperia m4 aqua (e2306)
Some time ago I unlocked the bootloader to root it using magisk and everything worked perfectly. Today in the morning I wanted to install Pexo Rom, so I blocked the bootloader with flashtool to install the stock room through Xperia Companion.
At the time of unlocking again the bootloader error, I have researched all day and I do not know what could have happened. I opened the dialler and enter the command *#*#7378423#*#* to see what was and said "Bootloader unlock allowed: no" when previously you could unlock it.
Any idea what happened or how to solve it?
Device Info:
Android Version: 6.0.1
Kernel Version: 3.10.49
Build Number: 26.3.A.3.111
Hello all, I'm new to this forum but am very preset on a computer forum I wont mention because I'm not aware of the link rules here.
I purchased a Lenovo Tab 4 10, I enabled OEM Unlocking, Unlocked the Bootloader to root my tablet, and when I booted back into the Android OS it had an update, so I updated it, rebooted, re-enabled Developer Options because it had turned it off after the Android update, now OEM Unlocking is greyed out, I've cleared cache, factory reset it, tried tricking it with dates, waited 10 days to see if there was a lock period, and it's still greyed out, tablet Bootloader now says "LOCKED" and I can not Re-enable OEM Unlocking to unlock my Bootloader again.
I'm Stuck and Any Help or Ideas would be Appreciated, I can find almost nothing on this tablet. so any help is greatly appreciated!
The Specs of my Lenovo Tab4 10 ( this is NOT the Plus or the LTE Version.) are below.
I Thank Everyone For Their Time
Model: Lenovo TB-X304F
Kernel Version: 3.18.71
Build Number: TB-X304F_S001014_181113_row
Hardware Version: Lenovopad TB-X304F
Software Version: TB-X304F_RF01_181113
RAM: 2GB
Storage: 16GB
CPU: Qualcomm Snapdragon 425
Viper_Security said:
Hello all, I'm new to this forum but am very preset on a computer forum I wont mention because I'm not aware of the link rules here.
I purchased a Lenovo Tab 4 10, I enabled OEM Unlocking, Unlocked the Bootloader to root my tablet, and when I booted back into the Android OS it had an update, so I updated it, rebooted, re-enabled Developer Options because it had turned it off after the Android update, now OEM Unlocking is greyed out, I've cleared cache, factory reset it, tried tricking it with dates, waited 10 days to see if there was a lock period, and it's still greyed out, tablet Bootloader now says "LOCKED" and I can not Re-enable OEM Unlocking to unlock my Bootloader again.
I'm Stuck and Any Help or Ideas would be Appreciated, I can find almost nothing on this tablet. so any help is greatly appreciated!
The Specs of my Lenovo Tab4 10 ( this is NOT the Plus or the LTE Version.) are below.
I Thank Everyone For Their Time
Model: Lenovo TB-X304F
Kernel Version: 3.18.71
Build Number: TB-X304F_S001014_181113_row
Hardware Version: Lenovopad TB-X304F
Software Version: TB-X304F_RF01_181113
RAM: 2GB
Storage: 16GB
CPU: Qualcomm Snapdragon 425
Click to expand...
Click to collapse
Welcome to the forums. From my understanding, the OEM unlocking switch is greyed out if the bootloader is already unlocked. But you say it's locked so I'm not sure what happened. I recently just got this tablet a month ago and one of the first things I did was unlock the bootloader. But the other day I saw that it said it was locked in the bootloader so I may be in the same boat. Haven't looked back in settings to see if the switch is greyed out for me or not.
For the future, if you want to stick around here, this tablet doesn't have it's own forum which is kinda of annoying. But owners of these tablets seem to all be posting in the Lenovo Thinkpad forum. Here's a link to one of the threads for this tablet. Maybe ask in there.
https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
One question. Was this update something that came out recently? Someone else said they had an update yesterday for another version of the tablet and was wondering if the Wifi only version had one too. I'm currently not near my tablet to check
There is No update unfortunately for me. due to the lack of support with this product I am going to buy a Dragon Touch 10.6" tablet because there seems to be more people that have tested this than my Tab4 10. thank you for your time.
Viper_Security said:
Hello all, I'm new to this forum but am very preset on a computer forum I wont mention because I'm not aware of the link rules here.
I purchased a Lenovo Tab 4 10, I enabled OEM Unlocking, Unlocked the Bootloader to root my tablet, and when I booted back into the Android OS it had an update, so I updated it, rebooted, re-enabled Developer Options because it had turned it off after the Android update, now OEM Unlocking is greyed out, I've cleared cache, factory reset it, tried tricking it with dates, waited 10 days to see if there was a lock period, and it's still greyed out, tablet Bootloader now says "LOCKED" and I can not Re-enable OEM Unlocking to unlock my Bootloader again.
I'm Stuck and Any Help or Ideas would be Appreciated, I can find almost nothing on this tablet. so any help is greatly appreciated!
The Specs of my Lenovo Tab4 10 ( this is NOT the Plus or the LTE Version.) are below.
I Thank Everyone For Their Time
Model: Lenovo TB-X304F
Kernel Version: 3.18.71
Build Number: TB-X304F_S001014_181113_row
Hardware Version: Lenovopad TB-X304F
Software Version: TB-X304F_RF01_181113
RAM: 2GB
Storage: 16GB
CPU: Qualcomm Snapdragon 425
Click to expand...
Click to collapse
I´ve got a similar problem, but I was already on Android 8 when I decide to Unlock Bootloader, an it was available from developers option, but I decide to perform a factory reset, letting the OEM Unlock Bootloader check (don´t know why yet, because when you unlock the bootloader it gets factory reset anyway), and after the reset I looked and now the option was greyed an unchecked, I was reading about and what I could find that you need to flash a stock rom so that maybe the problem could be solved.
There are two links that let me download a stock rom for the Lenovo Tab 4 10.
https://blogthetech.com/flash-file-lenovo-tab-4-10-tb-x304f-firmware-download-stock-rom/
https://firmware247.com/lenovo-tab4-a10-tb-x304f-firmware/
Don´t know which could work yet.
If you try, let me know.
Magisk Rooting
Unlocked Galaxy A10e(SM-A102W/Canada)No OEM Unlock OptionDevice Details
Hardware
Model: Samsung Galaxy A10e(SM-A102W/Canada)
Android version: Android 9(Pie)
System Partition Type: A-Only System Partition
Chipset: Exynos 7884
CPU Architecture: ARM 32-bit(NOT ARM64)
System-as-root: Supported
Software
Baseband version: A102WVLS3ATB1
Kernel version: 4.4.111-16763710
#1 Fri Feb 28 18:33:54 KST 2020
Build number: PPR1.180610.011.A102WVLS3ATB1
SE for Android status: Enforcing
SEPF_SM-A102W_9_0009
Fri Feb 28 18:21:51 2020
Knox Version: Knox 3.3
Knox API level 28
TIMA 4.1.0
Service provider SW version: SAOMC_SM-A102W_OYV_SOL_PP_0008
RF8N20K9RSJ
SOL/SOL/XAC
I've recently purchased an unlocked Samsung Galaxy A10e(SM-A102W) from Walmart and had it set up with Lucky Mobile, I purchased this device with intentions to root/modify after a quick Google search before I took off. I had asked the salesperson who had sold me the phone if it could be done, he told me yes and so far I've spent the last 5 days fixated on trying to get this phone rooted.
So far I've tried,
Enabling Developer Options
Enabling OEM Unlock | No option in Developer tools even after removing Google/Samsung accounts, Auto Updates > Off, playing with date/time settings, Auto Updates > On and re-flashing stock firmware
Enabling USB Debugging
Downloading stock firmware with frija and SamFirm *DEPRECATED applications.
Extracting AP file from stock firmware, copying to Internal Storage on Galaxy A10e Device
Downloading and installing MagiskManager.apk(7.5.1)
Patching AP file from stock firmware with Magisk Manager app on Galaxy A10e Device
(I have tried multiple patched AP files, from ones containing just /Meta-data/, boot.img, recovery.img and vbmeta.img to ones containing every .img)
Copying Patched AP file(magisk_patched.tar) from Internal Storage onto PC
Booting into stock recovery, Download/Bootloader mode | Is Bootloader already unlocked?
Flashing Patched AP file with Odin3B PatcheD/ModdeD v3.14.1 | Options set are "F. Reset Time", although I've tried "DeviceInfo", "Flash Lock", and "Decompress Data"
(I've heard with this model not to use "Auto Reboot"; using "Nand Erase" or "Re-Partition" will most likely damage your device!)
Galaxy A10e device returns message "SECURE CHECK FAIL : (BOOT)", "SECURE CHECK FAIL : (VBMETA)" and depending on the nature of the Patched AP file I used, I may or may not have to re-flash the stock firmware
In short, I'd really like to figure out if I can and/or how to root this device as of now.
Is there a reason my OEM unlock option isn't showing up in the developer tools?
Is going through the stock recovery(Pwr + Vol. UP, release Pwr on logo) and selecting Bootloader, proceeding to go into Download mode, mean my Bootloader is unlocked?
Tools and Resources
Patching/Flashing Software
- MagiskManager
- Odin
Official Samsung Stock firmware Applications
- frija
- SamFirm | *DEPRECATED
Official Samsung Stock firmware
- A102WVLS3ATB1
I also need to unblock the bootloader of this Samsung A10E to try to root.
I have tried to enable oem unlock with some manuals but this model has resisted.
Any luck?
Well, i also need help on that. I've successfully modded phones in the past, but i can't seem to find the hang of that particular model.
Any help appreciated. Thanks !