Database Users

I just Flashed Froyo Rom from Stock DI18 and never looking back

I just flashed Bonsai rom and I finally have froyo on my epic!
Although I had problem following instructions, I finally got it working.
I'd like share my experience of flashing froyo rom on stock phone in hope to help other people who haven't flashed a rom like me before. Please go easy on me, this was my first time flashing custom rom.
First, I copied Bonsai rom file to sdcard.
Then, I flashed stock DK28 rom using the Odin program. This was very easy to follow and was done very fast. Within minutes, I had stock froyo on my phone.
Next, I downloaded Clockwork MOD v3.0.0.x and follow the direction of installing samsung driver and activated the debugging mode on the phone.
After the computer recognized the phone (it took a while and I had to pull the USB from the phone and back again), I ran the run.bat and clockwork mod was installed.
Now, I had to boot in to recovery mode, which I had problem. I didn't know that I had to fully turn off the phone to boot into recovery mode. After the phone is fully turned off, press volume down, camera button and power button and hold all 3 buttons for while.
Once I was in the recovery mode, it automatically backed up data. This took a while. After that, I wiped data, cache and dalvik cache several times.
Then I installed Bonsai zip file while I was in the recover mode. It automatically installed and rebooted the phone.
But for me something went wrong. The phone had mixed up boot animation, and it booted to stock DK28 theme. Also when I touched the phone, it didn't respond and rebooted. I had to pull the battery and boot to recovery mode.
I then wiped data several times again and reinstalled the Bonsai rom. This time it rebooted correctly! I confirmed by checking the About in the phone.
So far its working good and Quadrant benchmark gives me 1800 range.
Also I am happy that after few tweaks, my stock earphone control is working!
Now I am a happy camper!!

Excellent. Check out the other ROMS when you get the chance.

I too just recently decided to root/new rom my epic. It was extremely easy and not nearly as complicated as I thought it might be. Went with Bonsai also because the instructions were so simple and I wanted a simple functional rom. So much faster and better! Few little nuances, (call log having sms messages which i fixed) and the speakerphone toggle on calls but other then that it is awesome. Anyone on the fence...take the jump.

I think I will take the jump this weekend for the first time. I have wanted to install froyo and try out the many custom roms for a long time now. I guess I'm just a little nervous but I'm sure there is not much to worry about.
Sent from my SPH-D700 using XDA App

i tried a few of the dk28 roms (frankenstein, bonsai, nebula, quantum) over the past week or so, and kept running into hiccups that didn't really entirely kill the enjoyment of having froyo on my epic, but it really soured the deal. i appreciate what the devs have done with the dk29 leak. i'm sure it leaves much to be desired, but i'm looking for a smoother experience so just today i flashed back to syndicate. have to say i'm very pleased with that decision

The reverse is the case for me. No DK28 ROM has been worth it to me in any case (it's not complete/'tis a leak anyway). Got tired of the stop gap performance and went back to DI18 a while ago and it is a breath of fresh air. Like night and day performance/battery wise.
Until official Froyo is out, i'm not interested anymore.

LordLugard said:
The reverse is the case for me. No DK28 ROM has been worth it to me in any case (it's not complete/'tis a leak anyway). Got tired of the stop gap performance and went back to DI18 a while ago and it is a breath of fresh air. Like night and day performance/battery wise.
Until official Froyo is out, i'm not interested anymore.
Click to expand...
Click to collapse
Im in the same situation as you. Ive tried all of the Dk28 roms and always came back to my DI18 set up. Most Dk28 roms worked well overall. However I personally couldnt get over the lag, no matter how small. With my current DI18 rom and kernel set up, everything flies. The devs have done a great job tho on all of the 2.2 roms.
Sent from my SPH-D700 using XDA App

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.

Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.

I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App

Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App

aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.

It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.

I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.

Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.

akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.

Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.

Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.

Try removing the SD card and booting.
Sent from my PC36100 using XDA App

rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!

It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.

bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?

Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.

herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.

Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?

Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol

akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

[Q] evo cm7 nightly freeze

i'm running cm7 nightly with latest radio, wimax, 1.90 pri and nv. everytime i flash a kernel my phone gets stuck at white screen and will not allow a nand restore whatsoever. my battery life is terrible even if i try pri 1.7 and nv 1.7.. wiping never helps.. why is this happening? any ideas???

Probably because you are doing something wrong. Just like this thread you felt compelled to start. You know you could ask this question in the CM7 thread or even the question and answer forum...
Ok now that that has been said what kernel are you trying to flash?
Sent from my PC36100 using XDA App

i placed the same question over on cyanogen forums and got no help. i was using cm7 nightly build 8. I wiped then flashed sz 0.0.9 no sbc kernel and 30 minutes later froze, rebooted and still stuck at white screen. Booted into recovery and only got amon_ra_1.8 never loaded. So i had to put the pc36 file on my sd card via laptop and managed to go into hboot that way. Let it update itself then reflashed cm7 nightly #8. Was working smoothly except for battery life which is why i did a back up and tried netatchy_toast_4.2.3. That worked a few hours and landed me back at frozen white screen with a nand backup that kept giving me a flash error. After 3 tries the backup loaded and thats where i'm stuck at. I think i'm about to flash cm7 build 12, the latest, see how it works, then give a shot to another kernel. Any ideas?

Yes. It's a nightly build. It's unstable, and no one is going to help because it's almost impossible to troubleshoot.
also netatch's kernels are for sense roms. Use an AOSP kernel.

Try the kernel in my sig. Seems to work pretty well.

tried to post in cm7 thread but got a "new user" warning saying i dont have enough posts to post in that area. so i had to start at the noob level..

HipKat said:
Try the kernel in my sig. Seems to work pretty well.
Click to expand...
Click to collapse
Im gonna give that kernel a shot if nightly 12 still sucks up my battery. Only thing is, thats the same kernel that got me frozen the first time lol. Maybe it will run better with nightly 12?

Do a full wipe of system, boot, data, and cache, then flash just the ROM and GApps package. If you still have issues, get a logcat, and post in the CM7 Nightly thread here.

sounds like a plan. just got done flashing #12. Colors in notification bar stay white sometimes now lol. I wiped first then flashed. Read somewhere you didnt have to wipe if flashing 12 over another nightly. Wiped regardless, just throwing it out there..
oh, do i need to reflash pri and nv or are they not an option for nightly builds? tried them once before and pri never showed up.

cm7 nightly #12 seems to have helped battery life alot. Taught my daughter to ride her bike, went to movies and saw "Rango", stopped by walmart, came home, battery remained strong. On nightly #8 it was dead in 3 hours. #12 seems like a winner so far!! Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!

quickstang1 said:
Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
Click to expand...
Click to collapse
There are NO PRIs / PRLs/ NVs, or any of those things. Those are never part of any rom flash. Those are either flashed separately, or obtained through a sense ROM via profile or prl updates.
Also, even though you are thinking things are fine with your current build, I am curious what recovery you are using... and what is your HBOOT. are you forever S-OFF?

using amon_ra 1.8, unrevoked forever. Cm7 nightly #12 is kickin a$$!!! No reboots, no battery drain, no weird glitches.. Stock kernel, cpu set at "performance", unplugged from 8am to 4 pm, using internet all day, wimax on, 3 weather widgets running, made it all that time and still had 15% battery left... Not sure what was changed in 12, but its a definite keeper!!!

[NOTICE] Gingerbread Related Bricking - May 27th 2011 update

