Related
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 ?
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.
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.
Hello everyone, i'm pretty new to software modding (started again yesterday) but i have successfully customized my previous Nexus 4 with Cyanogenmod in the past and other things thanks to very easy guides online.
Now that the guarantee is void, i'd like to mod my Xperia Z1 Compact.
After a lot of tears and Boot Loops™ i finally managed to install Cyanogen Recovery and Cyanogenmod.
Now i'd like to switch to TWRP, as it provides Nandroid backups, which CMR does not, but i can't find any reliable source for this.
The device doesn't show up in the devices list on their website, so i'm really unsure what to do as i don't want to brick my phone :laugh:
Also pretty much same situation with rooting, there are tons of various ways to root the device but the only tool i'd trust (Flashtool) doesn't allow me to root my phone.
Again i don't know which source to trust or what to do...
Any help would be highly appreciated!
Regards, Daniel
SinusStudios said:
Hello everyone, i'm pretty new to software modding (started again yesterday) but i have successfully customized my previous Nexus 4 with Cyanogenmod in the past and other things thanks to very easy guides online.
Now that the guarantee is void, i'd like to mod my Xperia Z1 Compact.
After a lot of tears and Boot Loops™ i finally managed to install Cyanogen Recovery and Cyanogenmod.
Now i'd like to switch to TWRP, as it provides Nandroid backups, which CMR does not, but i can't find any reliable source for this.
The device doesn't show up in the devices list on their website, so i'm really unsure what to do as i don't want to brick my phone :laugh:
Also pretty much same situation with rooting, there are tons of various ways to root the device but the only tool i'd trust (Flashtool) doesn't allow me to root my phone.
Again i don't know which source to trust or what to do...
Any help would be highly appreciated!
Regards, Daniel
Click to expand...
Click to collapse
Rooting with unlocked BL is easy with adb/fastboot. Just download twrp IMG and copy it to /adb folder, and download SuperSU zip file and copy to phone. Then connect phone in fastboot mode, (power off, hold volume up, and connect cable, release volume when you see blue led), and use fastboot command 'fastboot flash recovery [name of twrp file].img'. Now you have recovery. Reboot to recovery and flash SuperSU.
Twrp download - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827
SuperSU download - https://www.google.com/url?sa=t&sou...euHCzPuwbF5IscvgA&sig2=3urcTF6yAxkoYwUylGydvA
levone1 said:
Rooting with unlocked BL is easy with adb/fastboot. Just download twrp IMG and copy it to /adb folder, and download SuperSU zip file and copy to phone. Then connect phone in fastboot mode, (power off, hold volume up, and connect cable, release volume when you see blue led), and use fastboot command 'fastboot flash recovery [name of twrp file].img'. Now you have recovery. Reboot to recovery and flash SuperSU.
Twrp download - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827
SuperSU download - https://www.google.com/url?sa=t&sou...euHCzPuwbF5IscvgA&sig2=3urcTF6yAxkoYwUylGydvA
Click to expand...
Click to collapse
@levone1 Thank you very much! Everything has worked flawlessly =)
Hi guys. I already flashed the twrp on this thread but; how can i flash another recovery? Do i need to just flash it again the same way i flashed the first recovery? Will it overwrite the old one automatically? Thanks for the answer. I'm just new to this so i just want to make sure.
Maximuous said:
Hi guys. I already flashed the twrp on this thread but; how can i flash another recovery? Do i need to just flash it again the same way i flashed the first recovery? Will it overwrite the old one automatically? Thanks for the answer. I'm just new to this so i just want to make sure.
Click to expand...
Click to collapse
yes. you probably want to flash it in flashmode or with flashfire, ive broken my recovery a couple times now and got it to work again. flashing a recovery image will wipe the recovery partition eg the previous rec
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result
ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Quiet interesting this device...salut to programmers of this device...
hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.
ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..
Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice
Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?