Hi all!
Happy to share a workaround for root and successful DRM fix.
If you lose your drm key, that's okay, this fix will restore all function which depends on it (picture quality, super vivid mode, etc.....). There's nothing satisfying than using your phone at its full potential with your own custom. Spot the difference!!!!
1. Unlock bootloader
2. Flash boot.img (Patched to be compatible with the drmfix)
>>> fastboot flash boot boot.img
3. Flash recovery.img
>>> fastboot flash recovery recovery.img
4. Boot to recovery by holding vol - and power; then swipe to allow modification and Format data (mandatory)
5. Flash drmfix.zip
6. Flash Magisk 14.0
7. Boot to android, you're done!!!
Type *#*#7378423#*#* then >>Service info>>Configuration or >>Service tests>>Security to check if all your keys are active.
{
"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"
}
Download link:
# For boot.img here!!!
# For recovery.img here!!!
# For drmfix This does the trick
@pa7taloha Recovery Download link not working for me. Is normal TWRP also okay?
Edit: Nevermind, just saw its for F3311 not for F3111.
F3311? You mean Xperia XA or Xperia E5?
okhayko said:
F3311? You mean Xperia XA or Xperia E5?
Click to expand...
Click to collapse
I mean Xperia xa F3111. OP corrected, Thank you
Hi OP, still not working, all my is are "unknown"
okhayko said:
Hi OP, still not working, all my is are "unknown"
Click to expand...
Click to collapse
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
pa7taloha said:
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
Click to expand...
Click to collapse
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
okhayko said:
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
Click to expand...
Click to collapse
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
pa7taloha said:
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
Click to expand...
Click to collapse
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
okhayko said:
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
Click to expand...
Click to collapse
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
pa7taloha said:
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
Click to expand...
Click to collapse
Thanks buddy. Here is my boot.img that i was flash
boot.img file
For F3116 [33.3.A.1.97]
okhayko said:
Thanks buddy. Here is my boot.img that i was flash
boot.img file
Click to expand...
Click to collapse
Now
1. flash this bootF3116.img file, using the command "fastboot flash boot bootF3116.img" (without quotes)
2. Go to twrp recovery and "format data" (I suppose you already have flashed twrp)
3. Flash drmfix.zip
4. Flash Magisk if you need root.
5. Reboot
Download link
bootF3116.img
The compatible drmfix.zip
If you still have any problem let me know
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
bobladure said:
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
Click to expand...
Click to collapse
Hi, F3112 and F3116 has the same boot.img file so you can try to flash the boot.img, and drmfix.zip above your post and post your feedback here
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
cojocar.andrei said:
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
Click to expand...
Click to collapse
Sorry for late reply.
I will try to be clear as much as I can(bad english speaker).
We have tested this workaround to: xperia xa f3111(Mediatek, Nougat) and xperia x perfomance(qualcom, Nougat and 0reo) and it work fine in Nougat and Oreo too. I hope this will work too to the other xperia devices, so we can relate it.
I did not compile kernel from source, I have just extracted it with flashtool kernel.elf and unpacked/repacked it with AIK Linux/Carliv-image-kitchen. I am a Linux user.
For mediatek processor,
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init, .
Code:
on early-init
[COLOR="Red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.aee.rc
add this red line in on init
Code:
on init
export LD_PRELOAD libdirect-coredump.so
write /proc/self/coredump_filter 39
setprop ro.aee.enperf off
[COLOR="Red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
7. Open "fstab.mt6755" and copy in new text file the path to your system, it should be in the first line, we will use this later in the drmfix.zip
6. repack your kernel
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.mt6755" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip
For Qualcom processor
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init
Code:
on early-init
[COLOR="red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.environ.rc
add this red line to the last line.
Code:
export SYSTEMSERVERCLASSPATH /system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
[COLOR="red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
5. Open "fstab.qcom" and copy in new text file the path to your system, we will use this later in the drmfix.zip
6. repack your kernel, flash it
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.qcom" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/bootdevice/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip, and flash it.
Avalaible for clarification.
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
matan290 said:
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
Click to expand...
Click to collapse
Sorry to hear that, It is always recommended to do a full nandroid backup before flashing anything. To get rid of those Unknown error you have to reflash your firmware. What causes these error is that the drm.zip you've flashed has deleted the credmgr.db file in /data/credmgr/, this contains all your phone credential. May be you've flashed any drmfix(old drmfix in other thread) before flashing this, because this fix will not delete anything in your system. And no need to wipe cache/dalvik after flashing it.
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
matan290 said:
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
Click to expand...
Click to collapse
You can use flashtool and download a frimware the latest version by xperifirm which is integrated in the flashtool. Or if you want to use Pc Companion you have to relock your bootloader and unlock after it's done.
Related
Note: This thread is old. Currently you can just update the firmware and then root again using Easy Root Tool
This is a guide on how to update the Z1 Compact to any firmware without losing root on locked bootloader. For unlocked bootloader, please see post #3 ( http://forum.xda-developers.com/showpost.php?p=51254652&postcount=3 )
Requirements
Latest flashtool ( http://www.flashtool.net )
Rooted Z1 Compact (check here for how to root: http://forum.xda-developers.com/showthread.php?t=2642081 )
D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf from 'Firmwares' below
z1c-44-14.X.A.X.XXX-XX.system.flashable.zip from 'Firmwares' below
SuperSU ( http://download.chainfire.eu/supersu )
Latest Z1C-lockeddualrecovery(...).flashable.zip ( http://nut.xperia-files.com/ ) (atleast v2.7.117)
Firmwares
Here you can find some prepared firmwares. Note: Do not mix files from different firmwares!
Jelly Bean (4.3)
14.2.A.1.114 Generic UK (Darkimmortal)
z1c-43-uk.system.flashable.zip | share-online mirror
D5503_14.2.A.1.114_Generic UK-nosystem.ftf
Click to expand...
Click to collapse
KitKat (4.4)
14.3.A.0.681 Generic UK (Darkimmortal)
z1c-44-uk.system.flashable.zip | mega mirror
D5503_14.3.A.0.681_Generic_UK-nosystem.ftf | mega mirror
Click to expand...
Click to collapse
14.3.A.0.757 Generic DE 1279-6978 (louis0815)
z1c-44-14.3.A.0.757-DE.system.flashable.zip
D5503_14.3.A.0.757_GenericDE-nosystem.ftf | mediafire mirror
Click to expand...
Click to collapse
14.3.A.0.757 Generic NO 1279-4149 (nism0o)
z1c-44-14.3.A.0.757-NO.system.flashable.zip
D5503_14.3.A.0.757_GenericNO-nosystem.ftf
Click to expand...
Click to collapse
14.3.A.0.757 Generic UK 1279-4727 (codified)
z1c-44-14.3.A.0.757-UK.system.flashable.zip | gdrive mirror
D5503_14.3.A.0.757_Generic_UK-nosystem.ftf
Click to expand...
Click to collapse
14.3.A.0.757 Generic FR 1279-5365 (emilic)
See here: http://forum.xda-developers.com/showpost.php?p=52599589&postcount=385
Click to expand...
Click to collapse
14.3.A.0.761 Generic NO 1279-4149 (paul5425)
z1c-44-14.3.A.0.761-NO.system.flashable.zip
D5503_14.3.A.0.761_GenericNO-nosystem.ftf
Click to expand...
Click to collapse
Tutorial
You will not lose any data. It is still recommend to take a backup.
Copy D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf to your flashtool installation in the folder firmwares/
Put z1c-44-14.X.A.X.XXX-XX.system.flashable.zip on your sdcard (do not unpack)
Put Z1C-lockeddualrecovery(...).flashable.zip on your sdcard (do not unpack)
Download SuperSU and put on your SD card (do not unpack)
Go to the recovery menu and try flashing SuperSU. If it succeeds, proceed. Otherwise change recovery menu (TWRP is Volume DOWN)
In the recovery menu format /system (located under Mounts & Storage) (do not reboot!)
Install the following files in recovery (in this order)
z1c-44-14.X.A.X.XXX-XX.system.flashable.zip
Z1C-lockeddualrecovery(...).flashable.zip
SuperSU zip file
After installing go to Advanced => Power off (Power off might also be located under Power Options, depending on the recovery you use)
Boot your phone in flashmode (Hold volume down while phone is off and plug in your USB cable)
Open flashtool and flash D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf (select Wipe [Uncheck Data] and Exclude [Uncheck ALL])
You're done!
Hashes
D5503_14.2.A.1.114_Generic UK-nosystem.ftf
MD5: 47005E1E16B340A90B958919122F89AA
SHA1: 252C905F1F0213D809925BC32A955E421FE4C3E6
z1c-43-uk.system.flashable.zip
MD5: 6221178B6809EA943A0AB5654A9D6A2D
SHA1: 8B9BEAB4846927DED38018B93C56993BD017BFB8
D5503_14.3.A.0.681_Generic_UK-nosystem.ftf
MD5: 5D1BDD44DF531280984B60E810A87FFA
SHA1: 5ADE48599414BE47A0A7DD1BCB37C0F5518F7CCB
z1c-44-uk.system.flashable.zip
MD5: 148BDD3BEAEDE850CAF085ED82518FF9
SHA1: FB594821FBEA030657CA5D048DE2593194F18DF8
D5503_14.3.A.0.757_GenericDE-nosystem.ftf
MD5: D720CD278E0DB88F49FA22CBBE441720
SHA1: 3F4C47B841BD24511C30BB0E44030872BD93921A
z1c-44-14.3.A.0.757-DE.system.flashable.zip
MD5: 38FA3162C725B0E357FD8CDE1AA8CDE8
SHA1: F898DC9580D84D541C622307439B45A607A0A7A5
D5503_14.3.A.0.757_GenericNO-nosystem.ftf
MD5: 3E76A9E4DFE4BD6D2CE05DBBC0B09CB8
SHA1: 44EFFED69E881B08FF6F3AEEF0EDBE69C59187DC
z1c-44-14.3.A.0.757-NO.system.flashable.zip
MD5: A6B54DF73E5E0038152EC2AFFE4E7067
SHA1: DF6F497987D44F43ABF49C4BB98ECC49058F97C6
D5503_14.3.A.0.757_Generic_UK-nosystem.ftf
MD5: 915E348841834816216F4EFE6BB85D29
SHA1: 28EBCA4A3218E45C1C7B00C6DE494052A004DA0B
z1c-44-14.3.A.0.757-UK.system.flashable.zip
MD5: 9A8089751D964312E255ABC507AD1C90
SHA1: 2FC34DB65EA087C0D824502FE1E801027461EC49
D5503_14.3.A.0.761_GenericNO-nosystem.ftf
MD5: 3DD5723B43F834ED55E65A9B8DCCB0D2
SHA1: 84848D4C1ABBD4C2729E3BBCE0706A25379717F8
z1c-44-14.3.A.0.761-NO.system.flashable.zip
MD5: 771B257718FCE8CBE8E3EAE6F29B0765
SHA1: C737EEE5D1DB28F8F918A126A18EDCA7FAF8E5AF
Questions
I get an error in flashtool: "Cannot open bundle. Flash operation canceled"
You need the latest flashtool.
Click to expand...
Click to collapse
I am from Country XY but there is no firmware for my country? :crying:
It doesn't really matter what localization you use. The firmwares are almost the same. Your language will still be available.
Click to expand...
Click to collapse
Are these roms deodexed?
No. All roms are odexed.
Click to expand...
Click to collapse
I can't access recovery menu, when I boot my phone the light is orange, not green?
Somehow you lost your recovery menu. If your bootloader is locked you need to start again from the beginning of the rooting guide.
Click to expand...
Click to collapse
I have another error, which is not in this list!
Post it in the thread but note for successful help you need to provide the following:
dualrecovery version used
flashable system zip used
ftf no-system used
Click to expand...
Click to collapse
Proof
Confirmed working by pcpepik, Boes40 ( http://forum.xda-developers.com/showpost.php?p=51476157&postcount=156 ), tommy17 ( http://forum.xda-developers.com/showpost.php?p=51384084&postcount=125 ), mikk_11 ( http://forum.xda-developers.com/showpost.php?p=51341824&postcount=105 ) and many more on locked bootloader :highfive:
{
"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"
}
Credits
Darkimmortal
[NUT]
pcpepik
Hello,
Seems missing the download path of "Z1C-lockeddualrecovery(...)flashable.zip" and is it also copy to SD card?
Unlocked bootloader
Requirements
Latest flashtool ( http://www.flashtool.net )
fastboot and flashmode drivers installed
Z1 Compact with unlocked bootloader
ftf of firmware (check here http://forum.xda-developers.com/showthread.php?t=2631291 or general section for official firmwares)
SuperSU ( http://download.chainfire.eu/supersu )
Custom kernel with recovery (e.g. dualrecovery kernel or http://forum.xda-developers.com/showthread.php?t=2620794 )
Note: Kernel needs to be for the specific firmware version (dualrecovery kernel is only for latest firmware)
Tutorial
You will not lose any data. It is still recommend to take a backup.
Copy the firmware ftf to your flashtool installation in the folder firmwares/
Download SuperSU and put on your SD card (do not unpack)
Boot your phone in flashmode (Hold volume down while phone is off and plug in your USB cable)
Open flashtool and flash your ftf (select Wipe [Uncheck Data] and Exclude [Uncheck ALL])
After flashing, boot your phone in fastboot mode (Hold volume up while phone is off and plug in your USB cable)
Download a custom kernel and unzip until you have a file called *.img
Put the custom kernel inside the folder of flashtool called x10flasher_lib/
Open cmd and navigate to this folder (e.g. cd C:\flashtool\x10flasher_lib)
Execute the following command to flash the custom kernel (boot.img is the filename of the kernel, change if needed)
fastboot.exe flash boot boot.img
Boot your phone and go to the recovery menu
Note: This is different in some kernels, default is to hold volume up when the led lights up
Optional: If you are using dualrecovery kernel, flash the kernel flashable zip
Flash SuperSU zip
You're done!
Confused about point 5 : Install Z1C-lockeddualrecovery(...)flashable.zip
and warning post 1 : Do not try to flash the dualrecovery, you will end up stuck at boot logo!
So what to install on point 5?
Boes40 said:
Confused about point 5 : Install Z1C-lockeddualrecovery(...)flashable.zip
and warning post 1 : Do not try to flash the dualrecovery, you will end up stuck at boot logo!
So what to install on point 5?
Click to expand...
Click to collapse
Whoops, forgot to delete that step. Fixed now, thanks
what to do with error in flashmode :Cannot open bundle. Flash operation canceled
and point 5 should be power options, not advance
Boes40 said:
what to do with error in flashmode :Cannot open bundle. Flash operation canceled
and point 5 should be power options, not advance
Click to expand...
Click to collapse
You need latest flashtool. Ok thanks, for the tip, which recovery are you using? It's advanced in CWM.
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Same!
I have rooted Z1c with Android 4.4!
Hurry!
But supersu can't update. Some app can't rooted (eg. Greenify), Es explorer can't mount system r/w...
Titanium is still working though, Latest Xposed (beta) isn't, no root.
Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Root should still work. But to fix the problem, try this.
Download SuperSU from here: ( http://download.chainfire.eu/supersu )
Copy the file su from the folder arm to somewhere on your phone. (e.g. /tmp)
Give correct permissions (755)
Then copy it to /system/xbin and overwrite the old one.
Please let me know if it worked.
Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Could we update SuperSu from Play?
Or how can we solved: We have root, but we have an not working supersu...
Problem is I can't copy the file with rootexplorer. First time RE opens it asks for root, press yes of course but it looks it doesn't get root.
Boes40 said:
Problem is I can't copy the file with rootexplorer. First time RE opens it asks for root, press yes of course but it looks it doesn't get root.
Click to expand...
Click to collapse
What is the error message? And have you tried with adb?
And can you check if your system flashable zip has the same hash as in the first post?
With Root Explorer, first mesage is :The current file sytem is r only. Do you want to remount as r-write and continue the operation, / yes / su already exists. Do you want to overwrite it? / yes / Copy failed su to /system/xbin
Haven't tried with adb, how please?
How to check the hash?
thanks
zxz0O0 said:
What is the error message? And have you tried with adb?
And can you check if your system flashable zip has the same hash as in the first post?
Click to expand...
Click to collapse
After run esexplorer and granted supersu: 1. screenshot
After run supersu: 2.
After update normal (we don't have CWM...): 3.
Root checker: 4.
Supersu: 5.
All working except supersu...
Boes40 said:
With Root Explorer, first mesage is :The current file sytem is r only. Do you want to remount as r-write and continue the operation, / yes / su already exists. Do you want to overwrite it? / yes / Copy failed su to /system/xbin
Haven't tried with adb, how please?
How to check the hash?
thanks
Click to expand...
Click to collapse
Copy the new su binary to /tmp then do
adb shell
su
chown root:root /tmp/su
chmod 755 /tmp/su
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
cp /system/xbin/su /system/xbin/su.old
mv /tmp/su /system/xbin/su
papzi57 said:
After run esexplorer and granted supersu: 1. screenshot
After run supersu: 2.
After update normal (we don't have CWM...): 3.
Root checker: 4.
Supersu: 5.
All working except supersu...
Click to expand...
Click to collapse
Have you tried to replace su binary as I posted above and post #11 ?
Just followed ur instructions!
After successful flashing I can still enter Recovery.
Xposed Installer NOT working, requires writing permissions!
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
error:
block/platform/msn_sdcc.1/by-name/system /system
mount : Operation not permitted
255|[email protected]:/ #
for adb wich mode need: fastboot or flashmode or normal. (I forgotten...)
Su binary can't replace: permission denied
Guide: Getting Xposed Running​This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"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"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
I have this firmware
{
"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 try trough OTA and also in manual mode copyng file UL-ASUS_Z00E-WW-13.10.7.1-user.zip, but always i have this message
and no update.
My Asus ZenFone 2 Laser is ZE500KL, with root and TWRP.
I unroot it but I can not upgrade to marshmallows for a recovery problem, because my recovery in not stock. I tried to put another stock recovery, but when I search to update, this verify if the recovery was firmware WW-12.8.5.222, while finding the version 12.8.5.118 and fails update.
How can I restore its original recovery or all system including recovery ?
Please help me
Thank
Hi, I advice you to not upgrade because Marsmallow haves many bug (proximity sensor e battery drain). If you want update try to make factory reset first
Hi, your zip is a full rom not an ota... The ota 12.8.5.222to13.10.6.16 exists you can find it on google its named "WW_ZE500KL-12.8.5.222-13.10.6.16-fota-user.zip"
I think that if you want do your full rom maj, you must wipe and format all things... But i'm not sure
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Please help me i cannot update to marshmallow from my firmware 12.8.5.222 on OP.
I unrrot the phone and always i receive this message
Thinking that the problem was recovery and i flash with twrp another standard recovery but always same message.
So in which way i can upgrade to marshmallow, possibly without losing apps and data...please
Thank
Hispa
hispanico957 said:
Please help me i cannot update to marshmallow from my firmware 12.8.5.222 on OP.
I unrrot the phone and always i receive this message
Thinking that the problem was recovery and i flash with twrp another standard recovery but always same message.
So in which way i can upgrade to marshmallow, possibly without losing apps and data...please
Thank
Hispa
Click to expand...
Click to collapse
Apparently, your current recovery version does not match with your current firmware version. There are two possible workarounds-
1. Wipe system by executing "fastboot erase system" in fastboot mode. Then reflash latest official asus lollipop ROM. This will fix the recovery and firmware mismatch and you will then be able to flash MM via stock recovery.
2. If you are experienced with edit8ng updater-script, Extract all contents of MM ota. Open updater-script and remove all asserts and lines that say "abort". Then compress the contents again. (You can't edit without extracting coz zip is signed). Flash this modified ota zip via TWRP.
If you still can't flash it or you are unable to edit updater-script, pm me, I have downloaded the MM ROM, I will send you modified updater-script.
I can even convert this ota into .imgs so that you can flash directly via fastboot
sziraqui said:
Apparently, your current recovery version does not match with your current firmware version. There are two possible workarounds-
1. Wipe system by executing "fastboot erase system" in fastboot mode. Then reflash latest official asus lollipop ROM. This will fix the recovery and firmware mismatch and you will then be able to flash MM via stock recovery.
2. If you are experienced with edit8ng updater-script, Extract all contents of MM ota. Open updater-script and remove all asserts and lines that say "abort". Then compress the contents again. (You can't edit without extracting coz zip is signed). Flash this modified ota zip via TWRP.
If you still can't flash it or you are unable to edit updater-script, pm me, I have downloaded the MM ROM, I will send you modified updater-script.
I can even convert this ota into .imgs so that you can flash directly via fastboot
Click to expand...
Click to collapse
Very very big if you can upload updater-script and image i thank you.
In anyway in updater-script i see 4 lines with abort:
Code:
(greater_than_int(getprop("ro.build.date.utc"), 1450932645)) || [B][COLOR="Red"]abort[/COLOR][/B]("Can't install this package less than or equal WW_12.8.5.221_user(Thu Dec 24 12:50:45 CST 2015) device build time (" + getprop("ro.build.date") + ").");
ifelse( getprop("ro.product.name") == "OPEN_Phone", ui_print("OPEN SKU device"), (
getprop("ro.product.name") == "WW_Phone" || [B][COLOR="Red"][COLOR="red"][B][B][COLOR="Red"]abort[/COLOR][/B][/B][/COLOR][/COLOR][/B]("This package is for "WW_Phone" devices; this is a "" + getprop("ro.product.name") + "".");
) );
ui_print("Target: asus/WW_Phone/ASUS_Z00E_2:6.0.1/MMB29P/13.10.7.1-20160514:user/release-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "100,0,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,753664,753666") == "8af3f740e6ebbdf56700096039cefc8918322b9d" then
if range_sha1("/dev/block/bootdevice/by-name/system", "102,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,737279,753152,753664,753666,754178") == "cf88d7b8183bd71c4f9a980377c32bce5c33a559" then
ui_print("Verified the updated system image.");
else
[B][COLOR="red"]abort[/COLOR][/B]("system partition has unexpected non-zero contents after OTA update");
endif;
else
[B][COLOR="red"]abort[/COLOR][/B]("system partition has unexpected contents after OTA update");
so i change in this way...its correct ?
Code:
ifelse( getprop("ro.product.name") == "OPEN_Phone", ui_print("OPEN SKU device"), (
) );
ui_print("Target: asus/WW_Phone/ASUS_Z00E_2:6.0.1/MMB29P/13.10.7.1-20160514:user/release-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "100,0,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,753664,753666") == "8af3f740e6ebbdf56700096039cefc8918322b9d" then
if range_sha1("/dev/block/bootdevice/by-name/system", "102,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,737279,753152,753664,753666,754178") == "cf88d7b8183bd71c4f9a980377c32bce5c33a559" then
ui_print("Verified the updated system image.");
else
endif;
else
..regarding point 1) in which way reflash latest official asus lollipop ROM ?
Thank for support
Hispanico
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
Ok i try... i prefer second step because with first all my dta are deleted..
BUMMM
Hispa
A BIG THANK sziraqui
sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
Does this work with a Rom
I want to ask you,what twrp version do you installed in the screenshot? 3.0.0.0 or 3.0.2.0 ? My phone is like to you.. I cant upgrade to MM
sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
Many thanks for this help, it works like a charm !
Hi I have the same problem of the topic. I followed your solution. I changed the updater-script but now I have the problem with the zip file. WinRar tells me that the files I try to put into the zipare too big and it suggests me to use rar and not zip. What do I have to do?
At last I created the zip file with compressed folder windows but I cannot flash the new zip. I don't have any OS in my Laser.
I followed what you wrote.
I downloaded the firmware WW 13.10.10.44 from Asus web site
I extracted the content in a folder. I canceled updater-script and I changed it with your zip updater-script-modified
I put everything inside a zip
I tried to flash it but it doesn't work. I put a screenshot here https://ibb.co/Tkxq5hY
Since huawei started to mess around with online firmwares that twrp couldn't handle I decided to create my own offline package with updated firmware(s) and i thought why not create a offline package thread with latest firmwares in it.
This case we can always keep ourself up to date (system wise) without having to restore to stock recovery etc.
However this is a "dirty" way of update firmware and it will only update following partitions:
Boot
Cust
Product
System
Vendor
Version
All other partitions will stay intact! Why? Because if we add other partitions there's a HIGH potential of hard brick the device and I mean really high!
But with official packages it updates all partitions!
Yes. And we can't (for now, or never) re create this procedure we'd have to know how the UPDATE.APP is being built and we can't re create a UPDATE.APP for now.
So far only available homebrewed package is 394 created by me.
See post 2 on how to create your own custom offline package!
Downloads:
FRD-L09C432B934
https://mega.nz/#!j0QXjJKa!i5lOMYjO_GusfzCTT6qVAR7LgzVGdpLT4i66FKCrshQ
blackbuffalo said:
Here is Offline fw for L04C567B385 thanks @blackbuffalo
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Click to expand...
Click to collapse
Thanks @SnoopHTC
L19-C432B398
https://gofile.me/3wKsh/4wlivV41v
Nortonko said:
so coz the link from SnoopHTC is dead i made my own package for FRD-L19C432B398. Here is the link: https://webshare.cz/file/73v2t363K5/twrp-frd-l19c432b398-zip
Click to expand...
Click to collapse
How to do it yourself package.
In order to create a unofficial update package you'll need
Huaweiupdateextractor (google it)
Simg2img (google it)
This template
https://mega.nz/#!i1Y3Wa5J!VfELb8aRkA5bon_OlIRPNAS_xUAmzMq0I-rVywHbvi4
Now extract all needed partitions
Boot
System
Vendor
Product
from big update file
cust
version
from small update file *this can be found in any of the 2 extra small zips
Open cmd and navigate to the folder where you have to both simg2img and your system files. Now cd into your work directory to convert the images.
Simg2img.exe system.img s.img will give you a converted system image with the name s.img
Convert these following partitions
system
Product
Version
Cust
Vendor
Once completed check the update-script
The
c.img is cust
v.img is vendor
ve.img is version
p.img is product.
b.img is boot
s.img is system
you can change these names to its regular name like system.img for system or make it more confusing if you want [emoji14]
Make sure the partitions are exactly the same!
If you decide you want to change the name of the files from s.img to system.img make sure you do it correct!
Because system.img in updater-script is not the same as System.img in root of zip. If you have a captive letter in root and not in updater-script the zip will fail to flash.
Now simply compress the images into a zip and you're done.
Note: after you flashed your offline zip make sure to patch boot! Else it will reboot to recovery
Note you'll get result
Error: Unknown command []] this is not a issue since we're using stock huawei updater binary.
Sent from my FRD-L09 using Tapatalk
Your awesome work will save a lot :good:
Nice but it should not be in "roms etc" threads? More people will find it.
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
WYPIERDAALAAC said:
Nice but it should not be in "roms etc" threads? More people will find it.
Click to expand...
Click to collapse
Because I simply put it here
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
Hmm you might have to patch boot after flash??
PalakMi said:
Your awesome work will save a lot :good:
Click to expand...
Click to collapse
It will save a lot of time yes.
Sent from my FRD-L09 using Tapatalk
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
{
"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 FRD-L09 mit Tapatalk
LastStandingDroid said:
Hmm you might have to patch boot after flash??
Click to expand...
Click to collapse
What schould i do?
Rommco05 said:
I can't find simg2img version which works on Windows 10. One version shows me only
Using STDIN as input
Using STDOUT as output is that right?
Maybe don't know how use this program
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/dev-simg2img-windows-t3156459
This one works just great.
I forgot you might have to use a cmd to convert images will edit post 2
Silencer3007 said:
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
View attachment 4250767
Gesendet von meinem FRD-L09 mit Tapatalk
Click to expand...
Click to collapse
Patch boot with either Supersu or magisk.
Did the backup include version? I doubt which is why you'll get B394 in settings.
It doesn't restore the partition which contains the build number info.
extpumajl said:
What schould i do?
Click to expand...
Click to collapse
Patch boot and try again
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Patch boot and try again
Click to expand...
Click to collapse
Thx. Now is everything fine.
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Dominikrod said:
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Click to expand...
Click to collapse
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
Ah no its just that it has to flash boot as well ?
Sent from my FRD-L09 using Tapatalk
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
No need convert Boot.img, just rename then put it into zip
blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Great that you contribute ?
Sent from my FRD-L09 using Tapatalk
blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Bro can you confirm the build number is not NRDm keys ?
venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
It won't unless he packed the product files which stores the build info
Sent from my FRD-L09 using Tapatalk
venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
it not imcluded
blackbuffalo said:
it not imcluded
Click to expand...
Click to collapse
Ok,then it shows build number correctly?
Is anyone working on rooting this device? I just bought one and it seems to be a really nice tablet, except I'd prefer something other than touchwiz. Although I'd be perfectly happy with just rooting at least.
If there's no one rooting it, could someone help me find the resources to learn how to possibly root this device myself? I'm a beginner with modding android but I pick up things quickly so I'd like to at least give it a shot.
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
shahmir_k said:
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
Click to expand...
Click to collapse
OK! Make this thread, cause I'm working now on TWRP for this tablet.
Please after thread creating place here link to it... :good:
Thank you for the solution
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much. I am a newbie to the whole rooting android thing. I came across this post when trying to root my SM-T385 tab and thought it was too complicated. I tried many other simpler methods and nothing worked. Finally, I took my time figure out your solution and lo-behold it actually works.:good:
I am now a proud owner of a rooted android tablet.
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
crewdog said:
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
Click to expand...
Click to collapse
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
Thanks. I don't see "OEM unlock" in the developer now, so think I'm in the penalty box for a week. Bummer.
Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
What's the firmware build number?
Im having the same issue, help please?
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
My SM-T380 build number is: NMF26X.T380DXU1AQI7
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
joeyw007 said:
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
Click to expand...
Click to collapse
There is no "Fastboot Mode" in this model, like in many other from Sansung, HTC ets. Samsung also insert absolutely bad for ROM-creators KNOX system.
So here is S-shot for OEM is unlocked (and tablet is rooted)... But there no chances for "fastboot"
{
"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"
}
Under Linux I use Heimdall. Here is screen, where device are detected & ready to be flashed.
One thing about Heimdall... Version from repos didn't work with our device. So we have to compile it from Benjamin-Dobell github where this bug are fixed yet.
Building source is trivial:
Code:
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make
OEM Unlock Enabled On New Update
I contacted Samsung and spoke with them about the OEM unlock feature missing from developer options and explained I needed to root my table for development purposes for work. They gave me the usual reply of we don't support rooting. I replied I'm not asking you to. I'm asking you to unlock the boot loader on a device I bought, belongs to me and should be allowed to modify as I see fit. I am aware of security and warranty issues please do something about this. Remember Apples DE boggle. A few days later an OTA update puts the feature in my developer options. Coincidence or did they listen? Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Root Achieved!!! For Cellular South Build T380XAR1AQK3
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
OK with the new update the boot loader can be unlocked from dev options and the above method for rooting is %100 successful. Just make sure to tell Magisk Manager under settings to output patched boot.img to odin mode "img.tar" then just flash the patched_boot.img.tar via the AP slot with Odin.
joeyw007 said:
Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Click to expand...
Click to collapse
I know at last 3 person with the same situation... Sometimes, when we try to change region of firmware or try to root it out by progs like Kingo, Kingroot & CF-Autoroot it seems to Samsung, that You are dangerous hacker - and it set the 1-week "penalty" mode. So OEM-unblocking became disabled during this penalty period.
Like I said Who Knows, I am Curious...
I am curious if anyone missing the OEM Unlock feature in dev options running build T380DXU1AQI7 before this morning received an OTA update to build number T380XAR1AQK3 with the ability to unlock your bootloader from dev options. I haven't changed regions successfully flashed anything to this tablet and have had it for a month. OEM unlock appeared after OTA update this morning. Now I'm rooted and all is well. Before restarting your tablet if you root this build I would suggest turning OEM Unlocking on again after rooting, as it wipes your tablet, otherwise you will get an error message about not being able to boot unauthorized binaries and have to repeat the process.
Mefody said:
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
Click to expand...
Click to collapse
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
https://androidfilehost.com/?fid=889964283620778312
.
ashyx said:
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
Click to expand...
Click to collapse
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Mefody said:
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Click to expand...
Click to collapse
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
ashyx said:
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
Click to expand...
Click to collapse
OK! Thanks a lot!!! Will find all available info and try to play with formatting /data partition & setting on Your patch.
Awaiting Your special thread for this device. Anyway - You did a great job :good: