Related
Hi everyone, i just had my Xperia Arc stuck at the bootscreen after doing these steps.
I previously had the Generic firmware of Xperia Arc S for my Arc, on Ice Cream Sandwich flavor of Android.
Today i started trying to figure out how to flash the CM 9 Rom, because i have it on my Kindle fire, but it failed.
I've did all the steps to Unlock my bootloader, and, even tho my phone is eligible for that ( i checked it on the services menu ), i could not Unlock it.
After retrieving the Key and running the fastboot i had the Message "Remote: oem unlock failed".
After giving up to unlock it, i decided to install "X-Parts" and install the CMW so i could flash the .zip file of the CM9 Right from the SDCard.
Ok, thats what i did:
1. Installed CMW
2. Wiped Data / Factory Reset
3. Wiped Cache
4. Flashed .zip from SDCARD
5. Zip Installed
6. Repeated steps 2 and 3 again
7. Rebooted
Since them, i am stuck at the Bootscreen with the word "Sony" on it, which leads me to think that the rom was not flashed properly, otherwise i would see the cyan / black bootscreen.
Also, i can't manage to boot into "recovery mode" again, i am pressing Power + Volume Down but it is not working.
Any idea of what can i do now ?
How can i install cm9 properly and unstuck my phone ?
Do i need to unlock my BL in order to install CM9 ?
Thanks in advance and sorry about this, but i am sort of desperate this time
Just tried to Flash the "boot.img" file found at the CM9 zip folder using FLASHTOOL, but it says:
"20/016/2012 15:16:27 - INFO - FASTBOOT Output:
sending 'boot' (4916 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s"
My device IS rooted, and i can garantee it.
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
in order to flash kernels via fastboot you need your bootloader unlocked
it is bootlooping on CM because you arent using right kernel
not too sure why your having issues unlocking it, but this is probably the first thing you need to tackle
all i can recommend is to keep trying
but im sure someone more helpfull will be along soon!!
and just FYI, just because nobody is answering doesnt mean you need to start a new thread in another section, especially development as its hard enough to navigate without usless threads. just search or use google!
firedeimos said:
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
Click to expand...
Click to collapse
Do you understand that i can't even boot my phone ?
How am i supposed to Root it if i can't even make it boot ?
Please, any help here is welcome.
By the way, i AM searching, alot, for more than 4 hours already
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
yo-meister said:
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
Click to expand...
Click to collapse
So you are saying that i must try to Unlock my bootloader first, even tho i can't seem to make it boot ?
Not trying to be an ass, but i just can't seem to find a way to do it.
I have my IMEI wrote in a notepad file, but, once i try to unlock it's bootloader, it gives me an error. : "Remote: oem unlock failed!"
Not sure why this is happening, i am following the instructions on Sony Website...
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
yo-meister said:
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
Click to expand...
Click to collapse
I Love You.
Yes, i just did what you said.
We must ignore the LAST digit of IMEI, i was ignoring the first, since it was ZERO i thought that it would not matter.
Now that i have a new Bootloader Code, i used it and it worked.
Thanks a bunch, now, i must try to continue the process.
I will keep you guys updated
Update 1: The Bootloader is unlocked.
I tried to Flash the kernel.sin using the flashtool and seems like it was flashed correctly but i am still stuck in bootscreen.
Also, i still can't manage to boot in Recovery Mode to flash the CM9 from the SDCARD.
Any ideas?
Update 2: Flashed DoomKernel V04 Successfuly now i am trying to get into Recovery mode so that i can Finally Flash the cm9 rom in the sdcard.
wish me luck
Update 3: After booting into recovery mode, and trying to flash the CM9 .zip file, there is an error.
"Assert Failed: getprop..." From what i know of programming, this looks like the rom trying to assert that the values from the build.prop file must match either "LT18a","LT15i","LT15a" or "anzu".
Is there any way i can fix the file in order to make this "assert" directive works correctly ?
ha your welcome
i lost all my contacts when i first started all this, didnt backup with google account lol
now its just a case of...
put rom on SD CARD
BACKUP
wipe
flash kernel
flash rom
flash wifi modules (if required)
BOOT
and this is the first time i feel like i can say this...hit thanks if i helped haha
Just tried to Toggle the Assert Directives OFF from the DoomKernel but it is still checking for the asserts when trying to flash the Rom.
Any suggestions?
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
marcelloLins said:
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
Click to expand...
Click to collapse
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
pren22 said:
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
Click to expand...
Click to collapse
You mean Stock Firmware from Sony Ericson ?
Where can i find it ?
Is this one ?
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
I will try to flash it and see where i can get.
I just tried another flavor of CM9 (A nightly build) and i had the same error
marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
spidermoon said:
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
Click to expand...
Click to collapse
I am downloading this one :
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
Is there any problem with that ?
Update: These steps solved my problems:
1. Flash the 4.0.3 Android ICS Stock Firmware
2. Flash the Kernel from CM9
3. Wipe Factory and Cache
4. Flash the CM9
5. Flash Gapps
Reboot.
Thanks for all the help guys
I rooted and unlocked on my ics in HTC one X and no rom. But after HTC officially released Jelly Bean 4.1.1 , i unrooted again and updated in official Jelly Bean. now i wanted to use CM 10.1 rom and many days i searched a lot and failed to root again. please help me i got some problem.
#unlocked
# S on
# Hboot 1.36
#OS JB 4.1.1
#when i select recovery in Bootloader it show a error sign and restart
#failed to open master usb....
#i tried JB but it failed too
* i did a factory reset and now erase everything.
* if i make a call somebody can't hear my voice and some said very low voice.
please help me. Thanks in advanced
After you updated the phone you must unlock the bootloader (if you relocked it) and flash a new custom recovery.
Flash the new boot.img from the new rom, perform a full wipe in the recovery and install the new rom.zip !
Mr Hofs said:
After you updated the phone you must unlock the bootloader (if you relocked it) and flash a new custom recovery.
Flash the new boot.img from the new rom, perform a full wipe in the recovery and install the new rom.zip !
Click to expand...
Click to collapse
It's still shows unlocked and i wanna wipe or install from SD card but Recovery option not working.
Like i said, you must flash a custom recovery first. When you updated the phone its done with a stock recovery. A stock recovery is useless to us flashers.
Its all exactly the same as it was with ics.....
Mr Hofs said:
Like i said, you must flash a custom recovery first. When you updated the phone its done with a stock recovery. A stock recovery is useless to us flashers.
Its all exactly the same as it was with ics.....
Click to expand...
Click to collapse
r u saying to do follow the same way like i did for unlocked+root on my ICS ? i tried it but HTCdev not working like before.
Look.....you don't have to do the htcdev thing. You say your bootloader is unlocked. So flash a custom recovey and install a JB rom as usual
Mr Hofs said:
Look.....you don't have to do the htcdev thing. You say your bootloader is unlocked. So flash a custom recovey and install a JB rom as usual
Click to expand...
Click to collapse
okay on my way to try and i will get back to u. btw do u have any correct link of which i should follow ? Thanks a lot
Use this to guide you.
http://forum.xda-developers.com/showthread.php?t=1592355
But flash this recovery and not the one mentioned in the guide
http://db.tt/SPXdFfPw
Mr Hofs said:
Use this to guide you.
http://forum.xda-developers.com/showthread.php?t=1592355
But flash this recovery and not the one mentioned in the guide
http://db.tt/SPXdFfPw
Click to expand...
Click to collapse
C:\fastboot>fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'
C:\fastboot>fastboot flash philz recovary 5.6.1.img
error: cannot load 'recovary'
Put my linked recovery into the fastboot folder....
Then rename the file to just "recovery.img
Fastboot flash recovery recovery.img
You seem to have messed up the command mate
himel_htc said:
C:\fastboot>fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'
C:\fastboot>fastboot flash philz recovary 5.6.1.img
error: cannot load 'recovary'
Click to expand...
Click to collapse
i think u should rename it as : recovery.img
Husky34 said:
i think u should rename it as : recovery.img
Click to expand...
Click to collapse
Lol....beat you to it !
Mr Hofs said:
Put my linked recovery into the fastboot folder....
Then rename the file to just "recovery.img
Fastboot flash recovery recovery.img
You seem to have messed up the command mate
Click to expand...
Click to collapse
Yes u r right...thank u so much
cyMod RC2 loading......
#If i ever want to back to HTC official rom when the release the 4.2.2 what should i need to do ?
Well then you need to install the stock nandroid backup, flash the stock recovery and then update
Unfortunately, the process com.android.phone has stopped.....:crying:
after open first msg it and i can't do anything. what wrong i did ?
Sure you installed gapps too, and that it the right gapps ?
* flash boot.img
* make a full wipe in the recovery
* install CM10.1
* install gapps
* reboot
Mr Hofs said:
Sure you installed gapps too, and that it the right gapps ?
* flash boot.img
* make a full wipe in the recovery
* install CM10.1
* install gapps
* reboot
Click to expand...
Click to collapse
1.wipe everything then tried randomly all
2.cm-10.1.0-endeavoru
3.UPDATE-SuperSU-v1.00
4.gapps-jb-20130301-signed
#CWM-6032-advwipe-jb422-nontouch-recovery-endeavoru-v1.2
should i try anything else or change my recovery ?
changed recovery to TWR v2.5.0.0
flash boot.img
wipe factory reset
flashing CM 10.1 and gapps-jb-20130301-signed ...completed
rebooting system.....well again process com.android.phone stop
Why update su ? Link me to the thread please...
and try another rom for test purposes
Mr Hofs said:
Why update su ? Link me to the thread please...
and try another rom for test purposes
Click to expand...
Click to collapse
http://www.chainfire.eu/articles/129/SuperSU_v1_00_has_been_released_/
any good rom suggest please?
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.
Have you tried flashtool?
Sent from my LT18i using xda premium
tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks
Hi All,
I'm facing a critical problem. I have unlocked the bootloader using
Code:
fastboot -i 0x1ebf oem unlock
. I also ran the flashing CWM command in terminal
Code:
fastboot -i 0x1ebf flash recovery CM_Yureka_Recovery.img
. Which went succesfully as it shows messages like:
Code:
sending recovery...OKAY...writing recovery...OKAY...finished. total time 0.440 secs..
. But when I reboot into recovery mode, the cyanogen default recovery was there not the CWM recovery. Then I went to flash the SuperUser zip file browsing from sd card. Please note, that Internal/External I tried both. But its shows the typical signature verification failed error. I'm facing this problem on CM 12S. On CM 11s the whole rooting process went so well. So what should I do now? Need help ASAP. Thanks in advance.
goto development tool and uncheck update cm recovery then flash recovery again
matwaking said:
goto development tool and uncheck update cm recovery then flash recovery again
Click to expand...
Click to collapse
but update cm recovery only works at the time of OTA updates right? By the way, I tried that your procedure. But its not working !!!
das.palash89 said:
but update cm recovery only works at the time of OTA updates right? By the way, I tried that your procedure. But its not working !!!
Click to expand...
Click to collapse
Goto this post this will work.
LINK
das.palash89 said:
but update cm recovery only works at the time of OTA updates right? By the way, I tried that your procedure. But its not working !!!
Click to expand...
Click to collapse
no this overwrites the default recovery each time and worked for me though
I have device, kernel and vendor AOSP source available for my device. I'm trying to port LineageOS to my device. After a lot of work I was able to compile it. The kernel works just fine with the AOSP ROM but CWM only give black screen and the ROM not boot at all. It's just stop at the manufacturer splash screen, not even the boot animation comes in. It's mean no adb and no logcat. What's can cause this or how can I debug this problem ?
Try to fix the recovery first so you can debug the rom and isn't CWM discontinued already so try compiling TWRP or Cyanogen Recovery instead and it might boot.
3liteking148 said:
Try to fix the recovery first so you can debug the rom and isn't CWM discontinued already so try compiling TWRP or Cyanogen Recovery instead and it might boot.
Click to expand...
Click to collapse
I see thanks!
I have working TWRP recovery. Not my build but it's working. But how can I debug this?
And how can I found out what's wrong with the recovery?
Could found some info about the not working recovery by flashing a working one and getting last_kmsg after reboot.
"Untracked pid 280 exited with status 1"
Now how can I go deeper in debug? Is last logcat available somewhere just like last Kernel msg?
If you meet bootloop, you have to flash a rom which same android version like nougat. Allow ADB permission and reboot to recovery. Flash your rom without wiping data & cache. Get logcat with adb command and debug !
ps : i didnt read full, cant solve your problem
hiimpig1 said:
If you meet bootloop, you have to flash a rom which same android version like nougat. Allow ADB permission and reboot to recovery. Flash your rom without wiping data & cache. Get logcat with adb command and debug !
ps : i didnt read full, cant solve your problem
Click to expand...
Click to collapse
The main problem is the ROM I build not boots at all. It's mean no ADB and no logcat. Same with the recovery. Except it at least skip the manufacturer logo but still not ADB in recovery as well. Only the kernel works.
Gaboros said:
The main problem is the ROM I build not boots at all. It's mean no ADB and no logcat. Same with the recovery. Except it at least skip the manufacturer logo but still not ADB in recovery as well. Only the kernel works.
Click to expand...
Click to collapse
bump! ?
I have my answer from 3liteking148 at reddit. I write it down because it could be useful for someone and don't have to read through a lot of comment. This method required working recovery with adb or with file explorer. If the phone stuck at the manufacturer logo just reboot and get the files from /data/tombstones. The required information will be written there.
Gaboros said:
I have my answer from 3liteking148 at reddit. I write it down because it could be useful for someone and don't have to read through a lot of comment. This method required working recovery with adb or with file explorer. If the phone stuck at the manufacturer logo just reboot and get the files from /data/tombstones. The required information will be written there.
Click to expand...
Click to collapse
how do you get tumbstone