Hi!
This is my first time posting, but I have been using MIUI for about 6 months now. Its phenomenal. I recently updated to MIUI 1.5.6 on My EVO 4G. Ever since I did it The battery drains extremely fast compared to the previous version of MIUI i was using which was 1.4.3, I think.
The camera is also not working, it just goes to a black screen and then force closes.
I tries to change the kernel to Tiamat 4.0.1 and 4.0.2 but it fails each time I try to do it. I have tried other kernels including 2.6.35.8-bcblend-CFS-sim_io-classRCU, which may not be for gingerbread. Nothing works. I currently have 2.6.37.6-cyanogenmod-01493-g70877de Kernel installed and I need help getting a new one on here.
The phone burns through so much power now its insane. I used to get at least 14 hours out of it. Now, I had it fully charged about 20 minutes ago and its already down to 88%. Can anyone help?
Sorry if this is the wrong format or whatever:
Specs:
EVO 4G
Model: PC36100
Android Version: 2.3.4
Baseband Version: 2.15.00.11.19
Build: MIUI 1.5.6
I am almost a complete novice when it comes to this, so any help would be appreciated but if you could give explicit instructions on how to do everything that would be amazing.
Thanks!
Are you wiping cache and dalvik before flashing the new kernal?
Yeah, I reloaded MIUI after doing a format all and nothing changed. It still wouldn't let me flash the new kernel.
Use juicedefender beta for battery, use the camera fix from the miui.us forums (camera is a known issue, I had it at first, applied fix and all was fine) and flash a tiamat kernel manually through recovery, not kernel manager as for some reason kernel manager seems to screw up for me when flashing tiamat kernels.
edit: heres a link to the fix.
http://forums.miui.us/showthread.php?236-If-you-re-having-issues-with-your-camera-on-1.5.6
Also, I could be wrong but I believe some of the recent updates came stock with cm kernel, so flashing tiamat could also greatly help with battery. Try Tiamat 3.3.7 if youre having problems with newer releases as 3.3.7 seems to be the most stable.
I am flashing the kernel through recovery. Thats the only way I know how to do it. It always worked fine before and only now is it being problematic. I will try the defender app and see if I can find the camera fix. Thanks!
Jasonectomy said:
I am flashing the kernel through recovery. Thats the only way I know how to do it. It always worked fine before and only now is it being problematic. I will try the defender app and see if I can find the camera fix. Thanks!
Click to expand...
Click to collapse
Posted the link for the camera fix! and what do you mean your having a problem flashing kernels? Your still s-off correct? And make sure when you are transferring kernels to sdcard you unmount sdcard when done, some of the newer kernels have problems with transfering data to sdcard quickly, and when you unmount or eject your card it insures the transfer is successful instead off cutting it off half way through.
I noticed the link for the camera fix, Thank you so much! I an going into recovery and when I flash Tiamat 4.0.1 or 4.0.2 I get:
E:Wrong digest:
system/lib/modules/sequans_sdio.ko
E: Verification Failed
Zip Verification Failed!
Zip isn't signed correctly!
Installation aborted
I'll try 3.3.7 and see if that will install. Thanks again.
Try Kernal manager lite. It flashes the kernel for you. Battery drain is expected when switching Kernals. Wipe battery stats and give 3 days for Kernal to settle in.
Sent from my PC36100 using XDA Premium App
Jasonectomy said:
I noticed the link for the camera fix, Thank you so much! I an going into recovery and when I flash Tiamat 4.0.1 or 4.0.2 I get:
E:Wrong digest:
system/lib/modules/sequans_sdio.ko
E: Verification Failed
Zip Verification Failed!
Zip isn't signed correctly!
Installation aborted
I'll try 3.3.7 and see if that will install. Thanks again.
Click to expand...
Click to collapse
Usually mismatched libs mean youre using the wrong kernel. Cayniarb puts out multiple versions of tiamat for multiple devices. Make sure you downloaded the one for the evo (should say evo in file name) and not the one for the incredible, xoom, etc.
njonas01 said:
Try Kernal manager lite. It flashes the kernel for you. Battery drain is expected when switching Kernals. Wipe battery stats and give 3 days for Kernal to settle in.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Like I said, I recommend not using kernel manager lite for flashing Tiamat as I've had some problems flashing tiamat through kernel manager, most other kernels seem to be fine for me? Odd but it is the case. Although kernel manager would be good for downloading the kernels since it automatically picks out your device and you can be sure you download the correct kernel.
Thank you! Kernel Manager Lite seems to have worked! I'll see how the battery problems go after this flash.
The camera is the only problem left, and I can't apply the fix, I can't seem to find the /system folder...
You need to use root explorer as astro file manager and other basic file managers dont have the elevated privileges to view /system. The app is a couple of dollars but I HIGHLY recommend it to any and every rooted phone user.
MIUI 1.5.6
I downloaded and redownloaded the rom twice and flashed it twice, did the wipe/factory data reset and calkulin wipe and both times it would install different things for the rom, like the first time it didn't install Gmail or market den the next time it only installed market and settings and 3 or 4 other apps and thats it, and when i try sending a text, i choose a person and type the message, when i hit send it says, no valid user, message can't be sent, will someone please respond and let me know whats wrong? I would really appreciate it, my brain is going in all different directions, i hope you can understand what im typing because im very confused right now
Thanks,
Tj
Related
Hello all,
I followed the guide to root my phone that was titled "Idiot proof root quide" that can be found on the androidforums. I then installed fresh 0.3 and I've been running that for a while and had no desire to flash the new fresh roms. Well, now that fresh has released a ROM with froyo at its base I've decided to make the jump.
Yesterday I downloaded and installed the latest rom from fresh (3.1.0.1) but I was unaware that there were new radio updates and kernals to install. This is where I'm running into trouble. For some reason when I have 3.1.0.1 installed my phone wont stay connected to the computer. Once I plug the USB cord in it will ask me if I wan't to charge, disk drive, etc but then 2 seconds later it will disconnect. I've gone back to fresh 0.3 and it works fine.
SO, my questions are:
1. How do I install the latest radio for fresh (please help me with links, I've looked but have become easily frustrated)
2. How do I install the latest kernal with Amon Ra flash (it is my understanding that you need this to install the newest radio/kernal). I understand I need fastbook and the android SDK but I don't think I'm setting these two applications up correctly when I download them.
If you can direct me to any threads that will assist me I will greatly appreciate it.
Thanks!
another way you can try is putting the radios on before you flash the rom to fresh3. I would flash using AMon Ra just because there have been reports of clockwork not fully clearing cache/dalvik. The best way to do this in my opinion is if you have rom manager installed at the bottom you will find flash alternate recovery, use that then try clearing wiping everything and reflashing. If you put the radios on your sd card first jsut boot into froyo once then power down flash radio boot, power down flash wimax. boot.
then try and see if you usb is still having problems. If it is let us know.
Download the radios and kernels you want with your phone, then reboot into recovery. All of them flash like ROMs, just select the zip you want and flash it. Just don't wipe first.
I think the order would be kernel first, then radio, then WiMax if necessary. Always reboot at least between radio and WiMax, maybe after kernel as well.
RyboCollier said:
Hello all,
I followed the guide to root my phone that was titled "Idiot proof root quide" that can be found on the androidforums. I then installed fresh 0.3 and I've been running that for a while and had no desire to flash the new fresh roms. Well, now that fresh has released a ROM with froyo at its base I've decided to make the jump.
Yesterday I downloaded and installed the latest rom from fresh (3.1.0.1) but I was unaware that there were new radio updates and kernals to install. This is where I'm running into trouble. For some reason when I have 3.1.0.1 installed my phone wont stay connected to the computer. Once I plug the USB cord in it will ask me if I wan't to charge, disk drive, etc but then 2 seconds later it will disconnect so I went back to fresh 0.3 and it works fine.
SO, my questions are:
1. How do I install the latest radio for fresh (please help me with links, I've looked but have become easily frustrated)
2. How do I install the latest kernal with Amon Ra flash (it is my understanding that you need this to install the newest radio/kernal).
If you can direct me to any threads that will assist me I will greatly appreciate it.
Thanks!
Click to expand...
Click to collapse
New Radio: http://geekfor.me/evo/radio/baseband-215000728/
New Wimax Radio: http://geekfor.me/evo/radio/wimax-26023r01/
No need a custom Kernel for now, the ROM has its own, if you want a Kernel anyways you can flash Netarchy's Revision 3.7.6c - Froyoized but it has a side effects with the camera pixels!
SilverZero said:
Download the radios and kernels you want with your phone, then reboot into recovery. All of them flash like ROMs, just select the zip you want and flash it. Just don't wipe first.
I think the order would be kernel first, then radio, then WiMax if necessary. Always reboot at least between radio and WiMax, maybe after kernel as well.
Click to expand...
Click to collapse
3 out of 5? lol
Wow, thank you for the quick responses guys/gals! So it seems that I was making this more difficult than it needs to be.
Summary of what I need to do:
1. Flash new kernel if I choose to but each ROM comes with a custom kernel.
2. Flash new radio update.
3. Flash Wimax update.
4. Flash fresh 3.1.0.1
Now, I hope this also solves my USB issue that I'm having which only occurs when I have 3.1.0.1 flashed. I'm going to take omegasun18's advice and see if that will correct my issue.
RyboCollier said:
Wow, thank you for the quick responses guys/gals! So it seems that I was making this more difficult than it needs to be.
Summary of what I need to do:
1. Flash new kernel if I choose to but each ROM comes with a custom kernel.
2. Flash new radio update.
3. Flash Wimax update.
4. Flash fresh 3.1.0.1
Now, I hope this also solves my USB issue that I'm having which only occurs when I have 3.1.0.1 flashed. I'm going to take omegasun18's advice and see if that will correct my issue.
Click to expand...
Click to collapse
well i would do it ......
Fresh rom + radio, the reboot, wimax, then reboot again, then kernel, that's waht i did and have everything working no 30fps cap, wi fi tether and all the stuff (remember about the camera issue)
*edit* remember something, you have to left the custom kernel to the end, because as i told you before the rom has its own kernel and will overwrite any other you installed previously
So leave the kernel to the end? Does that kernel you recommended remove the 30fps cap?
yep make sure if you do a kernal you do it AFTER the rom. the radios shouldnt matteer since msot roms dont acctually change the radios when flashed. but i normaly start with the rom and work my way up but otherwise you have it.
RyboCollier said:
So leave the kernel to the end? Does that kernel you recommended remove the 30fps cap?
Click to expand...
Click to collapse
Well..................
I keep running into an issue where my contacts keep crashing when I open the people application or try to send a text message. Any idea as to why this might be happening?
RyboCollier said:
I keep running into an issue where my contacts keep crashing when I open the people application or try to send a text message. Any idea as to why this might be happening?
Click to expand...
Click to collapse
What rom? did you wipe?
I got the following message attempting to update my radio version to 2.15:
Amend Scripting (update-script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Pleases switch to Edify scripting (updater-script and update-binary) to create working up zip packages.
Installation aborted.
I am very sorry for bring up dead horse type topics, but all the research I try and do leads to circles for me. I'm as experienced with all of this (hopefully someday).
I tried to follow the instructions from
wiki.cyanogenmod.com/index.php?title=HTC_Evo_4G:_Full_Update_Guide
Is there another way to trick this update into installing maybe?
I used RomManager v3.0.1.1 and used Install ROM from SD Card. It probably flashed the message I got above but I wasn't able to see it.
I used Recovery mode and tried to do it manually, which is where I was able to see the error message..
I have an eery feeling I should be using Amon Ra vs. ClockworkMod ??
thank you!
EricFi said:
I got the following message attempting to update my radio version to 2.15:
Amend Scripting (update-script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Pleases switch to Edify scripting (updater-script and update-binary) to create working up zip packages.
Installation aborted.
I am very sorry for bring up dead horse type topics, but all the research I try and do leads to circles for me. I'm as experienced with all of this (hopefully someday).
I tried to follow the instructions from
wiki.cyanogenmod.com/index.php?title=HTC_Evo_4G:_Full_Update_Guide
Is there another way to trick this update into installing maybe?
I used RomManager v3.0.1.1 and used Install ROM from SD Card. It probably flashed the message I got above but I wasn't able to see it.
I used Recovery mode and tried to do it manually, which is where I was able to see the error message..
I have an eery feeling I should be using Amon Ra vs. ClockworkMod ??
thank you!
Click to expand...
Click to collapse
I agree that you should be using Amon Ra recovery. I would change to Amon Ra, and then try flashing the radios. That shouldn't give you any troubles. I'll attatch a PC36IMG of Amon Ra. Download it, be sure it is named PC36IMG, and put it on the main directory of your sd card. Boot into the bootloader, wait for it to scan and then ask you to update. Select volume up to accept the update. It will then flash Amon Ra V2.3. Once it's done, boot into recovery. It should now be Amon Ra Supersonic V2.3. Try flashing the radio update again, and it should work now
Thank You very much for the help!
It worked perfectly!
And.. I see Nandroid now!
The radio update took affect after the reboot and hopefully I'll see some results from it.
Now to get the nerve up to put a ROM and kernal on, although I don't know if I need a new kernal, but the update guide I looked at said the cyanogen rom should be installed with the Toast kernal.. so I suppose I'll do that too since it's seems to be what everyone else has been doing too..
Thank you again for the help/advice..
Hope one day I'll b
EricFi said:
Thank You very much for the help!
It worked perfectly!
And.. I see Nandroid now!
The radio update took affect after the reboot and hopefully I'll see some results from it.
Now to get the nerve up to put a ROM and kernal on, although I don't know if I need a new kernal, but the update guide I looked at said the cyanogen rom should be installed with the Toast kernal.. so I suppose I'll do that too since it's seems to be what everyone else has been doing too..
Thank you again for the help/advice..
Hope one day I'll b
Click to expand...
Click to collapse
Your welcome. I'm glad it worked out well. And you should have no trouble flashing roms, as the radio flash is far more 'dangerous' than flashing roms or kernels! Just be sure to make a nandroid backup of your stable system before changing roms or kernels. And wipe data, cache, and dalvik before a rom flash. Wipe just cache and davlik for a kernel flash. You'll be all set.
Sent from my PC36100 using XDA App
kernels
Last question, hopefully..
I've been reading up on whether or not to install a kernal after the rom.
I decided I'm going to try the MikFroyo4.5 Rom or cyanogen 6
It seems there's a debate as to whether or not an updated kernel is needed.
I decided on: netarchy 4.3.1-cfs-havs-nosbc
My big question.. Do I really need to do this?
I did a Nand Backup and it went well.
I'm going to do another in the morning because I'm paranoid, and clear off the backup files from my SD to my local hard drive, and make a list of the apps I have on it.. although I uninstalled quite a few just because.
I tried Titanium backup and it's installed, but the icon doesn't show.
So it sounds to me like my 2.1 is ready for retirement!
The most confusing part is to me is the kernel's.. I must have blinders on, I can't really find a real reason to update them aside from possibly more battery life or a speed enhancement?
If my 4G breaks.. it was meant to be!
Thank you!
EricFi said:
Last question, hopefully..
I've been reading up on whether or not to install a kernal after the rom.
I decided I'm going to try the MikFroyo4.5 Rom or cyanogen 6
It seems there's a debate as to whether or not an updated kernel is needed.
I decided on: netarchy 4.3.1-cfs-havs-nosbc
My big question.. Do I really need to do this?
I did a Nand Backup and it went well.
I'm going to do another in the morning because I'm paranoid, and clear off the backup files from my SD to my local hard drive, and make a list of the apps I have on it.. although I uninstalled quite a few just because.
I tried Titanium backup and it's installed, but the icon doesn't show.
So it sounds to me like my 2.1 is ready for retirement!
The most confusing part is to me is the kernel's.. I must have blinders on, I can't really find a real reason to update them aside from possibly more battery life or a speed enhancement?
If my 4G breaks.. it was meant to be!
Thank you!
Click to expand...
Click to collapse
You don't have to change kernel if you don't want to, but there's really no reason not to, as long as you have a solid nandroid backup to go back to. Roms come with a kernel cooked into it already, so its not required that you change it You always have the option change kernels, and there are various reasons to change them. Every phone may run differently on the same kernel . The kernel that comes baked into a rom may be great for one guy, but horrible on your phone. It takes a bit of playing around to find out which kernels are best for your phone. You may notice that with some kernels, your battery life is garbage, or the phone lags, or you get random reboots etc. Others you'll find perform great and have great battery life. A kernel that runs good on one rom may or may not run good on a different rom. There are a lot of variables, and as I said, you need to find out which ones work good for you, by trying them out. And be sure to use sense kernels on sense, and aosp kernels on aosp (goes without saying, but I've seen people make that mistake)
Sent from my PC36100 using XDA App
Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity
Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App
Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.
Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.
onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.
OK my Epic with Viper 5.0 will not flash Rodderick's Genocide Kernel. I was able to zip install on CW 2. whatever, with viper running and saw a huge difference in batt life over just the rom.Now that I have switched to EXT4 and CW 3.0 I get install aborted over and over. Could this be because the rom already has the kernel built in the rom and installed in or am I doing or missing something in the wrong?
My main reason for asking this is back when I was on RFS I did not have a problem with flashing any kernel and getting at the very least with heavy use a good day and a half of up time on the batt. Now its 3/4 if not less with heavy use on my current config.
It almost sounds like the zip u downloaded is not for CWM 3.x. But I know for a fact I installed Genocide using CWM 3.x so it should exist. Have you tried redownloading it? Maybe its messed up.?
Sent from my SPH-D700 using XDA App
I have tired another dl but still the same result. What gives. I guess its the matter of it the rom comes with the kernel that could be causing the issue too right?
Hi everyone, newbie to Android here looking for a bit of help. I took the time to sift through the forums and do my own research before posting and didn't find anything similar so here goes.
I flashed my Motorola Defy running stock Froyo 2.2.1 to CM7 using Defy Clockworkmod Recovery which I got from this site (link: http://forum.xda-developers.com/showthread.php?t=875233). No major issues except for the learning curve one has to go through when using Android for the first time, did take a lot of reading though. After flashing I noticed that I no longer picked up a cell signal, attempted to flash back to Froyo which, as far as I understood, was possible if you did your flashing through CWM. Anyway, after doing the factory/cache wipe and rebooting my phone freezes at the CM7 "Google" logo which comes up on boot. Attempted wipe several times, same result.
I tried flashing with RSD Lite 5.7 but after unzipping the CM7 file I get an error message regarding an XML file. The machine I'm running RSD on is Windows Vista and apparently there are some compatibility issues. Is my only solution running a Windows XP VM and attempting to flash from there?
Thanks in advance for your assistance.
Do you still have bootmenu and CWM on your phone? if so just install CM7. If you are able to install and boot into CM7, just keep it. No need to go back to stock froyo. You should use baseband switcher (http://forum.xda-developers.com/showthread.php?t=1052745) and switch to the correct depending on your region. This should pick the phone and data signal.
I too have vista with 32bit and had no issues using RSDLite, couple of folks have reported compatability issues but do not know. You can as well use XP if possible to flash back to froyo. Please charge the battery to sufficient say more than 70% and start flash.
premaca said:
Do you still have bootmenu and CWM on your phone? if so just install CM7. If you are able to install and boot into CM7, just keep it. No need to go back to stock froyo. You should use baseband switcher (http://forum.xda-developers.com/showthread.php?t=1052745) and switch to the correct depending on your region. This should pick the phone and data signal.
I too have vista with 32bit and had no issues using RSDLite, couple of folks have reported compatability issues but do not know. You can as well use XP if possible to flash back to froyo. Please charge the battery to sufficient say more than 70% and start flash.
Click to expand...
Click to collapse
I do have bootmenu, after flashing CM7 the CWM was no longer on my installed apps, tried to get it from market but that as well as other google apps were missing, unfortunately I attempted to go back to Froyo before flashing the google apps pack from what I understand flashing through bootmenu is done using RSD, correct? Thanks for the link to baseband switcher, Ill give it a try as soon as my phone is back up and running
metal_militia84 said:
I do have bootmenu, after flashing CM7 the CWM was no longer on my installed apps, tried to get it from market but that as well as other google apps were missing, unfortunately I attempted to go back to Froyo before flashing the google apps pack from what I understand flashing through bootmenu is done using RSD, correct? Thanks for the link to baseband switcher, Ill give it a try as soon as my phone is back up and running
Click to expand...
Click to collapse
as far as i understand if you just have bootmenu and can install CM7 then just download the google pack and then go back into boot menu and install the google pack then you should be good to go again.
sorry if i have mis-understood.
cheers
metal_militia84 said:
I do have bootmenu, after flashing CM7 the CWM was no longer on my installed apps, tried to get it from market but that as well as other google apps were missing, unfortunately I attempted to go back to Froyo before flashing the google apps pack from what I understand flashing through bootmenu is done using RSD, correct? Thanks for the link to baseband switcher, Ill give it a try as soon as my phone is back up and running
Click to expand...
Click to collapse
Don't worry is so hard to brick a defy read this thread, you will find so many answers and save time and headache http://forum.xda-developers.com/showthread.php?t=1216982
Just do simple things
Power on + volume down
+ volume up n down both thn u will see stock recovery wipe data factory n cache both n reboot
Viola ur Ph will start again
Sent from my MB525 using xda premium