[Q] darky 10.2 boot problem - Galaxy S I9000 General

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.

Related

Soft reboots in Kitchen-Builds

This doesn't belong here, but my lack of writing stuff prevents me from posting this where it is supposed to be
If possible, move this post into this thread: http://forum.xda-developers.com/showthread.php?t=1115958
So. JV5/JV9/JVO builds from kitchen with CF and HC kernels cause soft-reboots on my SGS I9000. I tested all of them by now. Tried the Talon Kernel 0.2.1 with JV5 and JV9, which caused boot-looping.
So I kept reading and found out that I was not the only one having this problem, but it seemed to be solveable by flashing a stock JVO first.
I already had Gingerbread Bootloaders, flashed JVK a while back, so I tried a few no-wipe ROMs as I mentioned above. All with the same problem. I lost connection to my cell network and it didn't come back. Somehow connected to the WiFi, I suppose. I could reproduce it by getting a GPS fix. But that was more or less related to my phone using wireless networks for positioning, which means that it switches on WiFi for just a second but without telling me.
Anyways, I thought I might have been wrong about the bootloaders being the reason to flash the stock firmware, so I did as it said: it specifically said JVO+ in the tutorial, so I went through the hassle and did the following:
- Flash an entire JVO firmware
- Reboot
(that one took a while)
- Full factory reset via dialer code
(that one took a while, too)
- reboot again, this time into bootloader, to flash a hc-speedmod kernel, to have root access and CWM
- reboot again, into CWM, to flash one of the ROMs I tried earlier
I ran back into my old trouble. So this is not an issue of the GB bootloaders or a previously installed version. The phone keeps soft-rebooting.
I re-installed the stock JVO firmware and flashed the speedmod kernel again, rooted via CWM menu and now I am just recovering my important applications via Titanium. Nothing bad happened yet, and it would have, with any of the kitchen ROMs Trust my, I almost tried them all
Nobody else wrote anything on that, so I thought I'd let you know there's no need to wipe all your data (like I did) and hope for the soft-reboots to be gone.
There's something seriously wrong there.
Anybody else having the same issues?
Cheers.
Andreas
Yep, I had a whole lot of trouble with the Kitchen JV5 release yesterday, ended up giving up and goind back to Darky's 10.1. Mine would boot, and when doing a media scan, would soft reset itself. I could get it to work eventually by powering down before media scanner completed then powering up. Bit odd - tried three builds of JV5 with different kernels but they ended up all being screwy. Ah well, will see what JVP brings...
glad to hear that I'm not the only one crazy enough to wipe his entire phone for a new (and fast) operating system.
Anyways... I am now back to my old status. Re-installed most of my apps, sync behavior, BT devices, wireless APs, etc. blayallah...
JVO with a hc speedmod kernel is by far the best and fastest ROM I have run so far.
Kitchen builds are dead to me until some of the people who ran into the same problems as I did confirm that those issues have been dealt with.
Just for your information:
- battery life seems amazing, at least regarding to the sensor. Hope it's any accurate. Had it unplugged over night and lost 22% battery life with WiFi on in a bit more than 10 hours
- it responds VERY fast, compared to any other ROM I had before
- bluetooth devices have to be set up again, for some reason my phone doesn't like my headset any longer. I can hear people talk but they can't hear me. However, the microphone does work when I use my headset for text2speech. Weird.
Anything else seems just the way it was before. Just faster.
I'd be glad to hear if someone could still help me out with the soft-reboots, if somebody else decides to use the kitchen builds either way I won't until somebody else tells me it's working now
Andreas
Why would u need to SOFT reboot ?
I don't *need* to soft-reboot. It just does that. Modem crashes, lost network connection. The phone doesn't actually entirely crash, it just restarts the network service and your phone is going to be offline.
That's a soft-reboot. No entire system crash or kernel panic, just the modem crashing.
That does happen when things are messed up
I'm having the same issue: on a JV5 and JV9 RomKitchen build with a JVO modem, as soon as I get a GPS lock, the phone soft-reboots.
paour said:
I'm having the same issue: on a JV5 and JV9 RomKitchen build with a JVO modem, as soon as I get a GPS lock, the phone soft-reboots.
Click to expand...
Click to collapse
guys, why dont you try the JVP v7 builds, its much better.
also, please select the default boot animation, else it will go into bootloop.
I can confirms that doing a no-wipe upgrade to JVP v7 fixed this soft-reboot issue.
Thank you for that information. I'm not in a flashing mood right now JVO is running just fine right now. Anything about JVP v7 that's worth the try?
JVO is running fine for now. So I'm not feeling like flashing everything over again.
Is there a simple way to just dump my current phone status, its ROM and everything somewhere to my harddrive and re-flash all of that over in case anything goes wrong?
andreas1979 said:
Thank you for that information. I'm not in a flashing mood right now JVO is running just fine right now. Anything about JVP v7 that's worth the try?
JVO is running fine for now. So I'm not feeling like flashing everything over again.
Is there a simple way to just dump my current phone status, its ROM and everything somewhere to my harddrive and re-flash all of that over in case anything goes wrong?
Click to expand...
Click to collapse
its pretty much the same stuff except very good speed optimizations, 2.3.4, and few UI tweaks.
its been the same since the first gingerbread leaks. we flash it for new builds dont we
...and now it's just pissing me off. JV9 Kitchen Build. On GPS Lock I get soft reboots. What the hell?!
Trying another one now... crap. I thought That would be fixed by now.
So. Kept me busy, just to be sure: Each and every combination I tried using 2.3.3 from the kitchen caused soft-reboots on GPS fix. The phone was very fast with the Talon Kernel and Ext4 FS, but I can't live without GPS
So I tried a non-wipe install over one of the not working 2.3.3 roms.
I'm on JVP now, not as fast as Talon, so it seems, but GPS works, getting a fix at my window within 5-10 seconds, no crashes whatsoever.
So. If anybody else experiences crashes like the ones I mentioned in the opening post, I can also confirm that the JVP ROMs seem to fix the problem.
Andreas
...as much as I hate talking to myself, it's still regarding the same issue, so I have to ask:
Saw the new kitchen build (JVR).
Two questions:
1. Is the soft-reboot issue finally fixed?
2. Is there a little language-switcher-button on the bottom left of the swype keyboard?
I use the JVO swype, and it has that button, and the new ones don't seem to have it any more? It's really nice if you need to switch between two languages all the time and you don't want to go into settings every time you need to switch.
Anyone know that? http://t1.gstatic.com/images?q=tbn:ANd9GcQC6orm5ZMAju2VzczB3MCbwEPeSH9yrYI6wxfdDGFCvkdpe7lQRg <- that one right here has it. Took me a long time to find that, because no swype version but JVO seems to have that feature.
I'd be glad about any answers to those two questions.
Andreas
andreas1979 said:
...as much as I hate talking to myself, it's still regarding the same issue, so I have to ask:
Saw the new kitchen build (JVR).
Two questions:
1. Is the soft-reboot issue finally fixed?
2. Is there a little language-switcher-button on the bottom left of the swype keyboard?
I use the JVO swype, and it has that button, and the new ones don't seem to have it any more? It's really nice if you need to switch between two languages all the time and you don't want to go into settings every time you need to switch.
Anyone know that? http://t1.gstatic.com/images?q=tbn:ANd9GcQC6orm5ZMAju2VzczB3MCbwEPeSH9yrYI6wxfdDGFCvkdpe7lQRg <- that one right here has it. Took me a long time to find that, because no swype version but JVO seems to have that feature.
I'd be glad about any answers to those two questions.
Andreas
Click to expand...
Click to collapse
I have tried the JVR base available in the kitchen---nothing to write home about,went back to STOCK--far better!I imagine the Kitchen as we used to know and use way back is now a thing of the past and the last nail was Tricky also leaving...
andreas1979 said:
glad to hear that I'm not the only one crazy enough to wipe his entire phone for a new (and fast) operating system.
Andreas
Click to expand...
Click to collapse
Guess that makes me crazy too
I've also been tinkering with customising ROM's myself to get to the boot-loop - getting pretty proficient at it now (guess I should read up a little more first)

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

