I've been running imnuts' debloated EE4 since last weekend. Rolled back to ED1/Flashed EE4/Edited build.prop ... After I flashed to the EE4 I had EE4 baseband but ED1 build still, hence editing build.prop
When I flased the EE4 the voice spoke occaisionally during first boot, which I assumed was the file structure being re-written. Phone has been working fine all week, no issues there.
This morning, out of curiosity, I tried to enter recovery mode, to see if it were voodoo or stock. vol.up/home/pwr and the samsung logo appears. But it doesn't enter into ANY recovery screen. It just stays at the Sammy logo until I pull the battery. What's up with that?
Also.... with file structure re-written, can this still be flashed back to say the stock rooted ed1 tar file still? Would there be any steps that need to be taken before attempting such?
Looking at voodoo log file lag fix is being enabled and such.
Have you flashed the clockworkmod recovery odin file?
And before flashing anything not using voodoo just disable it.
How would I disable voodoo ?
Just create a filed called disable-lagfix on your sdcard
Or disable it in clockworkmod
Just create a folder in the root directory named disable-lagfix and that does it? So far as cwm goes, that was one of the initial things I posted about. I've always been able to enter recovery mode by holding down up volume/home and power until the samsung logo appears. Then releasing them would bring the recovery screen up. Stock Samsung was blue lettering and then with cwm installed it was yellow with added options on the menu. Now if I try to get to that point, the recovery screen never comes up. It just stays at the Samsung logo and basically is frozen there until I pop out the battery. Phone boots fine into normal use.
Recovery may just need to be reflashed.
But yea you can disable lagfix just to try it so you know how. If disable-lagfix doesn't work try using an underscore instead. Just be sure to reboot so the conversion actually happens
Related
I am going to activate a new device today. Planning on letting OTA EE4 do its thing. Afterwards, what process should I follow to achive root?
Just do a little reading first before asking.
It's in one of the threads. I'll post which one if I come across it.
The step by step is there too.
Done PLENTY of reading before tackling this. Just lots of threads with lots of confusing steps. Just trying to consolidate this process into somewhat simple steps for the beginners. I will attempt to write out the procedure I follow tonight and post it for the beginners. Any help to get this started would be appreciated.
Yes. I have been reading too and did not see clearly how to root after OTA update
Sent from my SCH-I510 using Tapatalk
Can't Find "How to Root from Latest EE4 Update"
I have been reading and searching for the exact same thing - if it is anywhere to be found, it must be buried pretty deep.
There are two ways to root your device. Depending on what you want the end result to be, one way may be quicker than the other.
1. If you want Voodoo and Root, but don't care about custom roms or uv/oc kernels. You can simply use ODIN to flash jt1134's kernel and reboot. It should convert to voodoo on the first boot and you are done.
2. If you want CWM Recovery and the ability to flash custom roms/ kernels in .zip format w/ CWM, You can flash CWM in ODIN and then boot direct to recovery by using the Vol up + Home+ Power button combo, releasing power when samsung logo appers.
Once in CWM flash the rom and kernel of your choice(already on your SDcard) and then reboot.
3. If you want both jt1134's kernel and CWM you just use odin to flash both rebooting in between. First the kernel then CWM.
Once updated
1. Reboot into recovery
2. Wait till you're at the recovery loader
3. Take out battery, disconnect any USB
4. Boot up in loading mode (vol down, plug in USB)
5. When loading screen comes on, you can put the battery back in
6. Use Odin to load the latest CWM (http://forum.xda-developers.com/showthread.php?t=1112804)
7. It'll auto reboot and should put you back into recovery mode. You'll know you're in the right recovery if it's yellow and has the option to install zip from sdcard. If it doesn't take repeat steps 4-6 again (On my wife's phone I had to do it twice)
8. Use CWM to load PBJ's rooted kernel (http://forum.xda-developers.com/showthread.php?t=1104634)
9. reboot
Enjoy!
I too am trying to get guidance on this. I am at what I assume is stock ee4 after taking ota from rooted ed1 flash and I DID lose root.
I flashed the imnuts cwm onto phone a bit ago. It is current file updated yesterday I believe. The problem is that when I go into recovery mode via vol/home/pwr I get into what looks to be still the stock samsung recovery screen with no added options. Then lettering on screen is now blue though where I think it was different prior to flash? Leery of proceeding without some help !!
Thanx In Advance for Any Guidance !!
It has been suggested that you flash the Voodoo kernel after the ROM is installed via CWM it has worked better for many that way.
I tried flashing new cwm using method listed above in reply #7 .... after the flash completed the phone did reboot but to full reboot, it did not boot back to recovery. I shut phone down and go into recovery and it looks to be stock samsung recovery still but lettering is blue:
Android system recovery <3e>
Samsung Recovery Utils for BML
(selections list)
apply sdcard:update.zip
wipe data/Factory reset
wipe cache partition
format internal sd-card
no other options and lettering above is blue
down in screen I have yellow # Manual Mode #
looks to me like cwm flash did not take ?
Edit: Okay I got it !! I flashed again leaving battery out during whole process and now have voodoo cwm ....
On to next step *cringe*
Chopstix9 said:
I tried flashing new cwm using method listed above in reply #7 .... after the flash completed the phone did reboot but to full reboot, it did not boot back to recovery. I shut phone down and go into recovery and it looks to be stock samsung recovery still but lettering is blue:
Android system recovery <3e>
Samsung Recovery Utils for BML
(selections list)
apply sdcard:update.zip
wipe data/Factory reset
wipe cache partition
format internal sd-card
no other options and lettering above is blue
down in screen I have yellow # Manual Mode #
looks to me like cwm flash did not take ?
Click to expand...
Click to collapse
You have to force the phone to recovery mode after flash, by pressing vol up+home+power, releasing power after samsung logo appears. If the phone boots up w/ the stock kernel, cwm is overwritten by stock recovery.
hoppermi said:
You have to force the phone to recovery mode after flash, by pressing vol up+home+power, releasing power after samsung logo appears. If the phone boots up w/ the stock kernel, cwm is overwritten by stock recovery.
Click to expand...
Click to collapse
I flashed again and I am at the CWM Voodoo Lagfix Recovery v 4.0.0.1
I have transfered the imnuts debloated ee4 to the sdcard
I use menu up/down to navigate to selections. After going down to the apply update from sdcard I press the home key to select. It just jumps back up to reboot system now. This happens no matter what selection I attempt to activate using the home key ...
I know I am close, what am I missing here ?
Thanks Tons For The Help
hoppermi said:
There are two ways to root your device. Depending on what you want the end result to be, one way may be quicker than the other.
1. If you want Voodoo and Root, but don't care about custom roms or uv/oc kernels. You can simply use ODIN to flash jt1134's kernel and reboot. It should convert to voodoo on the first boot and you are done.
2. If you want CWM Recovery and the ability to flash custom roms/ kernels in .zip format w/ CWM, You can flash CWM in ODIN and then boot direct to recovery by using the Vol up + Home+ Power button combo, releasing power when samsung logo appers.
Once in CWM flash the rom and kernel of your choice(already on your SDcard) and then reboot.
3. If you want both jt1134's kernel and CWM you just use odin to flash both rebooting in between. First the kernel then CWM.
Click to expand...
Click to collapse
Thanks, I am in same boat, so many threads it is mind boggling.
I see that jt1134's kernel include the voodoo lag fix? What if I just want root. Really all I want it root so I can do some mild de-bloating, but want the phone in a position that if another OTA comes out I can just accept it without worrying.
Thanks!
Chopstix9 said:
I flashed again and I am at the CWM Voodoo Lagfix Recovery v 4.0.0.1
I have transfered the imnuts debloated ee4 to the sdcard
I use menu up/down to navigate to selections. After going down to the apply update from sdcard I press the home key to select. It just jumps back up to reboot system now. This happens no matter what selection I attempt to activate using the home key ...
I know I am close, what am I missing here ?
Thanks Tons For The Help
Click to expand...
Click to collapse
Choose the install zip from sdcard option, then navigate to where debloated rom is and select
Sent from my SCH-I510 using Tapatalk
addictedtocars said:
Thanks, I am in same boat, so many threads it is mind boggling.
I see that jt1134's kernel include the voodoo lag fix? What if I just want root. Really all I want it root so I can do some mild de-bloating, but want the phone in a position that if another OTA comes out I can just accept it without worrying.
Thanks!
Click to expand...
Click to collapse
Sounds like you just want a stock rooted kernel you can flash w / odin. Put in a request in and maybe one of the devs can accommodate you.
For now, I only know of jt's kernel for odin.
Sent from my SCH-I510 using Tapatalk
I'm curious if we will ever see a one click root app for this phone like gingerbreak? What will it take to make it that easy? I have gingerbreak for my tablet(honeycomb 3.0) and it's a snap to switch back and forth.
I only want root to be able to edit some files (starup sounds) and for titanium backup. AND I want to be able to get the OTA updates without having to remeber all the hoops I have to jump through.
I'd gladly pay for a simple root solution for this phone.
I got mine rooted and after many screwups I stumbled onto a 3 step process that was easy as pie. Read my post in this forum 'How I Got to EE4 Root' ....
Hi all. I'm new to android, but not to modding. I've been with xda for a few weeks and have appreciated the quality of the posts and tutorials. Btw-I have searched the forums and google and am still soo lost.
Any help would be appreciated.
Goal:
-To get stock kd1
Previous Config:
-Black Ice KD1, CWM recovery red, voodoo lag fix, ext4 on all, Bali 3.2 no uv, Juwe ram script
-was previously overclocked using tegrak ultimate to 1.2ghz, but about a day before my error it had been put back to 1.0ghz and tegrak uninstalled.
What I did (error):
-Boot CWM red wipe data, cache, factory reset
-boot download mode, flash T959VKB5-Custom.tar with Odin 1.7
-Phone reboots into stock android recovery (3e)
-selecting reboot phone bring galaxy s splash, then back to recovery
-selecting reinstall packages; it looks for the update.zip but I keep getting verification failed
What I Know
-verification fails because im using default 3e recovery
-i need to use odin to flash a new kernel with the 2e recovery
What I'm confused about
-All kernels that I've found are .zip, odin takes .tar
-I cant use the .zip kernels because I cant install a package
-I cant install a package because verification fails
-verification fails because using 3e recovery
-cant flash kernel with 2e recovery because i dont know how!
So again all comments are appreciated. Thanks for reading.
Mizun0h said:
Hi all. I'm new to android, but not to modding. I've been with xda for a few weeks and have appreciated the quality of the posts and tutorials. Btw-I have searched the forums and google and am still soo lost.
Any help would be appreciated.
Goal:
-To get stock kd1
Previous Config:
-Black Ice KD1, CWM recovery red, voodoo lag fix, ext4 on all, Bali 3.2 no uv, Juwe ram script
-was previously overclocked using tegrak ultimate to 1.2ghz, but about a day before my error it had been put back to 1.0ghz and tegrak uninstalled.
What I did (error):
-Boot CWM red wipe data, cache, factory reset
-boot download mode, flash T959VKB5-Custom.tar with Odin 1.7
-Phone reboots into stock android recovery (3e)
-selecting reboot phone bring galaxy s splash, then back to recovery
-selecting reinstall packages; it looks for the update.zip but I keep getting verification failed
What I Know
-verification fails because im using default 3e recovery
-i need to use odin to flash a new kernel with the 2e recovery
What I'm confused about
-All kernels that I've found are .zip, odin takes .tar
-I cant use the .zip kernels because I cant install a package
-I cant install a package because verification fails
-verification fails because using 3e recovery
-cant flash kernel with 2e recovery because i dont know how!
So again all comments are appreciated. Thanks for reading.
Click to expand...
Click to collapse
your so use to having the recovery file already put into system/bin so you forgot to do it when you flashed kb5
you see after kd1 it was no longer needed to push the recovery file yourself because its been implemented in all the roms since
so look into krlons CWM final and push the recovery file into /system/bin
then try again you wont get the error
dsexton702 said:
your so use to having the recovery file already put into system/bin so you forgot to do it when you flashed kb5
you see after kd1 it was no longer needed to push the recovery file yourself because its been implemented in all the roms since
so look into krlons CWM final and push the recovery file into /system/bin
then try again you wont get the error
Click to expand...
Click to collapse
Thank you. This definately sounds like the answer I'm looking for. But how would i go about pushing the file to the system if I cant boot my phone?
Will droid explorer still do that?
Mizun0h said:
Thank you. This definately sounds like the answer I'm looking for. But how would i go about pushing the file to the system if I cant boot my phone?
Will droid explorer still do that?
Click to expand...
Click to collapse
I think it'd be easier to get a ROM like this one:
http://forum.xda-developers.com/showthread.php?t=1063696
It already comes rooted so you can throw in the custom recovery file, then go back to a completely stock build (I think that's what you want).
After you flash that rom with odin, get both the files in the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1099374
You'll be able to get into CWM from there and that'll give you more flexibility.
You probably won't be able to get into download mode from the bootloop you're getting, so do a battery pull, then put the battery back in, hold down both volume keys, and while those are still pressed, press the power button. You should get a screen with a big yellow triangle with an exclamation mark in the middle, which you probably already know is download mode.
Thanks for the quick response. Worked like a charm until, only through impatience, come across another problem.
I was following the steps from this thread
http://forum.xda-developers.com/showthread.php?t=1141550
-I got cwm, flashed ext4 converter, flashed black ice, and then i wanted to install bali 3.1
-By mistake i downloaded the non uv package to the sd card. So out of impatience pulled the sd card and dropped the uv one on their.
-not to my surprise cwm didnt see any changes. so i went to advance, then reboot recovery
Now my phone boots straight to galaxy s splash and stays there. I cant access cwm or download mode. Any ideas?
Did you have bali 2.1 or higher before flashing the ext4 converter? If you don't it will soft brick, from what I know. Flash odin and restart.
Sent from my SGH-T959V using XDA Premium App
Mizun0h said:
Thanks for the quick response. Worked like a charm until, only through impatience, come across another problem.
I was following the steps from this thread
http://forum.xda-developers.com/showthread.php?t=1141550
-I got cwm, flashed ext4 converter, flashed black ice, and then i wanted to install bali 3.1
-By mistake i downloaded the non uv package to the sd card. So out of impatience pulled the sd card and dropped the uv one on their.
-not to my surprise cwm didnt see any changes. so i went to advance, then reboot recovery
Now my phone boots straight to galaxy s splash and stays there. I cant access cwm or download mode. Any ideas?
Click to expand...
Click to collapse
Check your mounts to make sure they are
Code:
unmount
mount
mount
unmount
You'll need to reflash a rom using odin though, you won't be able to use CWM until you do.
Thank you. worked great.
OK, so I was in the process of trying to flash Infused V2 beta 3, and just downloaded the 3e recovery and put it in system/bin and rebooted and all was good, was trying to install CWM from ROM Manager. ROM Manager said it sucessfully installed CWM 2.5.0.1 or whatever the latest version is. I decided to try to reboot into recovery from within ROM Manager and now I'm stuck at the Samsung logo. What do I do?
dufrenbk said:
OK, so I was in the process of trying to flash Infused V2 beta 3, and just downloaded the 3e recovery and put it in system/bin and rebooted and all was good, was trying to install CWM from ROM Manager. ROM Manager said it sucessfully installed CWM 2.5.0.1 or whatever the latest version is. I decided to try to reboot into recovery from within ROM Manager and now I'm stuck at the Samsung logo. What do I do?
Click to expand...
Click to collapse
hold the three button combo till it reboots and let go when you see samsung. (power and both volumes)
if that doesnt get you into recovery(3e blue recovery once here you reinstall packages twice) then hold three buttons again but let go when the screen goes black. if the phone doesnt boot it is in a semi brick situation . likely a premission problem or a corrupt recovery file.
odin may be needed to flash the phone.
a voodoo kernel like "defuse" may fix it as it will redirect the phone to cwm recovery not 3e (get the .tar file not the .zip file) it will do a voodoo conversion you will hear robot voices and it may take 10min so dont jump to conclusions.
if the kernel doesnt work then flash the unbrick package.
Well I just used odin to get me back. Thanks.
Ok now I have another problem. I just noticed that every time I reboot the phone, Handcent SMS basically reinstalls itself or something. Any setting or theme changes I make don't stick when rebooted. Any ideas? Man I'm angry. All I want is to flash Infused V2 Beta 3!
EDIT: and Tango does the same thing. I'm sure others will do it too, just havent reinstalled everything yet
ttttthhhhhiiisssss ssssssssuuuuuuuuuuxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
FYI, I'm trying a factory reset right now
Factory reset got me back to... well... factory unfortunately
I can't flash anything because when I go to my recovery menu I'm getting rainbows. I'm thinking this is due to the kernel that is flashed with infused v2.0.0. I just downloaded root tools and was going to use the pulldown editor, but when it said not to use on anything other than a Verizon phone, I accidentally hit the ignore button I guess? So I rebooted my phone and nothing was happening, so I pulled the battery and booted into red CWM and reflashed the serendipity rom. I rebooted out of red CWM and phone did not boot, so I went back to red CWM and flashed another rom I had, infused v2.0.0. My phone still did not boot, so I flashed the backup, update.zip and when it finished, I had green CWM, not red anymore. So just to try and get my phone working again, I flashed infused again, and this time it booted, along with the rainbows, as noted in the changelog with infused v2.0.0. So since I knew I could boot now, I rebooted into recovery to flash serendipity again, but the menu is just a rainbow, like on boot. I can navigate the CWM but I can't see anything, and the only reason I know is because I hit the power button, and I rebooted, and the first option in recovery is reboot. I wanna know if there is anyway to replace the kernel so I can see my CWM? or a way to flash serendipity with odin, because the kernel included with that contains no rainbows. Thanks in advance.
pr621 said:
I can't flash anything because when I go to my recovery menu I'm getting rainbows. I'm thinking this is due to the kernel that is flashed with infused v2.0.0. I just downloaded root tools and was going to use the pulldown editor, but when it said not to use on anything other than a Verizon phone, I accidentally hit the ignore button I guess? So I rebooted my phone and nothing was happening, so I pulled the battery and booted into red CWM and reflashed the serendipity rom. I rebooted out of red CWM and phone did not boot, so I went back to red CWM and flashed another rom I had, infused v2.0.0. My phone still did not boot, so I flashed the backup, update.zip and when it finished, I had green CWM, not red anymore. So just to try and get my phone working again, I flashed infused again, and this time it booted, along with the rainbows, as noted in the changelog with infused v2.0.0. So since I knew I could boot now, I rebooted into recovery to flash serendipity again, but the menu is just a rainbow, like on boot. I can navigate the CWM but I can't see anything, and the only reason I know is because I hit the power button, and I rebooted, and the first option in recovery is reboot. I wanna know if there is anyway to replace the kernel so I can see my CWM? or a way to flash serendipity with odin, because the kernel included with that contains no rainbows. Thanks in advance.
Click to expand...
Click to collapse
holy textwall, I can barely read what you typed...
Looks like you flashed an ancient version of Infused (2.0.0 beta - 2.0.0 final fixed the rainbows).
Odin or Heimdall can flash a fixed kernel - http://forum.xda-developers.com/showthread.php?t=1240136 covers how for Heimdall, I'm less familiar with Odin. Watch out, I've heard that Heimdall and Odin can interfere with each other if installed at the same time on Windows.
I've followed the instructions and the videos...I cannot get my Infuse to allow me to install a new ROM. I had a Captivate previously and flashed frequently. Tried to resist rooting & flashing but finally ran out of patience waiting for AT&T.
So I have root. I've copied the recovery file from the SDCard to the /system/bin...made sure the permissions were all copied from the original recovery. I reboot into recovery and re-install packages.
I then downloaded ROMManager and installed. Reboot into Recovery (3e) and re-install packages which then brings me to the green font CWM. If I choose to install zip from SD I don't specifically see any errors on the screen, but I end up getting brought back to 3e reboot...which never goes anywhere.
I haven't been able to find much help on this searching...I can't be the only one having this issue.
Flash community kernel through Odin and you'll have fully working recovery...flash...wait til it starts to boot....pull battery...replace batt ...hold vol up, vol down and power til Samsung logo appears and let go and it will boot into red CWM then your good to flash away
Sent from my SAMSUNG-SGH-I997 using xda premium