Database Users

Problem with friends Galaxy S

Hi.
My friend got her Galaxy no more than two weeks ago, and I installed the newest Darky ROM (10.1) on her phone, since it has been working fine on my own Galaxy S.
The problem is that her phone just stopped working... just like that.
She thought the battery was drained, so she charged it, and when booting it up it would remain in the samsung logo (boot screen).
Well I put it into recovery and formatted it into factory settings and thought it would be fine. Well it kinda worked: it started up to the setup wizard, choose language, insert SIM card etc. and finally when clicked the complete button, the screen stayed black and few seconds later a message came saying that there has been an error with the android setup configuration.
This is exactly the same phone as I have and mine is working perfectly fine. Dont understand why this phone is acting up.
Will re-flashing it with the same Darky ROM fix this?? The phone has got warranty, but I dont think they'll accept it anymore cause of the custom ROM I put in.
I also have a video of this, but since they assume I'm a spammer, I cannot insert any links for now.
EDIT: Problem solved --> reflashed with Darky's ROM, now working fine. Thank you both slaphead20 & MasterJam882

you can try reflash...or darkys ressurection...or ezbase rom

Just flash an official rom from www.samfirmware.com.
If u still have bugs and errors u know it's a faulty phone and u can send it to samsung without the fear that they wont accept because its an official ROM every user gets over KIES.
greetz

BLack screen after installing any rom

On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)

zxsq said:
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
Click to expand...
Click to collapse
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.

robertofelce said:
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
Click to expand...
Click to collapse
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|

zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
Remember that rr marshmallow releases don't work for SM N900. I guess that your phone is sm N9005. Right?
If it is, is awkward that you can't flash a rr marshmallow ROM

You should be in the T-Mobile note 3 forum?
Cm12.1 for the hltetmo: https://download.cyanogenmod.org/?device=hltetmo

zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
got exactly the same problem....Tried to flash repair stock rom with pit, with success, but doesn't change anything
can flash 5.0 stock or 5.1 port rom but not CM or AOSP..
if you find what happen....

Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.

rikymatteo97 said:
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
Click to expand...
Click to collapse
My note 3 smnN900t is doing that same thing and it sucks because I know I did everything perfectly!! What Kernel were you able to flash for it and where did you download it from? By the way thanks in advance for any help and info you can give!!!

Wrong forum
forum links .
http://forum.xda-developers.com/showthread.php?t=2574886

Please help I am having the same issue. Did anyone find a solution for this ?

sm core prime 360H custom rom error

Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it

Probably your internal storage if full or something. Which ROM were you installing anyway?

rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this

Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762

rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?

rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?

Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.

Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?

rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...

rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...

Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.

Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod

yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.

half blue half black screen after flashing a rom

hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution

rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue

You confirmed the model # in download mode? Tried using different version of TWRP?

I am facing same problem recently, did you find any solution ?

still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?

blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one

maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/

In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.

Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?

pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .

JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.

Solved turning off smart cover

Custom ROMs result in black screen

Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon

Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.

simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?

gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards

Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail

Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.

Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.

Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.