Hello, since i want to get miui on my huawei ascend p6, i have tryed to flash 4 diffrent roms, but they all get stuck on "huawei ascend" logo, and pretty much keep staying there. Im running omni kitkat, with tmrp recovery. And i have no clue what to do.
kamphoz said:
Hello, since i want to get miui on my huawei ascend p6, i have tryed to flash 4 diffrent roms, but they all get stuck on "huawei ascend" logo, and pretty much keep staying there. Im running omni kitkat, with tmrp recovery. And i have no clue what to do.
Click to expand...
Click to collapse
I was having problems flashing MIUI due to inconsistent "how to flash" here on the forum.
Then I followed this and it never fails
Boot into TWRP
1. Wipe data
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Wipe custom
Flash MIUI
This seems to work every time for me.
iwtfmcl said:
I was having problems flashing MIUI due to inconsistent "how to flash" here on the forum.
Then I followed this and it never fails
Boot into TWRP
1. Wipe data
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Wipe custom
Flash MIUI
This seems to work every time for me.
Click to expand...
Click to collapse
What MIUI should i flash? is there a speciel one?
iwtfmcl said:
I was having problems flashing MIUI due to inconsistent "how to flash" here on the forum.
Then I followed this and it never fails
Boot into TWRP
1. Wipe data
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Wipe custom
Flash MIUI
This seems to work every time for me.
Click to expand...
Click to collapse
Can't get it to work.
Related
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Zepius said:
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Click to expand...
Click to collapse
Guess I might as well wipe the cache and dalvik even on a dirty flash?
Thanks
I upgraded from CM10 M1 to M2 with only a wipe of Dalvik cache. Works fine.
I finished installing M2 after wiping both the cache and dalvik cache (figured I would do the cache just in case).
Worked great!
Thanks all
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
***what Nexus version do you have?*** i've used the below instructions with GSM GNex***
If you're coming from an AOSP CM9 rom, Do the following :
Download Maguro (or your models ROM+Gappsl).
- boot into recovery.
- Preform NANDroid Backup.
- Wipe Dalvik cache.
- Wipe Factory reset.
- Wipe Cache.
- install zip from SDcard>choose zip from SDcard>ROM.zip (your ROM)
- Flash Gapps.zip
- Flash kernel.zip (if you have one)
- go to Advanced> Fix Permissions
- Reboot system now !
- Enjoy.
***I've used this method for a trillion flashes !***
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
bk201doesntexist said:
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
Click to expand...
Click to collapse
+1
Hi All,
Seem to have a slight problem with flashing Custom Roms onto my GNex at the moment. Not too sure what's causing it to freeze when booting up. All I get is the X logo and will stay there until the battery dies.
I'm able to revert back to a Google rom and regain use of my phone. Just can't seem to flash any custom roms at all. It's happened with CM10.1, CM10, XenonHD Stable-2.0, Minoco.
I've attempted to flash with CWM and TWRP. Both get the same results. Prior to flashing I've whiped both the Cache and Davlik.
I have previously used CM9 and older versions of Minoco on this device. So seems odd that this is happening now.
Any advise or ideas towards what I should look at would be appreciated.
Thanks,
Drav
you have wipe data before flashing different roms... dirty flashing(only wipe cahce and dalvik) is only if you are updating the same rom.. this is how i normally flash ALL roms
1. wipe data/factory reset
2. wipe system
3. wipe cache
4. wipe dalvik cache
5. flash rom
6. flash gapps
7. reboot
8. wait 10 mins then do another reboot
9. enjoy
PS- the 10 min wait and reboot is soemthing i do that IMO lets the new rom settle
Thanks k786,
It's booted up in a custom rom now after following those step by step. Much appreciated! :good:
Cheers,
Drav
hi,everyone.
i've just tried to install cm11 in my galaxy nexus and it cannot boot on now
its installation is fail because status 7 in the cwm recovery
i still cant boot on my phone
can anyone help me
What version of CWM Recovery are you on? An update of the recovery to a newer build might help.
Break me off a piece of that Kit-Kat ROM!
What version of Android are you coming from? Anytime you are switching to a different ROM, especially from a JellyBean (4.3 or other) to a KitKat 4.4 ROM, you must do a clean wipe of your phone prior to installation. It sounds like you tried to do a dirty flash. Boot into recovery, and format data, cache, and dalvik cache, then try flashing the CM11 and Gapps.
If that doesn't work...try this thread. http://forum.xda-developers.com/showthread.php?t=2302599
tonykunyin said:
hi,everyone.
i've just tried to install cm11 in my galaxy nexus and it cannot boot on now
its installation is fail because status 7 in the cwm recovery
i still cant boot on my phone
can anyone help me
Click to expand...
Click to collapse
dwoods1983 said:
What version of Android are you coming from? Anytime you are switching to a different ROM, especially from a JellyBean (4.3 or other) to a KitKat 4.4 ROM, you must do a clean wipe of your phone prior to installation. It sounds like you tried to do a dirty flash. Boot into recovery, and format data, cache, and dalvik cache, then try flashing the CM11 and Gapps.
If that doesn't work...try this thread. http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
i am coming from the stock android 4.3 rom. I've tried wipe the data,wipe cache and dalvik cache.However,it just keeps saying installation error in the cwm touch recovery because of the status 7.
That method doesnt work for me. i still even cannot boot on my phone.how can i send it in again
OK, first you need to manually boot into your recovery by holding the volume up and down buttons at the same time and then pressing the power button. You should get into your bootloader and then be able choose recovery. I assume you have a backup...so just flash back to your stock android 4.3. Then once you are able to get back into your phone see if you can update your cwm. If updating you cwm turns out not to be the issue then go watch a YouTube video on how to fix the status 7 error. It basically involves copying the zip file you are trying to flash over to your computer and editing one of the files. Goodluck...let me know if this works.
tonykunyin said:
i am coming from the stock android 4.3 rom. I've tried wipe the data,wipe cache and dalvik cache.However,it just keeps saying installation error in the cwm touch recovery because of the status 7.
That method doesnt work for me. i still even cannot boot on my phone.how can i send it in again
Click to expand...
Click to collapse
check your baseband..you should be in the latest radio..mine is XXLH1..other rom required latest baseband..
Pretty sure it sounds like he is on an outdated version of cwm, status 7 errors can be signs of old recovery version. Fastboot flash the latest cwm.
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha
anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks
Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.
Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help
Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm