Database Info

[MOD][TEST] ART WhatsApp Fix 4.4

I happened on this post whilst trying to get some SystemUI.apk mods to take on ART:
http://forum.xda-developers.com/showthread.php?p=47604251#post47604251
I tried the modified libart.so file by @cernekee on my Moto X VZW Dev Ed (because a working phone needs to be broken fixed) and it seems to work. I've made a flashable file to remove the leftover WhatsApp parts and flash the new libart.so if you'd like to give it a go.
Steps to install:
1. Switch to ART. (You need to have stock SystemUI.apk and SystemUI.odex - see attached).
2. Flash zip in recovery
3. DO NOT WIPE DALVIK/CACHE
4. Reboot and profit reinstall WhatsApp from Play Store if needed.
As usual, make a backup first and please don't flash this if you are uncomfortable fixing a bootlooped phone!
{
"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"
}
If you screw up and wipe dalvik/cache, just flash the stock libart.so zip (attached) reboot then reflash the Mod.

Will this work on the brazilian firmware?

No clue. But this is a Nexus 5 libart.so and it's working on a Vzw Moto X so it most likely should. This isn't something I'd try with a locked bootloader though.

Just tried here and it's working perfeclty! Thank you!
I didn't even have to reinstall Whatsapp.
One question though: what happens if I try to wipe cache one day? Will it bootloop the phone?

MaKTaiL said:
Just tried here and it's working perfeclty! Thank you!
I didn't even have to reinstall Whatsapp.
One question though: what happens if I try to wipe cache one day? Will it bootloop the phone?
Click to expand...
Click to collapse
Yes but the fix is easy:
Hold power button (shut off) > boot to fastboot > boot to recovery > flash the stock libart.so > reboot > flash nexus 5 libart.so > reboot.
It has happened to me once so far lol.

question
i dont understand what do i have to flash , moto x libart, moto x stock libart , o systm ui odex ... can i help me a bit plx

bastianvy said:
i dont understand what do i have to flash , moto x libart, moto x stock libart , o systm ui odex ... can i help me a bit plx
Click to expand...
Click to collapse
Do you have root and custom recovery?

chaoslimits said:
Do you have root and custom recovery?
Click to expand...
Click to collapse
yes i do

bastianvy said:
yes i do
Click to expand...
Click to collapse
OK.
Make a backup of your phone.
Download all 3 zip files.
Enable ART if you have not done so already
Reboot and let Android optimize itself. Whatsapp should crash at this point.
Reboot into recovery and Flash Moto X_ART_Libart.so.zip
Do NOT wipe cache/dalvik and reboot.:fingers-crossed:
If your phone boots fine, launch Whatsapp. :victory:
If your phone boots but you have no status or notification bar, flash SystemUI_VZW_Odex_Stock.zip; a mod is breaking SystemUI.apk.
If your phone does not boot (most likely because you wiped cache/dalvik), shut it down (hold power button). Then boot into recovery via fastboot and flash Moto X_ART_Libart_Stock.so.zip.

chaoslimits said:
OK.
Make a backup of your phone.
Download all 3 zip files.
Enable ART if you have not done so already
Reboot and let Android optimize itself. Whatsapp should crash at this point.
Reboot into recovery and Flash Moto X_ART_Libart.so.zip
Do NOT wipe cache/dalvik and reboot.:fingers-crossed:
If your phone boots fine, launch Whatsapp. :victory:
If your phone boots but you have no status or notification bar, flash SystemUI_VZW_Odex_Stock.zip; a mod is breaking SystemUI.apk.
If your phone does not boot (most likely because you wiped cache/dalvik), shut it down (hold power button). Then boot into recovery via fastboot and flash Moto X_ART_Libart_Stock.so.zip.
Click to expand...
Click to collapse
thanks ^^, i will let u know how it goes to me, (sorry for my bad english)

is there a whatsapp fix for ART without flashing this file via recovery?
i've only root permissions on my 4.4 AT&T

P910iii said:
is there a whatsapp fix for ART without flashing this file via recovery?
i've only root permissions on my 4.4 AT&T
Click to expand...
Click to collapse
I would strongly advise against touching anything in /system/lib without having a backup via recovery. Don't do it.
Edit: It's especially dangerous if you mistakenly wipe dalvik/cache.

Thank you, i'll wait 4.4.2

Is there any way to flash this on a stock recovery or by any other means? I have 4.4 with stock recovery, SlapMyMoto root and MotoWPNoMo.

dicarli said:
Is there any way to flash this on a stock recovery or by any other means? I have 4.4 with stock recovery, SlapMyMoto root and MotoWPNoMo.
Click to expand...
Click to collapse
The new version of Whatsapp supports ART i guess.... Try it once...

