I'm on cyanogenmod7 nightly build 4 and trying to update to build 5 but the download finishes in less than a second and installs and pretty much wipes everything and most functions disappear. Obviously something is wrong with Rom manager. Any ideas?
Related
i finally broke down and rooted my Tbolt. I installed Rom manager and am trying to install a new rom. I have tried cyanogenmod 7.1.1 and also Liquid smooth 3.2 . the process seemed to go fine, but each time it got stuck at the splash screen,not the white HTC one, but the "intro" screen for the rom i am installing, i let it run for several minutes, finally removed battery and restored my backup.
anything i am doing wrong?
here is some more info on the phone,
Downgraded to 2.3.4 , rooted with revolutionary root, running the most current free version of Rom manager free from market
any help would be appreciated
First thought
Have you wiped the data of the phone before you tried to install the ROM? I am now expert here but I had a similar problem and when I searched forums for the answer that came up quite a bit. I might start there.
Also the ROMs have very specific install instructions and I would follow them closely to avoid any problems.
I searched and read so much before I rooted and installed my first ROM, it does get easier.
Good luck.
Update your CWM version in ROM manager.
It should be the top choice when you open ROM Manager - update Clockwork Recovery.
Make sure you have ample space on a FAT32 formatted SD card, as well a the minimum radio(s) required for CM.
Prior to flash, in recovery, make sure you wipe data/factory reset and clear cache - also go into advanced and format system.
Post back your results and we'll go from there.
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
I have 2 of the same phones (i747M with twrp 2.7.1 for d2att installed)
On one, everything worked flawlessly (the older one)
On the other, I had to talk to a developer of twrp to get twrp working...
Now I just realized that the camera app isn't working. It works fine when I restore to the touchwiz stock rom.
I tried wiping my entire device before installing the new stable build 6 rom for d2lte. I also tried flashing the weekly roms for that device on both phones
the result is the same: camera works fine on the older phone while on the newer one, it doesn't
Someone suggested that this might be a hardware issue.. Basically, the TWRP guys fixed my other problem by pulling the latest cyanogenmod build and compiling a recovery. -So I'm wondering if something can be done to make my camera work again on my new phone...
(Before all of this, I of course tried rebooting, closing other apps, clearing data, etc...)
Update: I tried flashing the latest cyanogenmod nightly (June 30) and the camera app worked, but I prefer slimrom
Another update: all the bug report shows when I reproduce the error is
Device: Slim-d2lte-4.4.4.build.6-OFFICIAL-5242
Kernel: 3.4.95-cyanogenmod-gd56ed95 [email protected] #1
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2
Hello and thank you for viewing my thread!
To start, my device is the OnePlus One, and i am running the latest Release of CyanogenMod 13 with the Latest Lightning Kernel for it's kexec/hardboot patch
I have tried multiple times, installing the multirom files, as well as flashing a factory image and flashing from a fresh install. Nothing seems to work.
The exact problem would be, even after performing the inject boot sector action, multiboot or the boot menu fails to appear.
I have no idea how to view kernel logs or anything of the sort. However i will gladly provide any logs or files if needed! Ill just have to figure them out is all.
Any help is greatly appreciated. Thank you in advance!
Edit:
1. I think i have the kernel ruled out as the problem as i have already tried a modified stock kernel, as well as bouffla's kernel.
2. The rom also doesnt seem to be the problem as i have tried both COS 12.1 and CM 13
3. The recovery seems to be ruled out as well. I rolled back to a previous version of TWRP and still have the same issue, no multiboot menu after proper installation.
4. This is really confusing. I even tried using the files built into the multirom manager application and that fails as well.
P.S. (on a semi-unrelated note)
I currently have a strong feeling it is a very low level issue (at least for my experience) due to the fact that kali nethunter is also failing to install and causing my device to brick every time i attempt an install.