Related
It's really a shame to start off in a place with a post that has someone mad at themselves for performing a soft brick on their relatively new Verizon Samsung Fascinate. I have to admit I love the phone, but after seeing some videos about DarkyMod I was so impressed I felt compelled to try it.
All I've done, far as I know, is Rooted the phone, but I also used Odin and apparently flashed the incorrect kernel. So what happens now is when I power on my Fascinate, I get a Galaxy S (GT-i9000) screen. At this point, the phone reboots. I know I'm an idiot for having used the wrong Odin kernel, but after attempting to decipher the post in the Darky's installation for "first timers" I apparently choose the incorrect kernel.
At any rate, I suppose I could ask for an experienced modder for the right kernel, the one that would allow me to perform the flash after I had installed the ROM Manager, etc.. But I doubt that would help. What I'm looking for is a file which has been removed from the forums here, and was originally in someone's Dropbox account.
I believe that the file that I'm looking for is the "Stock-i500-VZW-Kernel.tar.md5"... I might be incorrect, as I had mentioned I believed I had successfully "rooted" the phone, but when I used Odin to flash the kernel, I think that's where I went wrong. Can anyone help me find this file? Or should I get the modified kernel, which will allow me to perform the backups and then the flashing to this mod? Thanks ahead of time, I do apologize for the length of the post.
-
T.C.
Samsung Fascinate (Verizon) DL09
http://forum.xda-developers.com/showthread.php?t=867648
thats full d101 thread
http://forum.xda-developers.com/showthread.php?t=885262
thats full dj05 thread
both should be able to get you back to stock through odin then you can restart what you did. personally i keep both handy since i already had to use them due to an error that cause the phone to freeze up completely at the samsung logo. hope that helps
Thank you kdaz!
I'll give that download a shot real fast and see what happens. I'm assuming you've modded/rooted your Samsung Fascinate? Which of those Odin kernels did you use to successfully start changing things? I never did get past the "update.zip" part, it always came back with an error.
Thanks for taking the time to write a response, I really feel bad to post and have my first ever be a soft bricked phone, haha!
Quick thank you...
After looking all over the forums here, and elsewhere... I did find what I was looking for, though I didn't manage to restore the kernel and save my settings, I did unbrick the phone by reapplying the DL01 firmware with the Odin software. The forums here were a huge help, and I just wanted to say thanks!
haha glad you got it working. yes i have rooted and modded mine. got it last thursday brand new and was modding it on friday when i got back from vacation. friday night i feared that i had totally bricked it but luckily found both of those files on the forums. i believe i used the dl05 one then imediately updated to the dl09 radio and now running blaze voodoo kernel clocked at 1.2ghz and i honestly forget what rom lol waiting to use aosp
Thank god these phones are so easy to unbrick with Odin. Almost impossible to truly brick, though sometimes you might lose some data here and there or it won't save your data etc. That's why you might need to odin the full stock rom more than once
Thanks for the responses guys, kudos!
I had really hoped to start using Darky's ROM but it turned out that I didn't have the right modem file, or at least, that's what Darky said. At any rate I was kind of curious which custom ROMs you guys are using and why? The names alone should be sufficient, there's so much information here on these forums.
I admit I'm worried to reflash but at the same time, I know how to do it and if something goes wrong I just use Odin and apply DL01, or whatever the original ROM is called. Any thoughts about good and fast custom ROMs on the VZW Fascinate, guys?
Look for the full DL09 Odin, DI01 is really old and DJ05 was killed inside VZ before it was ever released to the general public.
As you have discovered, the Fascinate is its own animal and you cannot flash stuff made for other Galaxy S phones to it unless you feel like breaking your phone on purpose. Most of us are running one derivative or another of DL09 that has been hacked up in various ways to remove the stock bloatware, add root/themes, add new functionality into the kernel, etc. Some of us are using AOSP or CyanogenMod froyo-based roms which (still) have many/most things broken. We are finally about to have official updates to 2.2 and that is the missing piece that was needed to get full custom development working. Big changes will be coming before we know it.
[email protected]
I had just read earlier that there was a Froyo leak, I'll be really curious to see whether or not it speeds things up or not. It sounds like the custom ROMs are here for our VZW Fascinate but what I'm really looking (and waiting for like everyone else) is just Froyo. I'm grateful to everyone here who reached out and helped.
I'm not sure if my rooting days are done, but I got pretty scared when I thought I'd bricked this thing. Can't thank you guys, and the community, enough.
im currently running OTB ul1300 kernel which has the voltage turned down and processor speed of 1.3ghz and im currently running the dl09 supah clean rom. was running kaoscinate yesterday but missed being able to use my camera. the flashablility of this phone is great..i love just switching roms and kernels almost completely at will. cant wait until they get the leaked froyo out to use but im enjoying trying everything else until then.
tclore77 said:
I had just read earlier that there was a Froyo leak, I'll be really curious to see whether or not it speeds things up or not.
Click to expand...
Click to collapse
If you really want a boost in your phone speed, you should look into getting custom ROMs and kernels, not Froyo. There are a bunch of kernels out there that are overclocked (and even undervolted, to save battery life too) that will significantly improve your performance.
The best thing you can do with your phone is to get yourself a custom ROM - something like Blackhole 3.0 by sonofskywalker or SuperClean 0.4. Those will get rid of the bloatware crap that Verizon puts on your phone, and (more importantly) change the default search from that P.O.S. Bing back to Google.
OK, this is unbelievable.
The battery drain on XXJVO was driving me crazy. Reading the forums I noticed some people said the Android OS issue was fixed on 2.3.4. Yesterday, I flashed XXJVR with re-partition and bootloaders via Odin, using the OXAJVQ CSC. I also installed the Voodoo lagfix for XXJVR.
I did a factory reset before and after the flash. Did a battery pull, all the steps that we're used to.
For my surprise, a few minutes ago, the phone discharged in 8 hours to 47%. Guess what? Its the Android OS again. Take a look at the attached screenshots.
Did I do something wrong? Is this normal on 2.3.4?
EDIT: Following $omator and madrooster's advice, I decided to flash everything again from scratch and install all the apps directly from the Android Market. Apparently, the issue was being triggered by a restored appdata backup via TitaniumBackup. I've been using the phone for about a week now, with no issues at all.
im running custom rom gingerreal 7.1.4 JVQ with galaxianEE kernel and lagfix enabled. my modem is ZSJPG and csc XAJVQ.
no issues like u have.
but i have to say, that the battery drain is heavier than on froyo.
Man, that's pretty serious drain. I'm running Ramad's stock deodexed JVR since it was postes with semaphore kernel and my usage is never more than 15%. Why don't you post a pic of the bigger graph?
only way to avoid battery drain is that you remove the battery from phone
have no idea haw did you managed to break jvr but you did it =)
i guess youve runed some app that was not letting phone to sleep
or the system got some broken ones tat caused this (yes wrongly flashed system maybe hehe)
btw notice the blue line under your graph - it should look more like on attached screen
Im also running gingerreal 7.1.4 JVQ with semaphore 1.32 and after 2 weeks of use no battery drain.
Android OS is always below 10% (mostly on 4-5%)
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
jbdroid said:
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
Click to expand...
Click to collapse
Thanks jb. That could be the reason. I am using Voodoo kernel, maybe that's what causing the drain. Has anyone else on Voodoo experienced the same problem?
Heritz said:
Thanks jb. That could be the reason. I am using Voodoo kernel, maybe that's what causing the drain. Has anyone else on Voodoo experienced the same problem?
Click to expand...
Click to collapse
Were you playing orientation/sensor-based games?
jbdroid said:
Were you playing orientation/sensor-based games?
Click to expand...
Click to collapse
jb, I remember that I played Captain America in the morning, but the phone froze and I had to battery pull it. After the restart, I didn't touch it again for like 6 hours. In the night, the phone rang and when I tried to pick up the call, the screen wouldn't turn on, so I had to battery pull it again.
After I turned it back on, I checked the battery stats and noticed the Android OS was running crazy, as you can see in the screenshots.
Captain America afaik is not sensor based, and I battery pulled the phone after I played, cuz it froze. I'd love to blame the game, but I cannot.
Edit: But... looking at the stats, the orientationd process is right next to the Android OS. Could this happen if the phone wasn't resting on a flat surface? :S
Yup the orientationd process was burning you battery juice, the reason why you got Android OS bug. I guess you should try to change your custom kernel or if you really like your current phone setup, you should install Watchdog lite or any similar app to monitor system processes, such as Android OS, for unusually high cpu usage and just reboot your phone when it does occur
i wonder what else is broken in this guys phone that wathcdog and reserting will not fix =)
$omator said:
i wonder what else is broken in this guys phone that wathcdog and reserting will not fix =)
Click to expand...
Click to collapse
$omator help me out here. What kernel would you recommend for JVR that keeps everything as stock as possible but includes lagfix? I use Voodoo since it is pretty light, but it doesn't seem to behave so well after all.
stock + cfroot is always a win
jbdroid said:
The Android OS bug was fixed from stock JVQ onwards. The reason you guys experience that is because you are using custom kernels built from old source codes released by Samsung or heavily modified by the developer. Go complain to your respective custom kernel thread.
Click to expand...
Click to collapse
+1 very true the kernels for me to showd diffrnt results
No battery drain for me here I've been on it for weeks with heavy use friend, never pass 5 hours in any froyo firmware
Sent from my GT-I9000 using xda premium
Android os drain goes away for my 2.3.3 kg3 stock setup after wiping cache partition and dalvik cache. Ran for weeks and never came back.
Sent from my GT-I9000M using XDA app
This battery drain problem is caused by the kernel you have. It is caused by a bug in a specific device driver.
The phone tries to go into power save mode but something prevents it. When the phone fails to reach a low power mode, you see the battery drain. In summary, if you run a custom, non stock Rom you might not have the battery drain fix. Try to make sure that any custom kernel you use has the same kernel version as stock.
Wow that is pretty big drain.. On my xxjvr (2.3.4 ) it only uses 9 to 10% don't know what's wrong though
Sent from my GT-I9000 using xda premium
$omator said:
stock + cfroot is always a win
Click to expand...
Click to collapse
Not for me...
1. Clean the phone.
Flashed JVR (from samfirmware). Flashed CF-Root-XX_OXA_JVR-v4.1-CWM3RFS. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings (NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 22.00 hour battery was at 98%.
Next day in the morning at 10.30 hour, the phone beeps that the battery is at 15%... Looking in the Battery use, discover that in about 12 hours, the Android OS (90%) is draining the battery. OMG...
2. Fully charge the phone, clean the phone.
Flashed JVR (from samfirmware). Flashed speedmod-kernel-k15i-t10. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings(NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 22.00 hour battery was at 96%. Next day in the morning at 09.30 hour, check the phone.
Surprise! At about 12 hours, the battery "lose" only 4%. And NO Android OS in the battery use.
3. Next day, clean the phone. Fully charge the phone.
Flashed JVR (from samfirmware). Flashed TalonDEV-0.4.4.22-1200-I9000-BIGMEM-CWM3. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX. All closed by me in settings(NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 23.00 hour battery was at 98%. Next day in the morning at 08.00 hour, check the phone.
Surprise! At about 10 hours, the battery "lose" only 5%. And NO Android OS in the battery use.
4. Next day, clean the phone. Fully charged battery.
Download again the CF-Root-XX_OXA_JVR-v4.1-CWM3RFS.
Flashed JVR (from samfirmware). Flashed again CF-Root-XX_OXA_JVR-v4.1-CWM3RFS. Flashed JVR STOCK+ v1.41 aosp losckscreen ODEX.
All closed by me in settings (NO GPS, NO wifi, NO data, NO... nothing) and the mobile network mode set to GSM only. At 21.00 hour battery was at 90%. Next day in the morning at 07.00 hour, looking in the Battery use, discover that in about 8 hours, the Android OS (90%) is draining the battery and the battery is at 25%...
I'm not a specialist in Android, but with this experiment, understand that in my case, the "drayner" of the battery was decided by the kernel, and I decided to flash the JVR stock+ with speedmod-kernel-k15i-t10.
I don't say that the CFroot is bad or that another kernel is good, but for me CFroot don't works good.
Hi,
I just purchased a used Droid X to replace my mom's OG droid. I read as much as I could on rooting the DX and all that jazz (completely different coming from an HTC by the way... holy hell and I am sorry).
I have already rooted the Droid X, installed boot strap... etc.
Made a backup using recovery.
I searched the forum for "most reliable ROM" and came up with rubix 2.0
I flashed it through recovery and ended up stuck at the boot motorola logo.
Panicked and stressful I have to say! WTF! Now I understand why it sucks so much to have a locked bootloader. You CAN'T boot into recovery to flash your back up! Well at least I couldn't. I tried the home button, search button boot up method and didn't work. I was getting worried....
After reading more... I SBF'd it which is a completely new thing to me. It ended up being easy but it's really lame coming from the Incredible and Thunderbolt. Again, I now feel your pain!
Anyways, I really DO NOT want to go through that again. Do you have any idea how hard it was to find a downloadable SBF file due to the megaupload shutdown!!!! I have just re-rooted after using the SBF file found here: http://www.droid-life.com/2011/09/06/droidx-gingerbread-4-5-602-sbf-released/
So after all that I am just going to ask.
What is the most reliable ROM and what SBF file do I have to download to be compatible with it???
Remember... this is for my mom... I need a reliable, stable, bug free ROM. This ROM will likely be the one she will use indefinitely so please choose one that is as stable as can be.
Thank you for all your help.
That SBF is perfect for the newest roms.
The DX is on .605...but the kernel doesn't change at all so there is literally no change if you accept the OTA or not.
Stable GB Rom...
I haven't messed around with 1st init (blur based) for a long time...so I can't say for certain.
But as far as 2nd init goes...
I'd choose MIUI.
She'll love it.
Actually, I flashed MIUI to my mom's X (who is completely tech-retarded) and she has been on it for a good 3-4 months now...
http://rootzwiki.com/topic/11858-ro...charge-led-updated-bootmenu-charge-while-off/
The newest build includes a working "boot menu" that can get you into CWM from a power-off state if you ever need it.
Also...
Once you flash...
I'd HIGHLY recommend using said bootmenu to set her overclocking speeds / cpu governor.
I assume she won't be to worried about speed...
So I'd either underclock her a tad...
Or leave her at stock.
But be sure to set the CPU governor to "SmartassV2"
The phone sleeps like a champ.
Literally the second you turn the screen off...the phone sleeps...and stays asleep until a notification/screen is turned on.
FANTASTIC battery life due to this.
I mean...stellar battery.
Also, it's VERY stable.
No bugs what-so-ever...
My signature also has a DX specific rom install tutorial if you'd like a refresher on the DX.
The stock ROM isn't bad. We have a few users in my office that still use it and they have no problems at all. I like to flash a lot and I am currently on MIUI (ICS) but I am thinking about going back to Vortex. It is by far the most stable ROM I've found on the Droid X.
The best Blur ROM I flashed was Liberty 3 v2, great speed, battery etc. CM4DXGB is the best ROM I have ran, I have tried most of them and CM7 is my go to daily driver. Great overall performance, very fast, great battery once you get settled in and awesome customizations. I flashed it on my dads phone and he loved it, my Mom still has a flip phone! Haha
Sent from my DROIDX using Tapatalk
I wouldn't try liberty as a new user, there is a lot of customization that can confuse someone IF they aren't experienced. Apex has two days of battery life when calibrated so i would choose apex. no bugs and incredibly smooth!
Edit: Posted this in the wrong forum - removed.
Sent from my DROIDX using Tapatalk
I am currently using MIUI 2012.2.1 after trying liberty and one other. I really like it, but as is expected after rooting, i want to play around. Although after reading your post, not so sure. MIUI really is great. I can go 2 days without recharging if i shut down at night. I did manage to get into a boot loop requiring an SBF etc. This was traumatic, but now i know how my phone works!
So I would like to try CM7. I downloaded the latest for the Droid X. I guess MIUI does not let rom manager install roms so i have to use clockwork. No problem. Is there any thing i need to do special since i am on a 2-init rom? Do i just do a dalvik wipe, then install the zip?
Gadget_Guru said:
I am currently using MIUI 2012.2.1 after trying liberty and one other. I really like it, but as is expected after rooting, i want to play around. Although after reading your post, not so sure. MIUI really is great. I can go 2 days without recharging if i shut down at night. I did manage to get into a boot loop requiring an SBF etc. This was traumatic, but now i know how my phone works!
So I would like to try CM7. I downloaded the latest for the Droid X. I guess MIUI does not let rom manager install roms so i have to use clockwork. No problem. Is there any thing i need to do special since i am on a 2-init rom? Do i just do a dalvik wipe, then install the zip?
Click to expand...
Click to collapse
Do a system and a data wipe.
Beamed from my TF101 using Tapatalk HD
I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?
kalda01 said:
I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?
Click to expand...
Click to collapse
Thats what you called "SOD" screen of death. Just pull your batery when it happen. Also it might be kernel related try changing kernel
Sent from my Nexus S
I'm running CM7 since day one with whatever kernel it came with.
What other kernel might work with CM7 ?
There are still a couple though i don't think any are in development any more. Since it seems to have only happened once so no need to try out different kernels. I wouldn't worry about it at all unless it becomes a regular occurrence.
This seems to have happened to many others with the stable CM7 rom version.
In another post someone who had the issue reported that switching to Netarchy's kernel addressed the problem for him.
This happened already twice today so looks like I need to find a solution.
How difficult it is to replace just the kernel?
Get ahold of a GB compatible kernel, wipe dalvik cache and flash the kernel .zip file. Do a NANDROID backup beforehand (CWM -> backup) if you don't have a recent one already.
In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?
kalda01 said:
In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?
Click to expand...
Click to collapse
CFS is a fairer CPU allocation scheduler, and generally better for multitasking as well as overall performance. BFS is, in theory, better at doing only the "task at hand", but so far hasn't proven any better than CFS, and is additionally less stable most of the time. tl;dr, get CFS.
Kernel should work fine on 2.3.7, don't stress about it. In the event that something goes wrong, just make sure you have a backup anyway.
netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?
kalda01 said:
netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?
Click to expand...
Click to collapse
Yup, it's OK to use it anyway. Also kernel is flashed via recovery.
Sent from my Nexus S from Tapatalk
Any need to wipe or reset the phone before flashing a new Kernel ?
kalda01 said:
Any need to wipe or reset the phone before flashing a new Kernel ?
Click to expand...
Click to collapse
No need. Simply flash the kernel, via fastboot
flashed the kernel via recovery. I'll report back if the SOD problem is resolved.
5 days later and not even a single "SOD" freeze. looks like changing the stock kernel
did the trick.
3 weeks after flashing the Kernel and the SOD problem is back. 3 times in last 2 days.
Anything I can tweak to avoid these freezes ?
Hello good people of XDA i own a gs4 for about a year. Absolutelyawesome phone, ... But recently i've had some problem.
Ok so let me explain if i was to lock my phone for longer time not touch it (1 hour or half an hour) when i unlock touchwizz freezes tho i can use things like notification bar.
So i tried fixing it. it happened to me before
- my phone is rooted
-it's not the battery
The only thing that helps is install a custom rom or install a custom rom and then revert to stock.
And i do root the phone, i know i can fix it clean install custom rom then stock rom, but i really have a lot of stuff on my phone.
I am using stock rom all the time and it could be that the problem is Root or something i really dont have a clue
I apologize if i posted incorrectly please let me know if you have a soulution im glad to take it
mariovracun said:
Hello good people of XDA i own a gs4 for about a year. Absolutelyawesome phone, ... But recently i've had some problem.
Ok so let me explain if i was to lock my phone for longer time not touch it (1 hour or half an hour) when i unlock touchwizz freezes tho i can use things like notification bar.
So i tried fixing it. it happened to me before
- my phone is rooted
-it's not the battery
The only thing that helps is install a custom rom or install a custom rom and then revert to stock.
And i do root the phone, i know i can fix it clean install custom rom then stock rom, but i really have a lot of stuff on my phone.
I am using stock rom all the time and it could be that the problem is Root or something i really dont have a clue
I apologize if i posted incorrectly please let me know if you have a soulution im glad to take it
Click to expand...
Click to collapse
Are you sure it's not the battery I had the same issue with a previous gs3 and was remedied with ac new battery
1eyedmonster said:
Are you sure it's not the battery I had the same issue with a previous gs3 and was remedied with ac new battery
Click to expand...
Click to collapse
I dont think its the battery because you see if i install custom rom then stock its fixed for about 2 weeks then it "comes back" the problem
Idk i can try with a new battery maybe it'll do the trick