[URGENT HELP NEEDED]Stuck at flashing stock image

Hi guys,
I just tried to revert my nexus 5 to stock. I was running the stock rom with a custom kernel which caused a lot of lag issues for me.
What I did: fully wiped the device in TWRP and afterwards I let the Nexus Root Toolkit download and install the default 4.4.2 factory image. (flash stock + unroot)
However, during the process, it stucks at erasing userdata.
{
"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 afterwards, I decided to plug the device out and let it reboot. However, stucks at the bootanimation.
I am however able to boot into the bootloader and do the flashstock process again. Time after time it stucks at erasing userdata. Is this the final step of the process? the system is flashed to in theory it should be able to boot. When I try to boot into the recovery, it shows a 'dead' android.
Can someone please tell me what to do? I might have wiped the internal memory in TWRP which might be the cause.

sjondenon said:
Hi guys,
I just tried to revert my nexus 5 to stock. I was running the stock rom with a custom kernel which caused a lot of lag issues for me.
What I did: fully wiped the device in TWRP and afterwards I let the Nexus Root Toolkit download and install the default 4.4.2 factory image. (flash stock + unroot)
However, during the process, it stucks at erasing userdata.
So afterwards, I decided to plug the device out and let it reboot. However, stucks at the bootanimation.
I am however able to boot into the bootloader and do the flashstock process again. Time after time it stucks at erasing userdata.
Can someone please tell me what to do? I might have wiped the internal memory in TWRP which might be the cause.
Click to expand...
Click to collapse
Use a USB 2 port. USB 3 doesn't work well with adb.

aooga said:
Use a USB 2 port. USB 3 doesn't work well with adb.
Click to expand...
Click to collapse
I gave my usb 2 port a try and now it has finished flashing. THANK YOU VERY MUCH

sjondenon said:
I gave my usb 2 port a try and now it has finished flashing. THANK YOU VERY MUCH
Click to expand...
Click to collapse
No problem. Just remember that for next time

Soft-- Bricked after Phone Died, Please Help.

Ive looked through all the bricked threads and elsewhere and nothing seems to match my problem.
{
"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"
}
S-off. As you can see its been awhile since I have messed with my phone so forgive me. I found something that had what I needed and was stable(until now) and stuck with it.
So I connected my phone to a friends charger and it wasnt charging and it died. I got it charged and booted it up and it ran fine for about 2 minutes then apps started stopping and it rebooted, it now does this over and over. I tried the battery reset. The last apps to crash are always google play services related so I tried to flash a gaaps zip in hboot.I tried uninstalling/deleting those apps, it still crashes. I tried to wipe and restore/install in twrp recovery(which it usually says is successful). Ive tried flashing RUUs in hboot they stop after the first reboot and boot normally instead of back to hboot. It wont connect to adb(I may have done something wrong there). But whatever I do it boots up exactly how it was before. If I delete/uninstall anything it comes back, if I add something anywhere other than the external sd it disappears.
Please help I cant afford a new phone right now.
Update: Without an sd card in the phone it wont reboot but all other things are the same, apps still crash, still cant do anything to recover.
Update: I tried another sd card and it prevents the reboot, but still wont flash anything in the bootloader.
Update: I formatted my sd card and it doesn't reboot with it in now, atleast not automatically, it reboots when certain apps are opened or randomly after a long period. Apps still crash and still no luck with any flashing or recovery. I tried clearing all app caches with titanium, no change.
I think the internal and system partitions may be corrupted and stuck as is after reboot, the weird thing is I can delete things or add things and the changes stay until reboot, then its back to its original state, is that possible?

Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x

piyushkohli97 said:
Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x
Click to expand...
Click to collapse
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.

Kane5581 said:
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.
Click to expand...
Click to collapse
So u keep the ruu or flash some ROM after that?
Have you tried different RUUs?
I also recommend flashing the firmware for whichever Android version you are using.
Try firmware from this link http://forum.xda-developers.com/verizon-htc-one-m8/development/wip-4-17-605-9-stock-resources-firmware-t3196906
Flash firmware after RUU flashing.
I recommend the latest ruu if you flash it u will not need to flash firmware.
In previous post I told you to reset your phone from stock recovery did you try that?

Fail to Boot after after Google Play system update (Boot reason : init_user0_failed)

Hello all,
I wanted to report something that happened to me yesterday:
I recieved the following notification:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I selected "RESTART NOW" and when the phone tried to restart, it failed to boot (it didnt even reach the boot animation) and went into recovery. Within recovery there was an option (I think it was called Boot reason) to show the error that prevented the phone to boot into the OS. This was the error:
I tried to pull the files but I couldn't get adb access within the 8T stock recovery. I tried to reboot the phone from recovery but it failed to boot and I was back in the recovery with the same error.
The way that I managed to boot the phone was to select to reboot into recovery (while being in the recovery), and then select to reboot the phone. That, for some reason rebooted the phone and it was able to boot into OS.
My 8T is full stock, with locked bootloader running OOS 11.0.5.6.KB05BA
Hope this is helpfull to someone.

I just received the same notification again. I am not sure if it is regarding the same update as yesterday because it was not applied, or if it is a new one. I have not tried to restart the phone.

I received the same notification but my phone restarted with no issues.
If you can back up the files from internal storage then do that and then flash OOS.

O wow. I'm glad that didn't happen to me either. I don't think you can reflash the OS. I sugget you back up everything just in case it doesn't want to restart later.

You can try manual update Google play system update from:
Security & Lock Screen --> Google Play system update
Btw, I had that notification yesterday, and for now everything is OK, and Google Play system update is "Septembar 1, 2020". Which version is yours?

I am on September 1, 2020. If I tap on it, it checks for updates and then says I need to restart to complete the update.

When I tap says, "your device is up to date"....

So I backed up the phone with the Oneplus Switch app. Copied the folder to my computer (had to zip it becaust the transfer was failing on a .jpg). Selected restart and was faced with the same issue. I restarted again from the recovery (without first rebooting to recovery as in the first post) and I saw a glimpse of the boot animation and then the phone restarted again. After that it booted into the OS and if I check for updated it says that the device is up to date.
Hopefully this will be the end of this issue.

the issue is the canary magisk and secure boot trying a different magisk version repatch boot img and boot it to flash it

I haven't rooted or unlocked the bootloader ever on this phone. My phone is full stock. Locked bootloader running OOS 11.0.6.9.KB05BA. I still get this error when I reboot my phone. Up till now, doing the reboot to recovery "trick" as in the first post, or reboot into fast boot from within recovery, then boot into recovery, then start the phone. Manages to boot the phone.
I just hope that someone can figure out what is causing this.

bad pixel said:
I haven't rooted or unlocked the bootloader ever on this phone. My phone is full stock. Locked bootloader running OOS 11.0.6.9.KB05BA. I still get this error when I reboot my phone. Up till now, doing the reboot to recovery "trick" as in the first post, or reboot into fast boot from within recovery, then boot into recovery, then start the phone. Manages to boot the phone.
I just hope that someone can figure out what is causing this.
Click to expand...
Click to collapse
You can try to download main-component apk from APKmirror, just download latest one (Januari), innstall it, and try redownloading the system update and restart. In my case, it restart just fine. And am on Cyberpunk H2OS 11.0.6.8, BL unlocked, Rooted

see the error, you may flash the third kernel.
just flash back the original boot img, and you can install Google Play System Update successfully.
you may suck in this error screen 1-2 times when reboot with third kernel, just exit and reboot, it will boot into system normally, don't worry.

Question Poco X3 Pro Bricked - Boots to Fastmode

I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.

crashykk said:
I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.
Click to expand...
Click to collapse
Reboot your phone and observe on the top part of the phone while there is the POCO logo showing.
1) If there is an unlocked lock icon on the top, you should be able to rescue with TWRP.
{
"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"
}
Type the fastboot code to get to TWRP again so you can flash ROMs.
Read here for ROM flashing tutorial.
https://forum.xda-developers.com/t/4288121/post-85137963
Step 16 is a must.
2) If you did not see this icon during booting POCO logo, chances are you accidently locked your bootloader with MiFlash. In this case, find Xiaomi repair center for warranty support.

I know how to flash a rom, but TWRP does not see my internal storage. Like it wasnt there.
edit:
I flashed Orangefox recovery and it did the trick. I was able to place some rom on internal storage and install it, but now i have 12 gb of storage instead of 233gb?
edit:2
I formated data and it went back to normal. Now i have my 256gb back.

I think you were encrypted, please read more online and follow rom flashing instructions. You didn't follow it that's why you were in trouble.

I flashed, rooted, unbricked a lot phones back in the Samsung S6 days. Even Redmi Note 5 Pro from xiaomi, but never heard of something like rom encrypting your access in recovery.
I didnt flashed custom roms on my Samsung s8 and s9, cuz they had fine software. MIUI 12 is so bad that I considered selling that Poco.

You didn't follow instructions, TWRP works perfectly fine. And the step you missed is Formatting Data partition after flashing ROM which decrypts it. (thus why you couldn't access internal storage or boot)
And you will run into same issue with OrangeFox aswell if you do the same mistake. Flashing procedure is a lot different in new smartphones.

I didn't follow, cuz I didn't know that flashing procedure is a lot different in new smartphones. I looked at it, it looked very similar, so I went with old habits. Now I know what to expect.