ive just installed this rom from here using cwm
http://www.androidauthority.com/one-x-android-4-0-4-slim-ics-custom-rom-99065/
the rom installed fine but is when reboot it is stuck in a boot loop.
The problem i am having is that CWM wont mount into USB for me to load another rom.
Any suggestions???
waxb18 said:
ive just installed this rom from here using cwm
http://www.androidauthority.com/one-x-android-4-0-4-slim-ics-custom-rom-99065/
the rom installed fine but is when reboot it is stuck in a boot loop.
The problem i am having is that CWM wont mount into USB for me to load another rom.
Any suggestions???
Click to expand...
Click to collapse
I think this should be in the Q&A section
Having said that, did you flash the boot.img via fastboot on your computer (fastboot flash boot boot.img)? Also did you use the command fastboot erase cache? If not, try those
Sent from my HTC One X
yep did flash the boot img
didnt to the erase cache
how do i go about doing that?
waxb18 said:
yep did flash the boot img
didnt to the erase cache
how do i go about doing that?
Click to expand...
Click to collapse
And it was the boot.img you took from the rom download from the zip?
You go on cmd if you're windows, navigate to your fastboot folder
Type...
cd c:/(directory of your fastboot folder)
Mine would be
Cd c:/android
Then type
Fastboot erase cache
Ensure your device is in fastboot USB mode in the bootloader first.
Sent from my HTC One X
i manage do get it to boot up but im now met with the error
Unfortunately the ptocess com.android.phone has stopped
So what i have tried to do is delete Slim ICS, and install a new fresh rom from cynogen,, but it keeps booting to Slim ICS
Am i doing things correctly
Boot into CWM
Delete Data/Factory Reset
Wipe Cache
Wipe Dalvik Cache
Install ROM
Reboot
waxb18 said:
i manage do get it to boot up but im now met with the error
Unfortunately the ptocess com.android.phone has stopped
So what i have tried to do is delete Slim ICS, and install a new fresh rom from cynogen,, but it keeps booting to Slim ICS
Am i doing things correctly
Boot into CWM
Delete Data/Factory Reset
Wipe Cache
Wipe Dalvik Cache
Install ROM
Reboot
Click to expand...
Click to collapse
I'm unfamiliar with this error, however there are many posts in this forum which I have read which include this solution. Please use the search feature
Dont forget to click thanks!
Sent from my HTC One X
First and foremost upgrade to latest cwm 5.8.4.0 as earlier versions have usb mounting and charging issues. Once upgraded you can copy your desired rom and then flash.
In your steps, I didn't see flashing the boot.img that comes inside the rom.zip file. You should flash it using fastboot from your pc with
Fastboot flash boot boot.img
Fastboot erase cache
Before you boot your ROM. Otherwise, since cwm can't flash it, you will be booting whatever kernel is already installed.
Sent from my HTC One X using xda premium
eyosen said:
First and foremost upgrade to latest cwm 5.8.4.0 as earlier versions have usb mounting and charging issues. Once upgraded you can copy your desired rom and then flash.
In your steps, I didn't see flashing the boot.img that comes inside the rom.zip file. You should flash it using fastboot from your pc with
Fastboot flash boot boot.img
Fastboot erase cache
Before you boot your ROM. Otherwise, since cwm can't flash it, you will be booting whatever kernel is already installed.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Haha sorry, I presumed they had the latest recovery
Sent from my HTC One X
Related
Hey all,
So I've attempted this multiple times, and looked around for answers - founds some, but didn't quite understand them.
The name says it all: I have a PrimoU device and I am trying to install Paranoid Android. I have done the following:
Full wipe: wiped everything and formatted /system.
Then, I install the ROM from my SD card.
Next, I go to bootloader, fastboot, and flash the boot.img (Hellboy Kernel i think)
Finally, I install gapps.
Am I doing something wrong/ can anyone offer me a solution. I've seen forums saying that I am stuck in a "boot loop" and that I need to flash the boot.img... which I thought I did. I also tried to go inside the ROM and flash that boot.img but it made me loop on the HTC boot.
Regards.
gdomingo said:
Hey all,
So I've attempted this multiple times, and looked around for answers - founds some, but didn't quite understand them.
The name says it all: I have a PrimoU device and I am trying to install Paranoid Android. I have done the following:
Full wipe: wiped everything and formatted /system.
Then, I install the ROM from my SD card.
Next, I go to bootloader, fastboot, and flash the boot.img (Hellboy Kernel i think)
Finally, I install gapps.
Am I doing something wrong/ can anyone offer me a solution. I've seen forums saying that I am stuck in a "boot loop" and that I need to flash the boot.img... which I thought I did. I also tried to go inside the ROM and flash that boot.img but it made me loop on the HTC boot.
Regards.
Click to expand...
Click to collapse
Ensure that you use the proper command
fastboot flash boot boot.img.
Does the cmd say 'finished' at the end?
mihirengg19 said:
Ensure that you use the proper command
fastboot flash boot boot.img.
Does the cmd say 'finished' at the end?
Click to expand...
Click to collapse
Yes I used that command, and it says finished at the end. Which boot.img am I supposed to be flashing though? The kernel right?
gdomingo said:
Yes I used that command, and it says finished at the end. Which boot.img am I supposed to be flashing though? The kernel right?
Click to expand...
Click to collapse
Hellboy kernel,the latest one from the list.
mihirengg19 said:
Hellboy kernel,the latest one from the list.
Click to expand...
Click to collapse
So it goes: Wipe, install ROM, flash kernel (fastboot flash boot boot.img), install gapps... reboot?
gdomingo said:
So it goes: Wipe, install ROM, flash kernel (fastboot flash boot boot.img), install gapps... reboot?
Click to expand...
Click to collapse
Yes,just a change of order
Flash kernel,wipe,flash rom,reboot into rom,again into recovery and flash gapps.
(order doesnt affect much)
try like this
install kernel - latest hellboy kernel 15022013 - BE SURE TO NOT FLASH THE 4.2 ONE - flash only the one that has CM10 in its name.
boot in recovery
do a factory reset and then wipe system
install rom
reboot
reboot into recovery
install gapps
1ceb0x said:
try like this
install kernel - latest hellboy kernel 15022013 - BE SURE TO NOT FLASH THE 4.2 ONE - flash only the one that has CM10 in its name.
boot in recovery
do a factory reset and then wipe system
install rom
reboot
reboot into recovery
install gapps
Click to expand...
Click to collapse
Enter 1ce
Exit mihirengg19
1ceb0x said:
try like this
install kernel - latest hellboy kernel 15022013 - BE SURE TO NOT FLASH THE 4.2 ONE - flash only the one that has CM10 in its name.
boot in recovery
do a factory reset and then wipe system
install rom
reboot
reboot into recovery
install gapps
Click to expand...
Click to collapse
Thank you so much, I was flashing the 2013 kernel not the one with CM10.
No problem !
First off, I want to state that I'm a complete noob at everything. Okay so today I tried to install IceColdJelly v3.2 from CyanogenMod 10, following the instructions on the page. When I tried to flash the the rom, I got a failed error. After that, I decided to just reboot my phone but now it gets stuck on the CyanogenMod load screen, then reboots itself and loops all over again. Is there anything I can do? My phone doesn't appear on my PC when I plug it in. I'm completely clueless as to what to do now so please help me!
Thanks in advance.
Do you have the required hboot to run 4.2.2 roms?
Failed while installing rom means either a not supported hboot/base or corrupt download... just redownload the rom and extract the boot.img from it and put it in your fastboot folder and then do the following.
1. Go to recovery and go to mounts and storage>Mount usb and put the ICJrom.zip and gapps on your phone...
2. Wipe data/cache partition/dalvic and then flash the ROM and then gapps..
3. Go to bootloader and then flash the boot.img via fastboot and then fastboot erase cache
4. Reboot
vin4yak said:
Do you have the required hboot to run 4.2.2 roms?
Failed while installing rom means either a not supported hboot/base or corrupt download... just redownload the rom and extract the boot.img from it and put it in your fastboot folder and then do the following.
1. Go to recovery and go to mounts and storage>Mount usb and put the ICJrom.zip and gapps on your phone...
2. Wipe data/cache partition/dalvic and then flash the ROM and then gapps..
3. Go to bootloader and then flash the boot.img via fastboot and then fastboot erase cache
4. Reboot
Click to expand...
Click to collapse
How do I know if my hboot can run 4.2.2 roms? Can I update it if It can't?
technoa said:
How do I know if my hboot can run 4.2.2 roms? Can I update it if It can't?
Click to expand...
Click to collapse
If your hboot is above 1.31 , u can install 4.2 ROMs. .
And yes, you can update hboot
Sent from my HTC One X using xda app-developers app
i have rooted my htc one x
every time when i tries to install any custom rom into it and when i boot first time one error continuously shows "unfortunately com.android.phone stopped" i have also tried to reboot it again but the same problem remains
i have tried cm 10.1 RC5 and jellybam stable and many more roms , but the same problem remains always ..
help me plz
Are you sure you flashed the boot image and wiped everything properly (as described in most ROM's threads)?
Sent from my HTC One X using xda premium
that problem will mostly occur if you are installling a rom in unclean way..
make sure you do superwipe and before flashing rom flash its boot.img and do- "fastboot erase cache" afterwards
then flash it from recovery
TimeWasterNL said:
Are you sure you flashed the boot image and wiped everything properly (as described in most ROM's threads)?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i have followed this link for unlocking boot loader
"http://forum.xda-developers.com/forumdisplay.php?f=1533#root"
and then for rooting i have followed this steps
"http://www.youtube.com/watch?v=80lMHUgxwww"
and for installing custom rom i have follwed this steps
"http://www.youtube.com/watch?v=gxJf8xIVVC0"
plz help me
aseferfan said:
that problem will mostly occur if you are installling a rom in unclean way..
make sure you do superwipe and before flashing rom flash its boot.img and do- "fastboot erase cache" afterwards
then flash it from recovery
Click to expand...
Click to collapse
i am new in ROOT world
so plz tell me how to do it , whatever u have suggested me in your previous reply is not clearly understood by me , so plz make it clear
shivamtarzan said:
i have followed this link for unlocking boot loader
"http://forum.xda-developers.com/forumdisplay.php?f=1533#root"
and then for rooting i have followed this steps
"http://www.youtube.com/watch?v=80lMHUgxwww"
and for installing custom rom i have follwed this steps
"http://www.youtube.com/watch?v=gxJf8xIVVC0"
plz help me
Click to expand...
Click to collapse
most of the people here know the procedures. give us information that will help you solve the problem. like is your phone already rooted. the steps you do when flashing. like what did you really do before that error appears. something like that.
robchongke said:
most of the people here know the procedures. give us information that will help you solve the problem. like is your phone already rooted. the steps you do when flashing. like what did you really do before that error appears. something like that.
Click to expand...
Click to collapse
yes my phone is already rooted . i have also taken the backup of m stock rom . i have tried to install custom rom for 3 to 4 times but every time when i installs custom rom and when i boot it the above problem occurs so i restore my system with the backup , and that original stock rom is working fine
for flashing i have followed this :
1) unlocked bootloader
2) rooted it
3) installed clockwork recovery mode
4) now transfer the custom rom into the internal memory
5) reboot phone into bootloader mode
6) select "recovery"
7) wipe data/factory reset
8) wipe cache partitions
9) wipe dalvik cache
10) install zip from sd card-->choose zip from sd card-->select the rom
11) select yes
12) after installing the rom reboot the phone
and when the phone will rebooted the problem occures when the ui of new rom appears
shivamtarzan said:
yes my phone is already rooted . i have also taken the backup of m stock rom . i have tried to install custom rom for 3 to 4 times but every time when i installs custom rom and when i boot it the above problem occurs so i restore my system with the backup , and that original stock rom is working fine
for flashing i have followed this :
1) unlocked bootloader
2) rooted it
3) installed clockwork recovery mode
4) now transfer the custom rom into the internal memory
5) reboot phone into bootloader mode
6) select "recovery"
7) wipe data/factory reset
8) wipe cache partitions
9) wipe dalvik cache
10) install zip from sd card-->choose zip from sd card-->select the rom
11) select yes
12) after installing the rom reboot the phone
and when the phone will rebooted the problem occures when the ui of new rom appears
Click to expand...
Click to collapse
you do not need to root, flash custom recovery and unlock the bootloader everytime.
you did not flash the rom's boot.img. everytime you flash rom or kernel dont forget to flash boot.img. place the rom's boot.img inside your fastboot folder. then do the command:
fastboot erase cache.
fastboot flash boot boot.img.
then reboot.
robchongke said:
you do not need to root, flash custom recovery and unlock the bootloader everytime.
you did not flash the rom's boot.img. everytime you flash rom or kernel dont forget to flash boot.img.
Click to expand...
Click to collapse
yes i know that i do not need to flash custom recovery , root or unlock bootloader every time , i am just telling from initial stage
once i rooted phone , unlocked bootloader and flash recovery then i just install the rom but before that i am wiping all three things which i mentioned before this reply
and how to flash boot.img whenever i flash rom ?
shivamtarzan said:
yes i know that i do not need to flash custom recovery , root or unlock bootloader every time , i am just telling from initial stage
once i rooted phone , unlocked bootloader and flash recovery then i just install the rom but before that i am wiping all three things which i mentioned before this reply
and how to flash boot.img whenever i flash rom ?
Click to expand...
Click to collapse
yeah. you still have to that. extract the boot.img from the rom. place the boot.img inside your fastboot folder. boot your phone into bootloader. it you see fastboot usb you can now flash the boot.img.
open command prompt. navigate to your fastboot folder or you can just right click on the fastboot folder and select "enter comman prompt here" something like that. then enter this commands.
fastboot erase cache
fastboot flash boot boot.img
that's two different command.
robchongke said:
yeah. you still have to that. extract the boot.img from the rom. place the boot.img inside your fastboot folder. boot your phone into bootloader. it you see fastboot usb you can now flash the boot.img.
open command prompt. navigate to your fastboot folder or you can just right click on the fastboot folder and select "enter comman prompt here" something like that. then enter this commands.
fastboot erase cache
fastboot flash boot boot.img
that's two different command.
Click to expand...
Click to collapse
these things that you have said me should done before installing custom rom of after ?
shivamtarzan said:
these things that you have said me should done before installing custom rom of after ?
Click to expand...
Click to collapse
it does'nt matter it you flash boot.img before of after. but me i always flash boot.img first. because if you flash the rom first. you'll boot your phone to recovery then after you flash rom you'll boot to bootloader, where you will press power button + vol down. while if you flash boot.img first. after that just go to hboot then select recovery then flash rom. well that's just me. hehe.
robchongke said:
it does'nt matter it you flash boot.img before of after. but me i always flash boot.img first. because if you flash the rom first. you'll boot your phone to recovery then after you flash rom you'll boot to bootloader, where you will press power button + vol down. while if you flash boot.img first. after that just go to hboot then select recovery then flash rom. well that's just me. hehe.
Click to expand...
Click to collapse
flash rom means "installing any new custom rom from recovery-->install zip from sd card-->choose zip from sd card-->selecting the zip" am i right here??
shivamtarzan said:
flash rom means "installing any new custom rom from recovery-->install zip from sd card-->choose zip from sd card-->selecting the zip" am i right here??
Click to expand...
Click to collapse
yep. don't forget to wipe cache and wipe dalvik. if you are flashing a different rom.always do a full wipe.
robchongke said:
yep. don't forget to wipe cache and wipe dalvik. if you are flashing a different rom.always do a full wipe.
Click to expand...
Click to collapse
ok got it
now i am going to do this in this manner :
1) flash new custom rom's boot.img as u said
2) wipe all cache & dalvik cache
3) flash new custom rom
am i going on a right path??
shivamtarzan said:
ok got it
now i am going to do this in this manner :
1) flash new custom rom's boot.img as u said
2) wipe all cache & dalvik cache
3) flash new custom rom
am i going on a right path??
Click to expand...
Click to collapse
Don't forget to erase fastboot cache after flashing boot.img...
Also in recovery, you need to wipe data as well if your coming from a different rom...
-Sent from my IceCold One X!
shivamtarzan said:
ok got it
now i am going to do this in this manner :
1) flash new custom rom's boot.img as u said
2) wipe all cache & dalvik cache
3) flash new custom rom
am i going on a right path??
Click to expand...
Click to collapse
yep. and as i said before. if you are flashing different rom. dont forget to full wipe.
vin4yak said:
Don't forget to erase fastboot cache after flashing boot.img...
Also in recovery, you need to wipe data as well if your coming from a different rom...
-Sent from my IceCold One X!
Click to expand...
Click to collapse
how to erase fastboot cache ?
shivamtarzan said:
how to erase fastboot cache ?
Click to expand...
Click to collapse
there are only 2 commands when flashing boot.img via cmd:
fastboot erase cache
fastboot flash boot boot.img
so dont forget that.
shivamtarzan said:
how to erase fastboot cache ?
Click to expand...
Click to collapse
fastboot erase cache
robchongke said:
there are only 2 commands when flashing boot.img via cmd:
fastboot erase cache
fastboot flash boot boot.img
so dont forget that.
Click to expand...
Click to collapse
He needs to erase the cache after flashing the boot.img and not before!
Hi!
Yesterday i have downloaded and installed new rom for my HTC desire Z..
name of the rom is : aosp.4.2.2 20130627 vision
After installing the rom i installed gapps
version of gapps is : gapps-ics-20120429-signed
And i think i installed the wrong gapps beacuse when i was installing the gapps in the recovery mode...suddenly recovery mode closed...
Now..when i turn on the phone i get an error: Unfortunately setup wizard has stopped
And i dont know what to do please help
Boot to recovery, flash jb gapps, reboot
If this doesn't work
Boot to recovery, do a full wipe, flash ROM, jb gapps, reboot
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Boot to recovery, flash jb gapps, reboot
If this doesn't work
Boot to recovery, do a full wipe, flash ROM, jb gapps, reboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I forgot to write that when i boot to recovery mode and i do factory reset or full wipe or something else..recovery mode is closing after few seconds...and i cant to anuthing in recovery mode
Something is wrong with recovery then
Try to flash a new one with fastboot
fastboot erase system -w
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Something is wrong with recovery then
Try to flash a new one with fastboot
fastboot erase system -w
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I solved my problem !
I installed the JB gapps... ( this time recovery mode didnt close )
thank you !
After a long string of flashing failures with this device, I'm needing to update the recovery.
Unfortunately after it let me downgrade the recovery, no matter what recovery I flash (CWM latest or TWM) for the HTC One X, the god damn older version is still there.
I've tried updating it through One X One Click and CWM itself. But I have no idea what's going wrong or what's needed to be done.
[Edit]
Okay, it seemed to install with no errors this time.
Now I just have to figure out why the heck it always displays "HTC quietly brilliant" forever.
krisando said:
After a long string of flashing failures with this device, I'm needing to update the recovery.
Unfortunately after it let me downgrade the recovery, no matter what recovery I flash (CWM latest or TWM) for the HTC One X, the god damn older version is still there.
I've tried updating it through One X One Click and CWM itself. But I have no idea what's going wrong or what's needed to be done.
[Edit]
Okay, it seemed to install with no errors this time.
Now I just have to figure out why the heck it always displays "HTC quietly brilliant" forever.
Click to expand...
Click to collapse
so, which recovery did you install? which rom are you trying to install?
Recovery. Img is to be flashed through fastboot and not in recovery itself
Go in your fastboot folder
Open cmd there and give commands
Fastboot flash recovery recoveryname.img
Fastboot erase cache
And you're good to go :thumbup:
Sent from my HTC One X using xda app-developers app
Hello,
I have the same problem;
I was on recovery CMW 6.0.4.4. I tried to update to 6.0.4.5 or philz. Fastboot says okay after install, but when I restart to recovery, recovery is still 6.0.4.4.
What I haven't done is erase cache. Could this be it? Cannot try for the moment because I'm at work.
Thanks
Kverdoodt said:
Hello,
I have the same problem;
I was on recovery CMW 6.0.4.4. I tried to update to 6.0.4.5 or philz. Fastboot says okay after install, but when I restart to recovery, recovery is still 6.0.4.4.
What I haven't done is erase cache. Could this be it? Cannot try for the moment because I'm at work.
Thanks
Click to expand...
Click to collapse
yes, it might be... try to flash again recovery and to erase cache after OKAY message...
I tried it again with fastboot and than erase cache : doesn't work
Than I copied the recovery zip file to sdcard and installed it through clockworkmod recovery 6.0.4.4. Everything installed ok but when I reboot recovery it is still 6.0.4.4?
Any suggestions?
Thanks.
The zip is of no use, the recovery.img has to be flashed via fastboot (s-on devices have no other choice) try to flash a different recovery to check that works. Maybe the recovery is a bad download
I've found the solution.
It was a problem with my fastboot extension.
Thanks anyway