[Q] Help [KitKat 4.4.1][CM11.0] LegacyXperia - Xperia Arc Q&A, Help & Troubleshooting

im trying to flash [KitKat 4.4.1][CM11.0] LegacyXperia :laugh:
so ive flashed the stock ICS rom than flashed the boot.img thats in the zip folder ive downloaded but the device is not booting any more and i cant even get into recovery can any one help
now im going back superjelly bean till i find a solution for this

Mr.Doc said:
im trying to flash [KitKat 4.4.1][CM11.0] LegacyXperia :laugh:
so ive flashed the stock ICS rom than flashed the boot.img thats in the zip folder ive downloaded but the device is not booting any more and i cant even get into recovery can any one help
now im going back superjelly bean till i find a solution for this
Click to expand...
Click to collapse
Check MD5 if the download was clean.
How did you flash the boot.img?
Make sure the device is correct
Cheers,
AJ

Abhinav2 said:
Check MD5 if the download was clean.
How did you flash the boot.img?
Make sure the device is correct
Cheers,
AJ
Click to expand...
Click to collapse
i flashed the boot.img with flashtool as i always do

1. Unlock bootloader
2. Flash .587 ftf using Flashtool
3. Flash boot.img in the zip. Get in bootloader then "fastboot erase system" and "fastboot erase userdata" if your phone fail to boot
4. Boot into Recovery, then go to "mounts and storage", format /system, /data, /cache
5. Full Wipe
6. Install Nightlies or Releases
7. Install Gapps
8. Reboot system

Related

Phone keeps rebooting randomly, not charging

Help me please.
I was previously on ARHD ICS and i decided to try CM10. I did a wipe and flashed paranoid cm10 in CWM, then flashed the boot.IMG and then cleared cache etc.
However, the phone starts up, boots in to cm10...but doesn't charge anymore. It also reboots randomly when i use it and it get s stuck in a loop for a while and then it boots into cm10 fine again.
I've tried loads of different rome and its doing the same thing. PLEASE help.
Hboot is 1.12
Desperate here anyone,?
Sent from my GT-S5830 using xda app-developers app
Did you do a full wipe before flashing (/system, /data and /cache)?
Yep. Numerous times. I have no idea what it's doing. It will boot into the android system, I'll use it for 5 minutes or so without issue, then all of a sudden the 'shutting down' dialog appears with Android System in written at the top in the background..This is on all the roms i tried.
Very Easy To Fix This Problem
First You Must Unlock Your HOX ....
Flash Stock Recovery .... Then Do Factory Rest From BootLoader .
Now Extract "boot.img" From The Rom You Want To Flash ( use winrar/7-Zip )
Flash "boot.img" You Extracted From Fastboot By THis Command
Fastboot Flash Boot.img
Fastboot erase cache
Now Flash ClockModRecovery And Open It
Mount Use Storage From Recovery then Copy Your rom.zip To HOX .
Do Full Wipe From Recovery
And Now Install The Rom From The Recovery ........ and restart your phone
if your HOX stuck on first boot just reboot the phone and wait ...
sorry for bad english ...
I've already flashed the boot.img. This isn't the first time i've flashed a rom
Ok ..... do you try factory rest ?
Your Must Do Factory Rest And The Stock Recovery Only Can Do That
Flash The Stock Recovery ( Download From Attachments "StockRecovery.Zip" )
Fastboot Flash Recovery rstock.img
Then Back To HBOOT Menu And Do "FACTORY REST"
Now Flash "Boot.Img" For Your Custom Room " Must Flash Boot.Img First Then Flash The rom As I Know "
And The Other You Know
The Trick Here Is Format Your SdCard Completely By "Factory Rest"
ahmedaljaf said:
Ok ..... do you try factory rest ?
Your Must Do Factory Rest And The Stock Recovery Only Can Do That
Flash The Stock Recovery ( Download From Attachments "StockRecovery.Zip" )
Fastboot Flash Recovery rstock.img
Then Back To HBOOT Menu And Do "FACTORY REST"
Now Flash "Boot.Img" For Your Custom Room " Must Flash Boot.Img First Then Flash The rom As I Know "
And The Other You Know
The Trick Here Is Format Your SdCard Completely By "Factory Rest"
Click to expand...
Click to collapse
Ok guys - the phone charges but i still have the same issue of 'Shutting down' after 10 mins use.
I have flashed stock recovery, relocked bootloader and installed the RUU back to stock.
Same issue!!
Help
Out of ideas now. Could this be a hardware fault?

[Q] Paranoid Android PrimoU stuck in boot animation.

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 !

