Related
so I have a vibrant and was running 1.6 bionix mod on it, and i figured i would download 1.7 and flash it over. But before I did I wanted to flash back to stock via odin to download the OTA but when I did that I get a black screen after the galaxy s logo..I have looked and searched these forums and
I have tried this
http://forum.xda-developers.com/showthread.php?t=741027&highlight=brick
did not work
and I am currently trying to use eugenes froyo flash method, however I need to use adb reboot and adb cannot detect my phone because I assume it's not rooted anymore since I reverted back to stock..
any ideas?? on how to root my phone while it's in this soft brick or any ideas what to flash in odin to fix this ?? If this thread was unclear I will clarify any questions.
PS. ever since i used odin to flash Euguenes froyo rom whenever I start up the phone it goes straight to android system recovery and I do not have the option to do anything else. HELPPP
ok...reading up a bit more and it looks like I didn't disable voodoo lag fix before i flashed over the stock rom ?
now i am trying to run the fixes that this thread lists,
http://forum.xda-developers.com/showthread.php?t=782027
but i can not do any adb commands because my phone isn't rooted now, any way to root through odin?
Wykedx said:
ok...reading up a bit more and it looks like I didn't disable voodoo lag fix before i flashed over the stock rom ?
now i am trying to run the fixes that this thread lists,
http://forum.xda-developers.com/showthread.php?t=782027
but i can not do any adb commands because my phone isn't rooted now, any way to root through odin?
Click to expand...
Click to collapse
your phone doesn't have to be rooted to use adb ...
When your phone throws you into recovery with that media error, unplug your phone for 5 seconds, and plug it back in. Eugene put that in the instructions, and i didn't read that part either lol. If adb still doesn't work, you need to dl the right drivers again
dav3wash said:
your phone doesn't have to be rooted to use adb ...
When your phone throws you into recovery with that media error, unplug your phone for 5 seconds, and plug it back in. Eugene put that in the instructions, and i didn't read that part either lol. If adb still doesn't work, you need to dl the right drivers again
Click to expand...
Click to collapse
when you unplug the phone and re plug in what should the phone do?
is it just so the computer recognizes the phone or does it boot something up?
Wykedx said:
when you unplug the phone and re plug in what should the phone do?
is it just so the computer recognizes the phone or does it boot something up?
Click to expand...
Click to collapse
nothing will happen on the phone, but your computer and adb will recognize the phone
omg i was just about to lose hope and go into tmobile and make a bs excuse about how the ota update f'ed up my phone LOL,
thank you so much!! now i can flash the stock rom correct? or can voodoo still mess my phone up?
Wykedx said:
omg i was just about to lose hope and go into tmobile and make a bs excuse about how the ota update f'ed up my phone LOL,
thank you so much!! now i can flash the stock rom correct? or can voodoo still mess my phone up?
Click to expand...
Click to collapse
Haha no problem. As for Voodoo ... i never ventured there. I usually stick with JAC's or King Kilikkk's, but here's the uninstall/verification for Voodoo. Try it b4 you flash anything else just to be safe.
How-to Disable the Voodoo Lagfix:
1. Once again, you MUST disable the Voodoo lag fix in order to flash any other rom, kernel, or perform a nandroid backup. If you don't...well....lets just say I warned you.
2. Its simple. Create a folder on the root of your sdcard called 'Voodoo'.
3. Now, open notepad or something similar and save the blank file. Name it 'disable-lagfix'. This file cannot have any file extension, so remove it if it does.
4. Place your blank file into the 'Voodoo' folder you made on your sdcard.
5. In order to disable, simply power down your phone and power it back up.
6. FINISHED! You can now flash anything you'd like!
How-to Confirm Voodoo Lagfix is Disabled:
1. In adb shell or terminal type 'mount'
2. If it is disabled is should read '/dev/block/mmcblk0p2'.
3. If it is not disabled, it will read '/dev/block/mmcblk0p4'.
done and done, thanks again!!
I, an ignorant vibrant user eager to break into the world of ROMS, finally and successfully rooted my phone with the one click root.
One Click Lagfix from the marketplace immediately thereafter. Phone was blazing fast.
I decided to push my stupid limits. I tried to download and install Eugene's Vibrant Hybrid final ROM that would give me glorious, stock android. I followed the instructions I found for "installing a ROM":
Copy the zip to the root.
Boot into recovery.
Go into clockwork recovery.
factory reset.
install zip from sd card.
after that's done, reboot.
I got a little chimy, should-be-startup noise, (not the standard vibrant start-up noise, but what I expect would be the new ROM start-up noise I downloaded) and then nothing. Just the Vibrant screen.
I can boot into recovery mode, but I don't know what to do next. I tried to find the backup I made on Clockwork, but it was NOT THERE. I am now panicking and trying not to do anything stupid to my phone.
read on Eugene's site that it could be that I don't have the correct kernel flashed to support the ROM...? At this point, I kind of just want my phone back while having to lose the least amount of data. Please Help.
and before I tried installing the ROM, I used the one-click lag fix from the market on my already rooted phone.
Thanks!
james
Did you disable the lag fix before flashing?
Sent from my SGH-T959 using XDA App
no, didn't realize that it would be an issue until after flashing the ROM. I think I'm stuck in a boot loop... and I have access to a mac only at the moment. Tomorrow I'll have access to a PC if ODIN could help at all...
Search for "froyo that doesnt brick your phone" flash if with odin and after that flash back to stock.
Sent from my SGH-T959 using XDA App
Will this restore my data and settings...?? What will I lose?
In a weird. Everything. Unless you made an external backup. Eugene's will wipe the phone.
Sorry bud
Gl.
Sent from my SGH-T959 using XDA App
jamespwolpert said:
I, an ignorant vibrant user eager to break into the world of ROMS, finally and successfully rooted my phone with the one click root.
One Click Lagfix from the marketplace immediately thereafter. Phone was blazing fast.
I decided to push my stupid limits. I tried to download and install Eugene's Vibrant Hybrid final ROM that would give me glorious, stock android. I followed the instructions I found for "installing a ROM":
Copy the zip to the root.
Boot into recovery.
Go into clockwork recovery.
factory reset.
install zip from sd card.
after that's done, reboot.
I got a little chimy, should-be-startup noise, (not the standard vibrant start-up noise, but what I expect would be the new ROM start-up noise I downloaded) and then nothing. Just the Vibrant screen.
I can boot into recovery mode, but I don't know what to do next. I tried to find the backup I made on Clockwork, but it was NOT THERE. I am now panicking and trying not to do anything stupid to my phone.
read on Eugene's site that it could be that I don't have the correct kernel flashed to support the ROM...? At this point, I kind of just want my phone back while having to lose the least amount of data. Please Help.
and before I tried installing the ROM, I used the one-click lag fix from the market on my already rooted phone.
Thanks!
james
Click to expand...
Click to collapse
its just a simple user error. Honestly imo opinion, if you are using the lagfix option found on the market, flashing to other roms reformats /data and /system and such undoing it. So thats not where your issue came from the flashing. Before the flash, if you were on stock jdf, the flashing the hybrid final rom didnt update your baseband/modem.bin and i am pretty sure that would put you in your situation. Possible situation number 2. You had the ota update on your phone already. Meaning you were running ji6 then the rom update.zip may have been corrupted or incomplete.
to fix either one of these situations is simple. As long as the answer to my next question is a hell no. Did you flash jacs xmod voodoo kernel after you flash the hybrid rom?? The faster you reply to this the faster i can get to to a solution. You will also need a computer that has adb installed and properly recognizing your phone.
IF YOU DID FLASH THE VOODOO LAGFIX YOU WILL NEED ACCESS TO A COMPUTER WITH ODIN AND ANDROID SDK!! WETHER IT BE A MAC WITH PARRELLS OR A VM OR LINIX OR WINDOWS.
a4 moda said:
In a weird. Everything. Unless you made an external backup. Eugene's will wipe the phone.
Sorry bud
Gl.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That is not true. Anything on his internal memory will be perfectly intact. And if he can still get into cwm recovery, he adb push a few files to the root of his sd card and boot right up depending the cause
jumaaneface said:
its just a simple user error. Honestly imo opinion, if you are using the lagfix option found on the market, flashing to other roms reformats /data and /system and such undoing it. So thats not where your issue came from the flashing. Before the flash, if you were on stock jdf, the flashing the hybrid final rom didnt update your baseband/modem.bin and i am pretty sure that would put you in your situation. Possible situation number 2. You had the ota update on your phone already. Meaning you were running ji6 then the rom update.zip may have been corrupted or incomplete.
to fix either one of these situations is simple. As long as the answer to my next question is a hell no. Did you flash jacs xmod voodoo kernel after you flash the hybrid rom?? The faster you reply to this the faster i can get to to a solution. You will also need a computer that has adb installed and properly recognizing your phone.
IF YOU DID FLASH THE VOODOO LAGFIX YOU WILL NEED ACCESS TO A COMPUTER WITH ODIN AND ANDROID SDK!! WETHER IT BE A MAC WITH PARRELLS OR A VM OR LINIX OR WINDOWS.
Click to expand...
Click to collapse
I didn't flash **** after that. Just the Hybrid mod, then I was stuck. The steps I mentioned in my process were the only things that ever ever happened.
also, yes, I (was) running JI6 as well. Until this fiasco.
Eugene's thread for the hybrid mod also has files posted for, quote, "reboots and freezes" with the file name JFDkernanmodemji2.zip. All things that have been mentioned positively at one point or another in this thread. Since I am pretty sure I don't have the appropriate kernel to run the ROM, do I simply push the JFDkernanmodemji2.zip file to my root, flash it, then flash the ROM again and life will be good?
jamespwolpert said:
Eugene's thread for the hybrid mod also has files posted for, quote, "reboots and freezes" with the file name JFDkernanmodemji2.zip. All things that have been mentioned positively at one point or another in this thread. Since I am pretty sure I don't have the appropriate kernel to run the ROM, do I simply push the JFDkernanmodemji2.zip file to my root, flash it, then flash the ROM again and life will be good?
Click to expand...
Click to collapse
Indeed. If it doesn't work. U had a messed up download. At that point redownload and push to sd root
jumaaneface said:
Indeed. If it doesn't work. U had a messed up download. At that point redownload and push to sd root
Click to expand...
Click to collapse
how do I push files to my vibrant? Where do I start?
jamespwolpert said:
how do I push files to my vibrant? Where do I start?
Click to expand...
Click to collapse
Do you have android sdk on your pc?
jumaaneface said:
Do you have android sdk on your pc?
Click to expand...
Click to collapse
I think. When I open it, it the app is called Java and the titlebar says Android SDK and AVD Manager
jamespwolpert said:
how do I push files to my vibrant? Where do I start?
Click to expand...
Click to collapse
jamespwolpert said:
I think. When I open it, it the app is called Java and the titlebar says Android SDK and AVD Manager
Click to expand...
Click to collapse
boot your phone into clockwork recovery and plug in to computer. Then open a command prompt window. you can type in cmd into search bar in windows to open it up. Then type adb devices into the little black window. tell me what happens when you do this. Do you have gtalk or aim? This will go by faster If you have one
jumaaneface said:
boot your phone into clockwork recovery and plug in to computer. Then open a command prompt window. you can type in cmd into search bar in windows to open it up. Then type adb devices into the little black window. tell me what happens when you do this. Do you have gtalk or aim? This will go by faster If you have one
Click to expand...
Click to collapse
yeah, I've got gtalk.
gmail is [email protected]
Personal assist, wow that's awesome.
So what came if this? What's the outcome?
I'm curious, please update.
Sent from my SGH-T959 using XDA App
Push pppuuuuush..baby deliveried yet?? An update on steps by steps?
Hi
I looked around and saw a few ppl having trouble while rooting vibrant.
I've put update.zip on /sdcard, and when i reboot my phone in recovery mode it says something about my package not being signed.
So i googled and did this:
java -classpath "/home/ohai/Downloads/android-sdk-linux_86/tools/sign/testsign.jar" testsign update.zip file-signed.zip
(don't worry, i'm not that stupid, i DO have the sdk and the testsign installed here)
then renamed file-signed.zip to update.zip and replaced it on /sdcard, but still got the same message.
Does anyone have a link to a actually working update.zip to vibrant's froyo?
i'm using froyo.UVJL4, downloaded from samfirmware.com.
Thx in advance
?
Sent from my SGH-T959 using XDA App
Everyone's update.zip is usually different is what i'd think.
try getting titanium backup, click menu and click menu, and then CREATE update.zip
that might help you out.
Go to dec section and look for the jl4 rom from geodude(cant remember exact name...) His rom, odex or deodex both come prerooted with the 3e recovery fix as well. Flash that. KTB.
Sent from my SGH-T959 using XDA App
If you are comfortable using the voodoo lagfix you can flash the new voodoo 5 kernels. They come with the SU binary and clockworkmod recovery built in. Then download busybox and superuser from the market. You'd have to flash via ODIN though.
Thx for the tips, but i was not thinking about using modified roms... all i want is to root my default rom from samsung, is it possible?
You need the correct key to sign the zip file. My understanding is this key was not released by Samsung so you will not be able to sign your update.zip files to work with the 3e recovery.
The 2e recovery accepted a "test key" which is why we're able to use update.zip to root and use CWM.
The RATC method still works for rooting in the 2.2 Firmware. You can use SuperOneClick to root, and then replace the stock 3e recovery with the one from here. This is a modified 3e recovery which removes the signature checking.
How about trying the ALT METHOD in the Noob Guide (my signature)... then flash a stock rom with root?
http://forum.xda-developers.com/showthread.php?t=857974
personally, you are hurting yourself by not running a rom like Nero v3 or Eugenes Ginger Clones.
Rooting T-Mobile Vibrant Froyo 2.2 JL5
I have the T-mobile Vibrant US Phone. I upgraded to JL5 and have rooted my phone with a program from here:
http://forum.xda-developers.com/showthread.php?t=803682
Get the latest version and you might have to run the program 2 or 3 times for it to finish. Note on my phone these were the steps I took.
1. Put phone in USB Debugging Mode.
2. Plug usb cable to computer.
3. Run the rooting program above with windows administrator rights.
4. It will run then probably hang half way through and indicate WAITING FOR
DEVICE.
5. Shut windows program down.
6. Reboot phone (Turn Off then On).
7. Reconnect to usb.
8. Restart the Rooting Program and Root.
9. It should finish and ask if you want to test SU say yes.
10. That's It you should be good to go.
Hope this helps.
s15274n said:
How about trying the ALT METHOD in the Noob Guide (my signature)... then flash a stock rom with root?
http://forum.xda-developers.com/showthread.php?t=857974
personally, you are hurting yourself by not running a rom like Nero v3 or Eugenes Ginger Clones.
Click to expand...
Click to collapse
What's so good in those roms?
NihtSpi said:
I have the T-mobile Vibrant US Phone. I upgraded to JL5 and have rooted my phone with a program from here:
http://forum.xda-developers.com/showthread.php?t=803682
Get the latest version and you might have to run the program 2 or 3 times for it to finish. Note on my phone these were the steps I took.
1. Put phone in USB Debugging Mode.
2. Plug usb cable to computer.
3. Run the rooting program above with windows administrator rights.
4. It will run then probably hang half way through and indicate WAITING FOR
DEVICE.
5. Shut windows program down.
6. Reboot phone (Turn Off then On).
7. Reconnect to usb.
8. Restart the Rooting Program and Root.
9. It should finish and ask if you want to test SU say yes.
10. That's It you should be good to go.
Hope this helps.
Click to expand...
Click to collapse
JL5?
where did you get it?
atcasanova said:
What's so good in those roms?
Click to expand...
Click to collapse
You still can't get rooted & you want FroYo?
I attached cwm update.zip so just use that to get into CWM Recovery (Reinstall Packages, You may need to do it twice) and then just flash the following ROM
http://forum.xda-developers.com/showthread.php?t=881692
Master™ said:
You still can't get rooted & you want FroYo?
I attached cwm update.zip so just use that to get into CWM Recovery (Reinstall Packages, You may need to do it twice) and then just flash the following ROM
http://forum.xda-developers.com/showthread.php?t=881692
Click to expand...
Click to collapse
Sorry for being this dumb, but i don't have a clue of what is CWM
me too,
im desperately looking to root my vibrant from Bell canada. i just updated to JL2 using the kies pc software. i just got this phone for xmas so im quite new to it.
im hoping to find an app or website that can do most of the steps for me. or a youtube video with detailed step by step.
ive tried using the guide that s15274n wrote (btw, thanks for the awesome writeup) but i have the same problem of the update.zip file not passign the signature verifaction.
i would like to stay with a stock ROM for at least another couple weeks because of the super high chance of this phone bricking itself
my phone has a build date of 11.10
any thoughts?
thank you VERY much for any help
EDIT:
I have managed to root my phone! hurray!
heres how i did it:
i used the superoneclick method thanks to this link http://forum.xda-developers.com/showthread.php?t=803682
i used this guide to help me through the steps http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
thanks to everyone to put in work to make this possible.
THANK YOU!
chucked said:
me too,
im desperately looking to root my vibrant from Bell canada. i just updated to JL2 using the kies pc software. i just got this phone for xmas so im quite new to it.
im hoping to find an app or website that can do most of the steps for me. or a youtube video with detailed step by step.
ive tried using the guide that s15274n wrote (btw, thanks for the awesome writeup) but i have the same problem of the update.zip file not passign the signature verifaction.
i would like to stay with a stock ROM for at least another couple weeks because of the super high chance of this phone bricking itself
my phone has a build date of 11.10
any thoughts?
thank you VERY much for any help
EDIT:
I have managed to root my phone! hurray!
heres how i did it:
i used the superoneclick method thanks to this link http://forum.xda-developers.com/showthread.php?t=803682
i used this guide to help me through the steps http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
thanks to everyone to put in work to make this possible.
Click to expand...
Click to collapse
So many people figure out what was wrong and they are done. Thank you for posting your finding, I have been trying to Root my Bell Vibrant for a while.
Use SuperOneClickRoot - http://forum.xda-developers.com/showthread.php?t=803682
Works all the time for Vibrant!
Starting off i am a total noob when it comes to rooting…. so i followed a guide to root a galaxy s 2 but the i9100 model….so i rooted it and then i realized that i did the wrong model since the touch buttons werent working and all…so i looked for a i777 model and i followed that tut and rooted with the Clockworkmod and after i was done rooting evrything is fine….but the splash screen is still i9100 and yellow triangle and now i am also reading that u have to flash the roms back http://forum.xda-developers.com/showthread.php?t=1294574 like mentioned in there….....i dont know what to do now i just want my device to be a normally rooted device with everything working like before(EX. Splash Screen, Possibly Wrong ROMs?)….Please consider my noobyness and point me twords a step-by-step guide because i have already tried researching alot and i dont understand this stuff…. thank you so much for helping me.
dhaval33 said:
Starting off i am a total noob when it comes to rooting…. so i followed a guide to root a galaxy s 2 but the i9100 model….so i rooted it and then i realized that i did the wrong model since the touch buttons werent working and all…so i looked for a i777 model and i followed that tut and rooted with the Clockworkmod and after i was done rooting evrything is fine….but the splash screen is still i9100 and yellow triangle and now i am also reading that u have to flash the roms back http://forum.xda-developers.com/showthread.php?t=1294574 like mentioned in there….....i dont know what to do now i just want my device to be a normally rooted device with everything working like before(EX. Splash Screen, Possibly Wrong ROMs?)….Please consider my noobyness and point me twords a step-by-step guide because i have already tried researching alot and i dont understand this stuff…. thank you so much for helping me.
Click to expand...
Click to collapse
I did the Superoneclick as well and when I had the yellow triangle, you need a usb jig to get rid of it, but when I had the symbol my phone said SGS2 i9100 above the yellow triangle. The Yellow Triangle is just a counter on the phone from flashing a non stock kernel, the jig resets and it will say Samsung Galaxy S2 i777 again once it counter is reset. Just make sure when you buy one that it states for at least an sgs 2 i9100 *the one I bought from ebay said* and it will work.
HTH,
Charlie
Well thanks ... but I am a little worried about my Tom's and kernels..... I have no idea what they are but in the thread above he followed some steps to get his roms and kernels straightened out if I got of right.... but I have no idea what he is talking abt so how do I know if my rom and kernel are how they are supposed to be? And how do I fix them....? I feel like going back to factory firmware ( compleetely stock and then rooting again the right way...) please help me.....
Sent from my SAMSUNG-SGH-I777 using XDA App
Roms*
Sent from my SAMSUNG-SGH-I777 using XDA App
It's possible to get rid of the !/I9100 screen without a jig... Workarounds are linked from the first post of the FAQ.
Even if you have a kernel designed for our device, it will put up the I9100 screen if the last kernel flashed with Odin/Heimdall was something other than stock.
well i got that .... please verify what i am going to do before i sctually begin and mess up
1. Download The kernel + rooted system package from http://forum.xda-developers.com/showthread.php?t=1286432 (Does this also install busybox)
2. use Odin to flash it from download mode.
3.now this is the part i dont get in ur post here http://forum.xda-developers.com/showpost.php?p=18238883&postcount=106
U said:
Then flash this kernel using the method in http://forum.xda-developers.com/show...0&postcount=72
You may need to add "su" between "adb shell" and "dd" when on a stock kernel with rooted system.
Then always flash using CWM or the method above from then on.
Since i am a newbie, can u briefly tell me the steps i would do this... please? I really appreciate ur help.
Samsung Galaxy S II (SGH-I777)
Rooted stock + my kernel
Samsung Infuse 4G (SGH-I897)
CyanogenMod 7.1 (Built from source)
Galaxy Tab 10.1
Task650 KME v7.1 + Custom kernel based on Pershoot's OC kernel
Last device - AT&T Tilt2 (RHOD300) running XDAndroid FRX06
Click to expand...
Click to collapse
Also here in ur signature it says rooted stock+ my kernel... can u tell me what that means and the difference is between these methods:
--Method 1--Flash flashing codeworkx CWM then Super One Click(Method by jivy26)
http://forum.xda-developers.com/show....php?t=1285894
--Method 2--Flash through Odin(Method by Entropy512) *Flashes stock ROM with root*
http://forum.xda-developers.com/show....php?t=1286432
--Method 3--Flash codeworkx CWM then flashing through CWM(Method by Paulyhoffman)
http://forum.xda-developers.com/show...06&postcount=2
dhaval33 said:
….....i dont know what to do now i just want my device to be a normally rooted device with everything working like before(EX. Splash Screen, Possibly Wrong ROMs?)….
Click to expand...
Click to collapse
dhaval33 said:
well i got that .... please verify what i am going to do before i sctually begin and mess up
1. Download The kernel + rooted system package from http://forum.xda-developers.com/showthread.php?t=1286432 (Does this also install busybox)
2. use Odin to flash it from download mode.
3.now this is the part i dont get in ur post here http://forum.xda-developers.com/showpost.php?p=18238883&postcount=106
U said:
Then flash this kernel using the method in http://forum.xda-developers.com/show...0&postcount=72
You may need to add "su" between "adb shell" and "dd" when on a stock kernel with rooted system.
Then always flash using CWM or the method above from then on.
Since i am a newbie, can u briefly tell me the steps i would do this... please? I really appreciate ur help.
Click to expand...
Click to collapse
After you complete items 1 & 2 above, you will have returned the phone to stock, just like it was after it came out of the box, except it will also be rooted. If that is all you wanted to do, you can stop there. At this point, the yellow triangle will be gone, and the i9100 boot screen will be gone.
If you want to modify the phone further, you will need to add a kernel with clockwork mod recovery. However, if you flash a non-stock kernel with odin, the yellow triangle and i9100 boot screen will return. (I guess that's essentially what you did in the first place.) The method in item 3 above describes how to add a kernel without flashing in odin. You can actually do this one of two ways. 1) Using your pc, install the Android SDK, which will install adb.exe on you pc. (adb = android debug bridge). Then you can use adb from your pc to add the kernel to you phone over a usb connection. 2) From you phone, using Android Terminal Emulator. You can transfer the kernel image to your phone with usb, then use the terminal to add the kernel to your phone.
The advantage of adding a custom kernel is to make the phone run better, and to gain clockwork mod recovery. To educate yourself, you should read through Entropy512's Daily Driver kernel thread.
If you want to customize your phone further with a custom rom, you can flash anything from clockwork mod recovery without causing the yellow triangle or incrementing the flash counter.
Hope this makes things a little clearer. If you want to use adb or a terminal, you should be able to find lots of instructions in this forum, as well as elsewhere.
creepyncrawly said:
After you complete items 1 & 2 above, you will have returned the phone to stock, just like it was after it came out of the box, except it will also be rooted. If that is all you wanted to do, you can stop there. At this point, the yellow triangle will be gone, and the i9100 boot screen will be gone.
If you want to modify the phone further, you will need to add a kernel with clockwork mod recovery. However, if you flash a non-stock kernel with odin, the yellow triangle and i9100 boot screen will return. (I guess that's essentially what you did in the first place.) The method in item 3 above describes how to add a kernel without flashing in odin. You can actually do this one of two ways. 1) Using your pc, install the Android SDK, which will install adb.exe on you pc. (adb = android debug bridge). Then you can use adb from your pc to add the kernel to you phone over a usb connection. 2) From you phone, using Android Terminal Emulator. You can transfer the kernel image to your phone with usb, then use the terminal to add the kernel to your phone.
The advantage of adding a custom kernel is to make the phone run better, and to gain clockwork mod recovery. To educate yourself, you should read through Entropy512's Daily Driver kernel thread.
If you want to customize your phone further with a custom rom, you can flash anything from clockwork mod recovery without causing the yellow triangle or incrementing the flash counter.
Hope this makes things a little clearer. If you want to use adb or a terminal, you should be able to find lots of instructions in this forum, as well as elsewhere.
Click to expand...
Click to collapse
Wow thank you soo much thats exactly what i was looking for....that makes things a lot clear u have no idea...lol. What if i want to add themes and new boot screens in my phone would i still need to put clockworkmod ? what is the difference between the clockworkmod kernel and the entropy kernel? and finally wouldn't i just be able to flash the clockworkmod recovery from ROM manager? i also read on the faq not to use ROM Manager but that is how i boot into recovery so idk what to do. And would i be able to do this and still retain my apps, settings, my data and my unlock that i currently have?
dhaval33 said:
Wow thank you soo much thats exactly what i was looking for....that makes things a lot clear u have no idea...lol. What if i want to add themes and new boot screens in my phone would i still need to put clockworkmod ? what is the difference between the clockworkmod kernel and the entropy kernel? and finally wouldn't i just be able to flash the clockworkmod recovery from ROM manager? i also read on the faq not to use ROM Manager but that is how i boot into recovery so idk what to do. And would i be able to do this and still retain my apps, settings, my data and my unlock that i currently have?
Click to expand...
Click to collapse
Do NOT use rom manager on this phone. Clockwork Mod Recovery is built into the kernel. It is built into Entropy's Daily Driver kernels, and probably every custom kernel.
To enter clockwork mod recovery when you have a cwm kernel installed, just boot into recovery with the three button method.
Themes are usually added with cwm. Custom boot screen is done with a bootanimation.zip that is copied into the boot directory. Entropy's kernels also have boot animation support.
thanks i am going to do step 1 , 2 and then put entropy's kernel via adb.... but i didnt find any instructions on how to use adb to flash a kernel...
Download the kernel package and extract the zImage from it. After you install the SDK, put the zImage in the same directory as adb. Then run the commands in Entropy's post.
I suggest you read up on ADB first, so you have an understanding of the complete process.
Sent from my SAMSUNG-SGH-I777 using XDA App
thank you i got it now.... but i am still debating whether to use clockworkmod kernel or entropy daily driver kernel.... which one should i put on and what are the benefits in simple terms please... thanks
dhaval33 said:
thank you i got it now.... but i am still debating whether to use clockworkmod kernel or entropy daily driver kernel.... which one should i put on and what are the benefits in simple terms please... thanks
Click to expand...
Click to collapse
Entropy kernel includes clockworkmod.
Sent from my SAMSUNG-SGH-I777
Pirateghost said:
Entropy kernel includes clockworkmod.
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
codeworkx's goal with his CWM kernel was basically a "reference" kernel, as close to stock as possible but with CWM as far as I can tell.
Mine includes his CWM, but includes other features, look at my thread for details.
BTW, for some people, Droid Explorer happens to be an easy way to get adb working on Windows. I can't really provide any help beyond this as I'm a Linux user.
Entropy512 said:
codeworkx's goal with his CWM kernel was basically a "reference" kernel, as close to stock as possible but with CWM as far as I can tell.
Mine includes his CWM, but includes other features, look at my thread for details.
BTW, for some people, Droid Explorer happens to be an easy way to get adb working on Windows. I can't really provide any help beyond this as I'm a Linux user.
Click to expand...
Click to collapse
ok i got adb working by following adb for dummies guide but when i entered
adb push zImage /sdcard/zImage
it worked
but when i tried
adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
it gave me permission denied
I searched for this but i found differenct phones not galaxy s 2 i777...Please help
anyone have a solution for permission denied.... i did go into terminal emulator and put in:
su
dd if=/sdcard/zImage of=/dev/block.mmcblk0p5
Recorded in
Recorded out
there was something else too but is that all i had to do? how do i know i put in that kernel?
What does settings, about phone, Kendal version say?
Sent from my SAMSUNG-SGH-I777 using XDA App
dhaval33 said:
anyone have a solution for permission denied.... i did go into terminal emulator and put in:
su
dd if=/sdcard/zImage of=/dev/block.mmcblk0p5
Recorded in
Recorded out
there was something else too but is that all i had to do? how do i know i put in that kernel?
Click to expand...
Click to collapse
Reboot and run CPU Spy. If the [email protected] for the build machine was [email protected], it's mine.
Access denied means you need root access. In adb shell you enter su and the prompt will change from $ to #. Then enter the dd command.
If you used terminal emulator you have to have the zImage on the root of the sd card or it won't work.
Sent from my SAMSUNG-SGH-I777 using XDA App
Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man