4.3 OTA update fails due to modified file debuggerd - Samsung Galaxy Nexus

When trying to apply the OTA update from Android 4.2.2 to 4.3 to a rooted Samsung Galaxy Nexus, the process failed quickly with an assert error, something like:
assert failed: apply_patch_check("/system/bin/debuggerd", …
The cause was that the file /system/bin/debuggerd had been changed since the 4.2.2 installation. There was also a file debuggerd.backup, which was, however, equal to the file debuggerd.
I solved the problem by copying the 4.2.2 file debuggerd (attached here—unzip before use) from another Galaxy Nexus phone, which was still at stock 4.2.2, and copying that into the problem phone. To do this I used ES File Explorer in "Root Explorer" mode with /system mounted r/w.
After this operation the OTA update ran fine. (I had meanwhile downloaded it as a file and flashed it with the TWRP recovery.)
The question remains, which program had altered the debuggerd file? Since only programs with root rights could possibly do this, I have two main suspicions: ReKey and StickMount. I have not tested, but if anybody here has the same problem, please check which programs with root rights you have been running.
The attached file is from Android 4.2.2 yakju. We have an indication (see below) that the file may not be the same for takju. Could somebody please confirm or deny this?

Problem with the file
hgmichna said:
When trying to apply the OTA update from Android 4.2.2 to 4.3 to a rooted Samsung Galaxy Nexus, the process failed quickly with an assert error, something like:
assert failed: apply_patch_check("/system/bin/debuggerd", …
The cause was that the file /system/bin/debuggerd had been changed since the 4.2.2 installation. There was also a file debuggerd.backup, which was, however, equal to the file debuggerd.
I solved the problem by copying the 4.2.2 file debuggerd (attached here—unzip before use) from another Galaxy Nexus phone, which was still at stock 4.2.2, and copying that into the problem phone. To do this I used ES File Explorer in "Root Explorer" mode with /system mounted r/w.
After this operation the OTA update ran fine. (I had meanwhile downloaded it as a file and flashed it with the TWRP recovery.)
The question remains, which program had altered the debuggerd file? Since only programs with root rights could possibly do this, I have two main suspicions: ReKey and StickMount. I have not tested, but if anybody here has the same problem, please check which programs with root rights you have been running.
Click to expand...
Click to collapse
Thanks for the file.
It is not working for me though. Is it Takju?

masasin said:
Thanks for the file.
It is not working for me though. Is it Takju?
Click to expand...
Click to collapse
No, this is from a yakju phone.
Sorry, I assumed, perhaps falsely, that the debuggerd file in Android 4.2.2 is always the same.
If this problem occurs more often, perhaps somebody could upload the stock debuggerd from takju Android 4.2.2 as well.

hgmichna said:
No, this is from a yakju phone.
Sorry, I assumed, perhaps falsely, that the debuggerd file in Android 4.2.2 is always the same.
If this problem occurs more often, perhaps somebody could upload the stock debuggerd from takju Android 4.2.2 as well.
Click to expand...
Click to collapse
Mine was Takju. It seems they are incompatible. Do you know if I get sent an email automatically if a file is updated?

The stock 4.2.2 takju debuggerd image would be appreciated here, too! Thanks.

takju debuggerd
I pulled these files from the factory images "takju" (system.img)
4.2.2 (JDQ39)
takju-jdq39-debuggerd - This is for OTA - takju-JWR66V-from-JDQ39
md5: c7372f8a49253c29e7f4d691276e8564
4.3 (JWR66V)
takju-jwr66v-debuggerd - This is for OTA - takju-JWR66Y-from-JWR66V
md5: a64ce8343a8cc2a7248b1c0bbab766bf

Hello, can somebody, please, post original debuggerd file from yakju 4.3 (JWR66V) ... thank you

kubuss said:
Hello, can somebody, please, post original debuggerd file from yakju 4.3 (JWR66V) ... thank you
Click to expand...
Click to collapse
Posted above. I just removed Stickmount in the meantime. Also, I can copy and paste again!

Here it is buddy! <yakju 4.3 (JWR66Y)> version of file which will do the job of the OTA update.
I have finally found the solution to my "Error 7" after several days of thread reading and wrong assumptions. The culprit seems to be a past installation of stickmount and the usb otg helper which i use now !!

empsun said:
The culprit seems to be a past installation of stickmount and the usb otg helper which i use now !!
Click to expand...
Click to collapse
Which one is that? Is it any better than StickMount?

Stickmount didn't work for me, couldn't even mount a NTFS usb key for writing. On the contrary OTG USB helper has everything you need, minus the tampering of the aforementioned file, without informing the user about the problem it causes with the JB update
Sent from my Galaxy Nexus using xda app-developers app

So... How do I now "untamper" the file that stickmount screwed up... without a computer? Lol. I only have my phone and Nexus 10 currently. *sigh*

Volkrik said:
So... How do I now "untamper" the file that stickmount screwed up... without a computer? Lol. I only have my phone and Nexus 10 currently. *sigh*
Click to expand...
Click to collapse
I copied the file debuggerd from another phone, that was not yet updated, to mine. Then the OTA update ran fine.

You must find an identical (same md5 hash check) file from an other device and copy it over the tampered one, without running "stick mount" until the ota installs.

Related

[Q] B117 update - assert failed: apply_patch_check

Hi there,
for some time now I have been trying to update B116 to B117 getting the same error message every time:
View attachment 2311424
assert failed: apply_patch_check ("/system/app/HwCloudDrive.apk" ... )
E:Error in /sdcard/HwOUC/update.zip
(status 7)
I am guessing the update does not match the HwCloudDrive.apk (not sure, new to this). What have I tried:
1. Check the /system/app/HwCloudDrive.apk - not found in the folder, nor anywhere else on the phone. Searched the web, downloaded one apk, install failed for no reason (reason not stated, just that it failed)
2. Restoring factory settings several times
3. re-downloading many times
4. updating online as well as localy
So far nothing worked out. Some details about my phone:
Its P6-U06, android 4.2.2, baseband IMC1202_PENTA, kernel 3.0.8-00821, build B116SP01, bought in China, using New Zealand SIM (could this be a problem?)
Any help would be much appreciated
Thanks to all!
Same issue updating error
Hi! I'm stucked with the same problem, I have tried to update it from external, wipe all data but nothing is worked, did you find a way??
ouzoliny said:
Hi there,
for some time now I have been trying to update B116 to B117 getting the same error message every time:
View attachment 2311424
assert failed: apply_patch_check ("/system/app/HwCloudDrive.apk" ... )
E:Error in /sdcard/HwOUC/update.zip
(status 7)
I am guessing the update does not match the HwCloudDrive.apk (not sure, new to this). What have I tried:
1. Check the /system/app/HwCloudDrive.apk - not found in the folder, nor anywhere else on the phone. Searched the web, downloaded one apk, install failed for no reason (reason not stated, just that it failed)
2. Restoring factory settings several times
3. re-downloading many times
4. updating online as well as localy
So far nothing worked out. Some details about my phone:
Its P6-U06, android 4.2.2, baseband IMC1202_PENTA, kernel 3.0.8-00821, build B116SP01, bought in China, using New Zealand SIM (could this be a problem?)
Any help would be much appreciated
Thanks to all!
Click to expand...
Click to collapse
Hi there,
nope, I haven't found the way. I tried a few more time since the post, no change, still the same problem. I have posted the message on huawei support, no reply. I'm at the stage of no-trying anymore, waiting for the next update and see...
Mrpinkman said:
Hi! I'm stucked with the same problem, I have tried to update it from external, wipe all data but nothing is worked, did you find a way??
Click to expand...
Click to collapse
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
rutenio3 said:
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
Click to expand...
Click to collapse
up
rutenio3 said:
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
Click to expand...
Click to collapse
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
extrem23 said:
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
Click to expand...
Click to collapse
I need more information.
Is very little information as to touch something random change.
A minitutorial would be nice.
thanks
i have the same problem
rutenio3 said:
I need more information.
Is very little information as to touch something random change.
A minitutorial would be nice.
thanks
Click to expand...
Click to collapse
assert faild: apply_patch_check("/system/app/MyBitCast.apk". "7e89b40472e4fe3d1459fb19f02b2901f281cea9".
"01c881b5cd2aad035329684eddd0471644914bb2")
update.zip is not correct
Format Sdcard And Try Again. If It Didnt Work Download Latest B125 And Try Again Hope This Works.
Please supply more info about this fix.
extrem23 said:
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
Click to expand...
Click to collapse
Please explain: what line should be erased from this file?
Thanks
rainbringer said:
Please explain: what line should be erased from this file?
Thanks
Click to expand...
Click to collapse
Yes please explain a little further. I am having update issues as well.
My Huuawei Ascend Mate MT1-U06 Found an OTA Update HwOUC, I downloaded it, and when I try to apply the update it fails.

Galaxy Note 4.3 update as of 12/9/13 - discuss all 4.3 upgrade issues here

It can be downloaded via Kies or checking for software updates via About Phone
Someone who is downloading this before applying it grab a copy from your/cache folder and post it here please
im downloading an update now sweet
you can use kies to download the update
kintwofan said:
Someone who is downloading this before applying it grab a copy from your/cache folder and post it here please
Click to expand...
Click to collapse
grabbing it right now.
Nice...
Why is the right door always locked?
hasbrobot said:
Nice...
Why is the right door always locked?
Click to expand...
Click to collapse
or atleast i am trying to. i have root access and trying to copy/past from the cache folder to external sd or any other location for that matter seems to be failing. first time attempting this. what am i forgetting?
Keyan said:
or atleast i am trying to. i have root access and trying to copy/past from the cache folder to external sd or any other location for that matter seems to be failing. first time attempting this. what am i forgetting?
Click to expand...
Click to collapse
Is the file actually there but you aren't able to copy it over to external SD?
blazinazn said:
Is the file actually there but you aren't able to copy it over to external SD?
Click to expand...
Click to collapse
it is definitely there from what i can tell. It's named update.zip, it was modified today, and it is 614MB
maybe it wont let me grab it because the phone is on? should i power off and grab it via usb cable? currently trying to modify it via Root File Manager App.
Keyan said:
it is definitely there from what i can tell. It's named update.zip, it was modified today, and it is 614MB
maybe it wont let me grab it because the phone is on? should i power off and grab it via usb cable? currently trying to modify it via Root File Manager App.
Click to expand...
Click to collapse
Is it giving you any kind of error? Since it's Write only, you'll probably have to change the permissions to be able to copy it from the cache folder. You should be able to do it with Root File Manager. I know I can with Root Explorer.
blazinazn said:
Is it giving you any kind of error? Since it's Write only, you'll probably have to change the permissions to be able to copy it from the cache folder. You should be able to do it with Root File Manager. I know I can with Root Explorer.
Click to expand...
Click to collapse
well root file manager says it was read/write for the owner so i changed the permissions to read/write for all users. then i attempted to rename it to 1update.zip.....and then the file disappeared.
Keyan said:
well root file manager says it was read/write for the owner so i changed the permissions to read/write for all users. then i attempted to rename it to 1update.zip.....and then the file disappeared.
Click to expand...
Click to collapse
Weird, will it let you download it again since you renamed it?
blazinazn said:
Weird, will it let you download it again since you renamed it?
Click to expand...
Click to collapse
i tried running software update again and it gave me an error "Your device has been modified, Software updates are not available"
wellllllllllllll it looks like I botched it up big somehow. I definitely didn't delete the file. damnit
I'm d/l via OTA
fatesealer said:
Galaxy Note 4.3 update live as of 12/9/13
Click to expand...
Click to collapse
This is Galaxy Note 2 forum
rosedog said:
I'm d/l via OTA
Click to expand...
Click to collapse
I wonder what feature I'm NOT going to get...
---------- Post added at 02:21 PM ---------- Previous post was at 02:19 PM ----------
Keyan said:
i tried running software update again and it gave me an error "Your device has been modified, Software updates are not available"
wellllllllllllll it looks like I botched it up big somehow. I definitely didn't delete the file. damnit
Click to expand...
Click to collapse
run Triangle away and enable tracking and reboot (if you are already turn off tracking > reboot > turn on tracking > reboot ~ status should be normal now).
Keyan said:
i tried running software update again and it gave me an error "Your device has been modified, Software updates are not available"
wellllllllllllll it looks like I botched it up big somehow. I definitely didn't delete the file. damnit
Click to expand...
Click to collapse
Does it say say your device is modified under Menu > Settings > About Phone > status?
Try rebooting the phone.
blazinazn said:
Does it say say your device is modified under Menu > Settings > About Phone > status?
Try rebooting the phone.
Click to expand...
Click to collapse
i created a 0byte file named update.zip in the cache folder and rebooted, and now it is telling me it is ok to install. (my battle level is below 50% so it wont let me). so i cured the modified error. but the actual download is still MIA. says device status is normal. it was probably kicking that error because it couldnt find the update.zip since i somehow renamed it and it decided to play Where's Waldo.
Keyan said:
i created a 0byte file named update.zip in the cache folder and rebooted, and now it is telling me it is ok to install. (my battle level is below 50% so it wont let me). so i cured the modified error. but the actual download is still MIA. says device status is normal. it was probably kicking that error because it couldnt find the update.zip since i somehow renamed it and it decided to play Where's Waldo.
Click to expand...
Click to collapse
That's odd, mine is at 16% and d/l on LTE. I'm stock rooted.
Keyan said:
i created a 0byte file named update.zip in the cache folder and rebooted, and now it is telling me it is ok to install. (my battle level is below 50% so it wont let me). so i cured the modified error. but the actual download is still MIA. says device status is normal. it was probably kicking that error because it couldnt find the update.zip since i somehow renamed it and it decided to play Where's Waldo.
Click to expand...
Click to collapse
Strange that the download just disappeared. Have you tried searching for the file?
rosedog said:
That's odd, mine is at 16% and d/l on LTE. I'm stock rooted.
Click to expand...
Click to collapse
you can download it but you won't be able to install it until you are over 50% battery life.

[File request] debuggerd from KRT16S for LTE version

Nexus 7 2013 LTE
I found one already here:
http://forum.xda-developers.com/showpost.php?p=47642071&postcount=10
But it seems to me that it's for the Wi-Fi version.
So if anybody could please provide the LTE version I could update from 4.4 to 4.4.2.
Thank you very much in advance!
curiousde2002 said:
Nexus 7 2013 LTE
I found one already here:
http://forum.xda-developers.com/showpost.php?p=47642071&postcount=10
But it seems to me that it's for the Wi-Fi version.
So if anybody could please provide the LTE version I could update from 4.4 to 4.4.2.
Thank you very much in advance!
Click to expand...
Click to collapse
debuggerd from KRT16S (deb/LTE).
gtj0 said:
debuggerd from KRT16S (deb/LTE).
Click to expand...
Click to collapse
Thank you very much!
But how do I replace it, as I saw that the mentioned Wi-Fi version came in a flashable zip file?
Or can I just overwrite it with a file explorer like any other file?
curiousde2002 said:
Thank you very much!
But how do I replace it, as I saw that the mentioned Wi-Fi version came in a flashable zip file?
Or can I just overwrite it with a file explorer like any other file?
Click to expand...
Click to collapse
If you are rooted, then yes you can remount /system read-write and just overwrite the file with a file explorer or with adb push. If not, I can create a flashable zip for you. Let me know.
EDIT:
Attached the flashable...
gtj0 said:
If you are rooted, then yes you can remount /system read-write and just overwrite the file with a file explorer or with adb push. If not, I can create a flashable zip for you. Let me know.
EDIT:
Attached the flashable...
Click to expand...
Click to collapse
I tried to install the flashable zip with TWRP but it failed.
Then I pushed the unzipped file you uploaded first via ADB.
The process was finished without error but the timestamp of the file remained the same, 08dec, while yours is 10dec.
Nevertheless I tried the update to 4.4.2 via sideload again, and it failed again with the same error message, something like "system/bin/debuggerd has unexpected content".
Could you update to 4.4.2 with your debuggerd file?
curiousde2002 said:
I tried to install the flashable zip with TWRP but it failed.
Then I pushed the unzipped file you uploaded first via ADB.
The process was finished without error but the timestamp of the file remained the same, 08dec, while yours is 10dec.
Nevertheless I tried the update to 4.4.2 via sideload again, and it failed again with the same error message, something like "system/bin/debuggerd has unexpected content".
Could you update to 4.4.2 with your debuggerd file?
Click to expand...
Click to collapse
Was the device in recovery mode or booted normally when you tried the adb push? If in recovery, was /system mounted? What was the failure in TWRP with the debuggerd flashable file and what's the exact filename of the 4.4.2 update file you're using? That'll tell me the exact version of debuggerd you'll need to pass the checksum validation.
gtj0 said:
Was the device in recovery mode or booted normally when you tried the adb push? If in recovery, was /system mounted? What was the failure in TWRP with the debuggerd flashable file and what's the exact filename of the 4.4.2 update file you're using? That'll tell me the exact version of debuggerd you'll need to pass the checksum validation.
Click to expand...
Click to collapse
I did all this with the Nexus Root Toolkit made by Wugfresh.
The device booted normally when the adb push took place.
I added two screenshots, one of the zip install and the other one of the update.
The 4.4.2 update file is from the also failed OTA update which I found in the cache folder and then saved.
The filename:
f221553ab745f4671e2c2f6a2cb0e4bf857886ea.signed-razorg-KOT49H-from-KRT16S.f221553a.zip
curiousde2002 said:
I did all this with the Nexus Root Toolkit made by Wugfresh.
The device booted normally when the adb push took place.
I added two screenshots, one of the zip install and the other one of the update.
The 4.4.2 update file is from the also failed OTA update which I found in the cache folder and then saved.
The filename:
f221553ab745f4671e2c2f6a2cb0e4bf857886ea.signed-razorg-KOT49H-from-KRT16S.f221553a.zip
Click to expand...
Click to collapse
Ahhhh. I had a typo in the updater script. Try this one. I tested it this time.
gtj0 said:
Ahhhh. I had a typo in the updater script. Try this one. I tested it this time.
Click to expand...
Click to collapse
SUCCESS!!!
Everything worked perfectly, installation of the zip file took about one second, the sideload update a little bit longer
Thank you very much again for your help !!!

[Q] Need debuggerd file for Nexus 7 2013 (wifi) 4.4.2

I can't update using OTA or the sideload method since stickmount seems to have corrupted the debuggerd file. I get the error "system/bin/debuggerd has unexpected contents" while updating so I need the debuggerd file for 4.4.2 of my device. I tried searching but can't find it anywhere.
So does anyone have such a file that'll make updating work again?
Any instructions would also be greatly appreciated
I managed to find the correct file from here - http://forum.xda-developers.com/showthread.php?t=2566488 .
After I moved the file to /system/bin/ I was able to update! However, I did lose root, but regaining boot is easy.
For future reference, Stickmount makes a copy of the original debuggerd in the same directory, it's named debuggerd.backup.

[Q] Where is the ROM being downloaded to my phone?

I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
glfngmble said:
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
jhedfors said:
/data/data/org.lineageos.updater/app_updates
Click to expand...
Click to collapse
Thank You.
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
rigattoni said:
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
jhedfors said:
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
Click to expand...
Click to collapse
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
rigattoni said:
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
Click to expand...
Click to collapse
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
jhedfors said:
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
Click to expand...
Click to collapse
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
rigattoni said:
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
Click to expand...
Click to collapse
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
jhedfors said:
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
Click to expand...
Click to collapse
the guys in the G4 forum are mostly connected to the unofficial version. a complete manual installation is required.
But there are some rumors in the German forum, who are using the official LineAgeOS version, where the updater script is not working.
I´ll wait for the next update in a week... may be it´s just a minor issue which will be fixed soon.
is it possible to change that path?
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
darrylhadfield said:
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
Click to expand...
Click to collapse
Thank you!!!! :victory::victory::victory: It works!!
rarmz said:
Thank you!!!! :victory::victory::victory: It works!!
Click to expand...
Click to collapse
Happy to help!
Now, if I can just get the attention of whoever the device maintainer is, for the Note3, to figure out the TWRP scripting issue...

Categories

Resources