Hello, please i really need help
so tried good lock (Samsung systemUI), after that, the phone become unstable... I uninstalled it and the phone had a lot of fc of systemUI and other apps and random reboots, and sometimes it boot into recovery on its own sometimes into download mode, so i flashed another official firmware and did a factory reset , but no luck , then i flashed a ported Rom (Dr.ketan Rom) now my phone don't do a lot of fc and don't reboot into recovery and download mode on its own , but still having a lote of random reboots and a lot of freezes, any ideas guys? i looked everywhere but nothing
Same problem as you, but it's worst : I tried latest Good Lock 24.0.10 and after uninstalling it, I got a popup saying "SystemUI has stopped working", with black screen and can't do anything else than accessing menu with Lock Key (with reboot, shutdown buttons, etc.) :/
Tried to reflash ROM with ALEXNDR ROM for Note4 but same problem. Any solution ? I'm trying to restore Good Lock latest apk through flashable .zip to see if I can re-use my phone.
Related
Hi Guys,
I am having trouble with my i9505. When I am trying to boot it gets till the Samsung Logo and then nothing happens. Sometimes it reboots, sometimes the Display stays black. Sometimes it boots to the lockscreen and then reboots.
Here is what I tried to do:
- Factory Reset
- Flashing new Custom Rom
- Flashing Stock Rom via Odin I9505XXUFNB8 & I9505XXUBMGA (rooted and also not rooted)
- Flashing only Modem and Bootloader
- Flashing different Custom Recoverys and Stock Recovery
Sometimes I also can not boot into Recovery. I can always boot into Download Mode.
I already bought a new Battery (no changes). When charging the same behaviour.
ONE MORE THING: Phone always crashes seconds before getting to the lockscreen while booting! Is any hardware triggered in this moment (like a special ram, memory or something???)
So for people like me I want to start a threat concerning the most frequently HARD BRICKS.
I found nothing like this in any other threat so please do not close!
After installing an incompatible ROM by mistake now whenever I start or reboot my N910C I get a weird screen with random line for 1-2 seconds and then it boots normally.
Any way to fix that?
I've install the original rom with odin but with no result.
hi guys i have an issue with my device (i9500) since i had a bad efs partition which i successfully restored from a backup.
The device works perfectly, but as soon as you lock it, and wait a few seconds, you can't unlock it anymore. Screen stays black, and the only way to get it started again is by removing the battery. Then it keeps on working perfectly, apps, games, everything is fine, as long as you don't lock it (by pressing powerbutton or auto lock)
Either then it crashes or restarts.
Things i've done already:
- Soft reset
- Hard reset + cache wiped
- tried many different roms
- fresh stock rom installed with Odin.
Problem still persists.
Disable lockscreen till you find another solution.
Hi Guys,
I am facing a peculiar kind of problem in my phone (G900F) since yesterday.
What happens is that, if I tried
i) To restart my phone from the phone (reboot menu), the phone stuc in boot screen and then vibrate twice then after 5-10 sec the phone start rebooting all along once again with 2 vibration and this process keeps repeating until I pull out the battery.
ii) To access recovery (both hard- key combination or from reboot to recovery option in phone), the phone reboots and it stays in the initial screen for about 45 seconds and then the screen went black and freezes there until I pull out the battery.
iii) To access download mode ( both hard- key combination and reboot to download mode option in phone), there seem no problem.
The weirdest part is that, if I remove the battery for 5-10 min and re-insert the battery and do any of the above options; the phone reboots and i get the home screen loaded successfully with no problem . I can also get into my recovery after this 5 mins switch off just like the above. I also found the phone lags a bit in this home screen.
I almost did all the combination to get off this problem (stated below) but I keep getting this problem again and again.
I was in Sixperience v 3.1 with Pheonix Kernel v 10 and Philz CWM recovery and tried the below to try to fix the issue
1. Re-flashed Kernel from Recovery (Also, tried to re-flash kernel after uninstalling Xposed but no use)
2. Re-flashed Modem and Bootloader from ODIN once again (G900FXXU1CPF7_BL_G900FXXU1CPB8_MODEM_LTE.tar)
3. Reflashed ROM once again as a fresh install through Philz recovery.
4. Restore the cwm backup from recovery (which was backed up a week before.)
5. Flashed Samsung Stock MM ROM (G900FXXU1CPFH_G900FPHN1CPFD_PHN.tar.md5) as a fresh install.
After this stock ROM installation is done, the phone struck at SAMSUNG flashing logo and the blue LED keeps glowing for more than 30 mins)
Nothing works. ? Any idea on what is to be done to fix this issue? I am not sure, what i did but this problem keeps coming even after trying of all of the options since yesterday.
Please help to with your expertise.
Hi guys,
Trying to fix a friends x704f wifi only, but no luck.
It had Lineage 18.1 on it, and for whatever reason he did not like that, and went on to reflash stock with Lenovo's Rescue and Smart assistant which showed it a success rescue, but now Tablet boots to EULA, arrives to choose wifi and it crashes and reboots constantly, with no wifi icon being shown.
Lenovo rescue installed TB_X704_S000060_220916_ROW, so I factory reset it a few times from recovery, went through rescue again, installs same ROM, success, yet again it crashes at network selection, of if you do not touch anything, it crashes itself after about 20 seconds after being booted and if i hold the Power button and select shutdown, briefly the standard desktop shows with icons and than it crashes, so guessing ROM is there, it just can't boot.
Tried with QPST and latest ROM, but on eMMC xml selection I get error Document error on element program and name/value true.
Guessing baseband or some other thing should of been backed up before flashing stock again? if it helps, OEM lock is OFF, secure boot is ON what I can see from fastboot.
Thanks.
There must be something wrong with the persist partition, flash the persist.img again.