[G313HZ] Is there any way to compare TWRP recovery versions?

[G313HZ] Is there any way to compare TWRP recovery versions? - Samsung Galaxy Ace 4

I'm using G313HZ from Vietnam.
I tried all twrp versions including the official ones but all resulted in white screen glitches, except for 1. It's custom made specifically for this g313hz and that works without glitching.
That white screen glitch, I want to fix it myself. How can I tell what is done in that recovery.img? Is there anybody who has any experience with this device?

Related

Rogers GSM XT910 Help/Questions

Not too long ago I bought a XT910 from rogers used off a person. It had a problem,it wouldn't boot pass the rogers screen, well I got it once or twice, just to root it and it always booted fine in BP hardware + AP boot but no other way. After tinkering I got BMM installed, and was able to install any non stock based ROMS (AOKP types iirc).
I was wondering if anyone else has had a similar problem and if there is a way to get stock based roms like catalyst and Artmod to boot properly.
Or do you think there is some hardware problems on it? Like I said, non stock based roms seem to work fine, well some have a small lag issue on touching the screen and actions but so far Carbon 4.3 JB rom I have installed with the JBX kernel seems to be going fine (Even have GPS working fine too)
I just wanted to know anyones opinion on the matter. (oh, I bought the phone for only $80 CDN, figured it was a deal)
EDIT: BMM shows a Red LED when attempting to boot stock roms

This never looks like a hardware problem!

[Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)

Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r

expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?

illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks

Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4

[SOLVED]Touchscreen died after flasing the wrong rom on sk17i

I flashed Iced Bean 4.0 on my xperia sk17i and i think my touch screen died because of it, That rom has aroma installer and there was no my device on that list so i chose xperia pro. Installation was successful but touch screen didnt work. I reverted to stock using flashtools and it still doesnt work. Is there any way to fix this problem? i really need to try something so pleas suggest.
Just to be clear i'm not blaming on anybody, it is total my fault. I'm fully aware of risk installing custom roms so pleas help in any way you can
Thanks in advance

Have you tried to flashing a new kernel which was made for the phone? As far as I know drivers areusually stored within it in Linux / Unix systems so it might apply here for the touch screen as well.

i tried using command fastboot flash boot boot.img and generally did not work. I have unlocked bootloader. I had hard time finding guide to do that for my phone. I did revert to stock using flashtools and ftf file.

When you say fastboot didn't work, do you mean it could not connect to the phone? Where you in fastboot mode when you tried it?
I recently put the 4.4.4 AOPK rom (Link) on my phone and had trouble getting into fastboot to flash the required kernel, I think I solved that by using the flashtool.
If flashing the stock kernel doesn't fix the issue, perhaps using a custom one, which works with ICS, will help?
You can find some here: http://forum.xda-developers.com/showpost.php?p=47407355&postcount=3
-edit-
does this thread help you? [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)

Fastboot worked fine, but any custom kernel after successful flashing didn’t work. I have installed managed to install xperialegacy cm11 it has custom kernel and it didnt fix touch screen. I will try the link you posted. On the side note i bought another sk17 today, yes i love this phone LOL xD

Yess, million times thank you . I made it using this tutorial
here is what you have to do for fix your Bricked touchscreen.
What you need for that is any custom rom with an aroma installer.
1. Flash suitable firmware with Flashtool ( i flashed .587 Because i used Zellycream rom V4 )
2. Then Install any ics Kernel that you like (I installed messa hybrid kernel v4.3 )
3: Then install Any rom that has Aroma installer in it and does support your device, via Cwm recovery (I installed Zellycream V4)
3. While installing the rom choose ST17i in Aroma instead of SK17i
4. Reboot after installation is completed.
5. Wait until phone is On homescree.Nopw touchscreen should work but h/w keyboard not
5. Reboot again into CWM install "keymap_for_pro_XXXX.zip
Link here For Keymap Mini pro
6. Reboot phone again.. Now keyboard and touchscreen should be working. Also options for h/w keyboard should appear now.
Good luck,
It did worked for me hopefully its also going to work for you.
Notice : At first your Touch might not responce how it was before, but give it a time it will work fine after some hours or day or it might never work like before.Mine touch screen worked normally after 8 hours of installing the rom with this method.
Click to expand...
Click to collapse
Now i have questions. Can for some reason touchscreen die again? and also which rom do you recommend for good battery and camera? i like stock but i find it tedious to root and remove all the unwanted apps only to free up a couple of MB and potential screw something
Update: I see that i need to flash a zip which fixes tochscreen. when installing new rom. Is this hardware or software problem?

It would surprise me if the screen died again from the same issue, as the harmful code should have been overwritten by the fix.
I am not a developer though, just a normal user with some basic linux knowledge.
I'd suggest trying out Real ICS. I think I ran it before I got my new phone (I just recently started using the Mini Pro again) and can't remember having any complaints back then.
Other than that you could just go through the rom list. There are some which claim to be focusing on performance, I haven't tried them myself though.
I currently use AOKP kitkat (with some modifications, see this post) but I cannot yet if I'll stick with it. Maybe gonna try out this one http://forum.xda-developers.com/showthread.php?t=2277199 next.

I think im going to stick to the stock for the now. Camera is the best there

I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.

Bucov said:
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Click to expand...
Click to collapse
I'm confused. Didn't you solve the issue already?
If the damage is permanent, then maybe the touchscreen got damaged by using the wrong rom?
If you really want to have two working phones, you could get a replacent display from ebay. They start at around 30€ these days.

