[SOLVED]
Recently I've installed Oreo AOSP, I wanted to return flashing from TWRP but stucks on bootanimation, I tried with XGen but the problem persists
Also I tried through flashhtool but the program it doesn't detect my phone, also I tried with Emma, the process was completed correctly but when I boot up the phone the custom ROM is there
Im going to try flashing the Loire kernel through TWRP, at least I want to move to LineageOS
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
n0k0m3 said:
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
Click to expand...
Click to collapse
Already I solved the problem, i flashed the AOSP kernel in Existenz N, then I can boot as usual, however thanks for your answer
Related
I have xperia mini ST15i rooted with stock kernel and ROM ICS. Now I want to use some custom ROM like CM10 JB for it but there is no way to install the clockworkmode recovery on it I tried a tutorial which let me install the tool on my device ad I installed the ROM manger but it is reporting that CWM is not compatible with my device. When I press the Backup current ROM it just reboot and nothing happens, while in article they recommend the CWM to use a custom ROM.
I tried to install the CWM from http://mobilecon.info/install-sony-xperia-clockworkmod-for-ics-and-gingerbread.html
It is installing it but no way to use it.
I'm looking on this article to install the JB on my device.
http://www.teamandroid.com/2012/09/21/update-xperia-mini-st15i-st15a-android-411-jelly-bean-cm10-custom-firmware/
Now I want to know how can I use CWM to use make a recovery of stock ROM and use custom ROM, also how can I go back to stock ROM if custom ROM doesn't work.
avirk said:
I have xperia mini ST15i rooted with stock kernel and ROM ICS. Now I want to use some custom ROM like CM10 JB for it but there is no way to install the clockworkmode recovery on it I tried a tutorial which let me install the tool on my device ad I installed the ROM manger but it is reporting that CWM is not compatible with my device. When I press the Backup current ROM it just reboot and nothing happens, while in article they recommend the CWM to use a custom ROM.
I tried to install the CWM from http://mobilecon.info/install-sony-xperia-clockworkmod-for-ics-and-gingerbread.html
It is installing it but no way to use it.
I'm looking on this article to install the JB on my device.
http://www.teamandroid.com/2012/09/...-android-411-jelly-bean-cm10-custom-firmware/
Now I want to know how can I use CWM to use make a recovery of stock ROM and use custom ROM, also how can I go back to stock ROM if custom ROM doesn't work.
Click to expand...
Click to collapse
Try downloading xparts/xperia parts from playstore and install it. Hope your device is rooted when you try it
Btw for cyanogenmod you have to unlock the bootloader which voids warranty. If you want to unlock look in my signature there's a guide!
mihahn said:
Try downloading xparts/xperia parts from playstore and install it. Hope your device is rooted when you try it
Btw for cyanogenmod you have to unlock the bootloader which voids warranty. If you want to unlock look in my signature there's a guide!
Click to expand...
Click to collapse
I have already tried xparts but it also say that its not compatible with my device while I have rooted my phone already.
Check the command prompt log. is it saying successful installation?if then pressing the correct key after sony logo appears on start-up will put it on the CWM
avirk said:
I have xperia mini ST15i rooted with stock kernel and ROM ICS. Now I want to use some custom ROM like CM10 JB for it but there is no way to install the clockworkmode recovery on it I tried a tutorial which let me install the tool on my device ad I installed the ROM manger but it is reporting that CWM is not compatible with my device. When I press the Backup current ROM it just reboot and nothing happens, while in article they recommend the CWM to use a custom ROM.
I tried to install the CWM from http://mobilecon.info/install-sony-xperia-clockworkmod-for-ics-and-gingerbread.html
It is installing it but no way to use it.
I'm looking on this article to install the JB on my device.
http://www.teamandroid.com/2012/09/...-android-411-jelly-bean-cm10-custom-firmware/
Now I want to know how can I use CWM to use make a recovery of stock ROM and use custom ROM, also how can I go back to stock ROM if custom ROM doesn't work.
Click to expand...
Click to collapse
First of all,download the stock firmware from here: http://talk.sonymobile.com/thread/35239?start=0&tstart=0 (For security,if anytime,anything goes wrong..you can revert back to your stock)
Flashtool for flashing custom rom and kernel: http://androxyde.github.com/index.html?1350887833000
You can flash a custom kernel with CWM. I am using kernel Panic : http://forum.xda-developers.com/showthread.php?t=1861905
Firmware Flashing tutorial: http://forum.xda-developers.com/showthread.php?t=1695514
You have to unlock bootloader for flashing custom kernel.I think for flshing JB,sooner or later,you have to flash custom kernel anyway.Decide about unlocking bootloader.Searc google for "Official bootloader unlocking method"
Note: Installed CWM sometimes doesn't work if your phone gets stuck at sony logo after flashing custom roms.But custom kernel's CWM stays allways active.So,it is better.Just take a backup before flashing custom rom
alone_in_dark said:
First of all,download the stock firmware from here: http://talk.sonymobile.com/thread/35239?start=0&tstart=0 (For security,if anytime,anything goes wrong..you can revert back to your stock)
Flashtool for flashing custom rom and kernel: http://androxyde.github.com/index.html?1350887833000
You can flash a custom kernel with CWM. I am using kernel Panic : http://forum.xda-developers.com/showthread.php?t=1861905
Firmware Flashing tutorial: http://forum.xda-developers.com/showthread.php?t=1695514
You have to unlock bootloader for flashing custom kernel.I think for flshing JB,sooner or later,you have to flash custom kernel anyway.Decide about unlocking bootloader.Searc google for "Official bootloader unlocking method"
Note: Installed CWM sometimes doesn't work if your phone gets stuck at sony logo after flashing custom roms.But custom kernel's CWM stays allways active.So,it is better.Just take a backup before flashing custom rom
Click to expand...
Click to collapse
But why should he unlock bootloader if he only wants to install cwm?
@OP: Please make some screenshots of the installation progress in cmd and in the app. This error message could maybe help us :good:
Try this http://forum.xda-developers.com/showthread.php?t=1773227 it should work with locked bl too
then you need to reboot your phone and try to press volume down for multiple times when kernel logo (sony) appears
Ok guys, Heres what I do & what happens,
(model # C6833)
1- root device
2- install new boot kernel (adv-stock-v4) (( Even tried v5))
3- unlock bootlader (only had to do it the first time, bootloader stays unlocked)
4- install cwm/TWiRP
5- get into TWIRP or CWM & wipe as I should
6- install rom. (It wont install)
7- reboot
8- stuck @ sony logo. & then reboots,
9- reinstall stock rom
This happens every time I try to install a rom.
I also get the message before I reboot, no root, would you like cmw/twirp to fix it, I go with yes. & ive tryed no as well. no difference. Still get stuck @ Sony logo & get reboot loop.
Any ideas ?
Im not new at rooting & roming.
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Triflot said:
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Click to expand...
Click to collapse
I did the flashtool thing. ( I'll edit my post ) I did the boot.img & Im trying to use SlimRom. Everything seems to be fine until I try & install the rom. Then it goes to hell.
Btw, Slimrom is compatable.
So what's the actual error message you get upon installing a ROM?
Something like, installation canceled. could not install rom. It goes threw a few steps. gets a few things installed (or so it seems) & then it hangs & I get that message. I thought, at first, it may have been a corrupt download. But after a few times of downloading it. I kinda think its no longer that.
Have you tried another ROM? Someone else is also having boot trouble with Slim in its development thread.
No actually, I have not. I will soon though now. And report back. First I need a stock U.S. rom. Just in case. Cant seem to find one.
Been using a CE (Central Europe) based stock rom.
Just flashed 6.0.1 and am now seeing the battery percentage in values way above 100%. For example, my battery percentage is at 4,110%. Is anyone else seeing this?
Yeah I'm getting the same issue also.
Sent from my Nexus 9 using Tapatalk
Is this happening on a stock and unrooted device ???
Mine is stock, rooted.
Sent from my Nexus 9 using Tapatalk
Every report I've read about this issue is due to someone not running the stock kernel. Does this apply to you ?
Reverting back to the stock kernal or installing a kernal that's been updated to support 6.0.1 seems to have solved the problem.
oias.heeda said:
Mine is stock, rooted.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
kernal says 3.10.40-g909db78
[email protected] #1
fri aug 28 21:16:30 UTC 2015
before updating I was on elementalx
This has to do with the boot.img. I'm using chainfires modified one, but it is for MRA58N. Does anyone have the modified one for MMB29K? I might have to look into modifying myself but I've not done this before...
the.teejster said:
Every report I've read about this issue is due to someone not running the stock kernel. Does this apply to you ?
Reverting back to the stock kernal or installing a kernal that's been updated to support 6.0.1 seems to have solved the problem.
Click to expand...
Click to collapse
Makes sense. My N6 was doing this with a rooted kernel, and the problem went away when I flashed back to stock.
According to most accounts of this problem, the user forgot to flash the appropriate boot.img, vendor.img, or system.img before flashing the kernel/ROM.
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Neptaliuss said:
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Click to expand...
Click to collapse
Worked for me as well!
This worked perfect for me. I didn't need to reflash the system image either. Just the stock boot.img, then supersu, then ex kernel. All from within TWRP. Then reboot. That battery percentage was driving me nuts though. Thanks.
Neptaliuss said:
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Click to expand...
Click to collapse
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Don't flash a different kernel, just try RR first, boot and make sure it works.
Once that is done, then you can try flashing the kernel and see if everything works. If it doesn't, you have your answer.
Most custom ROMs are also builded just for their kernel so if u flash custom kernel then there is chance that ROM will not work as u expected. Just think about it when you are installing a custom kernel.
Today I did flash lite mode rom . It boots up but touch was not working...nothing was flashed even gapps.
Sometimes the recovery twrp too does not work.,touch lost. Now i suspect something wrong with the hardware.
But no issues with miui roms...Thats what makes me wonder
did you do it on the computer?
sibikallikkat said:
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Click to expand...
Click to collapse
You may want to try installing Radon Kernel. I've got an aftermarket display which also didn't work with a custom rom (Lineage OS), but after flashing Radon Kernel it worked flawlessly. You may want o try Radon 5.0 as I'm having trouble with 5.1.
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
xBinyWolf said:
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
Click to expand...
Click to collapse
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Retrial said:
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Click to expand...
Click to collapse
I already did and found no success, even repaired file system and did that thing of chaning in exfat2 then 4 again. Changing to Orange fox recovery solved my problem. Thank you for the reply.