[Q] Problem with installing ROM - Galaxy Tab 2 General

I have been running my 3113 on CyanogenMod 10 and decided to try RomsWell. Downloaded the file and went into recovery to install, wiped data, and now it seems to be stuck. I have these messages on the screen currently:
Starting Install
Installing Data
Installing System
System Install Takes A Moment or Two or Maybe Even Three
Creating symlinks
Setting Perms
Been sitting here for about 15 minutes with no progress in the progress bar under the android dude. Any ideas on how to salvage this?
Thanks

Think I got it working. Thanks

Related

G1 constantly loading data

hi guys,
i tried to change my gmail email just now and in an attempt tried the original method of factory reset.. i am running the CM4.0.4 ROM and that did nothing but i eventually figured out how to change the email..but ever since i did the factory reset the phone has been showing in the notification bar:
ongoing:
loading data, please wait
this has been going on for about an hour now...i have apps2sd working but all my apps run fine even after the reset.
any way to get to go away? thanks
Same here. I'm getting it on Cyan 4.1.11.1. This was on a brand new setup meaning ext wipe and phone wipe. Mod, should this question be moved to the Q&A section? I am looking into the issue. I think it may have something to do with My Backup Pro but I can't confirm this. It happened to me after using that app as well as when I did a bulk install via adb.
Run fix_permissions
Running a fix_permissions in console seems to have fixed the problem.

Problem: Android refuse to open 'Manage Application'-menu item

