Related
I flashed the accurate battery mod with the ji6 update and now it won't boot. I'm stuck in force closes during the boot process. I downloaded the stock battery file to my pc, but can't figure out how to get it on the sd card. currently I am able to boot into recovery mode, but it won't let me access my files to put the stock battery zip back on the phone. Can someone please help me with this
jstein222 said:
I flashed the accurate battery mod with the ji6 update and now it won't boot. I'm stuck in force closes during the boot process. I downloaded the stock battery file to my pc, but can't figure out how to get it on the sd card. currently I am able to boot into recovery mode, but it won't let me access my files to put the stock battery zip back on the phone. Can someone please help me with this
Click to expand...
Click to collapse
should have read to see if it's compatible with JI6 before flashing
you need to flash back to stock with Odin
flash froyo from euguene that won't brick with odin then downgrade to ji6 i suggest you after you downgrade flash bionix 1.7 with ji2 modem is the best rom and fastest out there
Intel_x said:
flash froyo from euguene that won't brick with odin then downgrade to ji6 i suggest you after you downgrade flash bionix 1.7 with ji2 modem is the best rom and fastest out there
Click to expand...
Click to collapse
why?
just reflash JI6 with Odin
problem fixed
his framework file is ****ed up, that's it
hydrogenman said:
should have read to see if it's compatible with JI6 before flashing
you need to flash back to stock with Odin
Click to expand...
Click to collapse
I was told in another thread that it should work. Do I need to flash back to stock, couldn't I just put the stock battery back on to essentially undo what I did?
hydrogenman said:
why?
just reflash JI6 with Odin
problem fixed
his framework file is ****ed up, that's it
Click to expand...
Click to collapse
That worked! thanks for the help
Re-Boot to "Recovery Mode" and "Wipe" Menu 3, 4
then reboot the phone again. It's work for me.
Please post questions in the Q&A forum or as part of the thread in which you found the item that caused the problem. This keeps the development forum from getting crowded.
Thread moved.
As far as modifications to the themes or anything else related to the framework, they tend to be VERY framework specific and frameworks change on each ROM version.
Sorry for being a noob.
but i install the voodoo lag fix through recovery mode and it stucked at vibrant/samsung loading page for 30 mins..i think something is not right..
i pull the battery. and reinstalled it. it stays in vibrant/samsung loading page now.
i tried recovery mode wipe all data...nothing work.
then i tried flash the origianl stock rom and it stucks...
i tried odin flashed the voodoo again...nothing works..
what should i do?should i flash another rom?
We'll need some more background on your current setup.
What Rom are you flashing Voodoo on and which voodoo are you flashing? You need to pick a voodoo that closest matches what the Rom is built on.
When flashing voodoo through clockwork, do you hear Linda? She should be telling you what progress you're making. It does take a bit of time so if you're hearing her then be patient.
Head on over to the developer section and flash Axura 2.2.5.7 which comes with voodoo. Easy peasy.
i m running stock tmobile 2.1 rom
download the Voodoo lagfix-only 3.0 Update.zip
i dont hear linda.
i am flashing the stock kernel and rom right now ..
waiting to see the out come after flash...
and i have a samsung captivate as well..
i know the processes of linda..
vibrant is not my phone..so...i really worried..
ok..stock kernal flashed..
stock rom flashed..
loading the tmobile and galaxys start page..then run into black screen.
chaolanren said:
ok..stock kernal flashed..
stock rom flashed..
Click to expand...
Click to collapse
Well lets get the phone working again first.
Did you use the .512 .pit and JFD .tar for a Vibrant?
yes i am flashing with 512 and stock rom.
i will try custom now..
From what I'm gathering the 3.0 voodoo update.zip is for the I9000 and not specifically for the Vibrant. I can't seem to find any Vibrant Eclair voodoo kernals.
Here's Supercurio's post for Vibrant Kernals Link. All of these are 2.2 Froyo Kernals.
Just to be clear that you got the true stock firmware read Here.
I personally would try any custom Roms until you get back to stock.
did i break my kernel or baseband?
i flahsed the true roms.....it is just not getting into the home page..
chaolanren said:
did i break my kernel or baseband?
i flahsed the true roms.....it is just not getting into the home page..
Click to expand...
Click to collapse
Try to flash them again using the link above.
Make sure you have Odin 1.3 or greater as well. 1.0 is known to be buggy.
I believe you broke your Kernal.
Try to download the files I linked to make sure yours aren't corrupt.
You can always try Eugene's froyo that doesn't brick. I can't find it on XDA at this time though...
EDIT - Here's working .pit and .tar stock files.
512.pit
T959UVJFD.tar
Hey drew if im out of line I apologize. But he said he had a captivate. Would the firmware be the same for our vibrants and the cappy.
Powered by Axura with a dash of Voodoo
thx bro,
trying again..even i use the same files..
but i realize i used odin 1.0 the 2nd time..
using 1.3 again to see.
he said it was stuck on the vibrant screen then he is also saying that he doesn't have a vibrant. Maybe he's flashing the wrong .tar that's why odin isn't working.
dude what's really your phone?
i m working on vibrant.
i m flashing vibrant rom on virbrant.
i have a captive. nothing to do with this
flashed again.. still black screen. after tmobile/samsung logo.
try to use this.
http://forum.xda-developers.com/showthread.php?t=790026
did you try checking the re-partitions?
i used 1.3 odin
and tried re-partitions.
well..i think...i need to try flash custom rom
can anybody tell me which rom i can flash through odin?
i see all rom manager ones..
This is Eugene's Froyo that doesn't brick.
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.htm
But wait for the suggestions of others before you flash this. Literally, how many minutes are you waiting for when it boots?
about half hour now..
iynfynity said:
This is Eugene's Froyo that doesn't brick.
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.htm
But wait for the suggestions of others before you flash this. Literally, how many minutes are you waiting for when it boots?
Click to expand...
Click to collapse
this is for vibrant right?‘
also i see this is zip. does it include tar inside? thx
EC01 must be old, right? Not so. I cannot give you the build date however, per request of...someone else. Its considerably newer than EC10, however. For some it may be hard to take my word for it, but I have never lied to anyone here.
In here you will find a new shiny radio, a voodoo or non voodoo EC10 kernel, courtesy of JT1134, and...a ROM!
No more hacking pieces together from other devices. No more crappy radios (hopefully). No more poor GPS (hopefully).
Please do not ask where it came from. I will not tell you. All file dates have been changed, the build.prop has been masked.
Please do not ask for an Odin. I will not give you one at this time.
Please enjoy yourself, I insist.
This ROM is ever so slightly tweaked. It is not a quality release by my standards (mostly because its stock). I recommend folks wait for the community rom to be finished. If you can't wait, by all means, flash away.
Does not include a kernel.
Debinged, browser included.
Debloated, yet contains most stock apps.
Custom boot animation, because I am not including the original kernel.
Dialer voicemail button points to Google Voice.
Your current kernel will be retained. So if you are using a Froyo kernel, you will be just fine.
Xoom boot animation because you will be using a custom boot animation supporting kernel.
Installation Instructions (read carefully)
---------------------------------------------------------
Make a nandroid backup.
Odin back to EB01 stock.
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
Boot once, then Odin clockwork recovery.
http://adbdev.com/danknub/cwm-recovery-ALL-3-30-FIX.tar
Boot straight to clockwork recovery, and flash my kernel of choice from here:
http://forum.xda-developers.com/showthread.php?t=1003017
Boot once, convert to voodoo if need be.
Boot back to clockwork recovery and flash rom.
Boot once, then Odin the radio.
Please follow these directions. There are apparently some kernel/cwr issues that are causing boot loops. If you decide to flash another kernel afterwards, be my guest. Don't wipe, however. The above directions are after hours of testing by IRC folks, and I THANK all of them!!!!!
Radio:
http://adbdev.com/danknub/ec01_radio.tar
Rom:
http://www.multiupload.com/ETEG610SJR
Reserved.
Edify compatible version coming out tomorrow.
<3 your the man
Much thanks man. You're always coming through for us. Thanks for continuing to work on the fascinate.
Sent from my SCH-I500 using XDA App
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
NM me. I followed your post to a T and I was able to flash a diff kernel then. THanks guys
Great work! Thank you for the work. I'll take your advice and wait for the community rom, but VERY much appreciate your work.
jrobinsky said:
for me, only your kernel works dude. I tried a few other ones after my initial boot and i get stuck on boot loops. IDK about anyone else, but thats my results.
Click to expand...
Click to collapse
I was able to get times_infinity's comavolt voodoo to work, but only if I ODIN'd back to EB01 stock, then ODIN'd ec01 radio, ODIN 03/30 cwm fix, boot directly to recovery, flash ec01 rom, flash comavolt kernel, boot was successful. Going to play with it a bit tomorrow.......errr later today after I get some sleep.
Copied from my "Most Thorough Method of Fixing Every Problem You Might Have" section in the recovery thread, and adapted to this post.
This will wipe your data, btw, so be sure to backup any important info. You can make a nandroid backup, but you will probably have issues if you try to restore the data to use with this ROM.
[SIZE=+2]Bestest Best Way to Install This ROM[/SIZE]
Download to PC
CWM-Recovery 3-30 Odin Package
MD5 Checksum: 00e90e790a70e2d66b6cba6a152de504
ec01_radio.tar Odin Package
MD5 Checksum: 099c7cf67e14fea5c9bbd886a83e48b1
CI500_VZW_EB01_FROYO_REL.tar.md5
MD5 Checksum: d04733ce540ab1af291cfa44d42c768e
atlas_v2.2.pit
MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538
Place on /sdcard
ec01_rom.zip
MD5 Checksum: 30849feb8d53b05c611fc9b03263a414
The kernel of your choice
Step-by-Step Installation - Important!
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package
Close odin, Unplug/replug the phone from USB, re-enter download mode, Re-open odin.
ODIN the modem
Unplug USB Cable, THEN reinsert your battery
Hold both of the volume keys and the power button down until a second after you see the Samsung boot logo, then let go
It should now boot into red CWM recovery
Wipe Cache only. Flash the ec10_rom.zip
Flash the kernel of your choice
Reboot. If you have installed a voodoo kernel, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
I can't stress enough how important it is to check your files for the correct checksum to verify that your download did not get corrupted (you can also use it as a way to make sure you have the right version). Also, follow these instructions exactly. You could potentially be wasting your time and anyone else's who is trying to help you fix whatever random issue you might be having, merely because you didn't follow the instructions.
I've been scanning threads for news of this mystery drop since your first hint and just as I'm about to cash out for the night... OMFG! You f'ing rock mate! Now, if I can only find the strength to hold out for the community brain child... I know it will be worth the wait. Oh, but a tasty new radio sure sounds delicious right now!
Thanks again Adryn for everything you've done to make this phone great!
Sent from my #@&$ing SCH-I500 using my %!#@ing XDA App
justin94 said:
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
Click to expand...
Click to collapse
For now you can just get them from the superclean thread. Same ones.
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Sent from my SCH-I500 using XDA App
tripacer99 said:
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Click to expand...
Click to collapse
Yes, I believe it was verified to work just fine.
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
lucas.scott said:
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
Click to expand...
Click to collapse
Are you using Adrynalyne's steps or GizmoDroid's steps? Did you reboot phone and let it fully boot into OS before powering down to pull battery to start new ODIN session?
of course ... and im no stanger to odin or anything .. new problem for me
lucas.scott said:
of course ... and im no stanger to odin or anything .. new problem for me
Click to expand...
Click to collapse
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
landshark68 said:
For now you can just get them from the superclean thread. Same ones.
Click to expand...
Click to collapse
Which kernel are you using from the superclean thread? eb01 or eb16?
DeezNotes said:
Which kernel are you using from the superclean thread? eb01 or eb16?
Click to expand...
Click to collapse
Neither. EC10
landshark68 said:
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
Click to expand...
Click to collapse
thanks for the link man . that did the trick . bad DL i guess . thanks .
These kernels are the stock ED01 kernel that have been modified to remove the recovery flash that happens with the standard stock kernel on every boot. Nothing else has been modified. If you flash this, you can retain CWM, but these do not have any other changes or enhancements. There are two versions, stock and boot animation support. Stock uses the stock Samsung boot animations that the phone comes with. The second version enables custom bootanimation.zip support. These packages are Odin only, and I have no plans on making a non-Odin version.
Download:
Stock
Boot Animations
Thanks for the work man!
Sent from my SCH-I500 using XDA App
The stock boot animation one fails in Odin with an invalid MD5 hash, but I extracted the zImage, put it into a CWM flashable zip and it installed fine.
Is there really any benefit to these kernels? Because
I get great results with your -100uv kernel!!
ChrisDDD said:
The stock boot animation one fails in Odin with an invalid MD5 hash, but I extracted the zImage, put it into a CWM flashable zip and it installed fine.
Click to expand...
Click to collapse
You do realize that the MD5 hash is the verify that what you downloaded isn't corrupt? And that redbend_ua has no method to verify the validity of a file? And that what you did completely ignores the point of making the files .tar.md5 files?
imnuts said:
You do realize that the MD5 hash is the verify that what you downloaded isn't corrupt? And that redbend_ua has no method to verify the validity of a file? And that what you did completely ignores the point of making the files .tar.md5 files?
Click to expand...
Click to collapse
Yea, I know all that, but I thought I'd give it a try anyway. I figured I could always Odin one of the whole packages if it didn't work. I did download it several times to see if it was a corrupt download, and they were all the same.
pntballer505 said:
Is there really any benefit to these kernels?
Click to expand...
Click to collapse
Yes, they can be packaged together with CWM for newbies.
I'm on stock ED01. To prevent running the stock recovery, I renamed the following files:
/system/recovery-from-boot.p
/system/bin/recovery
/system/etc/install-recovery.sh
After they were removed, I re-flashed Clockwork 3 via Odin.
I have to say, I've been running this totally stock ED01 kernel for a week now, and I'm getting the best battery life out of ANY of the 2.2 (EB01 through ED01) kernels I've tried. Consistently getting 48 hours per charge pretty easily with normal use. I tried the undervolted kernels, and I tried underclocking, both of which had some instabilities, but this has been totally solid. Who'd have thought... from a stock kernel...
ChrisDDD said:
I have to say, I've been running this totally stock ED01 kernel for a week now, and I'm getting the best battery life out of ANY of the 2.2 (EB01 through ED01) kernels I've tried. Consistently getting 48 hours per charge pretty easily with normal use. I tried the undervolted kernels, and I tried underclocking, both of which had some instabilities, but this has been totally solid. Who'd have thought... from a stock kernel...
Click to expand...
Click to collapse
The best battery life I have ever had with my Fascinate was using the EC01 ROM which is nearly the same as ED01. I've had horrible and now bad (it's better now, but not what I would call good) battery life with the community rom combined with OTB reloaded kernel.
I'm going to un-voodoo and flash this kernel and see what happens.
Is the kernel from ED03 any different at all? Could it be made recovery safe?
Any chance of adding the tether null to this? I love the stock kernel but need to tether without worry. Thank you
Thanks a lot
I saw alot of people asking about these, so I've repacked the stock Modem, Bootloader, Kernel and Recovery from the full .tar separately as Odin flashable .tar's for anyone who needs them. And also created a recovery flashable stock kernel.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Flashable in Odin:
Bootloader/BL:
Bootloader
Bootloader Mirror
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Full .tar thanks to @GSXeclipsePSI and SamMobile
Flashable in recovery(I used TWRP):
Stock Recovery Flashable .zip
Thanks so much for posting these. I upgraded modem, bootloader and kernel no problem.
Stock kernel seems to work better than the ktoonsez one (for me at least), but i don't think I can get SElinux to be permissive on the stock kernel (doesn't seem to stick when I use SElinux mode changer app), which in turn seems to mean I can't use Viper...so I flashed back ktoonsez kernel since I can't live without Viper
Any thoughts on what I may be doing wrong...I know this isn't a Viper thread, but I'm pretty sure I read over there that SElinux permissive was a must for Viper to work, so if stock kernel doesn't allow for that, then my next thought is it possible to have stock kernel that's SElinux permissive?
How did you guys install the stock kernel? I used odin, wiped cache, and all I get is the initial Galaxy S5 Power By Android logo and it never goes past this.
did you try pulling the battery before you start the phone up on download mode? I always have to do that first and the always works for me.
cyhamada said:
Thanks so much for posting these. I upgraded modem, bootloader and kernel no problem.
Stock kernel seems to work better than the ktoonsez one (for me at least), but i don't think I can get SElinux to be permissive on the stock kernel (doesn't seem to stick when I use SElinux mode changer app), which in turn seems to mean I can't use Viper...so I flashed back ktoonsez kernel since I can't live without Viper
Any thoughts on what I may be doing wrong...I know this isn't a Viper thread, but I'm pretty sure I read over there that SElinux permissive was a must for Viper to work, so if stock kernel doesn't allow for that, then my next thought is it possible to have stock kernel that's SElinux permissive?
Click to expand...
Click to collapse
I have the same problem, nothing sounds as good without Viper But i'm dealing with the stock kernel for now.
ALaz502 said:
How did you guys install the stock kernel? I used odin, wiped cache, and all I get is the initial Galaxy S5 Power By Android logo and it never goes past this.
Click to expand...
Click to collapse
As cyhamada says above, you sometimes have to pull the battery before going into Download mode. Also, try a different version of Odin. With Odin 3.09 flashing the full .tar results with my phone sitting on the boot logo.
Updated Bootloader/Modem, yet my Baseband hasn't changed from NK2, shouldn't it change to the OB1?
I'm running CM12, boots fine, LTE signal's been junk since upgrading to NK2 and was hoping this new modem would have some corrections. (Phoenix, AZ)
Paulenski said:
Updated Bootloader/Modem, yet my Baseband hasn't changed from NK2, shouldn't it change to the OB1?
I'm running CM12, boots fine, LTE signal's been junk since upgrading to NK2 and was hoping this new modem would have some corrections. (Phoenix, AZ)
Click to expand...
Click to collapse
You have to be on stock for it to stick, and sometimes it will take a couple tries of lashing it even then, usually the best way is to pull battery and then boot into download.
aaricchavez said:
You have to be on stock for it to stick, and sometimes it will take a couple tries of lashing it even then, usually the best way is to pull battery and then boot into download.
Click to expand...
Click to collapse
I actually got it to stick on cm12 after pulling battery.
spidey2483 said:
I actually got it to stick on cm12 after pulling battery.
Click to expand...
Click to collapse
Really? What i've always seen and experienced is that you have to be on stock, on previous updates I had to go to stock to get it to stick. I guess ymmv.
aaricchavez said:
Really? What i've always seen and experienced is that you have to be on stock, on previous updates I had to go to stock to get it to stick. I guess ymmv.
Click to expand...
Click to collapse
It stuck after I did a battery pull on the 3rd or 4th try, the blue "secure boot: enabled" appeared when it actually worked. I went from Recovery > Download, odin flashed, pulled battery, odin flashed and it worked.
bootloader went fine but modem causing me to hang on sammy screen and i cant seem to get past it no matter what i try.
tried kernel now im hung on GS5 screen. lol
aaricchavez said:
I saw alot of people asking about these, so I've repacked the stock Modem, Bootloader, Kernel and Recovery from the full .tar separately as Odin flashable .tar's for anyone who needs them. And also created a recovery flashable stock kernel.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Flashable in Odin:
Bootloader/BL:
Bootloader
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Full .tar thanks to @GSXeclipsePSI and SamMobile
Flashable in recovery(I used TWRP):
Stock Recovery Flashable .zip
Click to expand...
Click to collapse
Bootloader link is not working for me can anyone provide working link? Thank you all in advance.
ledezma2003 said:
Bootloader link is not working for me can anyone provide working link? Thank you all in advance.
Click to expand...
Click to collapse
It looks like it's up from here. Here's a mirror though.
Bootloader Mirror
aaricchavez said:
It looks like it's up from here. Here's a mirror though.
Bootloader Mirror
Click to expand...
Click to collapse
Thank you this one worked.
is there a way to root if were on lolipop?
darren.wlsn1 said:
is there a way to root if were on lolipop?
Click to expand...
Click to collapse
Have you tried CF-Auto-Root? Next thing after that I would say install TWRP and exit, it will ask to root if it doesn't detect root.
aaricchavez said:
Have you tried CF-Auto-Root? Next thing after that I would say install TWRP and exit, it will ask to root if it doesn't detect root.
Click to expand...
Click to collapse
ya i got twrp on through cf but had to sideload in twrp but never got sideload to open but now in stuck on tmo screen and never been stuck there
darren.wlsn1 said:
ya i got twrp on through cf but had to sideload in twrp but never got sideload to open but now in stuck on tmo screen and never been stuck there
Click to expand...
Click to collapse
How long has it been on the boot animation? First boot/first clean boot(new kernel, etc.) for Lollipop takes a while to build ART.
aaricchavez said:
How long has it been on the boot animation? First boot/first clean boot(new kernel, etc.) for Lollipop takes a while to build ART.
Click to expand...
Click to collapse
any tar i flash now is hanging on tmo screen for as long as i let it sit, im at point i just want it vto boot no matter what build i use
bit the bullet and reset in stock recovery
darren.wlsn1 said:
any tar i flash now is hanging on tmo screen for as long as i let it sit, im at point i just want it vto boot no matter what build i use
Click to expand...
Click to collapse
Here's what I would do if I were in your situation. Grab the full OB1 .tar and Odin 3.07 along with TWRP. I would: Odin TWRP>Do a factory reset>Pull battery>Boot into Download mode>Flash OB1>Let it sit for about 20 min. If you have adb set up on your computer I would also do "adb logcat" to see what exactly is going on. Although I don't recall if it'll pickup after a factory reset, I just do it so often on mine I never pay attention.
If that failed I would Odin TWRP and grab one of the Lollipop roms and flash that.