Does someone know, if this http://forum.xda-developers.com/showthread.php?t=2234627 is working on Xperia ZL too?
Gesendet von meinem C6503 mit Tapatalk 2
Android-Jeck said:
Does someone know, if this http://forum.xda-developers.com/showthread.php?t=2234627 is working on Xperia ZL too?
Gesendet von meinem C6503 mit Tapatalk 2
Click to expand...
Click to collapse
I tried - and does not work
С6502
To determine whether or not your device is compatible answer me this .
When you execute this in terminal, what is the size of TA?
su -c "cd /dev/block;cp mmcblk0p1 TA;ls -la ./TA;rm TA"
Do you see your IMEI when executing this:
su -c "cat /dev/block/mmcblk0p1 | grep -o 'IMEI HERE without last character'"
Do you see your serial nr when executing this:
su -c "cat /dev/block/mmcblk0p1 | grep -o 'serial here'"
This is case sensitive, so make sure you type correctly!
Sent from my C6603 using xda premium
i checked Enable insecurе adbd and it worked
So...just to understand... Does it work or not?
Gesendet von meinem C6503 mit Tapatalk 2
Android-Jeck said:
So...just to understand... Does it work or not?
Gesendet von meinem C6503 mit Tapatalk 2
Click to expand...
Click to collapse
Please download the latest update of the tool and check if your device appears compatible with the 'Compatibility Check'.
Android-Jeck said:
So...just to understand... Does it work or not?
Gesendet von meinem C6503 mit Tapatalk 2
Click to expand...
Click to collapse
work
Egan said:
Please download the latest update of the tool and check if your device appears compatible with the 'Compatibility Check'.
Click to expand...
Click to collapse
I had run the slightly older tool (or I think it is), and so decided to try this one as I have not yet unlocked.
The compatibility check gives and error.
{
"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"
}
An actual backup runs to completion. The problem in the code is here:
if NOT %imeifound% == %imei% goto compfail
The variables should be in quotes so if not found it doesn't simply vanish, i.e.
if NOT "%imeifound%" == "%imei%" goto compfail
There are other places with the same issue. However my REAL question:
In the file (which I checked manually), my IMEI is present WITHOUT the last digit. Should the above be looking for the whole number, or is that some kind of a check digit? I find it hard to believe my TA partition has the right IMEI absent one digit (and it does have the right serial). If I key-enter it without the last digit into this program it works fine.
I ran the backup option and it seemed to work.
I have the backup file is the proper directory but im not sure. seems too easy.
--edit--
the compatibility check also worked for me in version 6 of the unlock tool.
---------- Post added at 11:50 PM ---------- Previous post was at 11:43 PM ----------
Linwood.Ferguson said:
I had run the slightly older tool (or I think it is), and so decided to try this one as I have not yet unlocked.
The compatibility check gives and error.
An actual backup runs to completion. The problem in the code is here:
if NOT %imeifound% == %imei% goto compfail
The variables should be in quotes so if not found it doesn't simply vanish, i.e.
if NOT "%imeifound%" == "%imei%" goto compfail
There are other places with the same issue. However my REAL question:
In the file (which I checked manually), my IMEI is present WITHOUT the last digit. Should the above be looking for the whole number, or is that some kind of a check digit? I find it hard to believe my TA partition has the right IMEI absent one digit (and it does have the right serial). If I key-enter it without the last digit into this program it works fine.
Click to expand...
Click to collapse
I read somewhere that sometimes you leave off the last digit of the IMEI when you go through the bootloader unlock process with Sony.
hi i have test it
my ta is good ,
i attach my result .
so is it possible to get my drm back ?
It should be possible, you just have to run restore option. There seems to some people who have succeeded in backing it up, just make absolute sure that the MD5 sums match before you attempt to unlock the bootloader, or else you will not get the DRM keys back, and may possibly hard brick your phone. I'm going to try it once I can get my hands on a Windows computer so I'm able to do it myself.
Related
Recently got my new N7. First thing I wanted to do was to edit hosts file on it, but currently after fixing the issue with no visible devices in
Code:
adb devices
now I see my device, but it is always offline.
{
"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"
}
NetJunky88 said:
Recently got my new N7. First thing I wanted to do was to edit hosts file on it, but currently after fixing the issue with no visible devices in
Code:
adb devices
now I see my device, but it is always offline.
Click to expand...
Click to collapse
Is your adb version 1.0.31 or greater? Use "adb version" to see what version you are running.
device offline is usually wrong adb version
device not authorized is usually because you didn't accept the RSA prompt for the whitelist
sfhub said:
Is your adb version 1.0.31 or greater? Use "adb version" to see what version you are running.
device offline is usually wrong adb version
device not authorized is usually because you didn't accept the RSA prompt for the whitelist
Click to expand...
Click to collapse
First of all sorry for such delay in reply and my adb version is Android Debug Bridge version 1.0.29
UPDATE:
Updating tools through Android SDK Manager did help and now device is visible, but I have one more, what seems to me, easy question. Is it possible to edit one rooted file without rerooting whole main directory? I need to edit /system/etc/hosts file.
NetJunky88 said:
First of all sorry for such delay in reply and my adb version is Android Debug Bridge version 1.0.29
Click to expand...
Click to collapse
Upgrade your adb and you should see the RSA prompt and after accepting the prompt on the tablet, everything will work as you expect.
sfhub said:
Upgrade your adb and you should see the RSA prompt and after accepting the prompt on the tablet, everything will work as you expect.
Click to expand...
Click to collapse
As I wrote in update, that adb was successfully updated and it did help.
Just go to storage settings and untick mtp and ptp and try again. Sorry for muy english it's not muy native language
Enviado desde mi Galaxy Nexus usando Tapatalk 2
---------- Post added at 01:10 PM ---------- Previous post was at 01:06 PM ----------
I have the same problem and that solve it
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Any way to mark question as solved?
Problem solved
Seems That 4.3 Jellybeen you need ADB newest drivers follow this guide http://www.droidextra.org/2013/12/24/solved-fix-adb-devices-offline-100-working.html
NetJunky88 said:
Any way to mark question as solved?
Click to expand...
Click to collapse
OP can edit title and include solved. That does help people too.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
So I officially got the OTA and I managed to extract it from the cache folder and install it manually using TWRP. But when I try to install, while checking the system files (nearly to the end) it shows up something like this. See photo. Something with the keyboard has unexpected content.
{
"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"
}
Maybe somebody know what to do next? Or even share their original ime.so file?
Edit: I was going to update 4.3 to 4.4. My device is stock and rooted. Nothing more.
Gesendet von meinem HTC One X mit Tapatalk
ChiDi9901 said:
So I officially got the OTA and I managed to extract it from the cache folder and install it manually using TWRP. But when I try to install, while checking the system files (nearly to the end) it shows up something like this. See photo. Something with the keyboard has unexpected content.
Maybe somebody know what to do next? Or even share their original ime.so file?
Edit: I was going to update 4.3 to 4.4. My device is stock and rooted. Nothing more.
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
Try flashing the stock recovery then run the update normally through "check for updates."
ChiDi9901 said:
So I officially got the OTA and I managed to extract it from the cache folder and install it manually using TWRP. But when I try to install, while checking the system files (nearly to the end) it shows up something like this. See photo. Something with the keyboard has unexpected content.
Maybe somebody know what to do next? Or even share their original ime.so file?
Edit: I was going to update 4.3 to 4.4. My device is stock and rooted. Nothing more.
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
Somehow your latin input method editor library got changed. Either inadvertently by something you installed or it got corrupted.
Switching to stock recovery won't make any difference.
If you can find someone to get you the stock file, that might get you further down the road.
Alternatively flash the factory image with the nowipe option or flash scrosler's twrp/cwm flashable krt16s
THX for the replies! So anyone want to share the original Latin input method with me???
Gesendet von meinem Nexus 7 mit Tapatalk
sfhub said:
Somehow your latin input method editor library got changed. Either inadvertently by something you installed or it got corrupted.
Switching to stock recovery won't make any difference.
If you can find someone to get you the stock file, that might get you further down the road.
Alternatively flash the factory image with the nowipe option or flash scrosler's twrp/cwm flashable krt16s
Click to expand...
Click to collapse
Ok I managed to restore my Nandroid Backup of the stock 4.3 (restore system only) and I fixed it and could update!
Gesendet von meinem HTC One X mit Tapatalk
So I recently got a notification about the Android 4.4.3 update and of course I am rooted. I got TWRP recovery and I am ready to flaah the OTA .zip file.
Now my problem is that somehow my LatinIMEGoogle.apk is corrupted, but only the stock version (the one that can with the AOSP ROM). Now I am using the updated version from the Play Store and that's why I can write this message now. This problem prevents me from updating the Firmware of course. Now the only thing I need to do is to restore the system partition through recovery. I could find a Nandroid backup from the past but it somehow also already contains the broken LatinIMEGoogle.apk file so restoring didn't help. Now I am here to ask kindly if somebody mind sharing a Nandroid of the Android 4.4.2 system partition to let me restore via my recovery. I tried to search in XDA but somehow nobody has such kind of solution. (They always refer to the factory image from Google website) which I don't want! Because to set up my device from scratch takes a loooooot of time. Down below I have attached a photo of the flash failure so you know what I mean.
{
"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"
}
Gesendet von meinem Nexus 7 mit Tapatalk
I only need the system partion, that's all. No data, no boot, no recovery. (Because I have them)
OR you have another solution to this problem and it would be nice if you can tell me ?
Gesendet von meinem Nexus 7 mit Tapatalk
Hey, well I have more of an alternative though here, you can try to flash this:
http://forum.xda-developers.com/showthread.php?t=2771012
Its the stock 4.4.3 rom and I doubt you would have problems getting OTA after. If you're up to flash it, just be sure to back up beforehand.
Hope it helps.
Envoyé de mon Nexus 7 en utilisant Tapatalk
zaclimon said:
Hey, well I have more of an alternative though here, you can try to flash this:
http://forum.xda-developers.com/showthread.php?t=2771012
Its the stock 4.4.3 rom and I doubt you would have problems getting OTA after. If you're up to flash it, just be sure to back up beforehand.
Hope it helps.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Click to expand...
Click to collapse
I give it a try.
Edit: Tried and it is awesome! Thank you for this link!
Gesendet von meinem Nexus 7 mit Tapatalk
You can just use the factory image from Google. You do not have to flash all the partitions; you can pick and choose.
First extract the system.img file from the factory image archive, then push it using
Code:
fastboot flash system C:\path\to\system.img
drumist said:
You can just use the factory image from Google. You do not have to flash all the partitions; you can pick and choose.
First extract the system.img file from the factory image archive, then push it using
Code:
fastboot flash system C:\path\to\system.img
Click to expand...
Click to collapse
I will take note of this, thank you!
Gesendet von meinem Nexus 7 mit Tapatalk
drumist said:
You can just use the factory image from Google. You do not have to flash all the partitions; you can pick and choose.
First extract the system.img file from the factory image archive, then push it using
Code:
fastboot flash system C:\path\to\system.img
Click to expand...
Click to collapse
Wouldn't that wipe your device?
dragancla said:
Wouldn't that wipe your device?
Click to expand...
Click to collapse
It won't wipe it because you're only flashing the system partition of the device, worst thing that could happen is a bunch of FC's upon booting it. (which is unlikely but we never know)
Also @ChiDi9901 be sure you choose the odex version if you want to not have problems while getting some newer OTA. The stock roms are always odexed, just saying.. XD
Pls help ....
{
"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"
}
It's a branded O2_UK device
but this won't stop you to install any custom ROM
What do u mean? Can i debrand IT?
Gesendet von meinem HTC One M8 mit Tapatalk
To debrand you need to be s off
At the moment looks like just your bootloader is unlocked and a custom recovery is installed hence the modified status at the top
---------- Post added at 11:56 AM ---------- Previous post was at 11:56 AM ----------
Check out the comer guide in the General section I thing
---------- Post added at 11:57 AM ---------- Previous post was at 11:56 AM ----------
Comer= vomer
And now? Whats the best ican do?!
Gesendet von meinem HTC One M8 mit Tapatalk
tedeha said:
And now? Whats the best ican do?!
Gesendet von meinem HTC One M8 mit Tapatalk
Click to expand...
Click to collapse
Best you can do for what? Just because it's branded doesn't mean you can't use it on other networks that use the same radio bands.
What is it that you are trying to accomplish?
tedeha said:
And now? Whats the best ican do?!
Gesendet von meinem HTC One M8 mit Tapatalk
Click to expand...
Click to collapse
are you talking about getting it back to out of the box?
xunholyx said:
Best you can do for what? Just because it's branded doesn't mean you can't use it on other networks that use the same radio bands.
What is it that you are trying to accomplish?
Click to expand...
Click to collapse
If that is what you want the best you can do is re-lock at this point. Check out recommend posts and learn, some things you can do, others you can't.
You'll have to explain more here if you want more advice in this thread, like @xunholyx said.
joshuaw84 said:
If that is what you want the best you can do is re-lock at this point.
Click to expand...
Click to collapse
I would not advise the OP to relock the bootloader. The only reason to do so, would be to RUU, and I don't know if the O2 version has RUUs, anyway.
Relocking the bootloader render the phone unable to boot. It also drastically limits options (prevent installation of custom recovery, custom ROMs, TWRP backups, etc.).
redpoint73 said:
I would not advise the OP to relock the bootloader. The only reason to do so, would be to RUU, and I don't know if the O2 version has RUUs, anyway.
Relocking the bootloader render the phone unable to boot. It also drastically limits options (prevent installation of custom recovery, custom ROMs, TWRP backups, etc.).
Click to expand...
Click to collapse
Right, maybe it could have been phrased better, I myself see nothing wrong with the OP's current situation, however he seems concerned. So I thought I would ask a few questions to get to the root of the concern, and also suggested he take others advise and read some threads to learn more about what he is trying to do.
Thanks!
joshuaw84 said:
So I thought I would ask a few questions to get to the root of the concern
Click to expand...
Click to collapse
Yes, I agree with responses by you and xunholyx, in that the OP should clarify what the concerns are; and what they are trying to accomplish.
To the OP, if you can't tell whether the phone is branded or not, you probably don't need to debrand it! Debranding is typically to remove obvious branding differences, such as carrier logos, bloatware, or system limitations.
Tx...My question is...What Kind of custom Firmware can i flash with My branded Phone and what is the best Option?
Gesendet von meinem HTC One_M8 mit Tapatalk
tedeha said:
Tx...My question is...What Kind of custom Firmware can i flash with My branded Phone and what is the best Option?
Click to expand...
Click to collapse
You can flash basically any custom ROM meant for the M8, with the exception of those intended only for Sprint, Verizon (and dual SIM, and M8 Eye, which don't have many ROMs, anyway).
There is no "best" ROM for every user. It depends on your personal needs, and preferences. What is "best" for one person may not be for you. Your best bet is to read through the ROM threads, see which ones have features that you want, and try out a couple to see what works "best" for you.
Hello everybody.
I have unlocked the bootloader on my Xiaomi MI 9 SE and since then the apps Google PAY and Netflix don`t work anymore.
Yes, I should have ask the internet before unlocking... ... That´s annoying.
I checked the forums here and I dont`t want to use the idea from ths forum:
https://forum.xda-developers.com/mi-9-se/help/google-pay-t3927403
Does anyone maybe have a solution how to relock the bootloader again?
I´m on 10.2.9.0 Global Stable.
Thanks
{
"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"
}
balu1977 said:
View attachment 4776044
Click to expand...
Click to collapse
Where can I find this option and what app is it?
Miflash tool
Fastoob rom
Manual
I found something that helped:
https://forum.xda-developers.com/mi-8-Lite/help/lock-bootloader-unlocking-t3907086
See the Reply from @SubwayChamp.
@SubwayChamp Thanks a lot! I could relock my Mi 9 SE again and now GooglePAY and Netflix work again.
Here's what helped me with Google Pay. Run it as root. You need to install Sqlite client in Magisk modules.
Code:
am force-stop /data/data/com.google.android.apps.walletnfcrel
chmod 777 /data/data/com.google.android.gms/databases/dg.db
sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 444 /data/data/com.google.android.gms/databases/dg.db
Netflix works after installing Magisk module liboemcryptodisabler.
Have you paid with it?
Yes, about 10 times already
maciek90 said:
Here's what helped me with Google Pay. Run it as root. You need to install Sqlite client in Magisk modules.
Code:
am force-stop /data/data/com.google.android.apps.walletnfcrel
chmod 777 /data/data/com.google.android.gms/databases/dg.db
sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 444 /data/data/com.google.android.gms/databases/dg.db
Netflix works after installing Magisk module liboemcryptodisabler.
Click to expand...
Click to collapse
Could you explain step by step how to fix the gpay issue..?
I mean, where do I have to paste these lines to solve it.
Magisk + sqlite already installed..
Thanks in advance
Gesendet von meinem Mi 9 SE mit Tapatalk
Just paste them in any terminal app as root (type su and hit enter).
I found those lines on Polish MIUI forum.
Works, thanks a lot!
Gesendet von meinem Mi 9 SE mit Tapatalk
any solution for netflix?
diegochiva95 said:
any solution for netflix?
Click to expand...
Click to collapse
Magisk module liboemcryptodisabler.
I at least was now able to activate my paypal account on GPay. At least this step already worked for me. I was only confused that when booting the phone, below the Xiaomi Logo theres still "unlocked" written.
Although I was able to link Paypal with gpay after this method, I was not able pay. It says that it can't idetify the card
fgh11 said:
Hello everybody.
I have unlocked the bootloader on my Xiaomi MI 9 SE and since then the apps Google PAY and Netflix don`t work anymore.
Yes, I should have ask the internet before unlocking... ... That´s annoying.
I checked the forums here and I dont`t want to use the idea from ths forum:
https://forum.xda-developers.com/mi-9-se/help/google-pay-t3927403
Does anyone maybe have a solution how to relock the bootloader again?
I´m on 10.2.9.0 Global Stable.
Thanks
Click to expand...
Click to collapse
Hi how do you unlock this phone.im stuck at 50% cant verify phone error
exratz said:
Hi how do you unlock this phone.im stuck at 50% cant verify phone error
Click to expand...
Click to collapse
I don't remember every step. Sorry. But it was the usual (official) way and I used one of the tutorials here on xda. On the official Mi-Forum you can also find some help.