Develop Bugs

Galaxy ace 2 restarting itself.

My galaxy ace restarting itself. I try install roms , use odin , hard reset but non of them are working. Phone is opening and I can use phone for 10 seconds than it restart itself. Please help me.

jprice001 said:
My galaxy ace restarting itself. I try install roms , use odin , hard reset but non of them are working. Phone is opening and I can use phone for 10 seconds than it restart itself. Please help me.
Click to expand...
Click to collapse
Whitch rom you had install?

garak elim said:
Whitch rom you had install?
Click to expand...
Click to collapse
I can't install rom. Because my galaxy ace II is not giving respond for anything. Odin is not working , and wipe data is not working too..

And whitch rom do you have now. Stock or custom?

garak elim said:
And whitch rom do you have now. Stock or custom?
Click to expand...
Click to collapse
I have stock rom.

jprice001 said:
I have stock rom.
Click to expand...
Click to collapse
The phohe has low memory. Its normal when sometimes you got soft-reboot. But after 10seconds, its unsually.
When its soft problem the steps are:
- factory reset (when it not helped do next step)
- go to download mode and flash your rom via odin (when it not helped do next step)
- get root and uninstall bloodware (when it not helped do next step)
- try custom rom (when it not helped its probably hardware problem)
When its hardware problem the steps are:
- maybe is bad connection between battery and mobil, try to remove battery and give back (when it not helped do next step)
- maybe is bad battery , try new one or from other Ace II mobile (when it not helped do next step)
- I don't know , buy new mobile. ( this step must help you)

jprice001 said:
My galaxy ace restarting itself. I try install roms , use odin , hard reset but non of them are working. Phone is opening and I can use phone for 10 seconds than it restart itself. Please help me.
Click to expand...
Click to collapse
I have experienced this before. It's the death of your internal memory.
Only thing you could do is go to Samsung service centre to get it fixed or buy a new phone.
Sorry, mate.
Sent from my GT-I8160 using Tapatalk

jprice001 said:
My galaxy ace restarting itself. I try install roms , use odin , hard reset but non of them are working. Phone is opening and I can use phone for 10 seconds than it restart itself. Please help me.
Click to expand...
Click to collapse
The restart problem happened to me for the ace2nutzer version of the rom I downloaded here:
http://xda.mister-freeze.eu/XDA-files/ace2nutzer/CM11/codina/cm-11-20150714-UNOFFICIAL-codina.zip
Then I installed the ChronoMonochrome version and it managed to boot:
http://xda.mister-freeze.eu/XDA-fil...m-11-20150730-UNOFFICIAL-codina-universal.zip
However, I still could not get WIFI to work.... it seems that after flashing, the MAC address was set to 00:00:00:00. I know my router will never issue IP addresses to MAC addresses that are all zeroes.

S9 recurrent Rooting Problem - Screen o Death/Deep Sleep.

Brief :
Hello everyone,
I recently was asked by a friend to root his Samsung SM-G960F. I made sure to make a complete backup using ADB bridge and several other backup apps, in case anything happened.
I started using this tutorial :
Theandroidsoul - Samsung Galaxy S9 Root - (I'm sadly unable to post normal links because I'm a new user).
but due to certain unclarities, I was forced to follow another tutorial.
I ended up rooting using this method, following the instructions on this youtube video that seemed pretty straightforward and clear to me :
Waqar Khan - Video : watch?v=CfS0sEsAAtg
To resume it goes as follows :
1) - Installing TWRP :
- Toggling OEM Unlock and USB Debugging options.
- Using Odin.
- Flashing TWRP.
- Allowing modification on the system partition on TWRP.
- Wiping the data using TWRP and clicking on recovery afterwards..
- Flashing dm-verity and force encryption disabler zips.
---> TWRP fully functional.
2) - Rooting of the device :
- Flashing the N960F_Root_for_OEM_issue-devices from the SD card.
- Selecting "Patching the OEM and rooting with SuperSU".
DONE.
Note : It didn't contain anything about "Magisk" and according to the androidsoul website, I should've probably not allowed the System partition modification.
Problem :
The phone experiences now every now and then the Screen of Death/Deep Sleep : It gets blocked on the lock screen while it's partially showing it but stays unresponsive and I'm forced to hard reboot the phone faced with the apprehension and incomprehension of my friend.
I looked on the internet and the problem seems to be pretty recurrent. Many users are also experiencing this problem and like myself have no idea what to do. Some propose to install SOD-Killer to temporarily solve the issue. Some propose installing a custom ROM like elementalx without providing any further details on its compatibility with the root already installed above. Now even with SOD Killer, if the phone isn't charging at night, it gets discharged fast, and sometimes turned off by itself.
What are my options now ? How to repair this root, or undo that altogether ?
I read somewhere it might be because of KNOX not being completely/correctly disabled. Something must be triggering the SOD right ?
Is there an actual solution to this problem or should I go to stock ROM somehow ? Some users still experience this problem even if they rolled back to stock firmware. How to correctly unroot ? Can I unroot using my ADB backup or does it not include the partition system ?
I would be endlessly grateful if anyone could give me some of his time and help me solve this delicate situation.
Thank you very much for your help.

