[Q] Tried to flash new rom, red exclamation mark - HTC One X

Hi. I flashed my one x to a touchwiz cm9 which worked great. Then I decided to try out cm9 and it wouldn't boot into cyanogenmod. So I tried to go into recovery but it comes up with the red exclamation point. Could I have some help please, I'm in way over my head :/

yosh89 said:
Hi. I flashed my one x to a touchwiz cm9 which worked great. Then I decided to try out cm9 and it wouldn't boot into cyanogenmod. So I tried to go into recovery but it comes up with the red exclamation point. Could I have some help please, I'm in way over my head :/
Click to expand...
Click to collapse
I'm no expert, but I think that means you have somehow gotten rid of CWM..
Re-flash it again through fastboot. Use this version.
Edit: Also, before trying out any new ROMs (maybe this doesn't apply to those using the Aroma installer, but I do it anyway just to be safe), go into fastboot and do in cmd:
Code:
fastboot erase cache
Then go into CWM and factory reset, wipe cache partition and then advanced -> wipe dalvik cache.
Then you can go ahead and install the ROM.

Try erase cache in fastboot. Do you use the stock kernel? Domination mod (cm9 based) has a problem with Franco kernel. There you need to flash faux or stock.
Gesendet von meinem HTC One X mit Tapatalk 2

Northantrim said:
I'm no expert, but I think that means you have somehow gotten rid of CWM..
Re-flash it again through fastboot. Use this version.
Edit: Also, before trying out any new ROMs (maybe this doesn't apply to those using the Aroma installer, but I do it anyway just to be safe), go into fastboot and do in cmd:
Code:
fastboot erase cache
Then go into CWM and factory reset, wipe cache partition and then advanced -> wipe dalvik cache.
Then you can go ahead and install the ROM.
Click to expand...
Click to collapse
Oh thank you so much! That worked great. I had to flash the CWMR first and after I installed CM9 from zip, I flashed the boot.img from the CM9 zip and it booted straight in.
Thank you

yosh89 said:
Oh thank you so much! That worked great. I had to flash the CWMR first and after I installed CM9 from zip, I flashed the boot.img from the CM9 zip and it booted straight in.
Thank you
Click to expand...
Click to collapse
Glad it works

Related

[Q] <URGENT> Phone Dead! :'(

Hey guyz!
Well, Here's my story
I unlocked the bootloader of my Arc..... Flashed the 0.42 rooted .ftf file and well I had my arc.
I took backup of all my stuff and thought of installing CM7.
So well, I downloaded the latest CM7 Mod from the website stable one and fastboot'd (or whatever the language is) the boot.img into my arc.
And den I booted my phone into recovery mode, wiped my cache, system and data and flashed the update_cm7.1.zip file into it.
Not my phone after booting up dosent work. It shows the lock screen and within a second boots again :'(
I searched and found that I did not install the CWM Recovery and guessed that it was crucial for it.
Now I have a dead phone.
Can you Pleaaaaaaaase Help Me out!
My mobile is my life and my parents will kill me
Thanks Alot!
Install doom kernel via fastboot
Enviado desde mi LT18i usando Tapatalk
Done Doom Kerenal
Still going into Infinite BootLoop!!
you usually wipe everything(user data, cache, dalvik cache) after flashing the ROM
or try repeating the whole process
- flash .42 ftf file using flashtool 0.6.7 then disconnect device
- fastboot flash boot boot.img(from the CM7 package) then disconnect device
- power-on and go to recovery then flash the CM7 ROM then GAPPS
- wipe user data, cache and dalvik cache
- reboot
I suggest you also try FXP105 package here in XDA, I think it's more updated than the one from official CM7 site
terranox said:
Install doom kernel via fastboot
Enviado desde mi LT18i usando Tapatalk
Click to expand...
Click to collapse
What are you talking about?
DooMKernel is for stock based ROMs, not for CM.
I'd recommend to you to check out FXP's CM7, it's way better and stable, imo.
Rycon33 said:
you usually wipe everything(user data, cache, dalvik cache) after flashing the ROM
or try repeating the whole process
- flash .42 ftf file using flashtool 0.6.7 then disconnect device
- fastboot flash boot boot.img(from the CM7 package) then disconnect device
- power-on and go to recovery then flash the CM7 ROM then GAPPS
- wipe user data, cache and dalvik cache
- reboot
I suggest you also try FXP105 package here in XDA, I think it's more updated than the one from official CM7 site
Click to expand...
Click to collapse
Ill Try!
Thanks Alot!
Whats GAPPS?
And Dalvik cache? How can I clear it
SS4Serebii said:
Ill Try
Whats GAPPS?
And Dalvik cache?
Click to expand...
Click to collapse
Go here.
And dalvik cache is under advanced options in CWM.
Ok, Followed your steps but going into infinite boot loop :'(
Will try for CM7.2.0 - FXP10
SS4Serebii said:
Ok, Followed your steps but going into infinite boot loop :'(
Will try for CM7.2.0 - FXP10
Click to expand...
Click to collapse
Do that and follow these steps:
dp94 said:
Connect your device with your current ROM to a PC.
Put the ROM (*.zip file) on your sdcard.
Shutdown device.
Connect your device with fastboot mode (pressing menu button) to a PC.
Go to your fastboot folder.
Press shift key, right click and select "Open command window here".
Install kernel by using the command "fastboot flash boot boot.img".
After installing disconnect your device from PC.
Enter CWM recovery by pressing volume down button several times while booting.
Do a full wipe/factory reset, wipe cache, wipe dalvik cache.
Select install zip from sdcard.
Navigate to the folder you've saved the ROM and select it.
After installing select reboot system now.
Click to expand...
Click to collapse
Now I got the same problem as Serebii. I've done all you've said, but I just get a black screen flashing the kernel. The fxp-Logo doesn't appear and I can't get into recovery mode.
Have you guys flashed .42 firmware before?
Or are you using a different?
You'd have to flash .42 firmware (look into CM7 thread) and then do the above steps again.
guys, when flashing kernel, look closely on your fasboot command window if there's something like "1 bad blocks encountered" message
should be "0 bad blocks encountered" for the kernel to work fine from what I know
Did That
Still Nothing...
Although Unlike macmeir, I'm able to go into recovery adn first see SE, and den CM7 boot logo
And also 1 second of the CM7 Welcome screen.
Thats It
Yea, It isnt showing any bad blocks
Now I got my phone back to life. I flashed the .42 firmware with flashtool. But then I had to install the fxp103-stuff. I cleared all caches, etc. It's strange; I did it before but it didn't work. I don't know if I've done something different.
But I'm still not able to run fxp104 or 105. I won't try again soon, because I spend five hours to get my device working.
Thanx for your help and good luck to you, Serebii.
good for you.
btw, you can also try Doomkernel on stock ROM, it's a great combo, I always go back to that setup
OK,
I flashed the latest CM7.2 And My Phone's alive Again!
A Biiiiiiiiig Thanks to Everybody!!

[Q] Question about installing custom ROM

Hello and thank you for reading.
So I got an HTC One V almost a week ago and I'm digging it so far. I unlocked the bootloader, rooted it and then went to install a recovery. First I tried CWM because that's what I used on my Optimus V, but it didn't work. Then I gave TWRP a shot which was awesome because not only did it work, but I also thought the touch option was a nice addition to the recovery. So I found a Jellybean ROM for the One V and gapps, put them on my sd and went to flash them. Wiped Cache and Dalvik Cache just fine, but when I went to wipe the system I got an error message. Ended up soft bricking then spent another hour or so getting the stock ROM back on there. The next day I unlocked and rooted again and I even found a CWM recovery that worked. Wiped everything fine then went to install, but once again I softbricked.
So that being said, here's my question. What step am I missing? I thought I was following all the instructions, but I missed something, right?
you have to factory reset from bootloader
Sent from my HTC One V using xda app-developers app
Thanks for your reply. Please correct me if I'm wrong about the order of things here:
Go into my recovery, wipe cache, wipe dalvik cache, reboot into bootloader, factory reset, reboot to go into recovery again, flash ROM and gapps then reboot system
I came across something that said I had to flash the boot img that came with the ROM too so I guess that would be my last step. Sorry if it seems like a total noob question, I'm still learning. Once again your help is appreciated.
Yes flash to boot.IMG for cm10
Sent from my One V using xda premium
Flash with latest kernel
hit thanks if I helped u!!!
You guys are awesome! I just want to double check and make sure I have the order right, though because this would be the third attempt and I don't want to have to go through the process of installing the stock ROM, unlocking and re-rooting of the phone again. Even though it's easy, it's still a bit of a pain, you know?
So...
-recovery
-wipe cache
-wipe dalvik cache
-reboot into bootloader
-factory reset
-reboot to go into recovery again
-flash ROM and gapps then reboot system
-flash boot.img (in bootloader I'm assuming?)
-flash kernel (Once again..bootloader, right? I heard Hellboy was decent, but I'm going to read about that now)
I know it's kind of a pain, but a list in the correct order is the best thing for someone still somewhat new to this like myself. If there's something out of order or I'm flashing something in the wrong section, I'd like to know before I do it rather than find out the hard way :laugh: Once again, thanks for the replies. The person that got me into this suggested this forum over all others and I'm happy he did.
Do these steps in order-
1. Put rom+gapps in root of sdcard.
2. Boot into bootloader and select fastboot then connect phone to pc or lappy.it should say fastboot USB.
3. Now flash the latest updated kernel.
4. Then go into recovery from bootloader and factory reset,wipe cache partition and wipe dalvik cache.
5. Then flash rom.zip,boot into rom.
6. Then again boot into recovery and flash gapps.
Sent from my HTC One V using xda app-developers app
Trolls Royce said:
You guys are awesome! I just want to double check and make sure I have the order right, though because this would be the third attempt and I don't want to have to go through the process of installing the stock ROM, unlocking and re-rooting of the phone again. Even though it's easy, it's still a bit of a pain, you know?
So...
-recovery
-wipe cache
-wipe dalvik cache
-reboot into bootloader
-factory reset
-reboot to go into recovery again
-flash ROM and gapps then reboot system
-flash boot.img (in bootloader I'm assuming?)
-flash kernel (Once again..bootloader, right? I heard Hellboy was decent, but I'm going to read about that now)
I know it's kind of a pain, but a list in the correct order is the best thing for someone still somewhat new to this like myself. If there's something out of order or I'm flashing something in the wrong section, I'd like to know before I do it rather than find out the hard way :laugh: Once again, thanks for the replies. The person that got me into this suggested this forum over all others and I'm happy he did.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1996665
hit thanks if I helped u!!!
mihirengg19 said:
Do these steps in order-
1. Put rom+gapps in root of sdcard.
2. Boot into bootloader and select fastboot then connect phone to pc or lappy.it should say fastboot USB.
3. Now flash the latest updated kernel.
4. Then go into recovery from bootloader and factory reset,wipe cache partition and wipe dalvik cache.
5. Then flash rom.zip,boot into rom.
6. Then again boot into recovery and flash gapps.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Factory reset never seemed to work when I did it in recovery mode. Though I was skipping a few steps when I tried it so I'll give this a shot during the weekend and get back to you. Funny thing is I posted a reply as you posted your's :laugh:
bahubali67 said:
http://forum.xda-developers.com/showthread.php?t=1996665
hit thanks if I helped u!!!
Click to expand...
Click to collapse
So many more steps from the Optimus V :laugh: I'll give this a shot and get back to you. Thanks guys for all your help!
flash the boot.img(thé kernel) in fastboot,not in bootloader..here is the link to latest hellboy kernel.
http://forum.xda-developers.com/showthread.php?t=1954967
Just to clarify u are gsm right?
Sent from my HTC One V using xda app-developers app
mihirengg19 said:
flash the boot.img(thé kernel) in fastboot,not in bootloader.if factory reset from recovery not working do it from bootloader.here is the link to latest hellboy kernel.
http://forum.xda-developers.com/showthread.php?t=1954967
Just to clarify u are gsm right?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
CDMA, sorry for not being more specific about that.
Oh thats where u r going wrong!
Download the proper cdma kernel and rom! Use cm10+jmz primoc!
And use the recovery for Primoc! If u flash gsm images to ur cdma phone u will regret it!
Sent from my HTC One V using xda app-developers app
Depends on the ROM
First thing, for cdma, TWRP seems to work better so you're better off using that. After that, it depends on the ROM. I've found that AOKP is the easiest to flash. Get the AOKP ROM and the gpps, extract the boot.img from the rom. Boot to recovery, wipe everything from there (including factory reset so you don't have to go back to bootloader for that) flash rom and gapps, go to bootloader, flash the boot.img through fastboot then reboot. For other roms you have slightly different processes you have to follow. You can find the info on the thread for each

[Q] [Xperia S] CM10 Installation problems

Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Try doing full wipe and reinstall CM 10 as you did previously
Sent from my Xperia S using xda app-developers app
I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app
dumbl3 said:
I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I have the same problem My phone not boot in just freexperia logo and cwm5.5.0.4. My /data partition can't mount and format I can't install any rom:crying: Heeeeeelp:crying:
All will be fixed
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
Follow this thread for Kernel and Rom installation; http://forum.xda-developers.com/showthread.php?t=1879982
Follow this other to select your Rom; http://forum.xda-developers.com/showthread.php?t=1642480
And take that cm-10-20130110-UNOFFICIAL is CM 10.2 for such reason look for JB Gapps For Android version 4.1.2
I flashed the Rom very well, also the kernel. my problem were the Gapps. I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Regards,
apsanchezs said:
I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Click to expand...
Click to collapse
I do have the correct gapps. This CM is android version 4.1.2. Here I downloaded the latest for CyanogenMod 10.0.x which is for android versions 4.1.x.
Anyway after a whole evening/night of flashing I finally managed to get it working via hei1125 cm10 version:
http://goo.im/devs/hei1125/nozomi
I dont know what I did to make it working again, but it does.. CM10 does look a lot nicer then CM9. Although I heard it has some bugs, which yet I still have to encounter..
FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip fails
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
I'm on the same problem. Use FXP201 instead or wait until 203... The cm10-fxp202 doesn't work on my device too. Same procedure as Yours or update from 201 to 202 - all will fail on (my) nozomi.
Hello!
Hello! orange fix for this rom?if so, I would like to link to it? thank you very much :fingers-crossed:
Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel nozimi and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2
funky0308 said:
Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel hikari and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
i got same plobrem with You.
Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks
Enable signaturecheck in recovery before install. It worked for me.
Gesendet von meinem Xperia S mit Tapatalk 2
Make sure you flash the good .img before flashing the ROM !
alexdan2302 said:
Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks
Click to expand...
Click to collapse
It's always recommend to wipe all (cache, davlink even system) then flash.
Be sure to mount system and then try.
And of course, check is you zip file o.k (maybe download again)
Even if you updating cm to new version it's best if you wipe.
I know that's lot of work, but only then you'll have good battery life, smooth and fast ROM and stability.
Sent from my LT26i using Tapatalk 2
Reinstalled apps and Data from googleserver after a datawiped update shoudn't be a Problem, or?
Gesendet von meinem Xperia S mit Tapatalk 2
I had just the same problem today. I installed cm10 from recovery and did everything you did!!!!
What i did to solve this prblem is:
- Went into recovery.
- wiped cache and dalvik.
- flashed the latest CM10 (FXP215 to be precise) again!!
- flashed gapps again!!
- after flashing both zips I wiped dalvik and cache again.
- Than reboot.
If you keep getting into bootloops, keep doing these steps. Beliefe me man I had the exect same problam today and this solved it . Just dont panic or do something stupid and have alot of patients! :good:
But this is not a so called clean install. I use factory reset to have a clean install or just wipe data partition. After 1st boot I restore only some of my saved data with titanium backup.
Gesendet von meinem Xperia S mit Tapatalk 2

[Q] Boot Loop, Need help!

i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?
i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop
also not running the newest version of that rom, i am running v15a
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0

Pop-up com.android.phone has stopped

Hi there !
I have a problem with my phone, this afternoon i finally decide to get on CM 10.2, it seems that everything went well but i have the pop-up "com.android.phone has stopped" which pop again and again every second. I tried to wipe data from the recovery and with the option on the settings, and i also tried to put the phone on airplane mode and then switch it off but i still have the problem.
I downloaded CM, gapps and CWM with the links in the official CM10.2 thread and i read carefully the instructions, i don't think that i have forgot something.
Does anybody have an idea for this problem?
Popofthepop said:
Hi there !
I have a problem with my phone, this afternoon i finally decide to get on CM 10.2, it seems that everything went well but i have the pop-up "com.android.phone has stopped" which pop again and again every second. I tried to wipe data from the recovery and with the option on the settings, and i also tried to put the phone on airplane mode and then switch it off but i still have the problem.
I downloaded CM, gapps and CWM with the links in the official CM10.2 thread and i read carefully the instructions, i don't think that i have forgot something.
Does anybody have an idea for this problem?
Click to expand...
Click to collapse
flashed the boot.img? fastboot erase cache after flashing the boot.img? wipe cache and dalvik in recovery after flashing the rom?
Yes, boot.img flashed, wiped cache + dalvik + data, but i don't use fastboot erase cache, isn't it the same thing as wipe cache? Is it important to wipe right after i flashed the ROM ? I think i did it after i flash boot.img
Popofthepop said:
Yes, boot.img flashed, wiped cache + dalvik + data, but i don't use fastboot erase cache, isn't it the same thing as wipe cache? Is it important to wipe right after i flashed the ROM ? I think i did it after i flash boot.img
Click to expand...
Click to collapse
It is vital. I actually fastboot erase cache, before and after I flash anything through fastboot, and I never have any problems.
Hmm ok, does I have to get back on stock or i can reflash the ROM and the boot.img directly, like on the official thread?
Popofthepop said:
Hmm ok, does I have to get back on stock or i can reflash the ROM and the boot.img directly, like on the official thread?
Click to expand...
Click to collapse
you can reflash, but do a full wipe in recovery first,
format cache, system, data and sdcard.
copy the rom back onto the card.
fastboot erase cache, flash the boot.img from the rom.zip and fastboot erase cache again.
then back to recovery and flash the rom and you should be good to go
I still have the pop-up =/ I exactly did what you wrote. By the way, it's the last nightly that i flashed.
What version (date please) of gapps do you use? Could it be you're running gapps for 4.2 on a 4.3 rom?
Sent from my HTC One X using xda app-developers app
I downloaded the package for CM10.2.x, 20130813.
EDIT: hboot 1.72.0000, don't know if it can help.
Popofthepop said:
I downloaded the package for CM10.2.x, 20130813.
EDIT: hboot 1.72.0000, don't know if it can help.
Click to expand...
Click to collapse
That should be the right gapps for CM10.2. About hboot I don't know exactly but I think it should be supported.
I just flashed the last nightly, and the pop-up don't pop anymore ! But i can't activate wifi =/
Popofthepop said:
I just flashed the last nightly, and the pop-up don't pop anymore ! But i can't activate wifi =/
Click to expand...
Click to collapse
Flashed the boot.img of the installed nightly ?
sent from my .......
Yes, full wipe then flash boot and rom + gapps, like nogotaclue told me.

Categories

Resources