So I just tried something stupid, and I was wondering whether there was a faster fix than the one I'm imagining. I downloaded an altered screen state script for the Glitch kernel (would allow me to set my own governor) and instead of incorporating it into the script and flashing that, I just pushed it directly into the system/etc/init.d folder and rebooted. Now I'm stuck at the Glitch boot load screen.
My question is, can I reflash just the kernel to my soft bricked phone, or will I have to go completely back to EB01+atlas pit and reflash CM7, GAPPs, kernel, etc?
Thanks!
Ritchell said:
So I just tried something stupid, and I was wondering whether there was a faster fix than the one I'm imagining. I downloaded an altered screen state script for the Glitch kernel (would allow me to set my own governor) and instead of incorporating it into the script and flashing that, I just pushed it directly into the system/etc/init.d folder and rebooted. Now I'm stuck at the Glitch boot load screen.
My question is, can I reflash just the kernel to my soft bricked phone, or will I have to go completely back to EB01+atlas pit and reflash CM7, GAPPs, kernel, etc?
Thanks!
Click to expand...
Click to collapse
*Warning - I'm not an expert*
That said, the problem is going to be getting in to the proper CWM. If you can get into blue, I would try flashing the kernel. If you can only get into red, you might be able to get away with just reflashing the CM7 ROM. I'd try that first before going all the way back.
Great idea! I was practically allergic to the three finger recovery because I'd been told to avoid it, but when I did it I got to the blue recovery, flashed the kernel, and now I'm back up and running. I don't know if there's a world of pain and glitches for what I did, but I'm happy to just have something usable again.
Now the question is whether I want to retry this script with a legitimate flashing.
Related
So, I messed up. The plan was to uninstall RyanZA's lagfix, then flash JAC's new OC/UV kernel with Voodoo. I got distracted, and didn't uninstall the lagfix before flashing (through Clockwork, if that matters). My phone didn't boot after an hour, so I figured I'd nandroid back and not be so stupid this time. When I tried, I found that I couldn't because of the change to the /data from Voodoo. So then I figured I'd just use Odin to go back to stock, I've done it a couple of times before. That didn't work either, Odin went just fine, but it still doesn't get past the black screen. I read the Voodoo thread, and saw the "disable-lagfix" thing you can do, but now I can't mount my sdcard, and when I try to push it with ADB, it says permission denied. How can I fix this? Also, as an aside, since I flashed the stock back on, with the T-Mobile boot anim and all that, will I be able to get it replaced, if need be?
Flash this first:
http://forum.xda-developers.com/showthread.php?t=740558
Then flash back to stock with odin, worked for me.
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Zaphodb2002 said:
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Click to expand...
Click to collapse
Yeah, I soft bricked my phone yesterday and couldn't get it back up and running with the stock rom until after I flashed eugenes froyo rom first. My guess is that because eugene codes his roms to automatically format your OS drive it clears everything out and sets a fresh slate so you can than flash the stock rom back without issues.
Pure speculation on my part though. Glad you got it fixed.
I tried to install a custom boot animation and wound up having to use CWM recovery to get out of weird looping behavior. I'm not sure exactly what the restore function wipes (for instance, my Vegan ROM was still installed).
Since that episode I've been seeing more Forced Closures than before. I wonder if I need to repartition again. What values should I see if am or am not partitioned 2048/0 and where would I look for those? Thanks.
Surely someone can tell me what to look for as an indicator.
I promise to stop calling you "Shirley."
Rick,
I don't think it's personal -- there just is not a place you can look and see your
partitioning.
If you were boot looping, used CWM to stop it, repartitioned 2048/0 and are running
smoothly now I wouldn't worry about it.
Rev
EDIT: On further thought, I think if I were having glitches (like the FCs), I would
reflash back to stock, install CWM and clean up and reset as needed, and make
darn sure everything was working and exactly right -- and then go my way from
there. But that's just the way I work.
Thanks, Rev.
Thing is, I did not repartition (or, rather, re-repartition) after recovery. Have I necessarily reverted, due to CWM recovery, to the unreliable stock partition (bearing in mind that the device wasn't totally wiped; the Vegan ROM was still in place)?
EDIT: I understand that reflashing to stock and starting over will address any issue. I'm just trying to learn.
Rick,
If you boot into recovery using power/volume + and you get CWM you are still in
ClockWorkMod and have not reverted to stock recovery.
I understand you are trying to learn. I just don't like "flaky" anything so I "make sure"!
Rev
Girlfriend got a Fascinate yesterday and deemed me worthy enough to root it so she can kill all the bloatware (yay for me!). I've got root on the phone, and I understand that if I don't flash a custom kernel for the phone, it'll just break the recovery (using "cwm-recovery-all.tar") as soon as the phone boots up. She likes the overall touchwiz experience and all that, so I'm not sure of any rom's that are pretty stock cept for bloat, and any kernels I should use so recovery doesn't break.
I'm just concerned about getting recovery to stick so that I can perform a backup in case anything should happen.
I have a OG Droid, so all this bending over backwards for root and recovery is new to me and threads seem either too full of info or not enough for me, so here's me asking for help!
Either way, thanks!
Dustin
seraph_harim said:
Girlfriend got a Fascinate yesterday and deemed me worthy enough to root it so she can kill all the bloatware (yay for me!). I've got root on the phone, and I understand that if I don't flash a custom kernel for the phone, it'll just break the recovery (using "cwm-recovery-all.tar") as soon as the phone boots up. She likes the overall touchwiz experience and all that, so I'm not sure of any rom's that are pretty stock cept for bloat, and any kernels I should use so recovery doesn't break.
I'm just concerned about getting recovery to stick so that I can perform a backup in case anything should happen.
I have a OG Droid, so all this bending over backwards for root and recovery is new to me and threads seem either too full of info or not enough for me, so here's me asking for help!
Either way, thanks!
Dustin
Click to expand...
Click to collapse
You're just a few steps away.
First download this stock ed01 debloated/debinged stock ROM from link below and place in root directory of SD card:
http://www.multiupload.com/BKHF5DKJ18
also, choose a kernel and place on sd card. I recommend imnuts' PB&J variety-you might want to stick with stock voltage or -50uv for now. Be mindful to get non-voodoo if you aren't planning on getting into this. found here (try the 3rd or 5th option):
https://sites.google.com/a/imnuts.net/android/kernels
Next, use Odin to install your CWM again. When you boot up this time, boot directly into CWM by turning phone off, and holding volume down, volume up, and power (all 3) until CWM appears. flash your rom, and kernel. If you don't boot into cwm directly by this method, the stock kernel will overwrite CWM, which is what was happening to you, i believe.
after rom/kernel is installed, choose reboot system now from cwm.
Yeah, I just wasn't sure about what kernel would be good for her phone, so I just was kinda "stuck" at that point. ^^;;
But I will give it a go and she how it works out! thanks much!
Everything was a success, and there was much rejoicing!
They only thing I noticed was after the Samsung bootloop animation, it goes to the default "android" one instead of Verizon's... I'm sure there's a way to get that back, but its not in the system dump I have. I'm currently searching for it on the net ^^;;
Thanks again!
Edit: I was able to find a boot animation that had the first part of the Galaxy S bit without the Verizon part. When it booted it just repeated the "Galaxy S" animation. I thought by adding, renaming, and reversing the shutdown animation would at least give that back, but now I just get a black screen for that segment...Still working on it....I think it has to do with the txt file inside, but i'm not sure.
The PowerOn.wav is still present on the phone, but it doesn't play either.... >_<
Are you certain you put poweron.wav in /system/etc folder?
Yup, its there and plays fine in the media player, but I just noticed that there's also a PowerOn.snd file right above. Could that be interfering?
Make a backup elsewhere of that file, then delete it and see if that works.
Sent from mah Fascinate using XDA Premium App
The sound won't work with most kernels that are not stock because the boot sounds aren't actually turned on in the kernel
Swyped from my CM7 fascinate
Oh okay, any chance to get the default boot animation from any of you guys? She doesn't mind the sound "missing," but she would like the boot animation at least.
Eitiher way, thanks much for the info!
since it seems like you're using a stock Rom just debloated and rooted, you may want to think about just using the stock Kernel with the recovery wipe removed, it has two options one that sticks with the stock boot animation and may still have sound and one that allows custom boot animations. This kernel was created by imnuts and can be found here:
http://forum.xda-developers.com/showthread.php?t=1060457
Awesome, thanks! I'll give that a try and see how it turns out!
And it worked! Thanks again!
this is what i get for oding late at night but i managed to do something very very stupid I odined my phone with a one click package for my captivate
I've been able to get the phone back in mostly working order now though.. but i feel in my gut something still may not be right.
here is where i got the package
http://forum.xda-developers.com/showthread.php?t=1300843
This below is what version i accidently installed.
I897UCKI2 Android 2.3.5 Gingerbread
With Bootloaders - Link to thread - Second Post [With CWM Injected Kernel from Boog]
so after i made this mistake.. (noticed my phone had a at&t bootscreen an wouldn't load) I went forth an flashed stock firmware avail for aiotools for the vibrant an then installed the stock froyo bootloader
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
help sugestions banter calling me a noob I just want to make sure i did possibly everything to fix this mistake.
pintek said:
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
Click to expand...
Click to collapse
You,my friend, dodged a bullet here.
pintek said:
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
Click to expand...
Click to collapse
Well, when you say you are not able to get CM7 to install, what exactly is it doing?
Are you getting thrown into a bootloop (caused by CWR mismatch and pretty common)? If so, pull battery and boot into recovery and re-flash CM7 over itself again. No wipe. Then reboot.
You may have to flash a different kernel, like glitch or something like that. But try the above first. Should work for you. Does it still say ATT when you boot up?
Lucky for you, everything is good, but if you want to flash a GB or higher ROM, i would suggest you flash the bootloaders in this thread: http://forum.xda-developers.com/showthread.php?t=1117990
After that just flash CM9, and you *should* be good, if not, try flashing it again with wiping data, cache, and dalvik cache. I guarantee that will work.
I ended up having to format both SD cards an retrying install custom rom via aio tool an with luck was able to get cm7 installed then cm10 an i dno't have the ime error everyone else seams to have . I did before this flash the gb bootloader over this cause it was the only thing that managed to remove the at&t splash screen before the kernal.
Lesson I learned....
remember that the vibrant you use aio tool not a premade pack >.<
an ya i do own both phones so this does complicate things now an then <,<
I also have both devices. Set up two different folders on your pc, one marked i897 and the other t959. I also add i897 or t959 to any files that could possibly get mixed up in Odin.
Its peanut butter jelly(bean) time...
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737