Related
[Q] Browser doesn't work on CELB Froyo 4.3 =(? HELP!
1. Check 3G signal, basically is the internet working?
2. Try re-flashing CELB and make sure to flash the latest gapps too
It would be more helpful if you gave a more in depth view of your browser problem.
it would help you more if you posted this issue in CELB's thread. You will get better answers faster by people who use the rom and that may have came across the isssue
When i try to reply it says i can't and should start using the Q&A Thread? smh
BBoY177 said:
When i try to reply it says i can't and should start using the Q&A Thread? smh
Click to expand...
Click to collapse
That's due to a recent change in XDA's site policy - new users can not post in the development sub-forums until they have at least 10 posts in other forums. So, you were right to post your question here, as you had no other choice. DirtyBubble apparently wasn't aware of this either, or he wouldn't have said that.
I tried a fresh install of 4.3 last night (w/ gapps 12/28), no bootloops, but no market access or Google account setups either. I'm going to look at a few different installs in a couple minutes - check back in this thread later.
bftb0
I tried the following 3 trials:
Before starting, I did a Nandroid backup (from within ROM Manager/Clockworkmod) of my existing ROM - CELB 4.1. (I am not sure of whether this 4.1 ROM had gapps 12/28 in it or not - I believe it does, but iirc they were installed on a CELB 3.9 ROM, and then just overflashed to 4.1)
1) Wipe Cache, Wipe Data/FR, Flash CELB4.3, Flash gapps 12/28
Result: account setup does not occur; market app crashes or closes immediately. Tried doing a FR on this; next boot the kernel actually crashed. Didn't bother to check the browser**
2) Wipe Cache, Wipe Data/FR, Flash CELB4.3, Flash gapps 10/18
Result: Provided account creds; phone sync'ed just fine and restored settings; Market works; Web Browser worked.
3) Wipe Cache, Wipe Data/FR, Restore CELB 4.1 from Nandroid backup; Flash CELB4.3; Wiped CACHE ONLY.
Result: Everything works, including stock browser.
** I didn't bother to check the browser in this case because I have little interest in using a ROM without a Gmail account; it did occur to me later, though, that the default setting of the browser has been to use location-services, and that the stock browser has exhibited crashes on startup on other ROMs that did not have a Google account configured. You can turn this off in the browser - but only if it doesn't crash, because you need to get to the browser settnigs menu to deal with this, so that is impossible in this case.
I don't know if that is your issue or not, but you could try turning off location services in the Settings menu and see if that makes any differences. (I don't know if that will work, but it is easy to try). Anyway, that's two solutions: either overflash 4.3 on top of a prior CELB ROM, or do a clean install of 4.3 using the 10/18 gapps. (If you do the former, you can only wipe cache at the end if you are using ClockworkMod - or manually via ADB if you are booted into Amon_RA).
bftb0
My friend got an AT&T SGS2 last night, and I helped her put CM7 (stable - not a nightly) onto her phone. She wanted to send me a screenshot of a theme she installed, but everytime she tries to take a screenshot she gets the following error:
error: /mnt/sdcard/tmpshot.bmp (permission denied)
Screenshot is saved at null
I did a few searches on XDA and Google, but couldn't find anything related to the SGS2. Could someone shed some light onto this for me?
First I would recommend AT LEAST going to the newest nightly that CM7 OFFICIALLY put out #181 as it is better than the rc1 which did not have as many fixes in it anyways. Or I ACTUALLY would recommend using the newest nightly from https://s3.amazonaws.com/cyanogenmodbuild.s3.mortimer.me.uk/index.html which is EVEN BETTER with more fixes than #181 and definatelly better than rc1.
Second she can just hold down the power button and when the onscreen popup comes up choose screenshot. This MAY have worked on rc1 but that is a VERY OLD release and I cannot remember if it even had scrrenshot on the power menu screen. The link I put is from Sam3000 and he is just building from source without adding/deleting anything that the CM TEAM is fixing.
Sent From My KickAss ATT SGS2 SPORTING CM7
I think I'm misunderstanding something. The latest official nightly I see for the ATT SGS2 is Nightly 20 which can be found here:
http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
You said that the latest is 181?
I checked ou the Unofficial nightlies page you linked and had a few questions about those.
1. Are they safe to flash right over the stable 7.1 official CM7 release with a cache and dalvik wipe? Or do you have to wipe the entire phone?
2. Is there a specific unofficial nightly that you recommend? I know from running nightlies on my Atrix that some are amazingly stable and snappy, while others are most definately not. I'd like my friend to have a smooth experience on her phone. She's not tech savvy, and this is her first Android device. I'd like her to have the best experience possible, which is why I had her flash the stable instead of a nightly to begin with.
Also, I did more research into the error with screenshots. The Droid Incredible had the same issue which could be fixed by changing the permissions on some files in /system. I still can't find anything SGS2 related with the error though. So again, if anyone has any info for me about it I'd appreciate it. If its between running a line or two in ADB and experiencing with flashing various nightlies, I think I'd rather stick with the simple fix.
Thanks in advance!
You can flash the nightlies right over stable CM7 with just wiping Dalvik and cache. Also like RockRatt mentioned.. The newer nightlies are far better than the "stable" that was put out. I would just recommend grabbing one of the latest from sam3000's thread.
Not sure about the screenshot error. Try updating to a nightly and see if the problem is still present.
sent from my Galaxy SII
DeathKoil said:
I think I'm misunderstanding something. The latest official nightly I see for the ATT SGS2 is Nightly 20 which can be found here:
http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
You said that the latest is 181?
I checked ou the Unofficial nightlies page you linked and had a few questions about those.
1. Are they safe to flash right over the stable 7.1 official CM7 release with a cache and dalvik wipe? Or do you have to wipe the entire phone?
2. Is there a specific unofficial nightly that you recommend? I know from running nightlies on my Atrix that some are amazingly stable and snappy, while others are most definately not. I'd like my friend to have a smooth experience on her phone. She's not tech savvy, and this is her first Android device. I'd like her to have the best experience possible, which is why I had her flash the stable instead of a nightly to begin with.
Also, I did more research into the error with screenshots. The Droid Incredible had the same issue which could be fixed by changing the permissions on some files in /system. I still can't find anything SGS2 related with the error though. So again, if anyone has any info for me about it I'd appreciate it. If its between running a line or two in ADB and experiencing with flashing various nightlies, I think I'd rather stick with the simple fix.
Thanks in advance!
Click to expand...
Click to collapse
Yes #20 was the last OFFICIAL nightly for the SGS2 sorry about that. I am still keeping up with my old captivate flashing CM7 and CM9 on it and its last OFFICIAL CM7 was #181 so sorry about the confusion.
I would go with the newest from the link I provided from Sam3000's site. I use it for mine and the wife and ONLY update hers knce I know it is stable enough so she doesnt have any issues either. So I would say go for his newest that came out on 02-15-2012 and it should be totally stable for her. I only ever wipe Dalvich Cache between builds but for you updating hers I would suggest to flash the newest unofficial nightly, then before rebooting flashing it a second time for good measure. This way only wiping Dalvich all her apps and everything else will still be there.
OR if you have any issues and or want to make sure just do a titanium backup of all her apps. Then wipe data/factory reset (will wipe out any and all parts of what she already had), then flash the newesr nightly twice before rebooting, then flash gapps before rebooting, then boot it up, then reinstall any apps from the market needed, then open tibu and restore USER APPS ONLY, She wont have any saved data for the apps this way but your starting her off clean again.
Sent From My KickAss ATT SGS2 SPORTING CM7
Well I had my friend install the nightly from the 15th like was suggested.
Sure enough, she still can't take screen shots, though this time it is a different error. It says....
Media Unmounted
Unable to save Screenshot: mBitmap = null
It appears CM7's default install requires that you have an SDCard in order to take screenshots, pictures, videos, or recieve text messages with pictures or videos. This is "fixed" by going into...
Settings > Cyanogenmod > Applications > Check off "Use Internal Storage".
After a reboot, your internal memory will be mounted as /mnt/sdcard instead of /mnt/emmc. This fixes the issue in the latest nightly. It should be noted though that I had her try this on the stable 7.1 release, and she was still unable to take screenshots.
Everything is fine now. I am a bit disappointed that CM ships "broken" to an average user if they don't have an SDCard. Some users (like me) know how to fix it right away. Your average user would have no clue. My friend Erika (above average user) is very computer literate, but has no linux experience and would have never figured out that the "media unmounted" errors she was getting were because the default setup requires an sdcard or that you toggle the "Use Internal Memory" checkbox.
Anyway, thank you for the responses!
Ian
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre
Did I break my Tablet...?
I am a big PACman fan and have been using the rom on every one of my devices. I am also not new to rooting and flashing procedures and have done them on different devices many times including updating hundreds of times. PACman was quiet for a while but has started up again since August, so I was really looking forward to that until I had following problem:
1. Installed the newest rom with a factory reset beforehand.
2. Setup the device as usual.
3. Opened gmail --> Stuck on "Getting your messages"
4. Tried calendar, contacts and google music without success, as they display neither my music, contacts nor my calendars.
5. Drive and Maps are working though...
I have now done the following:
- Reverted all the way back to stock 4.1, rooted and upgraded to 4.4.2 stock.
- Flashed boot.img from PAC rom and installed it with gapps. Everything went perfectly.
- Added my google account during the setup process, opened gmail --> stuck on "getting your messages"
- Added a second google account, which is also not syncing.
Before this I already tried using different gapps (PA, CM, Banks), doing a playstore and play services reset. I am really not new to this and this is the 5th device I own that I rooted and installed custom roms on. My phone has PAC and is working flawlessly. I'm really lost here and would appreciate any ideas or help.
Rom versions I tried: nightly from 12th, 18th and 323rd with clearing cache and dalvik after install.
Gapps: Banks, CM and PA gapps 11th, 18th
When installing AOSB project, everything works flawlessly!
Something I am missing here? Please help!! This is getting so frustrating...
PS: Here are three screenshots of how it looks like (weird is that there are no timestamps in the sync tab)
http://imgur.com/sAEqmCE,UxNjuNa,zJ83DiT
moesus said:
Gapps: Banks, CM and PA gapps 11th, 18th
When installing AOSB project, everything works flawlessly!
Click to expand...
Click to collapse
the problem is in P.A.C ROM builds or in Gapps.
Rootk1t said:
the problem is in P.A.C ROM builds or in Gapps.
Click to expand...
Click to collapse
PAC rom can't be the problem, as all other users report no errors. I have tried different Gapps (always checked MD5 sums...) and this issue doesn't resolve. I am looking for any new ideas on the issue.
Personally I cannot explain the issue myself
So if anyone has an idea, please help!
Search for another boot.IMG, there have been issues with the cm boot and wifi modules, maybe the same with the PAC boot.IMG low/ connectivity would explain the lack of sync time stamps
Sent from my omni_pollux using XDA Free mobile app
Q&A for [ROM][Sep 25][4.4.4] I9100 AOSP NeatROM v8.0st
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
security settings crushing, and all is sloww
Hi there all
I have flashed this ROM 2 days ago and found it very good and fast.
Today i have played with the security (lock screen & apps permissions), i have chooses the face recognition for the screen-lock and a default security for all new apps.
Now all is so slow and cannot get into the security settings, it is crushing !
Please help.
I do not want to factory reset, i have already restored all my contact and apps, do not have the time to do this again.
Thank you all
My huge thanks to the developers of this amazing ROM. I really appreciate your work. With Apolo Kernel works perfect! Thank you.
eli1967 said:
Hi there all
I have flashed this ROM 2 days ago and found it very good and fast.
Today i have played with the security (lock screen & apps permissions), i have chooses the face recognition for the screen-lock and a default security for all new apps.
Now all is so slow and cannot get into the security settings, it is crushing !
Please help.
I do not want to factory reset, i have already restored all my contact and apps, do not have the time to do this again.
Thank you all
Click to expand...
Click to collapse
Eli,
I've been using the v8st for over 20 days now and have not come across such an issue.
But I have a different issue though:
The bluetooth mic levels when connected to the car's audio system renders very low voice that the person on the other end can't hear me so good.
Hope someone with a similar issue like yours' should be able to help you soon!
gps always on
Hello, i recently use this rom and find that may gps is always on in my battery usage even if i already turn off the location setting, how can i turn off my gps? Before this i found that my wifi also always on but i can turn it off by going to setting-->wifi-->advanced-->keep wifi and set always on when sleep to never, is there also settings like this for gps? Thankyou
Hi
Even by doing as per Post# 4, Wallpaper gets replaced but does not work.
Going by wallpaper details found MD5 error.
Few more issues on my device, new to this ROM. Flashed 2 days back.
1. How to increase the FONT & ICON size in Status bar, Key board letters are too small, notifications are small.
2. Screen and around the camera gets heated, during this time battery drains super fast.
3. BBS is not working, error message "Battery service could not be contacted"
Please help me with the above issues.
Thanks in advance
Sent from my GT-I9100 using Tapatalk 2
sunnyhot said:
Hi
Even by doing as per Post# 4, Wallpaper gets replaced but does not work.
Going by wallpaper details found MD5 error.
Click to expand...
Click to collapse
What post #4 are you talking about? What does not work? What gives you an MD5-error. Please be more specific.
sunnyhot said:
1. How to increase the FONT & ICON size in Status bar, Key board letters are too small, notifications are small.
Click to expand...
Click to collapse
You need to change the display density setting. Open the file /system/build.prop with a text editor and search for the line ro.sf.lcd_density=182. Change the value to something else. Bigger numbers give you bigger icons and fonts. The Default for SGS2 Roms is normally 240, Neatrom uses 182, that's why everything is smaller than on most roms. If you want to use 240, you can also flash this ZIP in Recovery: View attachment Density_240_v8.0st.zip. It's just a modified build.prop for 8.0st. There are also apps on the PlayStore that can change the density for you, but I never tried them.
sunnyhot said:
2. Screen and around the camera gets heated, during this time battery drains super fast.
Click to expand...
Click to collapse
Without more info it's impossibe to know what is draining your battery. You need to find out the app that gives you trouble with BBS or similar app.
sunnyhot said:
3. BBS is not working, error message "Battery service could not be contacted"
Click to expand...
Click to collapse
In Android KitKat, user apps are not allowed to access battery stats. It's part of Androids security policy. There's two ways to fix it:
Get Xposed Installer and install the Xposed Framework. Then, download the module Enable BatteryStats Permission - voila! Since Xposed is simply awesome for other tasks as well, I recommend this method.
If for some reason you don't want to use Xposed (e.g. if you use ART), then you have to convert BBS to a system app. There's several ways to do so, like Titanium Backup or Link2SD... However make sure that BBS gets installed in /system/priv-app/, and not in /system/app/, or else it will still not get the necessary rights.
Hi is there a way to reboot into recovery except from the home + volume + wake and also which Version of Apolo is the right one 7.1 CM?
Battery life?
Hi guys, was checking this rom out and it looks awesome!
How's the battery life though?
I'm currently on Resurrection Remix and the battery life when I have wifi on is really poor.
I'm basically looking for a 4.4.4 rom that gives maximum battery life.
Also are there any kernel recommendations?
Thanks!
Weird battery behaviour
Hello Guys. I met a very strange issue.
After flashed the ROM, the battery indicator acts very weird.
When the phone is fully charged, and I remove the charger. after reached 85%, and when the battery is gong down, the indicator is going up from 85% to 90 %.
Anybody met this ? and how to resolve ?
I already calibrated the battery, but the problem still on.
Click to expand...
Click to collapse
Try another batterry. I was facing the problem with an almost dead battery. With another one it's fixed.
---------- Post added at 01:39 PM ---------- Previous post was at 01:25 PM ----------
phirey said:
Hi guys, was checking this rom out and it looks awesome!
How's the battery life though?
I'm currently on Resurrection Remix and the battery life when I have wifi on is really poor.
I'm basically looking for a 4.4.4 rom that gives maximum battery life.
Also are there any kernel recommendations?
Thanks!
Click to expand...
Click to collapse
I'm running this with Apolo V0 kernel and I'm satisfied (on original Samsung 2000 mAh battery):
~33% a day of normal usage
~1% an hour idle (data on, sync on, location on)
~0.3% an hour night mode (data off, sync off, phone online) - translates to ~14 days of runtime
Have tweaked wakelocks/services.
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
txx3 said:
Hi is there a way to reboot into recovery except from the home + volume + wake and also which Version of Apolo is the right one 7.1 CM?
Click to expand...
Click to collapse
1. You can configure advanced power options to be able to reboot into recovery from a running ROM
2. Yes CM is the right Apolo for NeatROM (having superuser integrated)
Having troubles with wifi connection since this morning... My S3 and laptop works just fine but with s2 cant connect to apps like viber, whatsapp or hayday
DELETED
Today formatted extsdcard to FAT32, still I see media scanner issue.
What could be the problem? Pls help guys
Sent from my GT-I9100 using Tapatalk 2
sunnyhot said:
Today formatted extsdcard to FAT32, still I see media scanner issue.
What could be the problem? Pls help guys
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I had the same problem of battery drain because of mediascanner service running all the time and i didnt know the exact fix but i have read somewhere that formatting sd card would help fix this and it did, Anyway i didnt use much of my extSD so i removed it for now!! And no battery drain observed with mediascanner service
I can't get this to run on my phone. After carefully following the instructions my phone is stuck on the first boot screen with the yellow exclamation mark. Strangely it seems like I have TWRP installed which I can't get rid of. Even after installing the CWM linked to, the next time I manually enter recovery TWRP opens.
Update: Sucessfully installed a Cyanogen based ROM instead. Shame, I would have liked to try this one.
GAPPS not working?
Hi there, please help me. I can't get gapps to work/install. I first flashed beta version...nothing, then tried the stable version and only Chrome appeared in appdrawer. I still can't access play store (from the Nova Launcher menu option), the browser that came with the NeatRom doesn't start.
The rooting, flashing of the rROM etc all went well, according to the instructions, the only thing was that I couldn't format /preload as there was no such option in the CWM recovery. Could that be the problem maybe?
Please tell me, what am I missing here...
jokl81 said:
Hi there, please help me. I can't get gapps to work/install. I first flashed beta version...nothing, then tried the stable version and only Chrome appeared in appdrawer. I still can't access play store (from the Nova Launcher menu option), the browser that came with the NeatRom doesn't start.
The rooting, flashing of the rROM etc all went well, according to the instructions, the only thing was that I couldn't format /preload as there was no such option in the CWM recovery. Could that be the problem maybe?
Please tell me, what am I missing here...
Click to expand...
Click to collapse
No, Preload is not used in AOPS Roms, only at Sammy ROMs.
maybe your download of GAPPS or ROM is corrupted, check the MD5 file to see if there is any thing wroing.
Clear Cache from Recovery
Try to reboot
Try to re-install.
Somtimes something goes wrong and then you have effects as you mentioned.
GeScha said:
No, Preload is not used in AOPS Roms, only at Sammy ROMs.
maybe your download of GAPPS or ROM is corrupted, check the MD5 file to see if there is any thing wroing.
Clear Cache from Recovery
Try to reboot
Try to re-install.
Somtimes something goes wrong and then you have effects as you mentioned.
Click to expand...
Click to collapse
Sorry, but I gave up over AOSP and flashed the "stock" NeatRom 6.4 w/o any problems. Runs great!
Still, when I was searching for a solution, I found out, that it is possible that I didn't make a nandroid backup of /preload (when I was still on rooted stock samsung ROM - before flashing kitkat cwm and later AOSP NeatRom). I read that in the CWM recovery that comes with Siyah kernel - which I used to make a nandroid backup - you have to manually select to make a backup of the /preload part. in addition to all others... And i really didn't find a file with "preload" in the nandroid backup folder that I copied to my PC. If so, I am suppose to have trouble when/if going back to stock samsung ROM? If that is the case, maybe it would be good to update the guide for flashing the KitKat-based AOSP NeatRom. I don't really care right now, because I really like the stock NeatRom...I just hope it'll work...
NeatRom 8.0st and TWRP - no restore possible
Hi all,
hope, one of you will be able to support me ?
I'm not able to restore any of my TWRP backups done with TWRP 2.7.1.0 which came with the ROM.
All backups went well and were flagged as 'successfully'.
However, trying to restore one of them failes every time. It looks like after restoring SYSTEM and starting with DATA, it stucks.
One 'failed', no error code or any additional information.
I've a 32 GB SD installed on my i9100 and this is where I store all the TWRP backups.
Copying them to internal storage does not help.
Any ideas ?
Thx in advance,
BR,
This is a good room