Related
i want to know if i can keep the stock rom for my epic(Build:sph-d700 eclair.di18, kernel:2.6.29) and add a custom kernel? and which kernel is the best for battery life and speed? tired 2 times and bricked my phone both times. phone is rooted and used the one click root.
juice.ki11z said:
i want to know if i can keep the stock rom for my epic(Build:sph-d700 eclair.di18, kernel:2.6.29) and add a custom kernel? and which kernel is the best for battery life and speed? tired 2 times and bricked my phone both times. phone is rooted and used the one click root.
Click to expand...
Click to collapse
There's a sticky at the top of the forum that lists the custom ROMs and kernels available for the Epic.
I suggest you pick one and try it. If you like it keep it, if not, flash another.
You need to be rooted and you need custom recovery.
Via clockworkmod recovery, you can flash just a kernel to your stock ROM.
hope this helps
has anyone made a video on how to do it the right now on a EPIC? i tried it like 5 times with baby step step2 and it didnt work on DI18
juice.ki11z said:
has anyone made a video on how to do it the right now on a EPIC? i tried it like 5 times with baby step step2 and it didnt work on DI18
Click to expand...
Click to collapse
you need to be rooted. you also need clockwork mod recovery.
then you can flash a different kernel
yeah i have all that and ive watched videos on how to do it on other phones but not on the epic it seems easy but when i do it my phone mess's up! i put the zip in the root of the SD card power the phone off and put into clockworkmod instill the zip and it bricked my phone every time. not sure if im doing it right. thats why im asking if theres a video on how to do.
Do One-click-root, clockwork recovery (both should be done from the computer via USB debug mode) then, power off your epic. Next, Hold Volume Down, Camera Button and Power Button until the clockwork recovery screen pops up(should be green text, not blue which is the stock recovery). If you have the custom kernel already in your SD card, go to Install Zip From Card > Choose Zip from SD Card > (Custom Kernel)
And there you have it.
To flash any rom, you do the same thing
dude i did all that and it doesnt work. it says everything was installed but when i reboot it, it doesnt go pass the samsung.com screen. what kernel works with stock rom DI18??
I've tried both Phoenix Kernel 1.49 as well as Xtreme kernel's 1.0 version. Both work fine. I think you need to flash back to stock rom via Odin and redo the process... you know how to do that right?
i havent changed my rom im using the one the phone comes with i just want a custom kernel thats all! ive reset my phone 5 times in the last 24 hours trying to get this to work! and nothing.
The process is very simple for flashing a new ROM/Kernal, and you seem to have the concept down. You could try restoring to factory, re-rooting through the one-click to ensure it goes through correctly, than try flashing a new kernal then.
Also i know for new roms the first boot takes a while, im not sure how it is for kernals. Also i noticed theres a few different kernals around here, some for 2.1 and some for 2.2. Make sure you are using ones compatible with 2.1 if you are on the stock rom!
yeah i did that i tried babystep and step2 and both didnt work. i dont want to give up! but im over reseting my phone.
Do you get any errors at any point?
Sent from my Android using Tapatalk and Wifi/CDMA
when its installing the zip on other videos i see the yellow bar load till its done but i my phone it starts than big blue letters so up on the screen. and its goes back and it says its done and that it was installed but when o reboot my phone it wont go pass the samsung.com screen
Which kernels have you tried?
Sent from my Android using Tapatalk and Wifi/CDMA
babystep, step 2
I'm sorry but I dont know what babystep and step 2 are. Link?
Sent from my Android using Tapatalk and Wifi/CDMA
http://www.bakedsnackshack.com/source/
Its those kernels. I tried babystep and I too only see the samsung.com splash. Those kernels are probably optimized for baked snack. My guess is they dont play nice with the stock boot animation.
Sent from my Android using Tapatalk and Wifi/CDMA
Try Phoenix 1.49s.
Sent from my Android using Tapatalk and Wifi/CDMA
I'm curretly using xtreme kernal with stock rom, and then setcpu to have it set at 200min 800max... still not getting better battery life though. I think ill try phonex kernal next...
Sent from my SPH-D700 using XDA App
MODS: I am unsure of where to post this so sorry for the trouble.
So I work for Tmobile and love showing off my rooted mytouch 4g in all its glory.
So I requested a warranty exchange and got a TAIWAN VERSION w/ GOOD SCREEN in return. Like Day and Night.
Upon Receiving my warranty exchange phone it was 2.2.1. I attempted the same Visionary Root Process, (however was there some extra file i needed to DL? i forget)
After rooting my new phone, S-Off, I had flashed FAUX stock kernel 0.4.0b.
THEN THIS HAPPENS:
I cant get past the mytouch 4g splash screen. The first logo that appears. It gets stuck or bootloops. I can HBOOT and get into recovery 3.0.0.5
This is all i can do...i already asked for another warranty exchange...but in the meanwhile..how can i fix this problem or what did i do wrong?
ALSO can you backup one mytouch 4g and load it back up on another mytouch 4g with the same sd card? Thanks!
I had this problem with my MT4G when I flashed his kernal. It seems that his kernals are not designed to work with every 4g device. I hope you did a nandroid backup on the device. I was never able to get past the mytouch splash screen with his kernals
Sent from my HTC Glacier using XDA App
Well, at since you can get into recovery there should be a number of things you can do to get your phone to boot.
Download a new ROM to flash, if you are on clockwork 3 then you need CM7.
Clockwork has usb drive ability, turn it on, transfer the ROM then flash.
If you can get into HBoot or Recovery on ANY phone, you're safe. Hell, if you can't get into HBoot, your phone wouldn't even start up since HBoot is basically the equivalent to BIOS.
THE VERSION OF CLOCKWORKMOD RECOVERY YOU USE IS CRITICAL!!!
The version you are using is for Android 2.3 only.
Flash a v2 Recovery with adb or fastboot and reinstall your kernel, or install CM7.
HTC Glacier CM7 41
I am trying to do this. How would I get my comp.to.recognize the devise. Sometimes it says mass storage device detected sometimes not. So I need cm7 rom to b able.to boot?
Sent from my HTC Glacier using XDA App
Tiltpoet said:
I am trying to do this. How would I get my comp.to.recognize the devise. Sometimes it says mass storage device detected sometimes not. So I need cm7 rom to b able.to boot?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
If you've ever connected it via USB, it should have installed the drivers automatically (at least on Windows). I think the ADB driver only installs if you had "USB Debugging" checked. Mass Storage usually only refers to mounting the SD card; the driver for ADB is different. Look for something like Android Phone or Android ADB Interface in your device manager (again assuming Windows).
If you have ADB set up, try running the adb devices command. If it spits back the serial number of your phone, you should be okay to proceed.
Don't exchange the phone, fix it...
Just use another phone to copy the latest CM7 to the root of your sdcard and flash, if that doesn't work do the same thing with a PD15IMG.zip file to the root of your sdcard, hboot and restore to stock.
I have no problem with someone doing a warranty exchange for a hardware issue, but if you break your phone, don't make someone else pay for it...
i ended up solving the problem by doing what some of you had suggested. I flashed CM7 and WAH-LaH! when the phone got past the splash screen into CM7 i was on cloud 9.
Now What are the benefits of running CM7? as opposed to going back to Sense w/ Faux kernel again?
PLUS
how would i go back to a sense type rom again? would i go back into rom manager and flash a different recovery?
XDA you have been so helpful!
___bonus__also the haptic feedback on this phone was not as strong as my original..though idk if its just me or not..should i call tmobile and stop shipment of the OTHER phone? how is it i have a taiwan version plum W/ good screen?
There are no Sense-based Gingerbread (Android 2.3) ROMs available now ... Best practice its to make a Nandroid backup of CM7 with your installed CWM Recovery, then flash a version 2.x of CWM Recovery to install any Froyo (Android 2.2) based ROM.
HTC Glacier CM7 41
Tiltpoet said:
i ended up solving the problem by doing what some of you had suggested. I flashed CM7 and WAH-LaH! when the phone got past the splash screen into CM7 i was on cloud 9.
Now What are the benefits of running CM7? as opposed to going back to Sense w/ Faux kernel again?
PLUS
how would i go back to a sense type rom again? would i go back into rom manager and flash a different recovery?
Click to expand...
Click to collapse
Good to see it is working.
Its mostly personal preference at this point. Sense on the MT4G is pretty responsive and has some nice features. CM7 has its own tweaks and features. You loose the sense widgets but many can be replaced with alternatives in the market. You gain and loose relative in both ROMs So try out both and decide.
Use ROM Manager app to flash a new recovery. One of the 2. versions, then flash a froyo based ROM.
what about flashing kernels..are those "roms"
is cm7 itself pretty battery efficient? i still downloaded setcpu and set it to 11---.
2.XXX ..u mean like 2.5.1.4 for example..sorry not lookin at the phone atm.
++bonus
i also dl the cynogyn updater or wut not..wut url do i add for themes?
Tiltpoet said:
what about flashing kernels..are those "roms"
is cm7 itself pretty battery efficient? i still downloaded setcpu and set it to 11---.
2.XXX ..u mean like 2.5.1.4 for example..sorry not lookin at the phone atm.
++bonus
i also dl the cynogyn updater or wut not..wut url do i add for themes?
Click to expand...
Click to collapse
Kernels are not ROMs, the kernel is the underlying software of an OS. The kernel talks to the hardware and lets different parts of the OS communicate. Kernels are ROM specific, or Framework specific. A sense ROM can not use a AOSP kernel and vice versa.
CM ROMs can be good on battery, or not. It all depends on personal use and how you set it up.
That is a good recovery to use when flashing sense ROMs.
Not sure about the updater. If it is the one I am thinking, it hasn't been updated in a while. I think it has been abandoned in favor of ROM Manager. CM updater did come in some of his older ROMs, before ROM manager became the norm.
So I can or cannot flash fauxs kernel. I really liked the smartass profile. Also..I'm on cm 7 now...y do I get force closes on my market.
Sent from my HTC Glacier using XDA App
As people have already said, you used the wrong version of clockwork, also, use clockwork to flash a new rom. And make sure you use the right version.
Tiltpoet said:
So I can or cannot flash fauxs kernel. I really liked the smartass profile. Also..I'm on cm 7 now...y do I get force closes on my market.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Try fix permissions. If that does not work, do a full wipe (factory reset). If that still does not work, try re-flashing the ROM.
If you flashed a new kernel before you started having issues, this may fix it, or you may need to wipe caches and re-flash the kernel.
A lot of roms say that they require clockwork recovery 3.0.0.6 to flash them. I know there's a way to flash it manually, but I personally want to wait until rom manager supports it. Is it absolutely necessary that 3.0.0.6 is there? I have 3.0.0.5, and i'm fine with switching between that and 2.5.1.2 in order to flash roms. Namely, i want to flash royalmint as it looks quite sick. quite sick indeed.
If you're willing to use 3.0.0.5 to flash Gingerbread ROMs and 2.5.x.x to flash Froyo ROMs, then it's not necessary. It's a whole lot easier to have one recovery though, obviously. ROM Manager does support 3.0.0.6 as far as managing backups, if that matters to you.
If your fine with re-flashing then not really. There are some fixes and code improvements but for the most part its up to you. but i'd suggest the 3.0.0.6 just for the convenience and i haven't heard of anyone reporting issues related to it. So as far as being safe id say its as safe and flashing back and forth to begin with. but don't do anything your uneasy about cuz if something does happen you are solely responsible.
If nothing else you could flash the newest version of 3.0.0.6 just so you don't have to flash "stock" recovery when you need/want to recondition/retrain your battery.
http://forum.xda-developers.com/showthread.php?t=1014554
Isn't there a problem with backup in 3.0.0.5? Either way, the maker of Rom Manager works with the CM team, so there are literally 20 phones out that they are trying to provide support for. It's not that they guy has seen the fixes/updates in 3.0.0.6 and decided they were wrong, he just has a lot on his plate. The improvement is worth it, for compatibility, if nothing else. Add in the ability to charge while off in the newest 3.0.0.6 and it is literally a one-stop recovery. Do what you like, you don't NEED it, then again you don't NEED custom ROMs, or cell phones, or forums. So I guess it's all relative, but it IS important for flashing and ensuring a calibrated battery.
kimbernator said:
A lot of roms say that they require clockwork recovery 3.0.0.6 to flash them. I know there's a way to flash it manually, but I personally want to wait until rom manager supports it. Is it absolutely necessary that 3.0.0.6 is there? I have 3.0.0.5, and i'm fine with switching between that and 2.5.1.2 in order to flash roms. Namely, i want to flash royalmint as it looks quite sick. quite sick indeed.
Click to expand...
Click to collapse
You do not NEED the 3.0.0.6 but it does make life easier. If you don't mind re-flashing the images then more power to you.
3.0.0.6 makes life easy. Trust me. I flash backup and restore alot through diff builds.
Sent from my HTC Glacier using XDA Premium App
I love 3.0.0.6 and has made life a lot easier, but don't believe it is necessary. Have heard that some of the bootloop issues are from using 3.0.0.5, but don't know if that holds any salt. Some of the mods are not compatible with 3.0.0.6 though.
Sent from my HTC Glacier using XDA App
ptran said:
I love 3.0.0.6 and has made life a lot easier, but don't believe it is necessary. Have heard that some of the bootloop issues are from using 3.0.0.5, but don't know if that holds any salt. Some of the mods are not compatible with 3.0.0.6 though.
Click to expand...
Click to collapse
You're giving out bad information. As has been said over and over, 3.0.0.6 is absolutely necessary to flash both Froyo and Gingerbread ROMs, and there is NOTHING that it is not compatible with. With 3.0.0.6 installed, you can flash ANYTHING, which is why it's so highly recommended.
Not true. Some of the older mod scripts are not compatible with the newer clockwork recoveries (see faves to anything post by trueblue_drew) and thus will get a script error if you don't flash back prior to flashing it. Most mods will work, but NOT all.
Sent from my HTC Glacier using XDA App
ptran said:
Not true. Some of the older mod scripts are not compatible with the newer clockwork recoveries (see faves to anything post by trueblue_drew) and thus will get a script error if you don't flash back prior to flashing it. Most mods will work, but NOT all.
Click to expand...
Click to collapse
Please link to those mods so people are aware. So you're saying they work when flashed on 2.5.x.x but not 3.0.0.x?
Yes. I thought the same thing as you until I tried flashing an anything to mms favorites button this morning and then got the script error. Read through the post and found out why. Will post a link to the thread.
Sent from my HTC Glacier using XDA App
forum.xda-developers.com/showthread.php?t=885967&page=12
Sent from my HTC Glacier using XDA App
ptran said:
forum.xda-developers.com/showthread.php?t=885967&page=12
Click to expand...
Click to collapse
For those that might want that, that's good to know, thanks. I still think that considering all factors, 3.0.0.6 is still the best overall recovery solution, but it's good to know that it doesn't work for 100% of flashable items.
Agreed. Flashing back and forth seems like a waste of time overall.
Sent from my HTC Glacier using XDA App
ptran said:
Not true. Some of the older mod scripts are not compatible with the newer clockwork recoveries (see faves to anything post by trueblue_drew) and thus will get a script error if you don't flash back prior to flashing it. Most mods will work, but NOT all.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
And the devs for those mods only have to change the update script to an updater script. Its fairly easy to do, and is technically the right way to do things.
3.0.0.6 does not support flashing amend scripts. Google has moved to using Edify scripts, or updater-scripts. That is the only type of script that 3.0.0.6 will support.
and for those mods (that are not full ROMs and simply minor add-ons) you can select all clockwork recoveries, switch to 2.5.1.2, flash your amend script, reboot, all clockwork recoveries, 3.0.0.5, and you're back on 3.0.0.6. They are not (for the most part) game-changing situations where you find yourself in a bootloop and it is important to have a versatile recovery like 3.0.0.6. Most of the flashable fonts on XDA are amend scripts as well, so using that method is an easy workaround for cosmetic upgrades and other framework tweaks. You can make a mistake and put yourself in a bootloop flashing these things, but first timers and people struggling to understand what is important about the different recoveries are dealing with ROMs for the most part. If you are getting to the details with other mods, you should at least take the time to get to the details about ROM Manager and the differences in the available recoveries.
I had no clue that this forum had gotten bigger than an answer or two 0.o
Anyways, i have a couple of reasons for not flashing 3.0.0.6 manually. I'm still a bit of a noobie, i got my very first android phone on christmas and i have managed to flash multiple release candidates of cm7 since then. I haven't gained 100 percent confidence in my abilities yet. Also, the instructions say that flashing 3.0.0.5 in rom manager will flash 3.0.0.6, and 2.5.1.2 will flash stock recovery. It seems like if any newer recoveries were released it would be impossible to use rom manager to update it with the slightly different set up.
Also, i heard another guy say that having the phone boot in to recovery when plugged in to power could be a failsafe if the phone won't boot normally, so i'll stick with 3.0.0.5 until rom manager officially flashes 3.0.0.6 the easy way.
kimbernator said:
Also, i heard another guy say that having the phone boot in to recovery when plugged in to power could be a failsafe if the phone won't boot normally, so i'll stick with 3.0.0.5 until rom manager officially flashes 3.0.0.6 the easy way.
Click to expand...
Click to collapse
The original version of 3.0.0.6 in option94's thread also boots into recovery when plugged in.
Hi,
My warranty has just run out on my Nexus One so I've decided to unlock the bootloader.
My Aim is to get from stock non rooted Gingerbread to rooted Gingerbread with busybox, SU, and ultimately being able to boot into ubunto in chroot, I've been reading up on all this for a few days now but just need a small amount of help with Recovery, Gingerbread ROM choice, and the order that thing should be done, by someone who's done this before.
I take it the first thing is to install SDK and get The USB Driver working on PC, its running XP by the way.
Then I unlock the bootloader, !HELP! to do this do I enter hboot or fastboot, before connecting the phone to the PC? I have to copy 3 files somewhere and use ADB and run command for **** OEM unlock, can't remember the exact command, (I've got instructions for this) and then agree to void my warranty etc.
I then find and download the correct custom recovery image and copy this into the tools folder of the SDK. And install (got instructions for this to).
!HELP!
Which custom recovery image should I use? and which Rooted Gingerbread ROM is most popular ?
After installing the custom Recovery can I just flash a custom ROM? I've seen something about SU.zip mentioned, is this necessary?
If I can just flash a custom ROM, I do this by downloading and copying the custom ROM of choice to the root of my SD card. Start phone in recovery mode and install from SD? I then install the google add ons .zip (if required) using the same method.
Sorry for such a long post and so many questions but I can find all the information for what I'd like to achieve but not in one place and nowhere in any chronological order.
Any advice appreciated .
Please read the Wiki, "Root" guides, "Unlock bootloader and install custom ROM" thread. Execute until the point of installing custom ROM.
Look in "Recovery" section for recoveries, install the latest Amon_RA.
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
GB ROM
Im running CM7RC4 and am happy w/ it
MouseIdt said:
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
Click to expand...
Click to collapse
Thanks everyone, but this looks like the one for me, going to unlock bootloader now install custom recovery and flash su.zip.
I'll post back with how I went on. Wish me look
A apprehensive newbie ;-)
Flash this as well, otherwise you will lose your custom recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA Premium App
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Nooooo
Rusty! said:
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Click to expand...
Click to collapse
My understanding was 12 months but, your probably right. I've unlocked the bootloader now and fortunately my N1 is in good condition, funtioning correctly ( well at least for now, I'll have to cross that bridge if and when I get to it )
Getting on to custom recovery, I realised something wasn't quite right after my first attempt. I installed custom recovery but without su.zip on my SD card. I managed after rebooting my PC to complete the custom recovery with su.zip on the SD card and was successful in that I've got SU on my N1. However I am quite sure I do need to fix something with the recovery, can someone explain what method or how I do this now. I've unlocked the bootloader, I am rooted with gingerbread but with a dodgy recovery.
Or do I do exactly the same as I did with su.zip and push recovery from ADB and flash from SD card, making sure that fix-recovery.zip is indeed on the SD card.
Hope this makes sence?
Any help appreciated.
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I've got ROM Manager installed and if I want to try anything it tells me I have to flash clockwork mod recovery, I was unsure if It was safe to do this after using a completely different recovery image to get where I am now.
Sorry for being such a paranoid newbie, but we all got to start somewhere ;-)
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I think CM7 rc4 is next, I do want to get Linux up and running though, even if it's in a virtual environment (chroot). and deffinately would like to check some nice themes out, I've not even looked at themes yet, I suppose it's quite easy after unlocking bootloader, installing custom recovery then flashing su.zip though. But still any pointers where to start my quest wouldn't go a miss ;-)
Recovery
its safe to let rom manager flash clockwork,ive done it
I heared about amonRA but it seemed like clockworkmod was more commonly used so I went for that, but yeah it's fine to flash a new recovery, just remember that whilst it's rare things can go wrong, it's YOUR fault not anyone's here regardless of the advice you may get here if your phone gets bricked or screwed up.
That said I'm still new to this but I'm learning as I'm going, just remember to backup your phone using rom manager before doing anything major so that you can always recover your phone/rom.
I started out hacking my nokia 5800 so was keen to have a go with the android platform.
Sent from my Nexus One using XDA Premium App
CM7 stable
Have you upgraded to cm 7 stable? its a definate upgrade
Hey guys, I'm probably going to sound like a noob but I need some help with flashing a custom rom to my atrix. I've been trying for a couple of days now with no success. When I first got my atrix it was on 1.8.3. Upon trying to flash any roms I got stuck in a constant bootloop. So i figured I'd flash to newer firmware anyway. So I flash to 2.3.4. I follow the briefmobile instructions on rooting my atrix and the root appears successful. I then install tenfars cwm. Now back when i was on 1.8.3 I had unlocked the BL. but now upon my flash to 2.3.4 I notice that my unlocked symbol has gone away. Do i need to redo it? Anyways then I boot into recovery and have tried flashing aura or alien many times. It always says success, reboots and I reappear to my normal screen with normal kernel and all. The only difference is the extra apps in those rom's are installed. Thanks for any advice. I would love to flash a rom but not having my phone the way I want for the past couple of days is really making me tired of even bothering.
1) use romracers CWM
2) if you want the alien rom to look like the alien picture, you need to install the additional theme
3) pretty sure alien uses stock kernel
4) it doesn't hurt to re-do the pudding unlock
Sent from my MB860 using XDA Premium App