Mysterious problem after unbricking - K3 Note Q&A, Help & Troubleshooting

Hello,
I was having this ROM: LENOVO_K3_5.1_1552DEV_ROW_002_CUOCO92
and I was also using Xposed that was working normally. The xposed version was xposed-v71-sdk21-arm64.zip, it was working perfectly.
Unfortunatelly, I bricked my device and I unbricked following the steps and the archives of this video.
After I unbricked my device I flashed again the same rom and I tried to flash again the same xposed version (xposed-v71-sdk21-arm64.zip) but I couldn't.
I finally managed to install xposed-v80-sdk22-arm64.zip that was the only compatible but now it doesn't work properly.
When I open the properties menu, it is closed by itself.
Why Xposed can not work in the same rom after the unbrick procedure?
What happed to my device?
Should I had flashed other archives to unbrick my device?
Please help me....

Related

Broke WIFI on Brother's Phone

Help!
I was installing xposed on my brother's xt1095, and I borked it.
Here's what I did:
He started on stock 6.0 (bootloader unlocked)
I installed TWRP
Flashed xposed installer, supersu2.71, and then krait kernel.
It wouldn't boot
So I installed the kernel that I found in a thread for rooting marshmellow.
It boots, but WIFI doesn't work.
Any thoughts on what I should do?

Huawei P10 lite stuck on booting

Hi everyone,
While trying to install LineageOS (following the guide here) my phone is now stuck on "Your device is booting".
Note that I had my phone rooted before so OEM unlock and TWRP were already done/installed.
Unfortunately my backup seems to not have worked and I believe I might have erased more than I should, including system and vendor. So now I'm stuck with installing any OS to be honest.
My phone is an ARM64, prague, WAS-LX1A.
Can anyone help me please?
Thanks!
I was able to use the dload method to get back to stock rom.

Xposed sucessfully installed and rebooted but afterwards i get bootloops

So i sucessfully rooted my Huawei P8 Lite and installed TWRP. Then i tried to install Xposed v.89 for sdk23 (Android 6.0). The installation worked and it rebooted sucessfully, but after i installed the App on my phone it said xposed framework is installed but not active. So i tried to reboot my phone once more and this is when my phone started to be stuck in the huawei starting logo. I revoked everything and tried it a couple of times again and tried v85. It didnt change anything.
Can anyone help me with this because the virtual sensor module doesnt work without xposed framework being active and i just cant find a way to get it active and have the phone not get stuck while starting
My Huawei p8 Lite is running on android 6.0 with an ARM64 CPU
I hope anyone can help me with this.
Have you tried the uninstall zip?
You also shouldn't install a different Xposed zip if the one meant for your version didn't work. The others definitely won't work then.
Also, did you install any modules and tried to activate them? Maybe the module you activated is what caused the bootloop.
Sent from my Nexus 6P using Tapatalk

Root and Bootloop problem fix [Tested on RMX1993EX]

I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Lemmy554 said:
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Click to expand...
Click to collapse
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Almasd said:
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Click to expand...
Click to collapse
In Magisk Manager you have to "Tap to start SafetyNet check".
Oh I see. Thanks. It's ctsProfile: true. (Now I'm on stock rom with root)
Almasd said:
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Click to expand...
Click to collapse
How to unlock ur bootloader plz suggest me.
Risul49 said:
How to unlock ur bootloader plz suggest me.
Click to expand...
Click to collapse
I don't have RMX1993(EX) anymore. But below might help you.
If you are on ColorOS (Android 9) or RUI1 (Android 10) then you can directly follow the bootloader unlock tutorials on the internet. But if you are on RUI2 (Android 11) then you need to downgrade to RUI1 first.
I also did the same procedure.
But below is for RMX1901CN Realme X device procedure. I believe it would give you a hint.
1. I found Rollback_RMX1901_11_OTA_1190_all_EyyIUd8KYxPI.ozip (for Chinese version) firmware from Realme X Official Telegram group.
2. Then I opened it from the file manager and the device rebooted automatically and the downgrade firmware was installed. After that, I unlocked it with the DeepTesting app for RUI1 with instructions that I found on the internet.
Also, you might try this method: https://c.realme.com/in/post-details/1476520599785316352
Also, comments on this post might help (I have no idea Realme X2 Pro instruction is works for your device but JFYI): https://c.realme.com/in/post-details/1478098096796815360

Question Help with TWRP

i need help. i unlocked my bootloader, i attempted to install twrp. looked like it was successful. i go to recovery and i have this blue screen. HELP!
Oh this thread is here. Have you tried this?
[GUIDE] Unbrick Lenovo Y700 tablet
Windows guide, might work for other aswell. I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing...
forum.xda-developers.com

Categories

Resources