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.
Related
I'm kinda new to all this mod stuff, so before I do anything I wanna be 100% sure of myself.
I originally had ryanza's OCLF on my Vibrant, but when Voodoo came out with all it's praise, I decided to convert. So I undid OCLF and flashed Voodoo. To be honest, I saw no difference between the two lag fixes. OCLF was working fine for me.
But anyways, all was well for a few days before, one day driving to work in the morning, my phone is playing music when suddenly it freezes. Screen won't unlock, nothing lighting up, totally frozen. So I held down the power button for 5 seconds to shut it off and reboot, and it was fine again. At first it was happening intermittently, now it's pretty much every time I listen to anything. I figured it was a result of Voodoo, so I tried disabling it with the 'disable lagfix' folder. Still the same deal. I feel like it's something with the kernel modification causing the issue. Even if it's not Voodoo causing this, me with my OCD would really like to go back to OCLF, which worked fine. I haven't gotten the JI6 OTA yet, so I wanna go back to stock kernel/firmware before the update hits my phone.
My question is, will following this guide get me back to where I want to be?
forum.xda-developers . com/showthread.php?t=734475
Thanks.
coasterman927 said:
I'm kinda new to all this mod stuff, so before I do anything I wanna be 100% sure of myself.
I originally had ryanza's OCLF on my Vibrant, but when Voodoo came out with all it's praise, I decided to convert. So I undid OCLF and flashed Voodoo. To be honest, I saw no difference between the two lag fixes. OCLF was working fine for me.
But anyways, all was well for a few days before, one day driving to work in the morning, my phone is playing music when suddenly it freezes. Screen won't unlock, nothing lighting up, totally frozen. So I held down the power button for 5 seconds to shut it off and reboot, and it was fine again. At first it was happening intermittently, now it's pretty much every time I listen to anything. I figured it was a result of Voodoo, so I tried disabling it with the 'disable lagfix' folder. Still the same deal. I feel like it's something with the kernel modification causing the issue. Even if it's not Voodoo causing this, me with my OCD would really like to go back to OCLF, which worked fine. I haven't gotten the JI6 OTA yet, so I wanna go back to stock kernel/firmware before the update hits my phone.
My question is, will following this guide get me back to where I want to be?
forum.xda-developers . com/showthread.php?t=734475
Thanks.
Click to expand...
Click to collapse
busybox touch /sdcard/Voodoo/disable-lag && reboot
Let it finish, verifiy by:
mount
/data should mount like this if its disabled:
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
If it is on:
/dev/block/mmcblk0p4, it is still enabled. Good luck.
Once you have that lag fix undone, flash any kernel you need again, then reinstall the OCLF.
If you are still on the Stock ROM or a JFD based ROM:
1.) First disable Voodoo it's currently enabled
2.) Go to the Frankin-Twiz thread and download the Stock-Kernel-Vibrant.zip in the Original Post
3.) Copy the file to your internel SD card.
4.) Boot into Clockwork recovery and flash zip from sdcard.
silow said:
If you are still on the Stock ROM or a JFD based ROM:
1.) First disable Voodoo it's currently enabled
2.) Go to the Frankin-Twiz thread and download the Stock-Kernel-Vibrant.zip in the Original Post
3.) Copy the file to your internel SD card.
4.) Boot into Clockwork recovery and flash zip from sdcard.
Click to expand...
Click to collapse
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
dasunsrule32 said:
busybox touch /sdcard/Voodoo/disable-lag && reboot
Let it finish, verifiy by:
mount
/data should mount like this if its disabled:
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
If it is on:
/dev/block/mmcblk0p4, it is still enabled. Good luck.
Once you have that lag fix undone, flash any kernel you need again, then reinstall the OCLF.
Click to expand...
Click to collapse
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
coasterman927 said:
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
Click to expand...
Click to collapse
Then odin flash this kernel:
http://forum.xda-developers.com/showthread.php?t=733792
If you are wanting a full-on restore to stock, then odin:
http://forum.xda-developers.com/showthread.php?t=734475
Good luck.
Moved to Q&A
coasterman927 said:
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
Click to expand...
Click to collapse
The lastest release of Clockwork recovery is not a permanent flash. It is kept in an update.zip file on your internal sdcard which can be easily removed.
You can always follow the ODIN steps in the original link you posted. This will return the phone back to the way it was shipped. Note that it doesn't however wipe your internal sdcard.
If you want to keep your data intact flash only the kernel. Using the ODIN method will wipe your data (factory reset, however not your internal sdcard unless you check the repartition option).
If you are a One-Click root/lagfix type of person I wouldn't recommend using ODIN unless you had to resort to it.
I am unhappy with ji6, my gps and compass no longer work and i've had nothing but problems since the update. also the call waiting dial screen lag sucks. I would like to go back to my previous rom which was basically stock rooted with ji2 gps fix and accurate battery mod. I have this saved as a backup, but I am afraid to flash it. When I flashed the new ota update it bricked my phone. I was unble to load my previous backup through clockwork recovery. I had to completely wipe my data and start over. any advice on the safety of trying to flash back to my backup rom, will it conflict with the ji6 framework?
Thanks
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
yeah, maybe i'll try bionix first, It's just that I was really happy with the way it ran before this stupid update.
I also was fond of my setup before the update. Bionix made it better again. Hope you like it, worst case go back to stock.
I will say I would make sure you can revert to stock from bionix. I have seen a number of posts with issues, but that may be from people who had the oc kernel? I can't say with certainty.
Same here, i flashed bionix (first time using bionix) I flashed bionic 1.7 w ji2 modem oc/uv no voodoo and this thing flies! Gps is fine, navigation is usable.
s15274n said:
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
Click to expand...
Click to collapse
I tried flashing back to my backup...(stock, rooted with bat mod and ji2 gps fix) and it got stuck in the vibrant startup screen, same as when I ran the ota. I guess my previous setup is no longer an option. Before I try another rom and have to redo all of settings and apps again, I would like to try to at least get the gps working on the ota ji6. Any advice on how to do that would be appreciated. So far I have tried all of the things I was able to find in other threads...deleted gps data, made sure lbstest settings are stock, turned off wireless, etc. I still get no locks at all.
Is bionix really that good? I'm considering it. I'm on my stock rom, stock kernel.
I think i'm going to try it out.
Tried to flash a custom ROM for the 15th time or so, with the same result. E: Can't Symlink /system/bin/su
Failure at line 16
Have researched this error, thought I had it figured out. Obviously not. Feel like an idiot. I never had any problems loading custom ROM's on 2.1.
BTW, I am rooted thru S1Click, have backed up thru nandroid and Titanium, have installed 3e custom recovery, everything I have read I could be doing wrong I have changed. I have tried different makers- Bionix, Axura, Eugene, all with hte same errors, so I know it's not just the ROM file.
What am I doing wrong here?
I don't know.. but let's save everyone the trouble of answering this and let you odin back to stock.
It might be something you flashed etc..
tried that too. tried loading these ROM's right after rooting and adding ROM manager. It's just weird that know one can answer a specific problem like "failure at line 16". Surprised there isn't an answer to look up based on the Line 16 error.
I'm not pointing any fingers, because I don't know the answer either. Just know that if you you give me one of the basic replies, like try ODIN to stock, I've probably tried it.
What are you odining to? I've always had success going to back to jfd. Doesn't seem to be any issues with rooting or rom manager.
Trigger + Overstock = Awesomeness
yep. Odining to jfd.
One thing is that I always install 2.2 via mini-kies before attempting to install custom ROM. Reason being that for whatever reason, the super one click just does not want to install on 2.1. Could that be part of the problem?
Here's what I do and it works every time for me.
1. Odin to jfd
2. Root then install rom manager
3. Flash clockwork recovery
4. Download rom of choice to internal sd
5. Flash rom thru clockwork
6. Enjoy
That has never failed me.
Trigger + Overstock = Awesomeness
Check This Out....Tell me If It Helped You
http://forum.xda-developers.com/showthread.php?t=848737
I did it. FINALLY.
Loaded Simply Honey 2.5, and this thing is FAST and awesome. Such a cool ROM. I was so pumped when it actually worked. Thanks for all the help, guys. And all the great developers that put in hte time and work to make our phones what they should be. Good job, guys.
Glad you got it working. The first flash is pretty awesome.
Trigger + Overstock = Awesomeness
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
This is the safest way and the best way.
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