Develop Bugs

Heeeeelllllpppppp pppllleeeeaaassseee!!!!

so im a noob ive got an evo i just rooted a couple days ago everything was great i had netarchys 4.1.8 bfs kernel and baked snack flashed on it.....but then i tried flashing the beta 4.1.9 w/havs.....and now my phone is stuck at bootloader....i can still go into recovery but it just does the same thing and being the noob that i am i didnt do a nandroid back up.....heeellllppp pleeease!!!

I am Fully Rooted with Unrevoked 3.2 with nandroid backup. I just tried to install the Netarchy's 4.1.8 Kernel and I was stuck in the boot load up screen I think (white screen with HTC EVO4g) for awhile, so now I am restoring through a nandroid backup. Can i install just the 4.1.8 and no custom ROM?? Also which did you install first ROM or the Kernel? I was thinking of trying the DC 3.5 one, pretty new at all this.

eazyoutlaw said:
so im a noob ive got an evo i just rooted a couple days ago everything was great i had netarchys 4.1.8 bfs kernel and baked snack flashed on it.....but then i tried flashing the beta 4.1.9 w/havs.....and now my phone is stuck at bootloader....i can still go into recovery but it just does the same thing and being the noob that i am i didnt do a nandroid back up.....heeellllppp pleeease!!!
Click to expand...
Click to collapse
Try running this. I prefer the AmonRA. I am assuming you are S-OFF or nand unlocked
http://forum.xda-developers.com/showpost.php?p=8210546&postcount=1

i installed the kernel first netarchys 4.1.8 bfs and it was great then i installed baked snack rom and everything was perfect until i flashed netarchys 4.1.9w/havs......it said it was installed successfully but wen i boot up it cycles thru the roms start up screens.......i can still boot into recovery....

eazyoutlaw said:
i installed the kernel first netarchys 4.1.8 bfs and it was great then i installed baked snack rom and everything was perfect until i flashed netarchys 4.1.9w/havs......it said it was installed successfully but wen i boot up it cycles thru the roms start up screens.......i can still boot into recovery....
Click to expand...
Click to collapse
If you Amon or Clockwork recovery works, just reflash the rom you had on it from the flash from zip. Make sure you wipe

i tried it.....it says installation was aborted because it cant find update script...sorry im new to this....and im using ra recovery

Try going into the recovery screen wipe data and cache then reboot it should w
InfidelForLife said:
I am Fully Rooted with Unrevoked 3.2 with nandroid backup. I just tried to install the Netarchy's 4.1.8 Kernel and I was stuck in the boot load up screen I think (white screen with HTC EVO4g) for awhile, so now I am restoring through a nandroid backup. Can i install just the 4.1.8 and no custom ROM?? Also which did you install first ROM or the Kernel? I was thinking of trying the DC 3.5 one, pretty new at all this.
Click to expand...
Click to collapse
Go into recovery and wipe data and cache and then reboot. This happenned to me and I fixed it like that. Make sure the first thing you do when its fixed is make a backup it'll save you from pulling your hair out.

im trying to reinstall the romm now lets see.............booting up and.........its stuck at white black htc evo 4g screen now....

Use adb. Or does the recovery not offer usb toggle?
Sent from my PC36100 using XDA App

evohog said:
Try going into the recovery screen wipe data and cache then reboot it should w
Go into recovery and wipe data and cache and then reboot. This happenned to me and I fixed it like that. Make sure the first thing you do when its fixed is make a backup it'll save you from pulling your hair out.
Click to expand...
Click to collapse
Will this erase all my Previous Backups?? Or should I do a backup first then go into this and try install the Kernel?
eazyoutlaw said:
im trying to reinstall the romm now lets see.............booting up and.........its stuck at white black htc evo 4g screen now....
Click to expand...
Click to collapse
This is what's happeneing to me.

i just reinstalled my rom wiped cache and data now my phone is back from the dead!!! i really dont care if everything got erased as long as i can use my phone rite? thanks alot guys u guys r officially the best!!!

Glad to see it is back working! Do you know if I can install just a Kernel minus a ROM if I am rooted?

yes you can i did it.... but a costom rom i think is better

[Q] ClockworkMod Updated to 3.0.0.5

Hello all
I just updated to 3.0.0.5 and now when I reboot into revocery via Rom Manager I get to the HBOOT screen with the only options for:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I don't get the usual black background with green letters? From what I've read it should go to the black background but now with Orange letters?
Please advise at what I'm doing wrong. Which option should I use to get to clockworkmod 3.0.0.5
Thanks in advance
-g

A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.

patsfan1130 said:
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
Click to expand...
Click to collapse
The oldest version available is the current one I am on 3.0.0.5. There are newer version .6 .7 and .8? Do you know if those versions will produce the same issue?

After much reading this cwm3 is causing lots of problems. I've searched the forums for a write up on how to flash back to 2x but haven't found one. Does anyone have a quick write up to get this done either through fastboot or adb?
Thanks
-g

I have a thread in the dev forum updated today that explains exactly what you want.

I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?

tdiman said:
I have a thread in the dev forum updated today that explains exactly what you want.
Click to expand...
Click to collapse
Awesome tdiman! Thanks for the write up, it worked. I just needed to enable wipe!

sitrucz said:
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
Click to expand...
Click to collapse
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either

tdiman said:
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
Click to expand...
Click to collapse
First, thank you for your response. I'm not going to spend too much time on this since 3.x is the new standard. I use Cyanogenmod 7 dailys as my daily driver and rEVOlution 2.2 as my sense rom backup. So, if after a restore and rebooting and then wiping cache and davlik and possibly reflashing a froyo kernel, incredikernel 12/20, doesn't solve it I'll just restore from 2.x recovery, upgrade recovery, and then get a new backup. I'll do the same for Cyanogen and call it a day and start using cwm 3.x.
After testing I was unable to restore my rEVOlution rom using 3.0.0.8 from 2.5.1.2. I wiped cache and davlik and flashed a froyo kernel and still no dice. It was strange even though I could only see the boot logo the rom was fully booted as I had voicemails and I heard the voicemail notifications but the home screen never came up. I rebooted and still the same thing. So I reflashed 2.5.1.2 restored rEVOlution upgraded recovery then got a backup. I did the same for my Cyanogen nightly and I'm on 3.0.0.8 now for good. I wanted to pass this on to others. If I want to restore an older backup I'll just restore recovery to 2.5.1.2 and do a restore.

Can't flash a new rom

Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced

Hi bassjam
bassjam said:
Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced
Click to expand...
Click to collapse
What Rom is it you are trying to install?
Is there any error message showing when it stops?
At a guess It sounds as if you are trying to install a Corrupt Rom, you need to check the MD5 Checksum that come with the Rom to make sure they are not corrupt on download, before you try to install them.
What you need to do is download the Rom again, check it's Checksum With this MD5 Check 2.1 tool.
Then delete the bad Rom that on your SD Card, and replace with the new download [Checked with MD5 Check] Rom, and flash it.
Take Care
TheQuest

Agree with I'm TheQuest. That's maybe because of bad download. redownload back the rom and put back to your SD card. Do the nandroid restore (but if you dont have nandroid backup before, this also can be done by taking out your sdcard and put into your laptop/card reader).

Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?

Hi bassjam
bassjam said:
Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?
Click to expand...
Click to collapse
If you Change ROM's you are always advised to do a FULL WIPE.
Moving to Cynanogen RC4 from RC3 should not have caused your problem, but even when Updating a Rom you are advised to wipe the Cache Partition and the Dalvik Cache
Take Care
TheQuest

My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(

Hi bassjam
bassjam said:
My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(
Click to expand...
Click to collapse
Yes do a full wipe, it should help with the speed, good luck.
Let us know how you get on please?
Take Care
TheQuest

is the first time such a problem that happens
I had a htc magic, hero, desire and windows mobile phone before
with each phone, I had at less similar problem
for the first time, I wonder if this is not a hardware problem like writing speed of the processor...
for the moment i finished radio s-off, eng-off, and i put the recovery with fastboot( problem to get recovery with rom manager)
It's time to full wipe, about 30 minutes to wait if not more...
edit: full wipe ok after 15 min, i'm going to wipe with fastboot to be sur!?
redit edit: flash the phone with cyanogen rc4...
thx

something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx

Hi bassjam
bassjam said:
something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx
Click to expand...
Click to collapse
You should try to updating CWM to 3.0.0.6, and that should clear that. [hopefully ]
Take Care
TheQuest

amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)

Hi bassjam
bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
Click to expand...
Click to collapse
Glad to hear you have managed to get it fixed.
Take Care
TheQuest

bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)
Click to expand...
Click to collapse
Yes CWM 2.x can't write the ext4 partitions required by Gingerbread so you require cwm 3.x, you could have flashed this from Fastboot without first flashing a new ROM. If you didn't have CWM 3.x in the first place this was probably the source of your problems.

I don't believe it!
phone works during 5 five with cyanogen rom, I put the wifi on, and then bootloop( recognized problem on RC4)
i pull out the battery then restart the phone, and the phone has not started and the stay blocked to htc logo
PB: I have no recovery, impossible to to flash another rom. When I launch recovery, phone blocked on htc screen!
I tried to flash ruu 1.32 or 1.72 on fastboot mode... but phone still blocked on htc screen...
I don't know what to do
pls help
thx

[Q] Incredible 2 Bootloop and ROM Problems

Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:

DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison

chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:

chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.

U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app

I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.

Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.

gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.

Power down, pop the sd out, boot to recovery, rename file, profit.

gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.

digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol

almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks

I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.

[Q] MIUI for V One Help! (What in hells name am I doing wrong?!)

Hey there;
Firstly, thanks for your great efforts on the ports of your roms and consistent, useful forum help.
I appreciate that you probably get a load of these threads but I could really use some help with the installation of the ROM, as I've had a load of problems trying to install it.
I am attempting to install the MIUI rom (http://forum.xda-developers.com/showthread.php?t=1797515), and I am coming from the original software that comes with the device.
I have an unrooted One V, coming from the base OS and kernel. Currently, I can't get past the Jellybean Android screen (getting stuck on starting apps), and usually I can't even get past the MIUI screen at all. Here are the steps I've taken;
- I downloaded this kernel: boot-TK-USB-201302150054 from this thread: http://forum.xda-developers.com/show....php?t=1765687 and flashed it in fastboot, twice.
- Then launch into recovery, follow the instructions on your thread (format all apart from SD), and go ahead and install the .zip.
- Clear Delvik, clear Battery and Fix permissions, then proceed to reboot in an attempt to get in. At this point it hangs on MIUI screen for up to 5 minutes.
- I then try re-flashing the kernel in fastboot again. Still no help.
- I then try and reinstall the .zip from the SD card, and still no improvement.
I imagine I'm doing something very wrong, but I can't work out what it is and it's driving me crazy.
Can you help?!
Thanks in advance, Reasoner.

you are installing an older rom version which has no support..and is old

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Any chance you good point me in the right direction for an newer version?
Also, am I doing all the steps right?

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.

Reasoner said:
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Click to expand...
Click to collapse
Ignore this, tried again and got through! Thanks a bunch!