had lite'ning 1.4, updated to 6.1, now wifi issues

ok basically i bought the phone second hand with lite'ning 1.4 on it and the wifi worked perfectly ok all the time. Since it was very old i updated it to 6.1. ever since then I have had issues with the wifi. it will connect perfectly fine to the router but i have no connectivity from it, nothing will get any net access at all. This is also not 100% of the time, its MOST of the time but not all, i do have moments where it does work fine. very very odd.
I have since tried updating the kernel to ninpho 2.1.3 from the 2.0.5 that comes with lite'ning 6.1, but that made no difference.
Someone suggested i try a wifi fix app from the market so i downloaded "FXR wifi fix and rescue" and ran that. It ran ok, wiped all my wifi settings and i restarted, but it has not solved the problem at all.
i find it very very odd since if it was a problem with the kernel OR the rom then everyone would surely have exactly the same problem. I know some people report wifi issues but most dont seem to.
anyone have any other ideas?
The odd thing is that it worked before the update. That means that it will most likely be software related.
You could try flashing something totally different like MIUI or CM. They provide kernels too, so this might resolve it, if your kernel and rom don't "like each other". This usually shouldn't happen, but updates breaking wifi shouldn't too. So it might be worth a try.
Sent from my GT-I9100 using XDA App
if i went to something completely different i assume i would have to factory reset the phone to wipe it first? (or factory reset it AFTER installing the new rom?)
was trying to avoid wiping it as i dont want to spend endless hours setting up everything again. i have backed it up with the free titanium but id still like to not have to find out whether the restore actually puts everything back properly
its very odd as its not completely broken, sometimes it does actually work, and it always connects to the router itself without any problem.
Probably wrong modem for you, flash another one. You can find modems in the developement section.
ok thanks I will have a look at that. It is currently on XXKH3 which is what came with lite'ning 6.1. i am confused though, all SGS2 hardware is identical so if this modem in 6.1 is causing this issue, wouldnt it affect every sgs2 that uses that modem?
I found the "shipped modem collection" post in the original development thread so have asked in there which modem i should try.
ok apparently i should try XXKI3. for o2 UK provider.
although i have now read that wifi is not managed by modem but by kernel only. if this is true then modem will not help me
Well, if the wifi is not managed by the modem, try what I proposed you earlier. The simplest would be to flash CM. Make a backup of your current rom, then do a full wipe and install CM.
As for your data:
1. Titanium backup restores your apps with their data (if you wish). That means that, for example, your games will keep their saves, other apps their settings and so on.
2. Assuming that you have a google-account, you don't have to worry about your contacts, calender,... Just sync it before you flash.
3. The backup you make in CWM will backup everything in case CM doesn't work for you.
In case it does work and you'll want to keep it, the other two other parts of your backup will minimize the remaining work. Note that you shouldn't restore "standard"-apps like the media-player or the SMS-app if titanium backup tells you that the app is not currently installed on your fresh CM. This means that CM uses it's own media player or SMS app. It could lead into problems to mix TouchWiz apps with CM.
A side-note:
Don't use the "stable" version. It had more bugs than expected and they made it a RC again. However, it is still in the stable folder. Get the latest nightly.
Sent from my GT-I9100 using XDA App
yep i think it is kernel. just noticed that 1.4 had cf-root, 6.1 had ninph 2.0.5 and i then tried ninph 2.1.3 and both ninph's have had the issue. i just tried speedmod k2-13 as i already had that downloaded and so far the wifi has been ok so hopefully thats it fixed. i guess it was something to do with ninph (i am thinking that because i have it set to sleep the wifi when the screen is off that somehow ninph is not handling this properly).
possibly one good thing to come of it all, ive updated the modem to KI3 which is supposedly the best one for o2 UK so i may even save more battery and speedmod is meant to be really good for battery too. I still have lite'ning on it at the moment.
i might have a look at CM anyway but i do kinda like lite'ning (although i havent actually used anything else since the phone came with it!)
also need to look at wakelocks to see if i can save some more, although not sure how i go about 'fixing' them at the moment
The choice between CM, MIUI and the stock mods is the choice between three different UI's.
I've had all three of them for some time. As you got CWM, you can just create a backup and do a sightseeing tour through the world of custom roms. Believe me, it's absolutely worth it. To get an idea of the main differences, I've written a short overview for you:
Stock mods use Samsung's TouchWiz. The default user interface that you get when buying a Samsung Android phone. So it mostly looks and "feels" the same and you can't do much about it.
CyanogenMod gives you the pure Android user interface. It's the closest to the Nexus phones by google, but gives you some extras. It is much more customizable than stock roms. It's sleek and fast.
MIUI is a whole different story. They're "Redefining Android". I think calling MIUI an "Android custom rom" is an understatement. It's an entire OS. The result of putting the best from iOS and Android into one powerful OS. It adds tons of useful(!) features. If you've ever used Windows Phone 7 or an iPhone, you know what a big step forwards Android is when it comes to features. Switching from Android to MIUI is just like that. There is just so much more. It is BY FAR the most customizable Android you can get.
Wow. If I look at how long the texts are, I see that I'm pretty biased. :O
Well maybe because I've switched so often between them. The stock roms had no chance, because after I used one of the others I found out that TouchWiz doesn't cut it anymore. I hate how "iPhone-ish" MIUI is, but if I flash CyanogenMod I just miss so much. Giving you a list of what MIUI adds would be another long post of this length.
Sent from my GT-I9100 using XDA App
cool thanks will have a look at MIUI at some point.
spoke too soon earlier, the wifi is maybe slightly better on this speedmod kernel BUT when i wake the phone from sleep, it takes about 30 seconds before i can connect to the net with anything. the phone connects to the wifi straight away, but i have no connectivity for a good 30 seconds and then it starts working. (its not the router, i am getting a connection and an IP pretty much as soon as i wake the phone). also the 30 seconds or so only STARTS once i try to connect to something. if i wake the phone and do something that does not want net access for a few mins and THEN try to get on the net via wifi (which shows as connected the entire time) then again i have to wait about 30 seconds from when it first tries to connect before it will start working.
ok slightly confused again.
I have lite'ning 6.1, speedmod k2-13 kernel and XXKI3 modem. I am trying to get cwm installed so i can make a full backup image of the entire phone while i try to sort out the wifi issues. i downloaded rom manager from market, and selected the firstion option in the app 'flash clockworkmod recovery'. it brings up a menu saying 'confirm phone model' with AT&T galaxy S2, a coulpe of i9000s and a plain "Samsung Galaxy S2" which is the one i selected. it downloads something and says successfully downloaded clockwork mod recovery.
i then choose reboot into recovery. when rebooting it attemps to install something but then says "failed to verify whole-file signature" and aborts. so im just stuck with the standard recovery instead.
so now im confused, have i missed something?
Ehhhhm, you don't need to do it.
Have a look at the features of the speed-mod-kernel:
Current features:
Root and CWM:
- Automatically installs root (su)
- CWM 4.0.1.5 recovery
It already installs it right away.
Just in case you messed something up. You should flash the kernel again.
Besides that you don't need the RomManager at all. Just shut your phone down and boot into the recovery with the key-combo. Create and restore backups from there.
Sent from my GT-I9100 using XDA App

