Related
Ive been trying for about a week to get CM6 on my incredible. And i see some of the people on this forum have it. Ive contacted developers and users alike but for some reason I'm having trouble. After Root, I downloaded and installed Rom Manager but I'm unsure what to do next. I tried to flash Clockworkmod with the app, but when I boot up into recovery, I dont see The Clockwork menu, or the Nandroid backup option. I dont want to Flash the rom without being able to make a backup or install custom Update.zip files. Does anyone have any suggestions???PLEASE PM me for any suggestions!!!!!!!!!!!
If you aren't seeing the clockwork recovery, then you didn't run the reflash tool after you rooted. Run the reflash tool and it will load the custom recovery correctly.
what reflash tool?
unrEVOked 3, should be a link to it in this forum
I tried to run that but it keeps getting stuck. I might have to manually move files.
Sent from my ADR6300 using XDA App
Chances are if the unrEVOked tool isn't working, you may not have the right drivers installed. Check their wiki to make sure you do. Also, to get the nightly CM6 builds (when they resume, which will likely be shortly) you do have to buy the ROM manager premium license from the Market (which I recommend you do anyways as it goes to Koush who is the one responsible for developing CM6 for the DInc).
Here's the link to the wiki concerning the driver:
http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
Wow is this all I really nerd to do ? I already bought Rom manager, but clockwork isn't working. I guys updating the drivers will let me get clock work ? Do u run a custom Rom? Thanks!!!
This mod requires deodexed ROM so currently only made for SamSet.. If you have a deodexed ROM and need my assistant, please let me know
Strongly suggest you use ROM Manager by Clockworkmod to backup your ROM before doing anything
Thanks to brut.all, judison, Fightspit and setenza01 for this nice looking ROM
Instructions:
1) Download and install ROM
2) Use my zip as update.zip and flash in recovery
Download
For SamSet v1.6 ROM
Custom CSC for Singapore network users see here
This doesn't work. Applied the update fine, but when rebooted, black screen with a bunch of FC's. Had to restore. Was running ROM Samset 1.6 as recommended.
Did u use stock recovery or rom manager to flash?
Sent from my GT-I9000 using Tapatalk
First used rom manager and nothing happened. Then used stock recovery, applied, and when booted, got the FC's. I could see the percentage in the battery, but that's about it. The FC's would not let me do anything else. Any suggestions?
hmm.. i've tried it again and it works on mine. only difference is im using clockworkmod to flash (remember to mount /system first)
anyway, i've resigned so download again..
Just installed your Mod. Works fine on my Galaxy S.
Thanks a lot !
Thanks, nice work. I have searched such a mod.
raspdeep said:
hmm.. i've tried it again and it works on mine. only difference is im using clockworkmod to flash (remember to mount /system first)
anyway, i've resigned so download again..
Click to expand...
Click to collapse
Just tried it again, and seems to be working now. I applied update.zip from stock recovery and seemed to be fine. Thanks for the mod.
does this work on samset 2.0?
shaunm1989 said:
does this work on samset 2.0?
Click to expand...
Click to collapse
most likely not, jp2 is development firmware, i will make one but will not support it since i wont be using jp2 as my daily rom
installed, it works~ =)
does it look good?
the sceenie looks like the numbers are blurry ...
anyway to go back to stock samset battery if i dont like this one?
Could you make an update out of the images i have linked? it's a circle battery with % in it. also the charging got a few more images.
I can get the images into framework-res.apk with no problem but the problem i'm having is modding the two battery xml files and the packing the apk again to get it to work
i've already tried this:
http://forums.hardwarezone.com.sg/showthread.php?t=2812085&page=58
as it does not quite match the theme, i modded samset battery to fit the theme
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.
I am not sure where the fault lies, but I am having issues with ROM Manager and clockworkmod. They run fine and can be useful, but I find more often than not that I get errors when using them. I am thankful for the ability to flash RA from the manager because more often than not I end up switching.
My errors are:
Usually get the droid with the exclamation when trying to flash roms. I have tried via Warm Updater, ROM Manager and Clockwork Recovery. As soon as I flash RA, I am gold...
Today I tried to switch to Kings Unleashed R3 via ROM Manager and it got me stuck at splash screen... annoying but a backup is a savior!
For now I am going to stick to RA, but anyone else having these issues?
I had/have the same issues. Started out of nowhere. So, now I just d/l everything to my memory card and boot into recovery and manage everything manually. I also switched to RA, but, on my wife's EVO, it works fine. Very strange, but, that has always been one of the knocks on Clockwork Mod.
Personally, I've had no issues with clockworkmod. Its been very solid for me, but I have read many people who have had similar issues as you. I've also read that it doesn't do a very good job of whiping.
I dropped ROM Manager a LONG time ago. It's useless for my needs.
I'd rather use AR and flash anything in recovery
what version of cwm do you have installed?
newest rom manager also?
maybe there is a connection with the people having issues, I'm having no issues with 3.0.0.5 and newest rom manager
no issues With RA 2.3 gives you total control
Sent from my PC36100 using XDA Premium App
You are having issues because you are trying to load certain roms that use amend scripting which don't work with the 3.0+ recoveries of cwm. Try downgrading your recovery to an older recovery like 2.5 at the bottom of rom manager and give it a shot.
I have installed Android to NAND on a HD2 using the instructions here:
http://forum.xda-developers.com/showthread.php?t=905060
The ROM works and the phone works nicely as an Android phone, but I can't use ROM Manager. If I try to use ROM Manager to flash a different ROM it will download the file to flash and then restart the phone.
The phone will just boot as usual back into Android.
If I try going into MAGLDR and then into AD Recovery and Manually flashing the downloaded file it fails.
Is there some other setting I need here? Does ROM Manager work for other HD2's?
Thanks,
ANkh
I have the same problem. I installed Android (TyphooN CyanogenMod) on NAND with magldr and everything works pretty nice. When I go into ROM Manager, I can see the updates and even download them, but when I go to install, it just reboots the phone. I see others that have had success with the HD2 and Rom Manager on this forum. Any help will be greatly appreciated.
rom manager only works with clk bootloader, not with magldr.
^^^^^^^^^
True, ROM Manager needs cLK's Bootloader to work.
But cLK Lacks RMNET (you can call it stable data connection)
Yes ROM Manager only works with cLK, but just to add I use cLK and I use ROM manager at least three times or sometimes more a week.
Also I have been using cLK for several months now and I personally prefer it to MAGLDR< but that may not be the case for everyone else. I do admitt the data signal does suffer sometimes with it but the ability to use ROM Manager, charge my battery when off, and last but not lest being able to use \ADB fastboot commands is worth it to me.
Thanks for getting back to me guys.
I'll considering switching to cLK.
Thanks,
ANkh