Hi,
I've been using cyanogen mod 9 without any issues. recently i upgraded to cyanogen mod 9.1 and have been noticing minor glitches. nothing to be worried about. Recently i used Bluetooth to share files ( have used it before). when i powered off the Bluetooth it rebooted and is now stuck at boot animation. Also cannot connect to my PC. any suggestions or workaround to the problem? would be appreciated.
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
MistahBungle said:
Restore backup, reflash kernel and/or rom (boot into recovery, or factory reset (in that order). Or if none of those things are a goer, back to stock via Odin try those steps (try to restore backup first if you have one, if not reflash CM & if you get bootloop or whatever after a clean install of CM, factory reset).
Click to expand...
Click to collapse
I'm sure there is a bug in Bluetooth implementation in mod 9.1. I did a cache wipe, after that it was stuck in another kind of loop. rebooted normally, immediately Bluetooth turns on and it reboots again.
how do i reboot into recovery? previously i was using adb for that. i restored backup ( it was of mod 9) now it wont even boot.
ok. so i finally managed to get it working. i had accidentally restored mod 9 backup onto mod 9.1 so i used odin to flash ClockworkMod-Recovery_5.5.0.4 booted and now i'm back to a month older backup. Oh well since i have to restore my settings anyway why not try mod 10.1?
Related
so one fine day, stupid me went to install miui without doing a factory reset. then i realised the mistake, did it, and reflashed. the rom seemed laggy, so i decided to return to my previous installation of donuthd (i did flash doomkernel again)
i had an nandroid backup, so i restored, and everything worked fine except that there was no reception and "com.android.phone" keeps "failing". then i decide to try a fresh install, so i entered cwm, wiped everything, and flashed rom only to have the installation abort due to some incompatibility issue with cwm and the x10. i realised i had to have xrecovery, so i installed it again (even though i was sure i had it already) but it continued to boot into cwm, and i could only boot into xrec with my sd card removed, which is stupid because i cant flash anything then.
now, for some reason, after repeated restore attempts, my x10 is now stuck at the bootup screen (doomkernel) and refuses to go further. i accidentally deleted my nandroid restores (-.-, i know) so i cant restore anything, and i cant reflash the rom because cwm wont work.
in this case, do i reflash a stock ftf file? or...?
tangosierra_ said:
so one fine day, stupid me went to install miui without doing a factory reset. then i realised the mistake, did it, and reflashed. the rom seemed laggy, so i decided to return to my previous installation of donuthd (i did flash doomkernel again)
i had an nandroid backup, so i restored, and everything worked fine except that there was no reception and "com.android.phone" keeps "failing". then i decide to try a fresh install, so i entered cwm, wiped everything, and flashed rom only to have the installation abort due to some incompatibility issue with cwm and the x10. i realised i had to have xrecovery, so i installed it again (even though i was sure i had it already) but it continued to boot into cwm, and i could only boot into xrec with my sd card removed, which is stupid because i cant flash anything then.
now, for some reason, after repeated restore attempts, my x10 is now stuck at the bootup screen (doomkernel) and refuses to go further. i accidentally deleted my nandroid restores (-.-, i know) so i cant restore anything, and i cant reflash the rom because cwm wont work.
in this case, do i reflash a stock ftf file? or...?
Click to expand...
Click to collapse
try doomlords bootmanager v2. It has both xrec and cwm.
Press the menu button(left side) on the blue led colour and select xrecvory and install stock based roms.
if it doesnt work flash stock firmware via flashtool. Links can be found in my thread here: http://forum.xda-developers.com/showthread.php?t=1749426
tangosierra_ said:
so one fine day, stupid me went to install miui without doing a factory reset. then i realised the mistake, did it, and reflashed. the rom seemed laggy, so i decided to return to my previous installation of donuthd (i did flash doomkernel again)
i had an nandroid backup, so i restored, and everything worked fine except that there was no reception and "com.android.phone" keeps "failing". then i decide to try a fresh install, so i entered cwm, wiped everything, and flashed rom only to have the installation abort due to some incompatibility issue with cwm and the x10. i realised i had to have xrecovery, so i installed it again (even though i was sure i had it already) but it continued to boot into cwm, and i could only boot into xrec with my sd card removed, which is stupid because i cant flash anything then.
now, for some reason, after repeated restore attempts, my x10 is now stuck at the bootup screen (doomkernel) and refuses to go further. i accidentally deleted my nandroid restores (-.-, i know) so i cant restore anything, and i cant reflash the rom because cwm wont work.
in this case, do i reflash a stock ftf file? or...?
Click to expand...
Click to collapse
Try to flash some xRecovery kernel only (e.g. stock one) or flash just for now some of the fxp-based ROM's (via CWM)
Hi!
First of all, to give you some infos: I am runing the latest nightly CM11 on my LG G Pad 8.3 V500 and have the latest TWRP installed.
I was experimenting with a stupid app called LCDDensity for root (I am a noob and should not have done that) and it caused my G Pad to be stuck in a bootloop. I was able to boot into TWRP and the first thing I did was to make a complete backup. I then tried to wipe cache and dalvik cache but the device was still stuck in the bootloop. This was the point were I did not know what elso to do and so I wiped everything and installed the latest nightly (I was running a previous version when the bootloop happend). Everything is working again and I am on the latest version now, but all my data is gone of course.
My Questions are:
If I restore the backup I made when the device was stuck in the bootloop, will this then cause a bootloop again, or can I savely restore the backup? I don't know if that makes any sense, but I am afraid to restore corrupt data somehow.
Second Qustion is a noob question out of couriosity: What else could I have done to get the device to boot up again?
Thanks for your help!
What I would do if I were you
Wipe all
Restore nandroid of bootlooping ROM
Wipe cache + dalvik
Flash the same ROM on top of this nandroid
Reboot
Should easily fix your density issue
May even be able to just flash kernel (as opposed to whole ROM)
If this were me, chances are this app just changes build.prop to change dpi
So I would boot to recovery
adb pull the build.prop and edit it back to normal then push it back and change permissions and then reboot
Future reference
Noob mistakes happen to all at some point, experimenting is good, just always make a nandroid first!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hello,
I kinda have the same issue. I downloaded SuperSU while on CM13. And when I installed it it went into TWRP and after the installation there was the bootloop. I made a backup (while in bootloop) and I don't want to make a factory reset.
It's been a long time since I've done a backup (except the one in bootloop) so I can't restore.
Can I fix this with the adb (which I don't know how to use it) or can I make a factory reset then restore the backup or will it go into bootloop again ?
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
tshuford said:
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
Click to expand...
Click to collapse
I've had some issues before regarding actions within the CWM on my d2vzw. I got rid of CWM and installed TWRP 3.0.2-0. I was then able to do much more.
I had also read somewhere that CWM is an abandoned project and TWRP is kept current and is also recommended by Cyanogenmod for all their ROM's and other flashable files.
The link for the d2vzw TWRP is https://dl.twrp.me/d2vzw/
Good luck!
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.