Develop Bugs

[q] Please, need a little help here.

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

Flashing problem

Hey guys!
My Xperia Arc S is kinda new - 1 month old.
I was on Xperia Ultimade HD Rom for a while and wanted to install another rom, so i did via CWM Recovery.
All fine.
I wanted to restart my phone but it got stock in Sony Logo.
Because my bootloader cant be unlocked i rooted with kernel downgrade and CWM is not there after flashing due to the wipe.
So i flashed stock .tft with Flashtool and phone booted again.
Now when I'm trying to flash anything my phone gets always stuck in Sony Logo (even when i try Eagleboy's mode without wiping!).
Anyway: I'd like to install a custom rom.
Does anyone how to fix this?
Bootloader: Locked
Phone: LT18i
Rooted: yes
... and I have the 4.0.1.B.0.587 firmware installed right now.
Thanks in advance!

Phone Flashing problem
That's the only problem with locked bootloader's:crying:When you install some stock custom roms you have to wipe system to do a clean install which by default wipes cwm because it is installed in system for locked bootloader's.So if you have a problem with a install you have to flash another .ftf because you wiped cwm recovery.
When I first had arc I had a locked bootloader and it was a pain if something went wrong while flashinghaving to flash again etc! etc! It just got to stage where I had enough and took the plunge and unlocked the bootloader.:good:
I'm afraid it's one of those things you have to live with unless you unlock your bootloader:crying: ( I know you said you can't )there are quite a few stock roms that work but like I said if anything goes wrong you have to flash .ftf again.Probably a case of just trying each one Jader's rom alway's seemed to boot nice:good:

tallman43 said:
That's the only problem with locked bootloader's:crying:When you install some stock custom roms you have to wipe system to do a clean install which by default wipes cwm because it is installed in system for locked bootloader's.So if you have a problem with a install you have to flash another .ftf because you wiped cwm recovery.
When I first had arc I had a locked bootloader and it was a pain if something went wrong while flashinghaving to flash again etc! etc! It just got to stage where I had enough and took the plunge and unlocked the bootloader.:good:
I'm afraid it's one of those things you have to live with unless you unlock your bootloader:crying: ( I know you said you can't )there are quite a few stock roms that work but like I said if anything goes wrong you have to flash .ftf again.Probably a case of just trying each one Jader's rom alway's seemed to boot nice:good:
Click to expand...
Click to collapse
Hi, thanks for your answer
I tried to install 3 different roms till now - i wiped everything.
Then: Boot till sony-logo - I have to flash another tft with flashtool, Root again, and this takes time and is quite annoying.
I came from Samsung Galaxy S there wasn't the problem with the "bootloader" which is really annoying.
So: What should i do now?
I mean my CWM is not persistent and till now no rom worked.

Galaxy3User said:
Hi, thanks for your answer
I tried to install 3 different roms till now - i wiped everything.
Then: Boot till sony-logo - I have to flash another tft with flashtool, Root again, and this takes time and is quite annoying.
I came from Samsung Galaxy S there wasn't the problem with the "bootloader" which is really annoying.
So: What should i do now?
I mean my CWM is not persistent and till now no rom worked.
Click to expand...
Click to collapse
Hi totally agree it is frustrating!:crying: When you install some of these custom rom's they use Aroma installer are you unticking the reboot option in aroma installer and rebooting from cwm?Because you need to reboot that way (you seem to be doing everything right )
(1) Boot to cwm
(2) Wipe cache/Data/Advanced Dalvik cache
(3) Mounts & Storage format data/cache/system (NOTHING ELSE!)
(4) Install .zip on Sd card
(5) Choose options Aroma Installer
(6) Untick reboot option
(7) Reboot from cwm

tallman43 said:
Hi totally agree it is frustrating!:crying: When you install some of these custom rom's they use Aroma installer are you unticking the reboot option in aroma installer and rebooting from cwm?Because you need to reboot that way (you seem to be doing everything right )
(1) Boot to cwm
(2) Wipe cache/Data/Advanced Dalvik cache
(3) Mounts & Storage format data/cache/system (NOTHING ELSE!)
(4) Install .zip on Sd card
(5) Choose options Aroma Installer
(6) Untick reboot option
(7) Reboot from cwm
Click to expand...
Click to collapse
Yes i know , but thats what i did !
Wiped & formatting these settings and unticking reboot in aroma.
But it still doesn't work

Galaxy3User said:
Yes i know , but thats what i did !
Wiped & formatting these settings and unticking reboot in aroma.
But it still doesn't work
Click to expand...
Click to collapse
:crying:Like I said you seem to be doing everything rightHave you tried this rom http://forum.xda-developers.com/showthread.php?t=1994135 it's a two part installation but if I remember right this one seemed to install ok:good:

tallman43 said:
:crying:Like I said you seem to be doing everything rightHave you tried this rom http://forum.xda-developers.com/showthread.php?t=1994135 it's a two part installation but if I remember right this one seemed to install ok:good:
Click to expand...
Click to collapse
Haha i know. Thats why it seems strange for me too. But i need a custom rom and normally i would need a different kernel too.
But thats not possible. Sadly.
So nobody knows what i could change?

Galaxy3User said:
Haha i know. Thats why it seems strange for me too. But i need a custom rom and normally i would need a different kernel too.
But thats not possible. Sadly.
So nobody knows what i could change?
Click to expand...
Click to collapse
Only other thing you could try is changing your base firmware/ftf I notice you are using .587 base ftf try changing to another one, although Some of the custom roms recommend that firmware
Maybe someone else as any ideas

Απ: Flashing problem
If you accidentally formatted system then you removed the cwm. Try flashing the official ftf, install x-parts and redo everything without wiping system partition.
The other choice is to unlock your bootloader and you'll never face this problem again. I voided my warranty less a month after taking my phone, I knew that any problem will come up I could fix it myself
Sent from my Xperia Arc

Retrosid said:
If you accidentally formatted system then you removed the cwm. Try flashing the official ftf, install x-parts and redo everything without wiping system partition.
The other choice is to unlock your bootloader and you'll never face this problem again. I voided my warranty less a month after taking my phone, I knew that any problem will come up I could fix it myself
Sent from my Xperia Arc
Click to expand...
Click to collapse
Yep sure - but my CWM is gone when i wipe data. And I tried this: I flashed stock .ftf and installed xparts, then flashed a ROM without wipe - but doesn't boot and I cant access CWM again :/
And as I said i can't unlock my bootloader.

.. But the strange thing is just:
I even get bootloop when I install EAGLEBOYYS MOD (!) without WIPING anything! (just the recommended for sure)
That should not happen.

Why can't you unlock bootloader? Doing that would solve most of the problems you are facing. You don't have to downgrade to re root. Flash the stock kernel, install a new recovery then try again.
Sent from my Xperia Arc S using xda premium

If I go in service menu it says: Bootloader Unlock Allowed: No !
If I flash stock .ftf root is gone (?) -- RootChecker says that root is gone too.

Galaxy3User said:
Yep sure - but my CWM is gone when i wipe data. And I tried this: I flashed stock .ftf and installed xparts, then flashed a ROM without wipe - but doesn't boot and I cant access CWM again :/
And as I said i can't unlock my bootloader.
Click to expand...
Click to collapse
Galaxy3User said:
If I go in service menu it says: Bootloader Unlock Allowed: No !
If I flash stock .ftf root is gone (?) -- RootChecker says that root is gone too.
Click to expand...
Click to collapse
First of all - this thread: http://forum.xda-developers.com/showthread.php?t=1683957
I advice you to take step by step STRICTLY.
Or you can try to root with the FlashTool but I'm not sure if it will work with locked BL.
After that: http://forum.xda-developers.com/showthread.php?t=1955248
And for additional info: http://forum.xda-developers.com/showthread.php?t=1955248

TopperBG said:
First of all - this thread: http://forum.xda-developers.com/showthread.php?t=1683957
I advice you to take step by step STRICTLY.
Or you can try to root with the FlashTool but I'm not sure if it will work with locked BL.
After that: http://forum.xda-developers.com/showthread.php?t=1955248
And for additional info: http://forum.xda-developers.com/showthread.php?t=1955248
Click to expand...
Click to collapse
Thats how i rooted my Arc S!
Thats the only method that is working with locked BL.
And well, i took all the steps mentioned in the second topic you posted..
If you can't get it to work (stuck on Sony logo), then flash this in flash tool and then root again and do it one more time.
It´s ICS and kernel for Arc S but works fine on regular Arc. I use it myself on my Arc.
http://www.mediafire.com/?r0anos8emtx4iiy password is MMAS (If asked for)
Good luck and have fun with your superfast Arc with Ultimate HD™ ROM 2.0.
Click to expand...
Click to collapse
And this download link doesnt work :/

Galaxy3User said:
Thats how i rooted my Arc S!
Thats the only method that is working with locked BL.
And well, i took all the steps mentioned in the second topic you posted..
And this download link doesnt work :/
Click to expand...
Click to collapse
Here it is:
https://www.box.com/s/yu3dbp760kkyw7osoo41
https://www.box.com/s/9prbhnvkmyrglyoyl20j

TopperBG said:
Here it is:
https://www.box.com/s/yu3dbp760kkyw7osoo41
https://www.box.com/s/9prbhnvkmyrglyoyl20j
Click to expand...
Click to collapse
I flashed these files already after i got stuck at SONY logo but doesnt help..

Galaxy3User said:
I flashed these files already after i got stuck at SONY logo but doesnt help..
Click to expand...
Click to collapse
What does mean "doesnt help" ?
What are you trying to do and dont work, what is messages, what happens, did you have newest version of FlashTool, did you have installed ADB drivers, what's the error ?

TopperBG said:
What does mean "doesnt help" ?
What are you trying to do and dont work, what is messages, what happens,
did you have newest version of FlashTool, did you have installed ADB drivers,
what's the error ?
Click to expand...
Click to collapse
I mean when i flash this .ftf and reroot and install CWM all works fine.
But when I try to flash any ROM and doing all wipes etc. correctly it still gets stuck at SONY logo!
I have newest version of flashtool and ADB drivers installed. In flashtool there is no error.

Galaxy3User said:
I mean when i flash this .ftf and reroot and install CWM all works fine.
But when I try to flash any ROM and doing all wipes etc. correctly it still gets stuck at SONY logo!
I have newest version of flashtool and ADB drivers installed. In flashtool there is no error.
Click to expand...
Click to collapse
Which ROM are you trying to flash?
Is that ROM for locked BL ?

Q) Xperia S l26i rooted,unlocked bootloader. Now stuck in bootloop. Please HELP

Hi Everyone,
I wanted to install custom recovery in my Sony Xperia S L26ii , So rooted it a week ago. It is rooted for sure., I installed titanium backup and backed up everything. Yesterday I did unlock my bootloader so that I can install a custom recovery and custom rom. I followed the procedure of official way of unlocking bootloader by getting the key and unlocked it using fastboot command.
Till This everything works fine.I could boot into my device.
I flashed Twrp recovery adb fastboot. After this I wanted to backup my Stock rom. While I try to perform backup i got an error "unable to mount data" and it was unsucessfull.
I tried to reboot the system and shocked that it is stuck in boot loop now. I am seeing the word "Sony " and again it is rebooting,
I tried whatever I can by browsing internet. It seems I cannot use pc companion since I unlocked bootloader and installed custom recovery.
i tried to download tft file from somewhere and tried to flash through flashtools and got an error "ERROR - Processing of loader.sin finished with errors."
Dont know what to do. Any help would be highly appreciated. All I could access is TWRP recovery . currently I powered off the phone.
Please help me in the right direction.
Regards,
Suresh

ssuresh005 said:
Hi Everyone,
I wanted to install custom recovery in my Sony Xperia S L26ii , So rooted it a week ago. It is rooted for sure., I installed titanium backup and backed up everything. Yesterday I did unlock my bootloader so that I can install a custom recovery and custom rom. I followed the procedure of official way of unlocking bootloader by getting the key and unlocked it using fastboot command.
Till This everything works fine.I could boot into my device.
I flashed Twrp recovery adb fastboot. After this I wanted to backup my Stock rom. While I try to perform backup i got an error "unable to mount data" and it was unsucessfull.
I tried to reboot the system and shocked that it is stuck in boot loop now. I am seeing the word "Sony " and again it is rebooting,
I tried whatever I can by browsing internet. It seems I cannot use pc companion since I unlocked bootloader and installed custom recovery.
i tried to download tft file from somewhere and tried to flash through flashtools and got an error "ERROR - Processing of loader.sin finished with errors."
Dont know what to do. Any help would be highly appreciated. All I could access is TWRP recovery . currently I powered off the phone.
Please help me in the right direction.
Regards,
Suresh
Click to expand...
Click to collapse
It is the "ftf" file, not "tft". Try Flashing the stock ftf file immediately again after You get the error, it will work. You get the error first time.

Mirhawk said:
It is the "ftf" file, not "tft". Try Flashing the stock ftf file immediately again after You get the error, it will work. You get the error first time.
Click to expand...
Click to collapse
Thank you bro for replying and correcting me. Yes ftf file. I am downloading stock ftf from XDA forum (thanks for the member) and Will try to flash it (by pressing volume down and connecting usb cable to it) and will let you know.
Im just wondering , yesterday when I saw the phone in bootloop , I paniked and try to perform factory reset couple of times . Though it did not help in anyway. Will it disable usb debugging? If so is there any way we can reenable it from recovery or any other way?
-Suresh

ssuresh005 said:
Thank you bro for replying and correcting me. Yes ftf file. I am downloading stock ftf from XDA forum (thanks for the member) and Will try to flash it (by pressing volume down and connecting usb cable to it) and will let you know.
Im just wondering , yesterday when I saw the phone in bootloop , I paniked and try to perform factory reset couple of times . Though it did not help in anyway. Will it disable usb debugging? If so is there any way we can reenable it from recovery or any other way?
-Suresh
Click to expand...
Click to collapse
Nah it won't affect You while flashing the ftf file. You can always flash the ftf file using flashtool by fastboot, no matter what.

Mirhawk said:
Nah it won't affect You while flashing the ftf file. You can always flash the ftf file using flashtool by fastboot, no matter what.
Click to expand...
Click to collapse
Bro, You are great. That worked. It did revoked my root and locked bootloader though. But that is fine. I could do root and unlock the bootloader again..
A quick question. It all happened when I flashed TWRP recovery in this phone using this link (http://techglen.com/2014/02/12/install-twrp-custom-recovery-on-xperia-s-lt26i-nozomi/2/). I have already flashed TWRP in another HTC but it never caused this issue.
Is there any issue in installing TWRP in xperia sl ?
Should I use only CWM recovery?
If i can use Twrp , is there any good way/post or steps you recommend.?
Many Thanks again:good:
-Suresh

ssuresh005 said:
Bro, You are great. That worked. It did revoked my root and locked bootloader though. But that is fine. I could do root and unlock the bootloader again..
A quick question. It all happened when I flashed TWRP recovery in this phone using this link (http://techglen.com/2014/02/12/install-twrp-custom-recovery-on-xperia-s-lt26i-nozomi/2/). I have already flashed TWRP in another HTC but it never caused this issue.
Is there any issue in installing TWRP in xperia sl ?
Should I use only CWM recovery?
If i can use Twrp , is there any good way/post or steps you recommend.?
Many Thanks again:good:
-Suresh
Click to expand...
Click to collapse
Weird. It should not lock Your bootloader, since locking bootloader has different procedure. Anyways, TWRP works fine with Xperia SL. Even My phone is a SL and I always use twrp. Which version where You using of twrp? Use this version. And flash it using the command by connecting Your phone in fastboot mode:
Code:
fastboot flash boot openrecovery-twrp-2.8.0.1-LT26i.img

Mirhawk said:
Weird. It should not lock Your bootloader, since locking bootloader has different procedure. Anyways, TWRP works fine with Xperia SL. Even My phone is a SL and I always use twrp. Which version where You using of twrp? Use this version. And flash it using the command by connecting Your phone in fastboot mode:
Code:
fastboot flash boot openrecovery-twrp-2.8.0.1-LT26i.img
Click to expand...
Click to collapse
Bro. I flashed this recovery and now after reboot phone is going to recovery only. I manually tried to reboot it to bootloader and it is getting to TWRP recovery only. I tried to flash a Kitkat rom which was in my internal memory as zip file it failed with error " error executing updater binary in zip" did google search on it and got to know to overcome this error I had to be on TWRP 2.8.0.1 but we are already in that code, I dont know why I was still getting that error.
So I used the ftf file again to flash . I followed the forum "http://forum.xda-developers.com/showpost.php?p=28305266&postcount=3" to get the ftf file. I could see there are ftf for ginger bread and ICS , but I could only flash Ginger bread since I am getting error when I flash ICS ftf. not sure why.
Now having stock Ginger Bread rom rooted and bootloader unlocked.
I am happy that you brought me this far. It Would be great if you could guide me to proceed further to install any custom recovery and any custom rom of Jelly bean and higher. :good:
- Suresh
I also wanted to try something before you come online . so flashed the custom recovery which you have provided and flashed cyanogenmod 9 latest nightly and current status is
Rooted, bootloader unlocked, installed custom recovery(TWRP){with your wonderful assistance} , flashed cyanogenmod 9 nightly(ICS)
All I need now is a jelly bean rom or KITKAT rom (preferable )

ssuresh005 said:
All I need now is a jelly bean rom or KITKAT rom (preferable )
Click to expand...
Click to collapse
My Bad, that procedure installs a Kernel, and since it was not compatible with the ROM You were using, it only booted to the twrp. Copy the file to Your internal sdcard and use these following commands on Terminal Emulator app from playstore:
Code:
su
dd if=/sdcard/fotakernel.img of=/dev/block/mmcblk0p11
where fotakernel.img is the name of Your .img file.
It was weird that You go that error while flashing a Kitkat ROM. Which ROM were You trying to flash? If You wan to flash a Kitkat ROM, then follow the procedure here, no matter which Android version You are on, no need to do anything else.

[kernel][E6533][Z3+ dual][32.2.A.0.224](RIC disable, TWRP, root,dm-verity)

Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:

Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!

youngcube said:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
Click to expand...
Click to collapse
no need to flash superSU i think, it's already included in the kernel.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.

bruno$0 said:
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
Click to expand...
Click to collapse
Working wonderful with SuperSU 2.68 I have a doubt do you have a DRM Restore that works with this Android Version?

Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks

[/COLOR]
creepyvillager said:
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
Click to expand...
Click to collapse
No flashing a kernel doesn't wipe anything, if you're having a dilemma then take a backup of everything like apps, contacts etc using titanium backup, copy the backup folder to your external memory or computer then flash.
Hope it helps.
P. S ONLY INSTALLING A RECOVERY WIPES EVERYTHING.
---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?

njaya95 said:
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
Click to expand...
Click to collapse
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.

creepyvillager said:
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
Click to expand...
Click to collapse
I just found out to use this kernel i should have .244 firmware i bet you're at .185 so update it to .244 then try this kernel. I'm just downloading the firmware now using Xperifirm(https://www.google.com/url?sa=t&rct...9Q4Ht-00R24lisYcw&sig2=ac8ImW1ZY7AvFSZpG9I9mA) and i'll post what i did to the phone after the update.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
It's not, need to flash SuperSU I flashed 2.66 Beta

bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Hey can you help me, how to make this kernel SELinux status permissive.

njaya95 said:
Hey can you help me, how to make this kernel SELinux status permissive.
Click to expand...
Click to collapse
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.

bruno$0 said:
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
Click to expand...
Click to collapse
Okay ?

Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?

SugnaB said:
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
Click to expand...
Click to collapse
It's for 6.0.1 so don't flash it for 5.0.1, update the firmware then flash it cause Sony would have updated somethings in the kernel which won't work with old firmwares. The reason for boot working is maybe because of the phone rebooting from fastboot mode.
Hope it helped. [emoji4]
Sent from my E6533 using XDA-Developers mobile app

Did it need a Unlocked Boot-loader device?

sani007 said:
Did it need a Unlocked Boot-loader device?
Click to expand...
Click to collapse
offcourse.

Sorry for the noob question but I need to know the prerequisites,
Can I flash the Kernel right after flashing stock file OR....
Do I need to first unlock my bootloader
Do I need to have backed up my TA partition

hi there, i wanna update form .185 to .224. is it possible to update without wipe the data? and if it can, if i wanna root it, i just flash this kernel after fw upgrade, then flash supersu via twrp, am i right? thanks

If Xperia Z3+ Dual can't be bootloader unlocked, what's the point in this kernel?!

[a520f] Bricked after flashing boot partition with heimdall no Downloadmode/Recovery

Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
i cannot acces Download mode or recovery or boot the phone
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response

wolkengold said:
Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response
Click to expand...
Click to collapse
Can you boot to download mode? If you can, flash latest oreo.

iloveoreos said:
Can you boot to download mode? If you can, flash latest oreo.
Click to expand...
Click to collapse
no i cant... at least not with button combinations...

wolkengold said:
no i cant... at least not with button combinations...
Click to expand...
Click to collapse
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.

iloveoreos said:
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.
Click to expand...
Click to collapse
thanks, i will try if smart switch will help me.

wolkengold said:
thanks, i will try if smart switch will help me.
Click to expand...
Click to collapse
There is a small chance.

iloveoreos said:
There is a small chance.
Click to expand...
Click to collapse
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...

wolkengold said:
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...
Click to expand...
Click to collapse
Cool! Now what happens when you reboot to download mode from twrp?

SnowFuhrer said:
Cool! Now what happens when you reboot to download mode from twrp?
Click to expand...
Click to collapse
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.

SnowFuhrer said:
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.
Click to expand...
Click to collapse
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Flash stock firmware using Odin?

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.

SnowFuhrer said:
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.
Click to expand...
Click to collapse
sorry for the late response. You were right, i accidentally downloaded an older oreo release and thats why i could not flash it. I now downloaded the newest stock rom from updato.com and it worked perfect.
Thanks for your support

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked

jack364030 said:
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked
Click to expand...
Click to collapse
You are correct but...He sorted this 4 months ago.