MDOB rom messed up S4 (full wipe doesn't wipe everything?)

System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine

Help, im stuck with no sound, the weirdest thing ever!

So let's start cuz it's a big story. So i have a Samsung Galaxy S4 GT-I9505, rooted, TRWP Custom Recovery, i had plenty ROM's on him, everytime the ROMS worked perfectly except the bugs they already had....
The last ROM i had was Optimized CM12.1 JDCTeam. (http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696) it worked fine....
One day, they made an update of the ROM. Everything worked fine, until a morning 2-3 days after i made the update.... my alarm clock started ringing (as it was meant to be ) but the screen wasn't turning on.
I restarted the phone...but the alarm was still ringing when the phone restarted then it restarted itself. After this self restart....the phone booted with those optimizations (like the cache was deleted.) After it booted...surprise. No sound. At all. No sound in media player, no sound from calls, no sound when recieveing calls, no sound from my mic too.Then i noticed that movies from Youtube and from my gallery were playing in slowmotion, or not playing at all.
I though it was the ROM ...so i installed other ROMs....no success....all the ROMs i've installed had the same problem. No sounds at all.
Then i found a ROM, that played the Boot animation sound but all the other sounds were still not working. So of course this means it can't be a hardware problem anymore.
So back from the start.
Then i found this ROM, an S6 port : http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-s6-port-1-0-t3092479
This ROM specifies that i must install the latest lollipop bootloaders and modems for it to work. So i've installed the modems and the bootloader given in the ROM topic....then the ROM and surprize....the sounds were working again. But the new problem was that the SIM reading stopped working and the rom was unstable. I've tried other modems to no success for the SIM.
Other Lollipop and KK roms, thinking that the bootloader or the modem was the one that fixed the sounds, didn't work so i concluded is not the bootloader. And then i've installed this : http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-s6-port-1-0-t3092479 which at start it didn't played sounds. Then i've installed the bootloader from Albe95 S6 port post...and surprisingly sounds started to work on this ROM too. But from time to time the sounds dissapear..and i have to wait like some seconds to minutes for them to come back + the SIM still not working on this ROM . So somehow is the bootloader....but i dont get why it's working only on S6 ports..not even on MM ROM's is not working...
Can anyone help me ?
Edit : I forgot to mention that my partitions are F2FS....if this matters....
Posting a wall of text as you did here is a certain way to ensure your post gets ignored. You want to edit it and break your post up into discrete paragraphs so it is both readable and understandable.
Strephon Alkhalikoi said:
Posting a wall of text as you did here is a certain way to ensure your post gets ignored. You want to edit it and break your post up into discrete paragraphs so it is both readable and understandable.
Click to expand...
Click to collapse
Thanks for the tip I've edited the post....it is better now ? or should i cut some paragraphs?
No, that's fine. I probably should have PMed that to you rather than post it, but it's a bit too late for that. Sorry.
Anyway, your symptoms, where it occurs erratically, could still be a hardware issue. However, I think it more likely that your internal storage "glitched", and that is causing your problems. Make sure you have a backup of your IMEI and EFS by using Wanam's EFS Backup tool. Then grab an I9505 PIT file, a stock ROM, and Odin. Use them to partition the internal storage (which will format it), and install the stock ROM. See if your sound issues are fixed throughout the ROM. If so, then replace the recovery with TWRP and install the ROM you prefer.
If it still happens even after going through this, then it's almost certainly a hardware issue.
Strephon Alkhalikoi said:
No, that's fine. I probably should have PMed that to you rather than post it, but it's a bit too late for that. Sorry.
Anyway, your symptoms, where it occurs erratically, could still be a hardware issue. However, I think it more likely that your internal storage "glitched", and that is causing your problems. Make sure you have a backup of your IMEI and EFS by using Wanam's EFS Backup tool. Then grab an I9505 PIT file, a stock ROM, and Odin. Use them to partition the internal storage (which will format it), and install the stock ROM. See if your sound issues are fixed throughout the ROM. If so, then replace the recovery with TWRP and install the ROM you prefer.
If it still happens even after going through this, then it's almost certainly a hardware issue.
Click to expand...
Click to collapse
Thanks a lot sir, i'll try this as soon as i reach home. I let you know if it's working.
verdut said:
Thanks a lot sir, i'll try this as soon as i reach home. I let you know if it's working.
Click to expand...
Click to collapse
it seems that the problem wasn;t solved...i noticed something else, some roms , especially stock roms when i use the volume buttoms to change the volume....the rom restarts itself ....

Categories

Resources