so im trying to get MIUI on my evo, but when i flash it it sticks at the sprint bootloader. i got the rom from MIUI. anyone help?
Did you wipe everything before flashing? Have you tried other kernels?
i have wiped data and cache. and im sorry but im new at this, what is a kernel
first of all, try also wiping data ( i kno its hard, just back up with titanium backup), system, boot, and battery stats. that should boot right up.
Did you wipe dalvik? You need to wipe data/cache/dalvik when switching ROMs.
If you don't know what a kernel is then I HIGHLY suggest you spend a little time reading up on all this because that is Android 101. You should have known what a kernel is before attempting to flash anything. A kernel is basically the interface between the software and hardware of your phone. It has all the drivers and instructions that tell your hardware what to do. They are flashed the same way ROMs are flashed and can affect performance dramatically. Different kernels perform differently on different EVOs so you need to find one that works well for your device. Sometimes the kernels that come packaged with ROMs don't work well on some EVOs and can cause booting and performance problems.
Mas wipey before flashy! Wipe all data, save for sd card, twice before flashing this rom. The savaged kernel that comes with the rom is just fine. Also, I would avoid titanium backup like the plague, especially if you are going to use MIUI.
Swyped from my CM7 EvO
Related
At first I thought my issue was isolated to the 8.x snap kernels but now I am also having issues with KingX bfs 8 and netarchy's 4.1.9. I clear cache, and dalvik, flash the kernels and I either get a bootloop or the phone will load and just freeze after a minute or two. Flash an older kernel (kx bfs #6) and everything is fine again.
Is there something else I need to be doing aside from clearing cache and dalvik? What could be causing this?
hm i personally do not clear dalvik and cache when flashing kernels some roms i find i have problems when i do such as on Evio rom. you may try flashing the kernel with out wiping the data and see if it helps any.
also if you are using CM6 which i assume you are since you were using snap. not all kernels are compatible with CM since it is asop. this could also cause your boot loops. if it does not specifically say CM compatible i would assume it isnt.
lastly if you use setCPU make sure it is reconfigured to the new kernel. i normally get force close issues and not freezes but am trying to throw out anything can think of that might help.
The only kernels I tried with CM were the snap kernels. I gave up on CM and went back to Evio and tried the other kernels. I also delete SetCPU beforehand and reinstall it after the flash.
Gonna try flashing kx bfs 8 without clearing data....
EDIT: Still didn't work. It never gets past the "hTC EVO 4G" screen. Just hangs on it for a while and then reboots and repeats.
let us know i have the same problem flashing after clearing on evio. i believe it has to do with how the dalvik is moved to the cache partition so i never wipe when flashing kernel with it.
hopefully that works also the new evio 1.2 has king 8 presintalled
I noticed my phone acting a little funny with Kings #8, so I reverted back to #6 and my phone has been back to normal since doing so.
I'm going to flash VirusROM carbon as soon as he gets it up. It's packaged with #8 too so we will see what happens.
When I first flashed CM6 I repartitioned my SD card, maybe I need to do that again when going back to a sense rom/kernel? Going to clear everything in my phone and repartition SD card before I flash virusROM Carbon. Maybe that will clear it up.
Nope, that didn't work either.
Does anyone have any ideas why this is happening?
Could it be my recovery that's doing it? I'm using AmonRA.
Bump.
I just tried kingx bfs9 and once again- bootloops.
Does anyone have any ideas what could be causing this?? Please?
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
I have been rooted for awhile now, but I have held off from flashing a rom. I don't want to introduce any problems as things work good for the most part. I am interested in flashing though mainly for better battery life as I have read about from various roms and to remove CIQ and bloat.
I am rooted on stock rom, made a backup with CWM, and used Titianium backup for my apps. I have been reading up on flashing roms, and I am confused about the wipe. Do some roms require different wiping than others? Aren't there like three different types of wipe from CWM? Does wiping erase data on the internal SD card?
Any things I need to look out for that could cause issues? Any recommendations on which rom would be best to try out first? Thanks for any tips.
bigcletus said:
I have been rooted for awhile now, but I have held off from flashing a rom. I don't want to introduce any problems as things work good for the most part. I am interested in flashing though mainly for better battery life as I have read about from various roms and to remove CIQ and bloat.
I am rooted on stock rom, made a backup with CWM, and used Titianium backup for my apps. I have been reading up on flashing roms, and I am confused about the wipe. Do some roms require different wiping than others? Aren't there like three different types of wipe from CWM? Does wiping erase data on the internal SD card?
Any things I need to look out for that could cause issues? Any recommendations on which rom would be best to try out first? Thanks for any tips.
Click to expand...
Click to collapse
Some ROMs wipe during the install , some ROMs don't ..
At the very least you should wipe your Dalvik cache ...
You can wipe your cache if you like, if you wipe anything else, it is up to you or up to the ROM ..
Honestly , if you are installing a completely different ROM a full wipe is usually best, if upgrading the same ROM, usually a Dalvik wipe is all you need ...
Some people , me included, are on the brave side and only wipe the Dalvik and give the ROM a shot, usually though I end up doing a full wipe ..
A good tip is also to run the "Fix Permissions" under advanced in CWM after flashing a ROM/Theme/MOD ..
Just follow the instructoins the dev has given. I always wipe before installing a custom rom to avoid problems later.
Sent from my SGH-T989 using XDA App
badaphooko01 said:
Just follow the instructoins the dev has given. I always wipe before installing a custom rom to avoid problems later.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
DITTO!! ... I should have added this to my post, this should be your first choice ...
I tried to flash HONO Full Throttle V2, cleared cache, dalvik cache.
Now my phone keeps rebotting loopping. I tried to access ROM manager but it reboots before it can do it. I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Do i have to unbrick?
Any help is appreciated, thank you
When that happened to me, with a different ROM, I went ahead and pressed power again at that screen and it continued to CWM, didn't wipe/reset my phone.
neuty said:
I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Click to expand...
Click to collapse
That is what you are supposed to see. Press power button twice to "accept" the factory reset. It won't actually reset anything -- instead it will boot directly to CWM.
Oh, okay thanks so much RealyPssd and Drumist! Got a bit scared for a second there. Was able to flash back
Edit: I might have found the problem:
I tried installing HONO's P930 CM9 Kernel V5 and it did the same thing but worse, it didnt even let me past the CM boot guy.
Went through the same thing
I tried flashing HO!NO!'s CM9 Full Throttle this morning and went through the same thing. Sometimes it would boot into the OS, other times it wouldn't get past the CM9 guy, and even sometimes it wouldn't get past the HO!NO! logo. I even had a hard time getting into CWM via the factory hard reset method (I kept getting just a blank screen, but the phone was still on. I pressed the volume down button and that seemed to get it into CWM, although it could have just been a coincidence).
I tried re-flashing the ROM but still no change. So I then flashed CM9 RC-1 and haven't had an problems since.
From what I've read in the Full Throttle thread, the HO!NO!'s ROM already comes with HO!NO!'s kernel. I've also read that the instability is due to the undervolting that's taking place in the ROM (and I'd have to agree based on my experiences with overclocking).
If you really want CM9 go with the RC-1 (or even the nightly). I find it to be incredibly fast so far. Maybe HO!NO! can make a ROM compiled with the linaro toolchain that has a slightly less aggressive undervolting settings
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Wiped everything but had a backup
HO!NO! said:
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Click to expand...
Click to collapse
I was coming from a stock ROM that I had rooted with SuperOneClick, and installed CWM using Rom Manager from the market. When I went to install your ROM I first made a backup of the current ROM (i wanted to having something to fall back to). I did a wipe data/factory reset, wipe cache, wipe dalvik, then flashed your ROM. I also flashed gapps as well (could that have caused a problem?)
Does it sound like anything is off? I would really like to be running your Full Throttle ROM (it's the only reason why I tried to flash my phone in the first place)
Hello. My LGOG currently wont boot up. Its stuck at Updating Apps. That happened after flashing Viper 1.1 kernel and changing some freqs and voltages. I thought that re-flashing the same kernel would reset what I did and then boot up, but it didnt.
I did a nandroid backup but cant see how to restore it. So at this point, the only thing I think its factory reset, but thats the problem.
Im using stock rom (rooted and unlocked) and I paid a few bucks to get my data 3g working on this cellphone.
If I wipe everything, that configuration will get wiped too and I dont want that.
So I was wondering what would happens if I flash a new ROM, like Carbon 4.3.1, I was thinking on flashing with only wipe cache and dalvik, no factory reset or wipe system/data.
Will my LGOG work well? Will get stuck? Will be laggy after it?
Pros and Cons?
Thank you very much in advance for those who can give me a little insights on this one.