So im definatley new to rooting and have a quick question. I rooted using Z4, flashed djo5 modem, super clean rom and non voodoo kernel. When I flashed the stupidfast custom kernel it gave me a wierd looking boot screen. I think it flashed ok but in the about phone section it says kernel version 2.6.29 is it supposed to say stupid fast. Phone seems to work fine but not sure if kernel flashed right. Any feddback is greatly appreciated.
I am unfamiliar with that phone and firmware, but if everything works as it should I would say its ok, sometimes devs personalize installs like that, if you install voodoo lag fix for galaxy s the phone talks to you in sexy female voice during install.
Related
Hi,
Hope i'm posting this in correct place. I have a samsung galaxy s that is about a month old. It behaves differently than all other galaxy s phones when i try to install custom roms on it.
What i did after buying it was flash a speedmod kernel on it so that i could install custom roms. I then installed darky's rom v8.0 from zip. When you install his rom it should by itself install a voodoo kernel... thus replacing the speedmod kernel i put on there. Does it? Nope... the kernel reverts back to the factory kernel that came with the phone. So ok.. i'll just flash the voodoo kernel myself using odin. Works? Well.. about phone page says i now have voodoo kernel, but if i go into recovery what do i see? The default samsung recovery 2e tools when i should see a voodoo red screen with options. I have tried like a dozen times flashing different roms, then flashing back to JPY so i can start over and try different roms. What i find is that the phone simply won't install a kernel correctly when i am flashing a custom rom. Always back to
android system recovery <2e>
Samsung Recovery Utils
- for BML-
I'd like to know if anyone else heard of this happening before, because it kind of sucks. The phone seems to have like a mind of its own and i've asked in various rom irc channels and every1 says wow so weird but can offer no explanation. Oh.. the product code of phone is... GT-I9000RWYXEE. Hope someone knows whats going on here. Thanks.
I Know this should be in the Developer section, but I don't have enough posts. (Since you have to have at least 10 to do so...)
BUT, I installed a kernel from Blades which is the 1.6ghz with the latest version of CWM. The problem is that whenever I try to boot up the device it just stays on the first startup screen, and it also makes a weird popping noise from the speakers about every 10 seconds. I did wipe Dalvik Cache and I also made a back up before installing the new kernel. I've tried restoring but it does the same thing every time. Before installing the kernel I was running PRIMEORDIAL! v3.1...
Any help would be greatly appreciated....
Thanks
cdp
Hi Mate, You are not the only one. Unfortuantely 3.0.1 kernels don't work too well with 3.1 roms as you have discovered.
Not to worry though as this is an easy fix.
Simply flash the 3.1 stock kernel and you're up and running again. You can get it from here... http://forum.xda-developers.com/showpost.php?p=14283676&postcount=94
Wow, I didn't even realize that kernel was only for 3.0.1 lol. THANK YOU! Flashed it and it started right up! C:
You may now have wifi problems, since the kernel update will have installed a different module to the one you need, if this is the case just reflash whatever rom you are using.
Okay cool, I'm on wifi now and it seems to be working fine. So thanks again! :]
It seems alot of people are getting confused with rooting of the phones, and what they need to do, and it mostly seems like people from other phones, and well the obviously new person. I just want to help with his, as some of the threads are getting and I can see it being tough to follow a 40 page thread.
It seems to me alot of the confusion seems to come from the fact of the lack of locked bootloader, along with using ODIN to flash. I'm quessing everyone from HTC phones is used to a multi step process in regards to flashing root, as you have to load a hacked bootloader, turn soff etc.
If you have a stock ed2 charge. All you need to do is run jt's root/voodoo/cwm kernel found here http://forum.xda-developers.com/showthread.php?t=1092114
ffd173 in post 108 has some nice instructions on it. http://forum.xda-developers.com/showpost.php?p=14080378&postcount=108
The stock rooted roms you are seeing are (root stock ed1, root stock ed2) you can consider a rooted basic backup. Do not use CWM either the one from jt's kernel, or rom manager for backup and restore until a recongized dev says its okay. Use titanium backup for your backups and restores. It has been recommended a few times to not even touch ROM Manager yet, based on the way it is written to work vs what is here and how it is written
***one thing to note is that if you install a kernel using the voodoo lag fix, you must disable it prior to flashing back to any sort of stock based kernal/rom or any non kernel with the lag fix.
I am semi new with this as well coming from HTC phones, and only having this for this being my 3rd day. If I missed something in here or made a mistake please let me know and I can adjust and maintain this....havent had much sleep for a while and its getting to me
***one thing to note is that the kernel has now the voodoo lag fix such as these stock roms, you have to disable to voodoo lag fix.
Not sure what youre saying here. Are you saying that you have to disable the voodoo lag fix to install root stock ed1 or ed2?
Updated it. My apologizes.
Okay ... Don't laugh at me !! Have had the Charge since release date. This whole time I have been running stock rooted EE4 with CWM Voodoo Lagfix. I had to have a replacement phone sent to me as my CDMA radio died. Phone still worked on LTE radio. CDMA would be intermittent at best.
On to my question. I am planning to give GB a try and I am reading in threads about the toolbox and to access it via Term? I am assuming term is terminal function. This part is entirely new to me. Could someone point me to some term primers so I can research this?
Also, I have downloaded and extracted my Bloated_EG2__Gingerbread_ ODIN. Then I have
GummyCharged_GBE_2.0
GummyChargedGBE2.1
CWM_Recovery4008
I am assuming the EG2 includes CWM. If not, which will be easy enough to find out when I go to enter recovery, I will install the CWM I have downloaded. From what it appears to me, GBE_2.1 is an update to GBE_2.0 .... Thus I assume I need to install 2.0 followed by 2.1
Does this include voodoo lagfix? Or is that not needed when I up the phone to GB 2.3?
Just trying to sort this out and be informed before I start flashing this thing. The phone is stock out of the box EE4 as of right now.
Any help will be greatly appreciated.
Thanx In Advance,
Steve
Chopstix9 said:
Okay ... Don't laugh at me !! Have had the Charge since release date. This whole time I have been running stock rooted EE4 with CWM Voodoo Lagfix. I had to have a replacement phone sent to me as my CDMA radio died. Phone still worked on LTE radio. CDMA would be intermittent at best.
On to my question. I am planning to give GB a try and I am reading in threads about the toolbox and to access it via Term? I am assuming term is terminal function. This part is entirely new to me. Could someone point me to some term primers so I can research this?
Also, I have downloaded and extracted my Bloated_EG2__Gingerbread_ ODIN. Then I have
GummyCharged_GBE_2.0
GummyChargedGBE2.1
CWM_Recovery4008
I am assuming the EG2 includes CWM. If not, which will be easy enough to find out when I go to enter recovery, I will install the CWM I have downloaded. From what it appears to me, GBE_2.1 is an update to GBE_2.0 .... Thus I assume I need to install 2.0 followed by 2.1
Does this include voodoo lagfix? Or is that not needed when I up the phone to GB 2.3?
Just trying to sort this out and be informed before I start flashing this thing. The phone is stock out of the box EE4 as of right now.
Any help will be greatly appreciated.
Thanx In Advance,
Steve
Click to expand...
Click to collapse
EG2 is really old, you may want to go with a more recent GB leak like EP1Q/EP1W/EP3H... second no rom packages include CWM but are for the most part all rooted, CWM you will have to install with Odin after the rom then flash Gummy 2.0 and the 2.1 patch with a bootup between each rom flash to make sure it worked properly
edit: probably should've answered more questions Gummy 2.0 has a kernel with voodoo lagfix so it will enable after flashing the rom on first bootup, also the command terminal is fairly straightforward to use, I think the Gummy rom threads have a how-to in the OP on basic terminal commands... also as for your radio not working, it was probably a 4G sim issue as the CDMA and LTE radios are both controlled by the sim so if one doesn't work the other won't either, there may just not be as strong a CDMA signal so it seemed like it wasn't working
Great info thanx .... now when I go to update to 2.0, from the reading and even watching the video, I am going to delete all caches prior to flashing the 2.0 ... with the 2.1 just being a patch, can I just install it after verifying 2.0 works? Or should I delete the big 3 again before that one?
Chopstix9 said:
Great info thanx .... now when I go to update to 2.0, from the reading and even watching the video, I am going to delete all caches prior to flashing the 2.0 ... with the 2.1 just being a patch, can I just install it after verifying 2.0 works? Or should I delete the big 3 again before that one?
Click to expand...
Click to collapse
just cache and dalvik I think (might not even need that but I'd probably do it to be safe), don't delete data or it will wipe Gummy off and you'll have to reflash
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.