i have problem in installing custom roms in xperia s. I have unlocked the bootloader. i tried install paranoid 4.6 beta4, carbon-kk-unofficail and pure AOSP lollipop. All roms installed as per the instruction, but every time i got bootloop in all roms. In case of paranoid 4.6 beta4, i flash kernal which included in rom, than flash rom, after that phone boot correctly and rom runs fine, but wen i restart phone get bootloop then no CWM and no rom. In all that case i flash stock rom using flashtool to get work back and try different rom like carbon or pure aosp lollipop, but no luck. Roms which is not required unlock bootloader runs fine. i was using trinity vengence rom, which was running smoothly. before that i was on Ultimate BlackXS Ultra v1, which also runs fine but not stable. Currently i am on trinity vengence, ULB, rooted.
dxavinash said:
i have problem in installing custom roms in xperia s. I have unlocked the bootloader. i tried install paranoid 4.6 beta4, carbon-kk-unofficail and pure AOSP lollipop. All roms installed as per the instruction, but every time i got bootloop in all roms. In case of paranoid 4.6 beta4, i flash kernal which included in rom, than flash rom, after that phone boot correctly and rom runs fine, but wen i restart phone get bootloop then no CWM and no rom. In all that case i flash stock rom using flashtool to get work back and try different rom like carbon or pure aosp lollipop, but no luck. Roms which is not required unlock bootloader runs fine. i was using trinity vengence rom, which was running smoothly. before that i was on Ultimate BlackXS Ultra v1, which also runs fine but not stable. Currently i am on trinity vengence, ULB, rooted.
Click to expand...
Click to collapse
By bootloop do You mean stuck at boot animation or at Sony logo?
Following cases are normal:
1. 1st boot : It will continuously show You the boot animation for about 10-15 minutes. This is normal as the apps are getting settled in background.
2nd boot: will be stuck at Sony logo for 10 minutes. This is also normal. It is some kinda bug, but phone start after 10 minutes or so.
I installed both roms carbon and paranoid 4.6 beta4 properly, but pure AOSP lollipop not installed, got blank screen after flashing rom and kernel.
Related
I was running PACrom perfectly fine, I made a TWRP backup. I was trying to install AOKP 4.2.2 (which appeared to be successfully installed) and now my phone is bootlooping at the "Sony Turbo" logo, or it hangs there. I can't seem to reboot in to TWRP recovery either (power + VOL up at blue led). I tried reflashing the kernel in using fastboot tool but still the same result. Can't figure out what's wrong :/
Have unlocked BL w/o fastboot menu.
EDIT1: I also tried flashing the stock FTF for the R800a (4.0.2.A.0.42), and it's still stuck at the exact same screen (Sony Turbo logo). Which leads me to believe that it did not even flash the stock kernel.
EDIT2: Alright, nothing was working. So I decided to use the Sony PC Companion to "repair" my device. It's working now booting in to the OS (2.3.4), so I'm gonna try reflashing Turbo Kernel 3.1 and see if I still can't boot in to recovery.
EDIT3: Reflashed Turbo Kernel 3.1 successfully using FTF and Flashtool and am back on PACrom
pm2gonzales said:
I was running PACrom perfectly fine, I made a TWRP backup. I was trying to install AOKP 4.2.2 (which appeared to be successfully installed) and now my phone is bootlooping at the "Sony Turbo" logo, or it hangs there. I can't seem to reboot in to TWRP recovery either (power + VOL up at blue led). I tried reflashing the kernel in using fastboot tool but still the same result. Can't figure out what's wrong :/
Have unlocked BL w/o fastboot menu.
EDIT1: I also tried flashing the stock FTF for the R800a (4.0.2.A.0.42), and it's still stuck at the exact same screen (Sony Turbo logo). Which leads me to believe that it did not even flash the stock kernel.
EDIT2: Alright, nothing was working. So I decided to use the Sony PC Companion to "repair" my device. It's working now booting in to the OS (2.3.4), so I'm gonna try reflashing Turbo Kernel 3.1 and see if I still can't boot in to recovery.
EDIT3: Reflashed Turbo Kernel 3.1 successfully using FTF and Flashtool and am back on PACrom
Click to expand...
Click to collapse
Bro.. as far as I Know.. I am Using AOKP 4.1.2 .. and their is NO Version of AOKP 4.2.2 at all.. is that a typo.. or did u try to Install a ROM from the AOKP site which was not compatible at all..
Cuz I am using Turbo Kernel 3.1.. on AOKP 4.1.2 .. go here and check out my post.. might answer some of your questions.. with screen shots..
http://forum.xda-developers.com/showthread.php?t=1852529&page=48
EDIT 1.. if you try AOKP Once.. you wont go back to any other JB ROM again.. Its just amazing.
I have a boot loop problem when installing CM10.2, CM11, PAC ROMs on N7100.
I did every possible wipe and yet boot looping in animation.
The recovery is TWRP latest.
Is it a problem with the new bootloader with 4.3? I'm using it with Criskelo ROM and it works well.
Should I downgrade to the old bootloader? How?
Thanks
Ok im fed up trying different roms and always get stuck at rom's boot logo.
First of all my device details found in info app. (im using dn4 v2 rom at the moment)
Current baseband: ddufnd1
Using TWRP 2.8.3.0
Samsung GT-N7100
Bootloader : N7100XXUFND3
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x3
CPU part: 0xc09
CPU revision: 0
Now the problem:
im not able to get passed the boot logo of following roms which i checked.
CM11 official latest snapshot
Omni rom latest kk nightly
probam kk
Diamond rom 8
Omega rom latest
And some others.
All of them just get stuck at rom's boot logo and never go forward even i waited 2 hours :/
And i have a backed up stock rom that also dont boot when i restore from twrp. It was backed up by same twrp. It also get stuck at boot logo
And now there is are some roms which always work for me.
DN4 rom
some jellybean roms
Never tried any lollypop rom so not sure abt them.
But i want cm11 or omni kk rom. And both not working.
I will really appreciate if someone can tell me what is wrong with my device???
And give solution to it too.
Sent from my GT-N7100
i always clean install those roms, wipe everything except extsd and then installed those roms,
so don't say to clean install, i'm not a noob in installing roms.
Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.
I can't get my GT-N7100 to boot any Android 7.1 custom rom.
I used to install lots of roms earlier like Android 5,6 custom roms, then I went back to rooted stock again a few months ago.
Recently I tried to install Android 7.1 with the traditional steps: wiping everything (system/data/cache/dalvik/internal storage) then I install the rom and gapps, but I couldn't get any rom to boot. They all stuck on the rom boot logo playing without proceeding to the rom itself. Yet, when I restore my twrp backup of the stock rom it works fine.
I even tried to install android 6 yet it didn't boot as it used to do before, the same logo stuck thing happens without any progress.
Any idea how to fix that ? what could be the reason behind that ?
Should I reinstall a stock rom and re-root it again?
I can't find a good reason for what I have regarding that problem.
I have: GT-N7100 with the following:
OS: wesam.othman ROM 4.4.2 stock rooted rom.
Recovery: twrp 3.0.2
Kernel: AGNi pureSTOCK N7100
Boot loader version: N7100XXUEMJ5
SD Card: 32 GB
I'm using a script that swaps storage so I have nothing on my device internal storage.
Thanks in advance.
Fixed by doing the following:
Installing an original 4.1.2 stock unrooted rom.
re-rooting again using cf auto root.
installing custom recovery
installing a 4.4.2 modem
then finally installing the 7.1 rom