Hi all. First, forgive me if this has been questioned and answered before, but I face a really BIG BIG problem with my CWM made backups...
Regardless the are created right, and restored, the restored ROM gives me android.core.gapps errors continuously, rendering the phone unusable...
Maybe it's only my phone, I don't know, maybe CWM recoveries are young on my S4 variant and have bugs...
BTW: I own an S4 LTE Advanced (GT-I9506)
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
Related
I'm getting huge delays with some push-based apps (e.g. Whatsapp) since the update when I'm on the data connection. When I'm on WiFi everything is fine.
Does anybody else have this issue?
Whatsapp delay
Yes. I'm having the same problem for a month or so. ever since I installed cyanogen 7 on my galaxy ace, no matter what i did, whatsapp messages kept on delaying. I first tried restoring a nandroid backup, didn't work. I then tried reinstalling cyanogenmod, it worked for a bit but it then start failing again so i reinstalled cyanogen and did a nandroid. It didn't work. I thought it could be something the nandroid backup did to the cell, so i reinstalled everything from the beginning: flashed the device to original stock rom then root, cwm, and cyanogen again.
The delay i noticed then was not to take on account 3 to 4 minutes the most.
But now again! i open the app and start recieving messages from hours ago. The thing is i've been using the device during the hours that i should have recieved all those messages. I don't know where can the problem come from. All I know is this didn't happen before having cyanogenmod installed, and know it does.
Does anyone have the problem above? Does anyone know of a possible solution?
Thanks in advance!
I have exactly the same problem and i don't find any solution...
Well I've changed carriers twice since I created this thread and my problem has been solved long ago by itself. Maybe the first carrier's data coverage was weak or something. Well TBH with the first carrier I rarely got 3G, I was on Edge most of the time I recommend that whoever's having this issue should check his connection.
[Solved]
I think i at last found how to solve the problem. I bought an Lg O2x and obviously installed a csustom rom, (MIUI) it all worked fine until I did a nandroid backup in order to try a new rom, which i didn't like. After trying it i restored the nandroid backup, and whatsapp started misfunctioning again. I then installed the rom from the very begining, and configured all step by step and whatsapp didn't fail since then.
Conclusion: The same problem happened in two different devices which only had in common the cwm and a nandroid backup restored, diferent rom, diferent devices, different carriers. So try flashing the device from the start or reinstalling rom from cwm. Remember to wipe data, cache, and dalvik. and remember not to restore any backups at all.
Hope this can help you!!
Has anyone else had bad experiences with CWM Touch? I started to use it in place of TWRP since it would work with Rom Manager (which is still kind of useless compared to what it was on the OG Droid) but it has screwed me over twice. The first time was I was switching ROMs so I made a backup and when I went to restore it later it said MD5 sum mismatch so I was pretty much screwed. Just now I went to try and make another backup since I had just installed Paranoid Android and had everything setup and I wanted a backup before I flashed Clemsyn's elite kernel. Knowing that I didn't have much space left I selected clean nandroid space assuming it would get rid of the previous backups, after it finished it said it was done but never brought back the UI so I had to do a hard reboot.
Upon boot up it just hung at the Google screen, I did a few more reboots and got the same thing. I went into the bootloader via the three finger method (which to my surprise worked without connecting to a USB port, so I'm assuming this is a problem with the 3rd party recoveries and not the device itself?) and selected recovery but i was stuck at the Google screen again.
Time to switch back to TWRP!
TL;DR CWM Bricked my Nexus and the backups don't work
Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance
Update: Any ROM I install... Phone and sounds do not work.
Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.
Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
Hey everyone. I recently gave my Rogers note 3 to my wife. two days later she said it was acting up, and it kept saying com.android.systemui has stopped. when I booted into CWM I couldnt do a factory reset, and it was also saying it could open a bunch of directories. I was able to use CWM to restore to an earlier restore, but even then I couldnt do a factory reset, and CWM is still saying it cant open the directories.
After talking with another modder, he has suggested that my partitions are messed up. So, if this is the case, what is my best bet? should I use odin to reflash CWM, and then flash the stock rogers rom? She's not a power user and doesnt care for root. she just wants a working phone that has a stylus pen.
I have downloaded the latest CWM .tar, but can someone please help me find the stock rogers rom? rooted or not, i dont care. I just need help as Im helping her recover from major surgery and working 18 hour days right now so im burnt out.
Thanks in advance.
[SOLVED]
I was able to format the cache from CWM finally. Errors are all gone.