Hi guys,
I have the folloeing problem. I got a Samsung Galaxy S 2 from a friend, so now I wanted to root the device and install CM 10.1.3.
I tried this now serveral times with different kernels but always got stuck in the end when I flashed CM and rebooted. Then my phone always tried to boot CM but did not go futhere as the circling Cyanogenmod sign. (If you know what I mean)
I tried flashing my phone with: (Odin)
Rom: I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME
Kernel: PhilZ-cwm6-XWLSD-OXX-4.93.6-signed; PhilZ-cwm6-XWMS2-MOT-5.15.9; Kernel_Dorimanx-V8.43-[12-21]-[24-10]-TAR-FOR-ODIN
After resetting the Flash Counter with Triangle Away, I always installed CM 10.1.3 and gapps through "installing from internal SD". I also alwys wiped my cache
Is there anybody who can help me and explain me what I am doing wrong? I am still pretty new to rooting and flashing custom software
Thanks for your help!
Is there nobody who can tell me wethere I am doing something wrong?
Related
This morning as took my tablet the screen did not switch on, i tried to reboot then it stuck on bootanimation, then i tried to wipe; it still stuck on
bootanimation. Next I tried a complete wipe and installed a new Rom --> same Problem only goes to the bootanimation.
Then I tried to flash with odin, it tells me "complete write operation failed" and err:0x4. Nvflash isn't working too. So what can I do. I was on CM 10.1 nightly before, and evertything worked very well till this morning. I still can go to Download mode but twrp is not working anymore.
Thanks in advance in sorry about my poor english.
Regards.
Maybe the last edit will give you a hint:
http://forum.xda-developers.com/showthread.php?t=1276873
@dvb127 This morning the same happend to my Tablet. Could you find a way to fix it?
I have been running a CM-Version of january and switched to nightlies a couple of days ago. I can't remember anything else I changed
What I tried: flashed a new version of CWM (6.0.3.2) via ODIN and installed the january & newest CM via CWM. Both worked fine.
Still the same problem. When I boot the tablet it reboots several times and gets stuck in the CM bootanimation. Factoryreset and wiping /data causes a reboot.
NetZwerg said:
@dvb127 This morning the same happend to my Tablet. Could you find a way to fix it?
I have been running a CM-Version of january and switched to nightlies a couple of days ago. I can't remember anything else I changed
What I tried: flashed a new version of CWM (6.0.3.2) via ODIN and installed the january & newest CM via CWM. Both worked fine.
Still the same problem. When I boot the tablet it reboots several times and gets stuck in the CM bootanimation. Factoryreset and wiping /data causes a reboot.
Click to expand...
Click to collapse
I flashed a Stock Rom with Odin first, i had to too this in a win XP PC, because it didn't work in win8, rooted again, now I'm in cm again without any pproblems.
Hey, thanks a lot - worked for me as well
Hi All,
I've been having issues trying to install the CyanAOSP rom on my vibrant. It originally said the partition isn't compatible, but to click update again to install. I assumed it would re-partition for me. Anyway, i've booted to recovery, wiped everything, installed the zip and it just almost instantly goes to the samsung vibrant boot screen.
I've had to Odin back to stock twice now. Any help would be appreciated.
Thanks
Hi i kind of bricked my Mediapad 7 when tring to update Cyangen 10.2 to Cyangen 11. Need some help how to proceed.
First i booted into TWRP and tried to install the file
S7-301u V100R002C232B005 ICS Android 4.0.3 General Version.zip
to go back from Cyano 10.2 to stock rom 4.0.3. But this failed.
So i directly installed
cm-11-20140118-UNOFFICIAL-hws7300u.zip
Installation went OK. No, i didn't do a backup of the installed 10.2.
After reboot, the device is not booting but always going back to TWRP. What can i do?
What i tried in TWRP so far:
Reinstalling cm-11-20140118-UNOFFICIAL-hws7300u.zip
Reinstalling cm-10.1-20130526-UNOFFICIAL-hws7300u.zip
Wipe Cache
Factory Reset
Nothing helps. Always booting into TWRP v2.3.2.3 :crying:
Thanx for any help how to resolve this!
Forgot: During install of firmware there is a log-line:
E. Unknown File System: 'datamedia'
no slash between data and media
Solved
Solved it.
- Went back to stock recovery with "Auto_recovery_installer_for_huawei_mediapad"
- installed 4.0.3
- then installes cyanogen 11 with twrp
pillepalle555 said:
Solved it.
- Went back to stock recovery with "Auto_recovery_installer_for_huawei_mediapad"
- installed 4.0.3
- then installes cyanogen 11 with twrp
Click to expand...
Click to collapse
I had the problem of not being able to reinstall a stock rom as well.
How EXACTLY did you do it for the stock one?
I've also found out from a CM developer that stock roms can't be installed with the custom recoveries like TWRP or CWM.
Which is a nice thing to know since there doesn't seem to be any info on the forums about that.
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.
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.