Hi there, i'm writing this in hopes of someone reading it who give me some pointers.
i was running for the last years on CM 10.2.1 but i thought it was time for an update. update to CM 11.2 worked but my installed apps were making some weird troubles so i decided to do a factory reset and there my trouble started.
i flashed to boot.img in fastboot, cleared cache with fastboot cmd
format \system, \data, \cache and of course dalvik
flashed rom CM 11.2 (from official cyanogenmod site) via recovery sideload
rebooted and as my thread title says was stuck on CM boot sequence
i tried different CM roms, but always the same result. system wont end the bootup.
i even suspected a problem with CMW v6.0.4.8 and flashed TWRP from the CM 12.1 thread here in the forum.
so in short i can flash boot.img, recovery, different roms but in the end can't get it to work.
i would really appreciate some hints what i could do differently or maybe were i go wrong.
if you need more info i'm happy to supply them to you.
Thanks in advance.
solved by installing a TWRP backup and boot.img what i found on a german android site.
i was also able after that to install CM 12.1 unofficial and its running now. but i'm totally stumped what caused this weird problem to begin with. doesn't really matter now, i'm relieved it worked in the end.
Related
Hey guys!
Since I tried building Firefox OS -Boot2Gecko- on my Samsung Galaxy S2 (i9100) (FYI: I followed this walkthrough) , I'm having quite a hard time making my phone boot on any ROM I try to install. I still have an access to CWM Recovery and to the Download mode
* After failing to flash B2G's Gaia on my phone, I tried to flash the kernel back to the original one and to restore the CM 10.1 NIGHTLY backup I made before doing all this mess. No changes: stuck at CM's boot screen.
* Tried to get back to a stock firmware and ROM, stucks at boot screen ("Samsung Galaxy S II GT-I9100" screen), even after a wipe data/factory reset, wipe cache and wipe dalvik cache.
(In fact, I achieved to boot on a stock ROM once, but after some other manipulations to get my CM 10.1 back, I now can't get it to boot on any of them anymore.)
* I tried to follow the rooting + CyanogenMod walkthrough on CM's wiki, but the same happens: stucks on boot screen. However, after a wipe data, I reach CM's boot animation, which runs indefinitely.
* Right now I tried flashing with Siyah's Kernel, since the flash counter is not any of my concerns anymore. Whatever I try, I can't get anything to get past the "Booting the primary ROM" message.
However, I installed a stable CM9 on the secondary ROM and... it actually works. But even when cloning 2nd ROM to the 1st ROM, can't get the first to boot anyway.
I am not an expert in Android OS architecture, but could it be related to some kind of modifications made by B2G's build & flashing? Maybe some files in the /data or /system partitions have been altered and are not replaced when fllashing, leading to ROMs not loading up?
Any advice on this is welcome.
PS: English is not my main language, sorry if things aren't explained clearly. Tell me if you need any clarifications about it!
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
Sakujou_Kei said:
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Click to expand...
Click to collapse
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
TheATHEiST said:
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=1363738 (Kernel) and this one http://forum.xda-developers.com/showthread.php?t=2100558&highlight=script (ROM) ?
Ok so I tried the cleaning scripts I linked on my previous message, no changes. I can still boot on Siyah's second ROM, but can't get past the "Booting primary ROM" message.
Ideas anyone?
Some months ago I was flashing nightly and non stable zip. If you loose AOSP keyboard, Ok. At some point, after IOKP 4.3.1. flash, not beanstalk or even hellkat which I could not install, ALL ROM FAILED, all gapps idem.I only had a backup of IOKP and it isntall. TWRP 2.6.4.0 .img flashed by Odin 1.85 saved me once.
This time I felt unstability over several processes and only gave one order, reboot recovery. It all blaked, samsung in an out
Tried .tar of phielz touch, CMW. TWRP above refered showed itself but whem I thought the backup was over, it seems the OS was missing...
Now after flashing The new version of TWRP for t0lte I got nothing.
I know nothing of programming, code or whatsoever.
If somebody could give some suggestions that can help...:crying:
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on.
i tried the recovery through adb but it is not able to access my sd card where the recovery is installed.
am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling.
it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
rajesh.rajkot said:
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on.
i tried the recovery through adb but it is not able to access my sd card where the recovery is installed.
am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling.
it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
Click to expand...
Click to collapse
CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Ujwal Agrawal said:
CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Click to expand...
Click to collapse
Thanks Ujwal. appreciate your help. but at present it is not accessing my sdcard because of this bug. so nothing happens after i select recovery option in boot loader screen. so i may not be able to flash or clear cache or anything. can you please guide me how to install any newer rom or i might even install the stock cm13 which is still with me and was working fine till i installed the nightly update. please explain me how to install back cm 13 or any newer rom, please.
Could you go to twrp?
Have you tried to flash twrp using fastboot?
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Swarion said:
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Click to expand...
Click to collapse
Please follow one of the guides available, like this one, or the one in my signature.
You have to be aware that twrp 3 requires kernel isorec support, so you must have a kernel that supports isorec, and also you must have a 1GB system partition to be able to install any nogut or mm rom.
thank you so much managed to find this guide before you answered.
anyway thanks so much my s2 is running lineage smoothly and now we saved some piece of electronics of garbage to early the planet and me are thanking you so much for every one having the same problem as me go with philz touch recovery and then flash the twrp you want from there
all the best
Help!
I'm trying out a series of ROMs and now am faced with a puzzle. After wiping CM13 (system and all), I'm trying to flash an @amaces AOSP Marshmallow build, but TWRP is giving me grief saying it can't flash an older OS over a newer one.
It says the previous CM13 OS was dated 2017 (I don't think so....) while the one I am trying to flash is dated 2016 (yes, the @amaces ROM was posted in 2016).
So...I thought I had truly wiped the system. How can it know anything about a "previous" ROM?
Edit: Ugh. So I think this is because the CM12 and CM13 ROMs changed the partition table? Or they changed something and I need to get back to stock. Unfortunately my stock backup is gone (8gb). I've looked at all the various restores and they rely on files that no longer exist or are behind so many layers of pop-ups and -unders that it doesn't seem safe to wait and hope the download will eventually start. Succulent has a series of flashable zips to "restore" a tablet to stock, but if there has been a partition change, will his zips fix that?! I have the nooktablet_1_4_3_update.zip, but have no idea if that is even useful. It certainly can't be flashed with CWM or TWRP.
Edit-Edit: OK, I learned something(s). Apparently the issue was the version of TWRP I was using. I tried an older version and I was able to flash one of @amaces ROMs, but I also did manage to take the tablet back to stock using nooktablet_1_4_3_update.zip. It turns out that you can't flash that successfully with TWRP--at least not the versions I had. But I did have CWM 6.0.5.1 from succulent as altboot on my SD card. That was able to flash the zip and restore to stock. Good to know since everything else is gone. And, yes this time I also made a CWM stock backup and put it somewhere safe