Hi all,
I have a problem on my HD2 with CyanogenMod 7 (v 2.6)
When installing it on my phone everything was working perfectly.
but now... 4 months later, when i go to the menu, browse to Applications, and pressing Manage Applications or Active Services, the menu fades away, and returning to the Applications menu, there is no way of going into that menu.
Rebooting doesn't give any solution.
Does anyone recognize this issue, or know how to fix it?
Alright, Do you use CWM?
Do a backup.
Wipe Cache,
Under advanced:
Wipe Dalvik-Cache, Fix permissions.
Try again, booting will take longer, explanation by Cyanogen:
When Android starts up, the DalvikVM looks thru all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimize the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimized bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's reoptimized and the cache is updated.
Click to expand...
Click to collapse
Try if it works, if not, reflash the rom (that's why you did the backup), and clear those caches again, and fix permissions.
Good luck
I do have Rom Manager, when i want to backup it asked me to install CWM.
after installation and running the backup tool it rebooted without any messages.
I try get into the recovery mode, but i am failing doing that.
in the aMAGLDR v1.12 i held the Power button for a couple of seconds.
a menu appears.. there are 10 options, but non of them is related to AD Recovery.
what do i wrong?
BTW.. it's funny to see you as living in the same place
oops.. i think i screwed up some things..
In the rom manager menu, i selected the Fix Permissions item.
After a couple of minutes and applying of permissions i had to reboot the phone.
..and now it is in a reboot-loop.

[Q] Rom Manager - Fix Permissions problem

Has anyone else encountered problems running Fix Permissions from Rom Manager lately?
After Steven's warning here http://forum.xda-developers.com/showpost.php?p=49990427&postcount=62, I did a clean install and did not replace Browser or Gallery, all went well for a while, but then I began getting Trebuchet FC errors, rebooted to recovery to run Fix Permissions, but it is not avalible in the 6.0.4.7 CWM recovery, so I tried it through Rom Manager - noticed that it now has "toasts" rather than the old console type display, set it aside and let it run. Came back to my homescreen rather than the "reboot now" message that I was expecting. Re-booted and noticed a few user apps were missing, also got a few "android.process.media has stopped" errors as well as Trebuchet FC's. Convinced that I had a bad install, I formatted system, data and cache and flashed the latest nightly - 2/19 - oops, see http://forum.xda-developers.com/showpost.php?p=50470383&postcount=119 - getting stuck on the bootloader convinced me that I had something wrong with the EMMC, so I followed Leapinlar's (thanks again) Partition Repair guide at http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 - of course, the same thing happened again because of the bad nightly. Finally re-flashed the 2/15 nightly and got everything working again, ran fix permissions just to make sure. Actually sat and watched about a half dozen "toasts" and then my display went black, with occaisional SU "toasts" popping up until my homescreen came back on after about 10 minutes - not back to Rom Manager, no reboot warning, just sitting at my homescreen. I let it sit for another 10-15 minutes and rebooted, after starting, a few user apps missing, "android.process.media has stopped" errors as well as Trebuchet FC's. I started a Logcat and ran Fix Permissions again, same thing. Logcat is at https://dl.dropboxusercontent.com/u/20993724/lc022014.txt if anyone is interested, I am going to report to ClockworkMod.
After re-formatting system, data and cache, 2/20 nightly installed fine, all has been well for the last few days, but have not run fix permissions.
I believe koush and cm decided that fix permissions is not needed anymore.

Unfortunately mtp application has stopped s5 on boot no UI.

After i tried
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
on lollipop on vodafone uk, i got this error message on boot, i press ok and after reboot i got no root
Then i install superuser through twrp that i previously had and keep getting this error message on boot.
The thing is i cant get past it, its covering the whole screen no operating system ui just that in a white box and a press ok, which doesnt work until after 2 minutes.
EDIT: its just constantly saying programs has stopped responding in a loop and cant get into android system. How do i fix this, i tried fixing permission in recovery but that didnt work.
So what i can do without losing all my work on my phone.
I hope you made a backup before flashing root files
Boot into recovery, clear CACHES, reboot - see how you get on with that
If you flashed CF Auto Root, there was no need to flash SuperSU, as it comes part of CF Auto root, someone else just did that and ended up in a boot loop, had to wipe the phone and flash a stock ROM
Thats the thing i didnt, i watched a video saying it wouldnt delete your files rooting and decided not to backup.
I was stuck on samsung logo half the time and other times stick with "unfortunately MTP application has stopped." in a big white box blocking me getting into android.
I tried fix permission, clear cache and delvin cache and nothing worked.
I just system wiped and got in but lost all my work.
Fortunately Google backed up most of my photos and videos and contacts but no sms messages.
Now i gotta get all my apps back on my device and get it back to how it was and hopefully i did not mess any important texts.
Note to self: Always backup.
EDIT: i just had gaaps not working and giving server error, after trying out ways to fix that i tried all the normal stop app and clear cache, and then did fix permission in twrp, and after doing "also fix SELinux contexts" it messed me over and got me back to that white box.
so another note to self not to use "Fix SELinux contexts" as that messed up my system after getting 30 apps back installed.

[Q] S note Crashing loop PLEASE HELP A NOOB

HI Everyone, I am having this issue with my Note 3.
About six months ago I flashed the Lollipop software.
I backed up my S note files and could not recover them till I worked out this week they were in a zip file on my Google Drive.
Today I tried to get them back by downloading the Titanium file and restoring once I got Titanium working again.
I had to change my SuperSU too allow grant always and block Knox to allow Titanium to have root access.
Anyway, I tried restoring the file and it sat for about half an hour just saying it was restoring.
Then the phone shut off and restarted again.
Now I am constantly getting the Sorry S Note has crashed notification at 1 second intervals. I can see the phone is loading software in the background, but I cannot turn the notification off long enough to press anything else. It wont stop looping.
I have tried booting into recovery and wiping the cache and partition and factory reset. When the phone rebooted, it showed me the first setup page you see when you first start your phone for the first time, so I know the factory reset worked, but immediately the error started popping up again.
I tried booting into safe mode, and it still flashed up.
When you press ok, the notification immediately comes back again, so you have no time to do anything else.
You cannot go into settings, or press any other buttons, another notification shows up right away.
I am currently downloading a new firmware because I think this will be the only solution, has anyone else had this issue, if so how did you fix it, or will the new firmware be the only way?
Can you add screenshots pls?
*COUNCIL: S-Note use 2 folders that have to be in your internal memory: S Note Export (empty) and SnoteData (where you put your .spd files).

Categories

Resources