[Q] Gapps w/o Recovery // TWRP for GSI9.0 // Others

Hi,
last week I bought myself a Huawei P20 Lite as this one seems to be good comprise between size, speed and price and all together I find this device quite nice.
However I'm not a big fan of this ROMs, it's bloated and you have to confirm on each and everyhting, so I tried to reduce this dramatically and I began a long journey....
Unlock the bootloader
When I bought the device I wasn't aware about the issues that I may face (Downgrad, additional 4 Euro to spend) but OK, I thought it would be worth....
Installing Recovery
..but I couldn't be more wrong. It seems that there's no working TWRP for this device out there. I tried a lot, both on 8.0 and 9.1 but each time I tried to
wipe cache/dalvik the whole system got stucked and wasn't able to show the boot animation. So, assuming that there's really no working recovery out there, I continued to
directly flash different ROMs and try out my luck.
Rooting
This wasn't as hard as I though first, at least, as long as the ROM I've used had an advanced Reboot-Menu with the possibilty to boot to recovery, otherwise you end up somewhere in the desert and
may not be able to restart with boot.
The problem is, that this device required to patch the RECOVERY_RAMDISK partition, so in order to have Magisk booted, you required to use the Recovery. No big deal: just Power up
using VolUp and Power until the Huawei logo appears... normally.. It didnt work in more than 50% of the times...
Gapps (or Magisk)
OK, as I already indicated, I tried lots of them, but to be honest, none of them really convinced me (all was done on EMUI9.1 "AB" and not EMUI8 "A only")
GSI Phh Treble: nice, but this is one of thinks I did not checked in depth, as almost all (?) are based on this one...
OmniRom from OpenKirin: works perfectly out of the box, SafeteNet is working, Magisk can be installed, but no advanced boot menu and I find it a little bit overloaded...
MicroG ufOffical: I would go with it, everyhting worked, it's slim BUT I couldn't get my Banking-App working, not even after appliying multiple MagiskHide Prop-Settings...
Descendant: This one was by far my favorite... Really slim, advanced reboot-menu, but I couldn't flash Gapps. OK, so I tried MicroG: this can be installed using Magisk. After some trouble (e.g. you have to install DroidGuardHelper so that the OS recognizes an "Update") I got MicroG working, but I coulnd't get it with my Banking-App. In this ROM I couldn't even apply any MagiskProp Hide-Settings. Only Post-FS worked. OK, as I'Ve failed using this approach, I thought: maybe I can use Gapps with this image.... but as I stated at the beginning: I do not have any working Recovery.
So my questions:
Is there any working Recovery out there? TWRP 3.3.x supports to be flashed in RECOVERY_RAMDISK (and there's also offical support for P20 Pro) As of now I wouldn't even care about decrypted data, but at least be able to wipe and do a factory reset....
Or: Is it possible to install Gapps from a running (rooted) system?
Or: can I patch system.img with Gapps before flashing it to the phone?
But perfectly: did anyone get Descendant running with MagiskHideProp? Maybe even got MicroG running on it?
I'm currently out of ideas, did someone else had such a trouble with that device?
Best regards,
Peter

Well, yes. Kinda the same as you but I didn't try that many roms. I tried a fair bunch of twrp versions though. And I managed to use twrp to flash roms and if I remember well even do a dalvik/cache wipe with one of them - but I might be imagining that one. It is worth noting that you can actually use some twrp versions for other huawei devices on the p20 lite. Try at your own risk. There is a lot more development going on for the p8 lite (2017) for example. I tried the lineageos version that was posted herefor that device and it worked quite well.

Weird problem of ghost touch & image retention.

So guys when I got my phone (around 1.5 years back), I didn't face any kind of ghost touch issues or image retention problems(till 1.2 years). But as soon as I unlocked bootloader and installed custom roms, I started facing image retention problem but no ghost touches. Then I installed MIUI again, but this problem was still there. So, I used Twilight to solve this problem. Then again I unlocked my bootloader and started flashing custom roms, and now I face ghost touches, screen freezes and image retention problems. Then again I installed MIUI latest version using Mi flash tool but still I was facing ghost touch issues. So I though of installing this MIUI version(the oldest one): beryllium_global_images_V9.6.14.0.OEJMIFD_20180730.0000.00_8.1_global
and after installing this the ghost touches are gone but the screen retention problem still persists(without Twilight fix).
So, is there any way to fix this retention problem by using some other MIUI version?
When I unlock the bootloader and flash custom roms over this version of MIUI: beryllium_global_images_V9.6.14.0.OEJMIFD_20180730.0000.00_8.1_global
then I never face any ghost touches or other problems, but as soon as I update the custom rom from TWRP, then again I face ghost touch issues. I even tried dirty flashing old firmware but it didn't work.
So I thought maybe its due to the MIUI version installed before flashing twrp and custom roms and somehow after updating the custom rom/flashing some other rom, the vendor/firmware is changed and this leads to ghosting and retention.
The problem is everything started when I started flashing custom roms 3 months back, before it was completely fine with MIUI. (And yeah I'm flashing MIUI and locking the bootloader correctly).
And I can't get my display changed as the phone is out of warranty.

Android 10

try some custom kernels like lawrun, they have the latest screen drivers. If it does'nt work wipe everything with TWRP and start fresh. I recomend MIUI.EU stable. it is better than official global ones, more features, less bloatware and more fixes. All AOSP roms are not 100% stable. Also, everytime you make some change in TWRP like wiping or installing something, make sure to reboot to recovery before proceeding.

Better Mobile App

welcome