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
Related
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
I would relock and the re-unlock your hspl and see what happens. That is indeed a weird problem (that you can't send your phone in for).
Good luck
TheWizzard2203 said:
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
Click to expand...
Click to collapse
sounds like a defective phone!!!!
Yeah, that was my idea too. I tried relocking and reunlocking it with HSPL, but that doesn't matter.
But the problem is, how do I explain this to HTC if I want to send the phone to them for repair? I can't tell them that the problem only occurs when I install a custom made rom.
Pfff okay, I found the solution. It wasn't a hardwareproblem after all. I went through a terribly long trial and error procedure but finally pinned the problem down to only one cabfile, named HD2MemTweak found in the registry tips and tricks section of the general forum of the HD2.
I'd installed the lastest official 3.14 rom and installed all the cabs I was used to. But noticed, after several reinstalls, that when I installed that specific cab and rebooted the phone, everything went wrong. So I installed it without that cabfile and allw as working fine again. Then reinstalled HSPLv3 and installed the latest NRG Cookie Classic rom, which works fine again.
So that was the problem indeed. But one thing is strange of course, is that the mentioned cabfile used to work and suddenly stopped working. Could this maybe have something to do with the fact that the latest roms were build on the new 3.14 official rom? Who knows.....
Hi.
In first case.. Sorry for my English
I have a little problem with the touchscreen on my Galaxy S.
I think it's something with firmware. Sometimes don't work about 20-30 pixels on the left and the right side.
It makes me mad, because i need move the widget from one screen to next one, and isn't working. So, i have to open SGS tools, and do TSP update (touchscreen firmwareversion). After update is Pass on the screen and everything works perfectly, BUT only for a moment (sometimes few hours, max one day).
Then i have to do everything again
Does anyone know what to do?
try to make a nandroid backup and then reflash your firmware or do an hard reset and see what happens
No, this isn't working.. I had a lot of different ROM and I did hard reset etc. (2.1, 2.2, 2.2.1)(JPU, JPY, JM1/2)
Now I have Darky ROM 7.7 and OCUV Kernel. I thing, somewhere in phone is correct firmware, because when I did update I don't have to turn on wifi or 3g. Update is working offline and then everything work..
I recently tried changing my theme, i rooted my phone, Downloaded ROM manager and Clockworkmod, when i installed it all, it bricked my phone- I unbricked it by updating the firmware with Odin, but now the touchscreen is not working - At Alll.
Help :\
Yesterday I needed to take a picture and used my Galaxy S. for it. After that I connected my phone to my laptop USB port and got an unknown device error. Assuming it was a driver problem I re-installed them keeping the same error.
I also got telephony problems before, after some minutes calling the other side couldn't hear me anymore and I needed to put the call on wait and back to continue the call.
Both problems together made me decide to update my Darky 10.1 Extreme edition to the latest 10.2 Extreme edition. I took my sd card out and copied the darky 10.2 zip to it using my laptop. Put it back in and used Astro filemanager to copy it to the internal sd. Because I can't use the usb port this was the only way.
Rebooted to recovery and flashed 10.2. After reboot the screen stayed at the boot screen with green Darky text for half an hour without doing anything. No vibrate or anything. I did read some info about 10.2 before i downloaded it but missed the lagfix point. Tried to get into recovery and luckily that worked. Turned on the lagfix, did hear the computer voice 2 or 3 times and last time it said lagfix was enabled. Rebooted to recovery again, checked lagfix was on, also for next boot, and flashed 10.2 again. Same problem, hangs at bootscreen.
Turned lagfix off again and flashed the old 10.1 again. Same problem again, this time only bootscreen with white SG text and both button lights on. Nothing for the rest. Flashed back, after lagfix enabled, to 10.2 again without luck. Again bootscreen only.
Someone knows how to fix this? Because of the usb problem I can't use Odin. I did read somewhere now there might be a cable problem or a dirty usb connector on the phone. Checked the connector visually and can't see any dirt, I also keep it closed when not using it.It does load the battery also when connected to my laptop. At least it did when I first got the unknown device error.
1) USB Error
I am not sure you have Only installed the USB driver alone or Kies it self. Anyway, try this http://support.microsoft.com/kb/315265. Scandisk with delete currupted file on your disk drive and replace with default window file. You can reinstall your driver/Kies on your laptop after scandisk complete.
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
from.insider said:
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
Click to expand...
Click to collapse
If your boot takes so long, you doing something wrong
First boot, yes... it takes some time. But then, the animation isn't finished yet and I'm already good to go (after media bla bla bla)
@OoZic
For darkys rom... i had the same problem.
First flash Ficetos resurection 10.2, then make shure lagfix is ON (full lagfix - check in voodoo control app) and then flash 10.2 extreme edition
For details go to
http://www.darkyrom.com/community/index.php?threads/v10-2-final-what-are-you-waiting-for.4253/
I had the problem too
Thank you for your reply from.insider
Problem is the phone can only do bootscreen and recovery. The device isn't recognized in any way. Tried it on 2 computers (laptop/PC) with different multiboots (Win7 X64 and Vista X86 on both). Maybe that is because the OS isn't loaded and can't go to MTP?
Is there a way to copy something from external SD to internal SD within recovery menu? Because that way I can copy a JVP or JVQ image to internal. Now there are only the 10.1 and 10.2 zips from Darky.
FSCK didn't find any problems btw.
Thanks again.
Problem solved, my Galaxy is unbricked and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
OoZic said:
Problem solved, my Galaxyd and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
Click to expand...
Click to collapse
Can you copy and paste the the answer and post it here man, i cant find the post your talking about and my phone has the exact same problem.
Hi All
I have an issue with my S5 Plus (G901F) a few days ago I rooted, TWRP and installed the stable MM ROM from Tkkg1994 and have been happily using my phone. This morning while I was opening the Gmail app the device rebooted and when it came back up I noticed WiFi was not on. Pressing the quick menu WiFi button turns it green for a second before going back to disabled. Likewise going to into settings - WFi and using the slider does not work either, it just goes back to off.
So far, I have wiped ART/Dalvik, reflashed BL and Modem, factory reset. Wiped the whole device and redid everything including diffrerent ROM's on the same BL/Modem (CPE1) and have the same result.
Everything else works, just not WiFi, I should also add I have tried with and without the SD card and disabling/enabling other radios (GPS/BT) in different combos has not worked either.
Has anyone come across this and can they suggest next steps?
I'm currently downloading the stock ROM that came with my phone to see if that helps.
Cheers
Stock ROM did not help.
Did you find solution? I have recently started to have same issue with same device.
jaakla said:
Did you find solution? I have recently started to have same issue with same device.
Click to expand...
Click to collapse
Probably not. The S5 seems to suffer a lot by such issues. I bought mine 3 months ago in a shop. It worked for about 2 months very well. Then all of the sudden it became hot in my pocket so i had to quickly remove the battery. After this the device suffered by ocessional reboots. Nothing helped. Even trying to reflash the stock firmware by trying several Pit´s.
Finally got a replacement as obviously either the RAM or the CPU got defective. The other phone lasted for one week as the wifi module got defective there. Nothing helped either. Now it´s my 3th S5. This weekend my flashlight and camera stopped working. Fortunally got this fixed by reflashing the stock firmware.
Honestly I like the phone but it seems to be quite buggy. Never got such problems with my old S4 and am thinking about going back to the older device.
dude try flashing 4 files flash through odin
Hey guys, I have some problems with my s4 and hoping you could fix these. I'll try my best to include details of what I did and any details that are missing that I will include
Started with me trying to install lineage ROM on my s4 when things started to grease up.
Ok the problem is the phone would not boot to the main OS but when it did I flashed the recovery(twrp)with odin which seemed to work for about a minute or two before powering off. Also I couldn't get to the recovery(twrp) even when pressing the correct combos I just flashed it again and again until it worked but wouldn't work sometimes. I went back to the stock ROM which didn't work either.
I know I am missing out on a few details but if any of you guys can help me that would be great.
partition error ?
Crooton said:
Hey guys, I have some problems with my s4 and hoping you could fix these. I'll try my best to include details of what I did and any details that are missing that I will include
Started with me trying to install lineage ROM on my s4 when things started to grease up.
Ok the problem is the phone would not boot to the main OS but when it did I flashed the recovery(twrp)with odin which seemed to work for about a minute or two before powering off. Also I couldn't get to the recovery(twrp) even when pressing the correct combos I just flashed it again and again until it worked but wouldn't work sometimes. I went back to the stock ROM which didn't work either.
I know I am missing out on a few details but if any of you guys can help me that would be great.
Click to expand...
Click to collapse
try this, have problem like that, but i cant use any os greather than kitkat
but make sure you DUMP your partition that mentioned ! to PC
https://forum.xda-developers.com/galaxy-s4/help/battery-disconnect-upgrade-os-t4005567