Up

Why are you flashing the N960F files to a G960F phone?
N960F is the Note9

*Detection* said:
Why are you flashing the N960F files to a G960F phone?
N960F is the Note9
Click to expand...
Click to collapse
Thank you for your reply.
Dear God, I just noticed that. I just followed the tutorial on theandroidsoul . com/ samsung-galaxy-s9-root / Would you please be so kind and help me fix it ? I really don't know what to do next. My friend's expressed his discontent many times now and I'm really embarrassed. I would be really grateful if you could help me.

Cretinosaurus said:
Thank you for your reply.
Dear God, I just noticed that. I just followed the tutorial on theandroidsoul . com/ samsung-galaxy-s9-root / Would you please be so kind and help me fix it ? I really don't know what to do next. My friend's expressed his discontent many times now and I'm really embarrassed. I would be really grateful if you could help me.
Click to expand...
Click to collapse
Why not try from the scratch again.
Like going full stock.
Atleast that's what i do on Xperia XZ.
I guess Samsung is difficult.

Cretinosaurus said:
Thank you for your reply.
Dear God, I just noticed that. I just followed the tutorial on theandroidsoul . com/ samsung-galaxy-s9-root / Would you please be so kind and help me fix it ? I really don't know what to do next. My friend's expressed his discontent many times now and I'm really embarrassed. I would be really grateful if you could help me.
Click to expand...
Click to collapse
Flash stock > Follow tutorial on XDA for the G960F

Use Odin to flash stock.
Get stock from sammobile website.
Then RESEARCH before rooting.

basicreece said:
Use Odin to flash stock.
Get stock from sammobile website.
Then RESEARCH before rooting.
Click to expand...
Click to collapse
Then never offer to do this for a friend ever again.

Thanks to all of you for your propositions. I will try to do like you said and get back to a stock ROM. I will indeed avoid to ever root for someone else again. This is too big a responsibility for me to take.

[A11/CTL1+ and A10/BTJ3+] [MOD] [S20 Ultra] JBNCK Fixes and Tweaks v2.0

