I updated my vibrant today via kies to JI5. Immediately prior to that I did a nandroid backup. I was experiencing some buggy things after the update, and then I saw that Samsung pulled the update. So I decided to revert back to my previous build. I ran Clockwork recovery and did the nandroid restore. It all seemed to go well. Rebooted the phone and now, well, its stuck on the Vibrant Samsung screen. Nothing else happens.
Did I do something wrong? Is there a way to get back to my previous build, or even back to original stock condition??
PLS help...thanks.
BTW- I can manually get into recovery mode, so i guess I am not hardware locked. I just don't know what the best thing to do next. Thanks.
The new build has a different kernel that is not compatible with previous builds. You can download odin, the 512 pit file and the original JFD tar file and restore to stock that way. After that you can use your nandroid backup to get back to where you were.
doenloading files now
thanks so much...i will try that! fingers crossed.
WORKED! Thanks so much.
What "buggy" things and what did you have installed on your Vibrant before you did the update.
This? Which is 100% your fault?
http://forum.xda-developers.com/showthread.php?t=795390
heygrl said:
What "buggy" things and what did you have installed on your Vibrant before you did the update.
This? Which is 100% your fault?
http://forum.xda-developers.com/showthread.php?t=795390
Click to expand...
Click to collapse
You're right. The settings thing was my fault by installing the wrong MobileAP. But there were other strange things happening as well. A lot of force closes with widgets - particularly "word clock." Also, the phone would freeze and the display would stay on whenever I received a text message.
I guess it's possible that all of that was the result of the wrong MobileAP. But the fact is that the update was pulled due to "known issues" according to Tmo. So its safe to assume - at least for me - that this update is not ready for primetime.
EDIT: To be more accurate - the update was pulled by Samsung for reasons unknown. Tmo then tweeted that the update had "known issues." And now there appears to be a JI6 roaming around. So if JI5 were perfect, why the JI6?
pdefazio said:
You're right. The settings thing was my fault by installing the wrong MobileAP. But there were other strange things happening as well. A lot of force closes with widgets - particularly "word clock." Also, the phone would freeze and the display would stay on whenever I received a text message.
I guess it's possible that all of that was the result of the wrong MobileAP. But the fact is that the update was pulled due to "known issues" according to Tmo. So its safe to assume - at least for me - that this update is not ready for primetime.
EDIT: To be more accurate - the update was pulled by Samsung for reasons unknown. Tmo then tweeted that the update had "known issues." And now there appears to be a JI6 roaming around. So if JI5 were perfect, why the JI6?
Click to expand...
Click to collapse
I had little issues after I updated to JI5. Swype was very inaccurate, other keyboard were very buggy as well. GPS was not working very well, and there was more lag than before. So I did a reset and all of those bugs went away.
i just flashed bionix 1.3 from JI5 through clockwork with no issues.
Wierd that you had any...
adm1jtg said:
The new build has a different kernel that is not compatible with previous builds. You can download odin, the 512 pit file and the original JFD tar file and restore to stock that way. After that you can use your nandroid backup to get back to where you were.
Click to expand...
Click to collapse
Ok, I just flashed from JI5 to bionix 1.3 through clockwork with no issue. Or does JI5 and bionix have the same kernal? hmmmm
Related
So, I returned to stock, did the update, it failed - or so it seemed. The radio is DI01, but the stupid no service notification is still there. Is there a way to apply just the remaining update? I am already rerooted, launcherpro'd and just applied the deodexed rom - and dont want to do it all over again.
yankeeboy73 said:
So, I returned to stock, did the update, it failed - or so it seemed. The radio is DI01, but the stupid no service notification is still there. Is there a way to apply just the remaining update? I am already rerooted, launcherpro'd and just applied the deodexed rom - and dont want to do it all over again.
Click to expand...
Click to collapse
No, if you just applied the de-odexed rom, there's no way that update is going to work.
Check with Frost, I assume his rom was based on DI01, so you probably have all the updates to the applications, but not the OS (since you're still getting the service notification).
If you go back to stock, I have an update that skips the modem that I made for myself, but there's no chance it's going to work for you at this point.
namebrandon said:
No, if you just applied the de-odexed rom, there's no way that update is going to work.
Check with Frost, I assume his rom was based on DI01, so you probably have all the updates to the applications, but not the OS (since you're still getting the service notification).
If you go back to stock, I have an update that skips the modem that I made for myself, but there's no chance it's going to work for you at this point.
Click to expand...
Click to collapse
I guess its not really a big deal, and don't want to bork the phone over a silly notification sound. I hoping to see some frozen yogurt rolling by soon and Im sure it will be included then
Thanks for your reply
namebrandon said:
No, if you just applied the de-odexed rom, there's no way that update is going to work.
Check with Frost, I assume his rom was based on DI01, so you probably have all the updates to the applications, but not the OS (since you're still getting the service notification).
If you go back to stock, I have an update that skips the modem that I made for myself, but there's no chance it's going to work for you at this point.
Click to expand...
Click to collapse
I flashed the update from jt1134, was trying to get back to stock but need the DH12 build.prop. i'm downloading the system dump but internet is slow does someone have it?
If you have Updated your Vibrant to the J16 and you had no problems, or if you updated and you now have problems. Please post it here. I would like to see some numbers on how well this is working out. I personally am waiting to update, I just keep postponing the update.
Post in this format
Hardware locked or not-Rooted or not-Any other mods-J16 worked or not-If J16 worked, is GPS better
Please follow the above format and keep questions to a minimum. This is just to see the totals of how the J16 is working out.I will update the numbers as we go.
J16 worked - 3
J16 not working - 1
Working on 1 phone
Didn't work on the other.
On the one it's working on, the only unusual sw added was OCLF, Titanium, CWModRecovery. I installed those on a stock phone long enough to make two backups and then removed all traces including the update.zip that cwmod left behind. The tmo update went just fine.
I only removed OCLF on the other and had a bricked phone after the update.
Would've been easier if you made it a poll.
I updated via ODIN, and it's passed the tests with flying colors.
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
First off, wrong section... should be in Q&A.
One way to fix it was to get SetCPU, and make sure the minimum CPU speed is 200MHz
You should also give more information. Have you flashed eb01 with odin before installing SC? How often do these sod's happen? Do you use the clock app?
Sent from my SCH-I500 using XDA App
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
GizmoDroid said:
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
If you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package ROM from this post
While reinserting your battery, hold both the volume keys and the power button down until a second after you see the Samsung boot logo
You should see CWM recovery now
Flash the SuperClean ROM from this post, Wipe Cache/Dalvik Cache only.
Reboot. If you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot, enter CWM and flash theme, Wipe Cache/Dalvik Cache only.
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
Click to expand...
Click to collapse
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
str8havoc said:
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Are you running setcpu ? And if u are and u have a profile for when the screen is off, disable it. That should to the trick
Sent From My Samsung Galaxy S Fascinate Using XDA Premium App - Running Superclean 2.9.1 - 2.2 Froyo
sneakysolidbake said:
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Thacallmehess said:
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Click to expand...
Click to collapse
Your post isn't helpful to the forum at all, at least there's some community members who like to help keep our forums organized and clean so our Mods aren't overwhelmed. (See how easy that was)
@ OP, there is definitely a SOD patch somewhere in the Fascinate forums that Adrynalyne put out a bit back. I apply it along with the Camera mod every time I flash any new version of Superclean based on EB01/EB16. I'll see if I can post a mirror later when I get back home and you still haven't found it.
The SOD patch is already incorporated in to the latest SC. Gizmodroid's process (based on Adryn's solution to problems with SC2.7 iirc) is your best bet at this stage and worked for me. I would also recommend avoiding TiB as much as possible based on Adryn's comments in the SC2.9.2 thread. If you use Gizmodroid's process, please post your results in the relevant thread. I'd be interested in finding out the degree to which that process solves the issues generally.
I had the same problem. Follow the directions above flashing the stock and then upgrading and avoiding the apps noted above (I think youmail was a big part of my problem) and you should be good to go.
GizmoDroid said:
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
Click to expand...
Click to collapse
Thanks everyone for the fast replies even the one telling me i was in the wrong section. Sorry about that
I use both Youmail and the clock app all the time, so thats probbealy why i'm getting the SOD. I also install my apps from my SD card using Astro File Manager and it sounds like that could be causing my problem to.
I installed SetCPU and set the min. to 200mhz, hope that will fix my problems if not
Q1: can I download another clock app and be ok or will it do the same thing
Q2: is there any way of fixing the Youmail app or should I use another voice mail app.
Just want to thank everyone that keeps XDA up and running you guys rock. Love this Forum!
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
mrjake1970 said:
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Click to expand...
Click to collapse
Are you using the voodoo lag fix?
I think the majority of the incompatibility people are seeing with the fixed cwm is might be some broken compatibility with rfs. It's supposed to be able to handle both, but I think changes in jt's initramfs or changes in the project voodoo files in the kernel that CWM is put into are the root of the problem.
Maybe I'll get some time this weekend to look at it.
In the meantime, everyone should go voodoo/lagfix
yeah giz, im using the superclean "stock" voodoo...
r
tonight im going to go flash happy with the original odin file i used to bump to froyo, and the other old cwm with the broken fixpms and the non fixed superclean 2.9.2 and see if that helps.
i cant be late for work again tomorrow with no alarm from a frozen phone lol
Samsung Fascinate
SuperClean 2.9.2 Voodoo
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
What is the sleep of death?
Update...
I reflashed the original EB01 tar file, modem and the 3/30 red CWM, along with the original copy of the non-fixed superclean 2.9.2 ROM and i am running fine so far with no SOD issues.
As long as this holds true for the remainder of the day I'm going to flash the updated CWM tonight to try and narrow down which of the 3 things i suspect in my previous post is causing it.
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
I downloaded setcpu and put it to 200mhz and been running fine since yesterday. I hope it will last the rest of the day.
Sent from my SCH-I500 using Tapatalk
created a sleep of death..
so, guess what? i created the sleep of death on my phone, and i know exactly what caused it.. not only that, but remembering back to my last sleep of death experience - it was the same exact scenerio..
i was running EC10 debloated, jt's 4/8 voodoo.. i flashed a theme to check it out.. didnt like it, so i re-flashed EC10 over it, with wiping dalvik and reg cache..
booted fine, however i started to notice clock lag almost immediately.. screen went off, and next time i tried to open the phone, i had to hit the power key 4 times before it would light up.. sounded familiar to me from last time, so i let it go about 1.5 hours.. sure enough, would not wake up.. had to pull battery to get it to boot..
i did a nandroid back to prior to the theme flash, and seem to be running ok.. however i am going to do the "clean" flash again tomorrow back to EB01 again just to be sure..
im convinced that is what caused mine both times..i will also be doing that every time i get tired of a theme instead of just flashing a new ROM..im guessing themes are leaving pieces parts behind somewhere that don't play nice with a ROM reflash over it..
I have been having SOD issues ever since I rooted and got set up on SC 2.9.2. However today, I decided to leave my GPS on and since I did that I have not had any SOD. Granted today is not a perfect example because not 45 minutes went by without using my phone, but it seems to have made things better for now, except my battery drains because of it.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/foru...21-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I'm running
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
I did TiB but have since uninstalled and used My Backup (free). I'm using GoLauncher and related apps. I do use YouMail and will not stop. I know its redundant but I installed the SOD patch too.
I'm going to try all the bandaid fixes first before re-flashing everything.
Search adrenalyne's threads. He had one with a sod patch.
Sent from my SCH-I500 using XDA App
My coworker is not able to OTA update her completely stock (never rooted/modded) Facinate to 2.2, but when she goes to System Updates->Check New, there is a pop up that says "Please Wait" that stays on the screen for a while, then just goes away and nothing happens.
Also, if you go to System Updates->Status, it says "Server Unavailable" Code: 500.
The only thing I can think of is that Verizon is only letting particular regions update at a time to prevent the server from bogging down. Any ideas?
Verizon seems to be having network issues since 2am. Even if you have a data connection, they probably offlines the OTA servers until the problem is resolved.
http://community.vzw.com/t5/4G-Disc...TE-outage-ETA-for-repair-and-other/m-p/513354
She is on stock DI01, and we downloaded the Verizon official ED01, but it says that it cannot find EA28. So, we downloaded EA28 official zip, and now it says that it cannot install because it needs DL09. Sooooo, should we now look for DL09? There has got to be a more simple way...
I'd leave her at stock and just be patient. Verizon's system will come back.
still down
I am having the same issue, even tried the DL09 no luck
I've had the same issues since the day the update came out but I had ODIN'd EB01 and then ODIN'd back to Dl09 and tried everything but got the server unavailable issue. I gave up and just flashed the ED01 update.zip.
After a lot of trying different things and giving up, an awesome dude posted the solution here: http://forum.xda-developers.com/showpost.php?p=13313409&postcount=12 . I followed the steps and it worked like a charm.
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
artvandelay440 said:
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
Click to expand...
Click to collapse
This method is well known, but the OP was asking about OTA.
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Teddybear2 said:
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Click to expand...
Click to collapse
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?[/QUOTE
Root Kernel is KG1 from Odia. Happened before with the other Kernel as well. I already cleared cache. There is no insecure KG2 for T-Mobile available. Any idea how to make the Kernel rootable/ insecure. I suspect it must have something to do with the Kernel. For rooting, I try always to get the insecure version of the branded one. Different kernels (insecure/ secure) that do not completely match could cause this?
Maybe I have done something wrong which is the solution. Let's start from scratch how I rooted the phone.
I had original Kernel on the phone. From this one, I upgraded straight to the insecure, rooted and than just put one the most recent one.
Is this causing the problems? So better upgrade to the next official one, than use the insecure to root and than put the official one back on. All done via ODIN? Would this be the solution?
Click to expand...
Click to collapse
I used KIES to get the orginal KERNEL on the phone. So far no problems there. I want to test it over a couple of days and then root it again. Hope this fixed it.
2 Hours later
Okay, after roughly 2 hours I came back in this loop with Internet/ Messages. I cleaned the RAM and now it works fine. Why does this happen? Never had this before. Is this an App causing or just the Kernel. I could use ODIN to get back to the first Kernel that was preinstalled. Phone is currently not rooted. However, when I use ANDROID system Info (App), under BuidlINfo I see Type: USer and USer: Root. Should I probably unroot first as the system is confused and thus these errors appear?
Hope some could help here to clarify.
Need help and advice to fix problem!!!!!
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
Click to expand...
Click to collapse
I always thought power on/off is similar to Reboot. I was proven wrong. I just rebooted with volume up+home+power. Since then phone is stable. Sometimes TWLauncher crashes and reloads.
Thanks for the support. I think this has been fixed....hopefully.
Teddybear2 said:
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
Click to expand...
Click to collapse
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
0semaj0 said:
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
Click to expand...
Click to collapse
Problem was that a system file for synchronisation (syncmldstmo.apk) was deleted. I do not know how, but I could restore it with Titanium. Since then, all my problems seem to have vanished.
My Apps does not work. I do not see any downloaded app. Seems to be a Google problem since I stumbled over several threads.....no solution so far. I asked them directly. No solution.