Hi
I installed Thiaz ROM and the ICS theme which there is a link to on his V2.4 page. All was running fine and dandy for a day. I installed all of my programs, apps, etc, and used App2SD to move some of them to the SD. Each time I did this, it said 'failed' the first time and then allowed them to be moved on the next. I rebooted the phone a couple of times and never had any problems. After I had got things set up as I wanted them, I rebooted into CWM and did a new backup. I then rebooted and went into bootloop.
Cleared data, dalvik and even battery stats. Tried fixing permissions. Nothing worked at all, still boot loop. Did a factory reset and restored the backup and still bootloops.
If I restore to the original backup from when I first put on the ROM (no ICS theme), it works OK. Then after a few hours and after I have turned on and off successfully a few times, I get the old bootloop again. I have not messed around with any system files, etc. One time it was after I moved a file with File Expert but I uninstalled that programme and haven't used since.
Any help or suggestions would be very gratefully received as I don't really want to go back to the stock V21a but I can't be doing with setting up everything on my phone from scratch every day either!
I hope someone can help me.
Related
Alright, so here's the issue. I searched and could not find anything close to this...
I have stock JH7 installed. Installed Clockwork (via Rom Manager,) backed up my ROM, Metamorphed a theme, didn't like the theme, tried to use Clockwork to restore from my backup. Clockwork would go through all of the files, but when it gets to "ReceivedFiles," it just hangs. I let it run through the night, approximately 5 hours, and in the morning it was still in the restore process at this same step. I knew something was wrong, so I unplugged, removed battery, and booted it up. My phone just sat at the Galaxy 'S' screen and would not start up.
After several more attempts with 2 different backups (always hanging at the same place) I finally wiped data, cache, & dalvik cach, then booted it up. All was well and working stock. Then I shut down, booted into recovery, opened Clockwork, and attempted to restore again. My phone is currently sitting at the same step as before.
Any clues? I've attached a picture of its screen.
Did you pull the battery out? Mine is stuck as well....was updating to Serendipity 5.1.
Finding update package...
Opening update package...
installing update....
And it's been there for over half hour
I pulled it and can get back in the phone just fine. It seems to still get stuck there though.
So I got my continuum 3 weeks ago, first Droid phone. Decided to root, took me about 5 hours finally figured it out using SuperOneClick.
Wanted to check out some custom ROM's so I plugged my USB cable in and transfered the .zip file to my sd card and booted into cwr and tried to install the .zip from the sd card and rebooted, nothing was different or had changed. Did that a few times and realized that I hadn't wiped user data or cache or delvik so I did that all in the cwr and installed to .zip rom and rebooted.
This time when I rebooted a few things were different. All of my apps were in alphabetical order, the home screen was back to stock except for my background was one I had just installed. My contacts were gone (thank God I backed them up).
So I rebooted again.... hung at Samsung logo....
I had also put the Peanut Butter Jelly time kernal on my sd card out of luck I installed that and rebooted. This time everything was the same as my previous horror boot except all of my apps that were set to run on boot fc'ed and all of the other apps that I have are just icons. None of them open or they do and fc. Market will not open. My phone is a phone and a camera and the browser works.
I am very new to droid but learn quickly. I cannot post on the continuum dev threads because I am a noob. Hopefully one of the continuum devs will see this and know what to do to help.
Thanks a ton, I do not mind donating for help.
I'm just gunna give you the whole story.
I'm using TWRP Recovery.
I'm coming back to my d2vzw after a couple weeks of not using it (I got a different phone through work). I'm now back to using my GS3. I decided to update to the latest ROM version. I installed the slimROM stable that was just released, it was slow and they animations were choppy (which is really weird for slim). So I decided to try a different ROM. I've used carbon before, and I really like active display and HALO, so I decided to install that. It installed just fine, installed all my apps, rebooted. It froze on the initial splash screen, didn't even get to the boot animation. So I figured it was just a bad install, so I formatted and flashed from my external SD. Again, first boot just fine, then froze on second boot. So I put a https://plus.google.com/+AlexKruger/posts/dJGXsrAZvj4 in the ROM's community. They suggested that it might be a bug from installing it from my external. So I formatted, then moved the files over to internal, and flashed again. It booted fine, I got to the home screen and restarted before I did anything else. Froze, again. Then someone suggested, that I format, install it, boot all the way, reboot into recovery, wipe cache/dalvik and dirty flash from internal storage. Did it, froze on reboot. So I formatted one more time, and went to boot into recovery while figured out what to do, I accidentally booted into the system. It booted just fine, I went through the set up and activation screens, and it worked. So I rebooted, froze. Then someone suggested I switch recoveries, so I installed the latest CWM recovery, and tried everything all over again, still freezes on reboot.
I know I could just use a different ROM, but it's gotten to the point that I need to fix it. I want to get it to work because F*** you.
Please any help would be appreciated. Thank you.
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
Somehow my phone is bricked, although I still am not sure if it's because I actually did something wrong or it just decided to brick itself out of spite. Here's the rundown of events:
This past August I rooted my phone and installed cm-10.2. I made a backup of the stock rom beforehand (which for some reason is dated from 1970). Since then there have been a bunch of bugs, but nothing super major.
Today I decided to upgrade to cm-11, so I backed up everything important to my PC and used the auto-updater. I got a Status 7 error and the installation didn't complete, and I got stuck in a reboot loop that kept returning me only to the bootloader. I read on another forum that the problem was probably my CWM version (6.0.1.2 instead of 6.0.1.3). Anyway, I tried restoring one of my backups, but the bootloader said the folder was empty and no backups were found. I ended up reinstalling cm-10.2 and gapps from the same zip files I used months ago. This let me properly boot up my phone, but for some reason the google play store still wasn't working. I did a simple reboot and it started working again, so I downloaded rom manager and updated cwm. Rebooted into bootloader, made another rom backup, and tried again to install cm-11. Same error, install aborted. This time, however, my backups magically reappeared (along with an extra mystery backup that had today's timestamp but was ~10 hours in the future), so I restored the original (1970, stock rom). Things boot up fine.
I decide to try installing cm-11 one more time because at this point I assume that if it fails again I can safely restore a backup or at the very least reinstall cm-10.2. It fails again, but this time, when I try restoring any of my cm-10.2 backups I get a DM5 mismatch error and it immediately stops. Restoring 1970 is different, it starts recovering but then halfway through says "error restoring /system" or something like that. So now I'm left with no choice but to reinstall cm-10.2 from the same zip file again. Only this time, booting up only shows the cyanogenmod logo forever. I go back into bootloader and my backups are once again suddenly not recognized. I make a new backup of my broken phone to see if it will make the folder show up. I reboot, and now that new backup is the only one that does show up. Trying to restore gives me a DM5 error. I've now tried reinstalling cm-10.2 several times, but my phone will never get past the cyanogenmod logo. I'm out of ideas for how to get my phone to work.
My questions:
1. Any idea how to unbrick my phone? I have not done any factory resetting because I was worried it would erase my backups and also I don't really see how it would help.
2. Does anyone have a backup image I could use? I don't have mine stored anywhere but on my phone's internal SD, but I could maybe try loading one from my external SD if I had one.
3. What did I do wrong here? From my viewpoint it seems I basically tried the same thing twice and got different results. Is there something I'm missing?
4. If I get a new photon q, how the hell should I go about installing cm-11? I know people have gotten it to work before. Which version are you using?
Thanks for any and all help
I'm guessing you don't have a backup of stock?
Have you tried restoring stock everything using RSD Lite?
Also, how long have you let the phone sit? If the phone requires a 'fsck' (file system check) on you /data partition, you could be waiting for an hour or more at the boot animation.
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
DRH48 said:
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
Click to expand...
Click to collapse
See this thread for information on how to restore stock... always a good idea to know how to reset the phone back to a complete stock configuration