Hi there,
I've combined some custom-kernel-like tweaks into a single flashable .tar file and I wanted to share it with you.
This .tar file contains:
-patched vbmeta image
-working magisk root with full Android 11 support
-magisk manager helper preinstalled
-a cleaned up boot screen + no bullsh*t on boot screen
-a cleaned up unlocked bootloader screen + no bullsh*t on unlocked bootloader screen
Prerequisites
-an unlocked bootloader
-firmware version CTL1 (A11)/BTJ3 (A10) or newer
-Odin 3.XX.X
-all data backed up
-fully functional brain
-stock recovery and firmware (this will not work if you have a custom recovery or run a custom rom)
STOCK BASED ROMS LIKE BEYONDROM WILL ALSO NOT WORK!
PLEASE NOTE:
-I am not responsible for a bricked device, please make backups and make sure to
always have the official firmware if something goes wrong
-flashing this requires you to factory reset your phone or else the phone won't boot
Instructions:
-unlock your phone's bootloader
-boot into download mode
-in Odin uncheck auto-reboot
-put the .tar file into the AP slot (If it doesn't work try USERDATA)
-after flashing boot into recovery with the key combination
-select factory reset and confirm (This will wipe everything from your phone)
-after factory reset reboot into system
-setup the phone and restore your backup (if you made one)
-Install Magisk and you're good!
If you have any problems
Please don't just comment "Doesn't work" and instead tell me about
the errors you encountered, your software info and other information
you think would be helpful.
Happy flashing!
If you still have questions make sure to ask them below
DOWNLOAD CTL1+: https://1drv.ms/u/s!AtNTTTF5vqOe73aVGDPSRGr5aria?e=dICFlS
DOWNLOAD BTJ3+: https://drive.google.com/file/d/1KqOGRbAy4fY1ghro4HoP-eDDYh4G7b5Z/view?usp=sharing

Tried it on my friend's phone,works great.Thanks

Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..

@[email protected] said:
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
Click to expand...
Click to collapse
This doesn't say anything. Can you tell me what custom ROM you are running? If you are on rooted stock also tell me.

Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..

@[email protected] said:
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
Click to expand...
Click to collapse
Geeeeeez! Update your phone! You have to have OneUI 2.5 BTJ3 or OneUI 3.0 CTL1 at least. What are you doing on 2.1? If you don't update, this will break your phone.

Okay buddy,ty..will do that.

Hi again m8,can i update Android 11,,One GUi 3.0,RP1A200720.012 G988B...

And ,or which file i have to use??

@[email protected] said:
And ,or which file i have to use??
Click to expand...
Click to collapse
Depends on the version. I don't want to be rude but how did you even manage to root your phone with this lack of knowledge?
If you update to Android 11/One UI 3.0 you chose the One UI 3.0 one. If you only update to 2.5 you chose 2.5. Remember to check the end of your firmware number:
There are supported firmware endings:
One UI 2.5:
-BTJ3
-BTJ4
One UI 3.0:
-CTL1
-CTL6
-Any One UI 3.0 firmware above that.
Download SM-G988B / Galaxy S20 Ultra 5G SM-G988B in Samfw - Samsung firmware download
Pick your CSC there, chose the newest one preferably (A11), press "Download on website", unzip it and flash it with Odin while in download mode. You should know how to do that.
After it's finished, complete setup (do not restore any backups yet!) and go into download mode again. Flash the file as AP or USERDATA (whatever works) and perform another factory reset. Done.

So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?

BCityModz said:
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
Click to expand...
Click to collapse
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha

JanBoyGamer23 said:
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
Click to expand...
Click to collapse
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.

JanBoyGamer23 said:
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
Click to expand...
Click to collapse
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.

BCityModz said:
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
Click to expand...
Click to collapse
That can't be an issue with the script as it doesn't modify anything related to the camera

JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
Ok I may have to make a copy of my girls phone and flash original back to the phone and go again.

JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
yea IDK, did it all over again, even booting up to make sure the cam was working. same thing black screen when i open the camera app.

ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??

frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
Short answer: Yes
Long answer: You are unlocking your bootloader and flashing a custom image so you lose your warranty and trip knox

frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
If you want to use s health: Download build.prop editor, grant it root access and and change the value of 'ro.config.tima' from 1 to 0

I'm desperate

My redmi 8 needed an update, I downloaded it, I restarted it, then the screen went black and no longer turned on
Before restarting, my cell phone said that if it was not compatible I would have to restart manually (data / system / updates)
The name was "PixelExperience_Plus_begonia-11.0-20211009-1026-OFFICIAL.zip"
What I can do? the USb doesn´t recognize it when connecting it to the PC
It has a solution?

flipflipVeler said:
PixelExperience_Plus
Click to expand...
Click to collapse
What time is it ?
it's PE bugs time ! aka the worst rom ever aka worst than miui
flipflipVeler said:
The name was "S***Experience_Plus_begonia-11.0-20211009-1026-OFFICIAL.zip"
Click to expand...
Click to collapse
This forum is for RN8 (Ginkgo/Willow) ask in begonia forums
flipflipVeler said:
My redmi 8 needed an update, I downloaded it, I restarted it, then the screen went black and no longer turned on
Click to expand...
Click to collapse
Why are you convinced that it need an update ?
if your phone is working fine = leave it alone
updates are the main reasons of apps FC and bootloops ...

Yep, like age old wisdom: if it works, don't fix it...

Question Touchscreen not working

Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.

zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money

persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.

to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful

persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash

I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong

Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.

persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters

Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).

persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.

Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.

persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.

Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.

Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.

persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.

So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.

persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.

As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.