There is no way to rule out GB as the cause of this failure right now. All we have is theories and the best fitting one is an emmc chip failure. Until we can find a user with a brick, who is still s-off, we can not learn more.
DO NOT FLASH OVER BRICKS, We need you to have s-off for trouble shooting.
UPDATE
We need info from brickers and non brickers please see
Please see here http://forum.xda-developers.com/showthread.php?t=1098363
--old post--
It has came to our attention, over the last few days that the recently leaked Gingerbread radios maybe causing a oddly large number of bricked phones.
This can affect any Thunderbolts running Gingerbread (except CM7 users), even after running fine for several days.
The cause at this point is not completely understood, and AndIRC as a whole recommends you revert back to Froyo until we understand it, or have a new leak.
When bricked, the phone is sent into an endless bootloop, no matter if you are booting into Android itself, or into the recovery. Trying to revert after the bootloop does not fix this issue.
Theories:
GB Radio causing corruption on the emmc:
Undisclosed chipset issue (Sorry no details will be coming unless verified)
GB miss reporting battery stats, aka just dead battery (Debunked by ryan2600 and I)
"Not sure if its the radio, i got a bootloop experience this morning after tethering my tablet on a freshly charged tbolt, few minutes later the phone died and stuck in a bootloop, there are times i can go to bootanimation sometimes it goes up to HTC screen and dies, I can go to HBOOT but before i can do anything the phone dies.
Good thing i have a 2 extra battery and an external charger from ebay, I swapped the battery and my phone is back to life, it seems like the GB roms are not charging the battery properly and reporting that the battery is around 80-90%" http://www.reddit.com/r/Android/comments/hk54l/if_youre_using_the_leaked_gingerbread_build_or/

Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App

I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!

Awww fiddlesticks! Well at least I get my baby back. Landscape Rosie is the girl for me.

swimminsurfer256 said:
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Click to expand...
Click to collapse
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.

Wow this sucks, I don't really wanna go back to froyo

Thanks jcase and Team AndIRC! I nearly flashed the latest BAMF GB update. I'm glad that I stuck with 1.6.3

Wow, mine just started 2 mins before this thread went up. I was sitting at my desk and saw it reboot and now it won't stop. It actually loads up Android entirely, gets to Lockscreen and then restarts.

zskate311 said:
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone using the GB Radios (ie everyone on GB but CM7 users)

jcase said:
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Click to expand...
Click to collapse
Ah didn't see that. Does bootloader not work?

Well crap, back to froyo I go then, just to be safe.

*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.

I actually think I read about this somewhere else in the forums. I don't know if he was running gb but I'm guessing so. Thanks for this, I'll be reverting back later.
Sent from my ADR6400L using XDA Premium App

adrynalyne said:
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
Click to expand...
Click to collapse
It's all your fault.
Sent from my ADR6400L using XDA Premium App

reverting now... can I just flash a froyo radio and rom or do I have do the whole process in OP?

Thanks for looking out for us
Sent from my ADR6400L using XDA App

Thanks for the heads-up!

Might as well Nandroid my Ginger builds so I have them for when we get a more stable radio release. Curses Verizon! I will miss my Sense 3 elements!

This sucks! Thanks for the heads up, though, Justin!

Bootloader works. I ran into this problem once. Have a backup of the ruu handy. It will get you back to a stock rooted froyo state
Btw...I'm staying on gb. Ill take a risk.

something strange happened

so I had everything flashed over a week ago and all was running smoothly, but today I left my phone alone for awhile while I went and played some football. I came back and only the softkeys were on and nothing was responding. I pulled the battery and turned it back on, but was thrown in to a bootloop. now I'm in download mode attempting to flash everything again in ODIN (heimdall doesn't work for me) and the flashes are failing. I'm going to wait for this one to fail, then probably going to attempt going back to EC09 or whatever the one before GB was. any idea what could have happened, or better steps to move forward?
thanks in advance,
jake
EDIT: tried a different USB port, and ODIN worked. need to keep that in mind to prevent myself from panic attacks in the future.

What I have noticed with the current mods are there are some bugs. When I flashed tb's nod my phone went crazy luckly I had a back up and was fine so I would let them work out the bugs or let them know so they can fix it. Also remember the gb update is a leak so the ROM alone has bugs so it could be many things.
Sent from my SCH-I400 using xda app-developers app