Looping on CyanogenMod boot screen!

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

installing custom rom

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!

Help with HOX

I was before on a custom ROM but when the official 4.2.2 was released i went back to stock and updated my phone to 4.2.2. And now i managed to go back to custom rom. I unlocked the bootloader and flashed CWM and installed superSU everything was okay! I wiped cache..system ... then i installed MagioROM R4 and flashed the boot.img file but my phone just dont start stays on HTC screen.. before i made a backup when my phone was on 4.1.2 (i think that) i tried to restore this backup using CWM and flashed the boot.img the phone booted normally but the touchscreen didnt respond ! please help ? I would like to have the MagioROM but if that doesnt work plz help me get back to a working phone
i have this file : OTA_ENDEAVOR_U_JB_50_S_hTC_Asia_WWE_4.19.707.3-3.14.707.24_release_3346060yp26w70ibi8zm1g.zip
can it help ?
4.19.707.3
cid: HTC_044
And it seems i downloaded the magioROM from here http://forum.xda-developers.com/showthread.php?t=2438840 which is for XL i think .. is this the problem ? if i downloaded the ROM from here : http://forum.xda-developers.com/showthread.php?t=2415164 will it work normally ?
blingo999 said:
I was before on a custom ROM but when the official 4.2.2 was released i went back to stock and updated my phone to 4.2.2. And now i managed to go back to custom rom. I unlocked the bootloader and flashed CWM and installed superSU everything was okay! I wiped cache..system ... then i installed MagioROM R4 and flashed the boot.img file but my phone just dont start stays on HTC screen.. before i made a backup when my phone was on 4.1.2 (i think that) i tried to restore this backup using CWM and flashed the boot.img the phone booted normally but the touchscreen didnt respond ! please help ? I would like to have the MagioROM but if that doesnt work plz help me get back to a working phone
i have this file : OTA_ENDEAVOR_U_JB_50_S_hTC_Asia_WWE_4.19.707.3-3.14.707.24_release_3346060yp26w70ibi8zm1g.zip
can it help ?
4.19.707.3
cid: HTC_044
Click to expand...
Click to collapse
yes flashing a rom for the one xl is the same as flashing a rom which is intended for a samsung or sony phone, it's a completely different phone so won't work!
firstly you need a different recovery, get philz touch recovery and flash it, that will solve the touchscreen problem.
Now do a full wipe from recovery, data, system, cache and sdcard.
load another rom onto sdcard.
flash the boot.img from the rom and then do the command "fastboot erase cache". This is very important and may possibly be why magio wouldn't boot
now flash the rom and enjoy.
blingo999 said:
I was before on a custom ROM but when the official 4.2.2 was released i went back to stock and updated my phone to 4.2.2. And now i managed to go back to custom rom. I unlocked the bootloader and flashed CWM and installed superSU everything was okay! I wiped cache..system ... then i installed MagioROM R4 and flashed the boot.img file but my phone just dont start stays on HTC screen.. before i made a backup when my phone was on 4.1.2 (i think that) i tried to restore this backup using CWM and flashed the boot.img the phone booted normally but the touchscreen didnt respond ! please help ? I would like to have the MagioROM but if that doesnt work plz help me get back to a working phone
i have this file : OTA_ENDEAVOR_U_JB_50_S_hTC_Asia_WWE_4.19.707.3-3.14.707.24_release_3346060yp26w70ibi8zm1g.zip
can it help ?
4.19.707.3
cid: HTC_044
Click to expand...
Click to collapse
Now your device restored 4.1.1 rom ? If so flash Philz_Touch recovery then install the OTA.zip via recovery, after that flash boot.img from OTA, then fastboot erase cache > reboot.
nogotaclue said:
yes flashing a rom for the one xl is the same as flashing a rom which is intended for a samsung or sony phone, it's a completely different phone so won't work!
firstly you need a different recovery, get philz touch recovery and flash it, that will solve the touchscreen problem.
Now do a full wipe from recovery, data, system, cache and sdcard.
load another rom onto sdcard.
flash the boot.img from the rom and then do the command "fastboot erase cache". This is very important and may possibly be why magio wouldn't boot
now flash the rom and enjoy.
Click to expand...
Click to collapse
Thankyou for the info . i'll download the ROM tn8 and comeback with what will happen
virgolib said:
Now your device restored 4.1.1 rom ? If so flash Philz_Touch recovery then install the OTA.zip via recovery, after that flash boot.img from OTA, then fastboot erase cache > reboot.
Click to expand...
Click to collapse
Thats it thanks sir ! everything is working fine now

Categories

Resources