I am just wondering why people use Clockwork. Every set of directions I have found to load custom roms involve Amon's. I am just curious as to why people would use Clockwork and if there is any advantage to it. Everything that I have found about people bricking their phones always involve someone using Clockwork so it doesn't seem to me that it would be a good idea to use it.
It's kinda "easier" but like you said all instructions pretty much use Amon's. Plus clockwork has caused tons of problems with Eris's so it really shouldn't be used. Anyway there's no real answer to this question, people just choose it.
I used it for a bit cause it was put on my phone when I flashed a 2.1 rom a few months ago. I wanst aware it was so dangerous. Flashed multiple roms with it, made nands, used it to upgrade SU... all was well for a few months, then while trying to flash a custom rom I started to realize it was causing my phone problems. I even flashed to an alt recovery (amons) using rom manager. That was the problem tho. I had amons but clockwork was still controlling everything and my phone (which had been running flawlessly for months) started to act up real bad. So I did alot of reading here on xda and learned clockwork can be mucho dangerous with the Eris. I went to the Eris Dev subforum and found a post on how to safely flash back to amons from clockwork. Did it, wiped the phone, put on a new froyo rom, and presto, no more issues. It may work fine for a little bit, even a few months, but silently in the background it screws with your Eris' brains lol. Glad I fixed that!
Sent from my nonsensikal froyo using XDA App
Related
Where could i find this for the Eris? I dont wanna use rom manager for a temporarily solution. I wanna be able to fastboot the .img to the phone for a permanent solution
I wouldn't use either of those, especially Clockwork. It is known to brick the Eris. In fact, every story that I've read about someone bricking the Eris, it always involves Clockwork. You may want to look up Amon's Rom Recovery or something like that. That's what everyone else almost has done. But you really want to avoid Clockwork for the Eris.
smokedkill said:
I wouldn't use either of those, especially Clockwork. It is known to brick the Eris. In fact, every story that I've read about someone bricking the Eris, it always involves Clockwork. You may want to look up Amon's Rom Recovery or something like that. That's what everyone else almost has done. But you really want to avoid Clockwork for the Eris.
Click to expand...
Click to collapse
Trust me I know all about that, ive been using Amon Ra for some time and ive been rooted for a few months, I just wanted to switch over to clockwork to try something new, ive used it before through rom manager and had no problems, but i wanted to be able to boot into it using Vol-Up and Power
...a pain in the ass for the Fascinate. The gf has one of these phones, and after seeing what I've done with my G2, she wants me to root and flash a nice rom.
Problem 1 (not so small): we both use macs at home.
Problem 2 (huge): after reading through the development forum - it doesn't look that easy to root, nor flash a decent rom on the Fascinate!
not only do some roms require you to have a specific kernel flashed to use them. Some roms require that you don't use the latest CWM. Also, none of roms seem to be using Gingerbread AOSP completely. They seem to be pieced together with Froyo.
Believe you me, I am not a dev in the slightest. Therefore, I am looking for a safe way to root and flash a decent rom to her phone. If there isn't, then I'll just let her run stock.
Is this easier than I'm seeing it?
enserio said:
...a pain in the ass for the Fascinate. The gf has one of these phones, and after seeing what I've done with my G2, she wants me to root and flash a nice rom.
Problem 1 (not so small): we both use macs at home.
Problem 2 (huge): after reading through the development forum - it doesn't look that easy to root, nor flash a decent rom on the Fascinate!
not only do some roms require you to have a specific kernel flashed to use them. Some roms require that you don't use the latest CWM. Also, none of roms seem to be using Gingerbread AOSP completely. They seem to be pieced together with Froyo.
Believe you me, I am not a dev in the slightest. Therefore, I am looking for a safe way to root and flash a decent rom to her phone. If there isn't, then I'll just let her run stock.
Is this easier than I'm seeing it?
Click to expand...
Click to collapse
Honestly, it is not that difficult. Just takes some getting used to. Obviously you have done a bit of reading, I know it seems daunting, but I promise, once you have it down it is nothing. The kernels...Most ROMS are kernel switchable, within reason. MOST of our ROMS require the RED CWM, which honestly is not a big deal, the orange is just too glitchy. And as far as the ROM's being pieced together with Froyo...Well, I am no dev either, but yes, I believe most of the ROMS are a Frankenstein of sorts, but we don't even have a Froyo source to work with yet. So the dev's, in my opinion, have done an AMAZING job. In terms of flashing on a Mac, I am not sure if Odin works on a Mac, Heimdall does though I believe. Rooting is extremely simple, it is only the flashing the right CWM, modem, etc. that may confuse you. Honestly, if you just keep reading the right things, you'll see it is pretty simple. I recommend Adrynalyne's Super Clean 2.9, and Big Loof's Steel Blue theme, with the EB16 kernel (Also Adrynalyne's).
http://forum.xda-developers.com/showthread.php?t=948722
This thread has a good walkthrough, I'd follow it through Post #5... using Superclean. It's an incredibly performing full Froyo rom. Remember that Froyo is not officially out on this phone, she's running Eclair right now. Gingerbread is a ways off (though punk kaos is making great progress).
Before EB01, rooting for me was just clicking a single button.
I never had to root again since flashing EB01. For flashing itself, its just download, reboot to recovery, and flash. Not sure how its a pain in the as as it doesnt even take a minute or so.
I did end up installing 3.XX CWM from ROM manager, but I only reboot into orange CWM if i reboot using ROM manager. If I dont, I end up rebooting to red CWM.
Thanks for the responses. Put a few things in perspective. I totally forgot that she is still running Eclair and Froyo isn't officially out for these phones. My mistake, and now that makes complete sense to me why most of the roms are froyo based or patched. Another thing that made me hesitant is that Odin doesn't run on mac, and I would have anything to save the phone (unless I use one of the pcs at work) if something goes awry. I will read up on Heimdall and see if I can use that.
My apologies if I sounded bothered or uptight about the situation, thanks for the well-mannered responses to my mini-rant. Of to read up a bit more, starting with the link postd and Heimdall.
Found a quick guide for rooting the Fascinate with a Mac. Now my issue is...switching to EB01 without Odin because SuperClean needs it, correct?
Folks...
I've been using ClockworkMod for a while on my HTC Incredible and today I received my Woot table.
I installed ClockworkMod on the tablet and did a backup of my "stock" image (I applied the 3588 update).
From reading these ROM threads, it looks like there's some differences in how I am used to interacting with Clockwork and some of these warnings sound pretty ****ing dire...
If I install a ROM, isn't going back to my previous backup a matter of formatting and restoring? It sounds like some of these ROMs interfere with Clockwork in such a way that could result in a bricked device. I've been wiping and restoring on my Incredible for almost a year now and I've never heard of a ROM dicking with Clockwork before...
What's the difference or am I making a mountain of a molehill here?
There is a very specific version of CW that bekkit put together for the G=Tab. The problem isn't the rom messing with CW, it usually is Rom Manager that will mess with it. Rom Manager usually will want updated, especially with CM installs.
I have had to nvflash the tablet in the past after upgrading CW via rom manager.
The other issue that is common, and I have had happen to my beloved Dinc, is having to repartition the storage. The groundwork for the Dinc was much, much more stable than the default tapNtap that is released with the tablet.
Something some people may also miss is the kernel for GB is much different than the kernel with froyo.
Rest assure, bricking this thing seems to be an accomplishment and almost impossible. Trust me, I have given my best effort to do so. With nvflash or adb almost any tablet can be recovered.
One last thing to look out for, how internal storage is handled. Some roms use internal as emmc (like the Dinc), while others mount as sdcard. CW doesn't handle this switch gracefully. You can mount usb storage in advanced menu and move the recovery files over if needed.
While dharr18 is mostly correct there are a few ROMs floating around out there that will have trouble with clockworkmod. TwoTapsX and TnT Lite 5.0 (both currently held from distribution by the developer) are based on a UAT build (3991) that require using the stock recovery and bootloader from build 3588+ to install correctly. There is some speculation that this may be the standard going forward.
Thanks KJ, I forgot about those two as I have not loaded them to date.
dharr18 said:
The problem isn't the rom messing with CW, it usually is Rom Manager that will mess with it. Rom Manager usually will want updated, especially with CM installs.
.
Click to expand...
Click to collapse
Yeah, I fell into that trap... really FUBAR'ed my tab until i had to nvflash a full recovery.
dharr18 said:
Thanks KJ, I forgot about those two as I have not loaded them to date.
Click to expand...
Click to collapse
You're welcome. I run TTX regularly (well... in between my attempts to find creative new ways to brick this thing...).
Deacon,
The truth is there ARE some dire consequences. Bricking a G-Tablet is extremely hard,
but you can lose data. If something breaks on your tab and your have loaded a ROM
you do not have a warranty. There are risks involved.
And in my opinion a lot of people try to do too much too fast and too often wind up
in dire straights.
There are stickies on most of the recovery/problematic stuff. Good to read them first.
Rev
the problem isn't with the ROM
I follow roebeet and the tnt lite ROM - VS is updating their boot loader from 1.1 to 1.2 in some of their OTA updates. Mostly the 3588 and the 3991. If you are playing with those or it came installed then it can be a bit of a hassle depending on what ROM you are playing with. I updated my gtab to 3991 and was able to nvflash it back to 3588 and install vegan5.1 and tnt lite up to 4.2 without any issues. Just be sure to read up and be able to complete an nvflash if it gets ugly on you. I really recommend learning a little linux - nvflash is a breeze in there.
Hi,
I've been reading and reading but am not fully comforatable making a decision on what to do here, really want to avoid bricking my baby I'm running a Bell Atrix with Version 4.2.11.MB860.Retail.en.FR. I really want Gingerbread and am tired of waiting for Bell to release it, even if they did, I would have to somehow return to a stock Bell Rom. What is my best option to upgrade right now avoiding any kind of bricking, memory or battery issues? Links would be great
I don't have any links for you, as I'm on my phone right now, but as a first step you need to flash the IHOP_bell.sbf to unlock your bootloader.
This is probably the riskiest part since you're flashing an sbf, but it's small and quick. If you have osx or linux, sbf_flash actually feels safer to use than the glitchy rsd lite from moto. After that install cwm using moto-fastboot. Once you have the clockwork mod recovery system it becomes very easy to switch roms from directly on your phone. Look for gobstopper by nfhimself. He was kind enough to put together some really good stuff for us.
Something to note: 2.3.4 and cm7 are both somewhat buggy at this stage. Buggy enough that I've gone back to 2.2.2 for now. I can put up with fc's but I can't have my main phone rebooting or freezing, or having irregular battery so often
Sent from my MB860 using XDA Premium App
Not sure of all the differences between the Bell and ATT versions but there is a great n00b guide here:
http://forum.xda-developers.com/showthread.php?t=1154600
You still have to look around a bit to find all the things you need. Unlocking the boot loader and rooting really aren't all that difficult.
Like maledyris said, its really easy to switch ROMs once you get CWM (Clockwork Mod) installed.
I'm a n00b and had no issues following Swiftks instructions.
Be sure to pay attention and don't try something for ATT only.
Have fun!
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks