Related
Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I already did:
Root
Backup TA
Unlocked Bootloader (official way via Sony website)
What I already tried to install custom recovery:
RecoverX App on PlayStore -> Recovery not booting when tapping the sony logo while booting (black screen for some seconds then reboot to Android)
Xperia S Dual Recovery (Linux script) -> Installation successful but no chance to boot one of the recoveries via Vol +/-, no blue LED, boots directly to Android
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
EDIT 13:58
After further reading this looks like the way to go:
[RECOVERY] CWM-Based Recovery 6.0.2.7 for Xperia S (UnlockedBootLoader){JB}[20130824]
Correct? I don't want to end up bricking the device by trying different things. Can I flash CM11 ROMS using this recovery? The post says "do not use this for flashing CM10.1 (u will need to use the CM kernel for that)" which keeps confusing me ...
And how do I remove the recoveries already installed (list above) but not working?
real_sl4cker said:
Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
Click to expand...
Click to collapse
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.
Mirhawk said:
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.
Click to expand...
Click to collapse
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S
real_sl4cker said:
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S
Click to expand...
Click to collapse
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.
Mirhawk said:
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.
Click to expand...
Click to collapse
Thanks. I already found the current PA build in the thread (4.5 beta2) and apart from German translations missing in PA settings up to now it performs well [emoji3]
my phone is not booting after switching rom from pa lollipop experience beta9 to pac rc3. it gets stuck at bootanimation. tried both philz and twrp to wipe and flash another rom. cm11, pac, pa, mokee nothing boots now. can anybody help me out? i'll be very thankful.
Flash Fastboot ROM for Redmi 1S...there is a loads of tuts available on net how to !
Shahi00 said:
Flash Fastboot ROM for Redmi 1S...there is a loads of tuts available on net how to !
Click to expand...
Click to collapse
yea, this should do. the process is a bit lengthy though. anyway, thanks for the help man.
GreyBlood said:
my phone is not booting after switching rom from pa lollipop experience beta9 to pac rc3. it gets stuck at bootanimation. tried both philz and twrp to wipe and flash another rom. cm11, pac, pa, mokee nothing boots now. can anybody help me out? i'll be very thankful.
Click to expand...
Click to collapse
here .This is solution for no boot problem .all aosp roms work fine
eswarvf said:
here .This is solution for no boot problem .all aosp roms work fine
Click to expand...
Click to collapse
I did the same. Downloaded the fastboot rom and flashed it via MiFlash. Couldn't flash it using cmd at first because there's no driver of redmi 1s for 32-bit os. Then tried MiFlash and it worked. I had to format all though, not formatting the storage didn't work out. It got fixed the day i posted this. Anyway, thanks for giving a solution (even if i already fixed my phone).
Q&A for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cucumber09 said:
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/mmcblk0p23
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.4.0 (thanks to @Rohan purohit for compiling it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader it partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.
BTW, I don't own any of this work, I just adapted recovery images for using them from FOTA partition. And recoveries are not compiled by me.
Click to expand...
Click to collapse
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Vp10 said:
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Click to expand...
Click to collapse
It is CM bug, it will be fixed in next nightlies.
Hi bro, i see new twrp update in xperia l thread ..
I hope you to update them ..
Thangs
cucumber09 said:
It is CM bug, it will be fixed in next nightlies.
Click to expand...
Click to collapse
And how we can flash new nightlies without recovery?
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
digt said:
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
Click to expand...
Click to collapse
[emoji782]
AggelosGR said:
And how we can flash new nightlies without recovery?
Click to expand...
Click to collapse
Recovery is accessible, just press many times vol rocker 'till you will enter the recovery.
---------- Post added at 20:59 ---------- Previous post was at 20:55 ----------
2ALL
I'm reading Q&A section not often, better write to main thread or tag me (if you are not quoting me), so I will see the notification.
How to solve image unstability in FOTA TWRP?
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
e-bert said:
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
Click to expand...
Click to collapse
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Thanks & new question.
Remorcer said:
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Click to expand...
Click to collapse
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904)?
Thanks again.
e-bert said:
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904).
Thanks again.
Click to expand...
Click to collapse
Everyone has its own taste in roms, I like stable and clean roms and would suggest cm11 or PA, try some of the roms and I'm sure you'll find your favourite.
Bliss pop is good.try it ,the battery is good.smooth performance and id say not much sound glitch .
Sent from my nicki using XDA Premium 4 mobile app
All hail to all cucumber..
its so frustrated to install kernel only for recovery..
and its more frustrating when your phone not responsive because incompatible kernel.
i recommended to install this trough recovery..
more reliable and low risk..
if you cant install from recovery (signature verification failed), first install another kernel to get unsigned recovery (niu kernel example)..
its a long way, but i'm prefer this than risking my phone because wrong command..
tested in resurrection remix rom 5.1..
Installed fota twrp with terminal, it freezes
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Stuck on cyanogenmod boot
Flashed it and now i'm stuck on the cyanogenmod boot screen
is TWRP better or CWM...?
i flashed the twrp version 2.8.3.0 stuck on boot animation and when flashed 2.8.5.0 loop of recovery...m on xenon hd 5.1.1 rom...can anyone help???/ i want to flash twrp recovery
Neemac said:
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Click to expand...
Click to collapse
It is for Xperia M, not Z2. So it won't work on it.
@Neemac i think z2 have official fota twrp, so why you not use them?
Sent from my C1905 using Tapatalk
Can someone create an ELI5 "for dummies" video on how to flash a custom ROM and kernel to this device? Because no matter what guide I follow I can not get a custom ROM to boot with a custom kernel installed, it either loops at the Google splash until I turn it off, loops a few times then kicks me to fastboot, boots but the kernel isn't actually installed, or just hangs at the Google splash and never actually starts to boot the ROM. I've been told so many conflicting things it's not even funny, over on the Benzo thread someone told me kernels go in A with the ROM, didn't work it led to the device booting but the kernel not actually being installed. Before that I read that kernels go in B, that doesn't work either, it always leads to the other mentioned issues.
ryaniskira said:
Can someone create an ELI5 "for dummies" video on how to flash a custom ROM and kernel to this device? Because no matter what guide I follow I can not get a custom ROM to boot with a custom kernel installed, it either loops at the Google splash until I turn it off, loops a few times then kicks me to fastboot, boots but the kernel isn't actually installed, or just hangs at the Google splash and never actually starts to boot the ROM. I've been told so many conflicting things it's not even funny, over on the Benzo thread someone told me kernels go in A with the ROM, didn't work it led to the device booting but the kernel not actually being installed. Before that I read that kernels go in B, that doesn't work either, it always leads to the other mentioned issues.
Click to expand...
Click to collapse
Hi,
Did you at least try to follow xanaxdroid (Benzo ROM developer) how-to, to flash the ROM? It works fine...
Not sure what issue you have if you followed his method, because it just works as is! :good:
Good luck..!
Have you tried DU aka dirty unicorn 12.5.3 aka 8.1 android
flash DU zip then twrp then reboot after the first bootup then enter recovery and flash kernel
Also certain kernels are notorious for not playing nice with certain ROM /kernel combos. I always recommend Flash kernel to get your feet wet as it works with just about everything.
I agree with previous post. Some kernels just won't work. If time use factory image and flash kernel. That way validation of flashing order since most kernels expect a stock kernel build to replace.
I quoted you in a kernel thread with the exact kernel and ROM you want to use. I listed a step by step that I performed minutes before I posted it so I know it works.
hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers