Need help! having problem after flashing :) - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

I guys, I dunno why but, after upgrading from ICS 4.0.4 XLQ1 stock with CWM to Zeta 4.0 I'm having a lot of problem.
For flashing the rom I've done:
- a Full Wipe (Cache, Data, Dalvik)
- Flashed Zeta 4.0
- rebooted
- Flashed Dedraks' Kernel
- Rebooted
- Flashed Pimp My Room
- Rebooted.
Firts time I booted up the 7.7 it went in bootloop, so I've repeated all the process, and than the problem seemed to be solved.
But, after some hour of usage, the 7.7 just went crazy, with random reboot, root acces that doesn't work for "ES Filemanager" and "Filemanager HD", and a toons of other problem....
what should I do guys? any advice?
Thanks in advance!!

maybe restock and then get back to ics? sometimes it works.
best regards
Sifou
Galaxy Tab 7.7

Related

[Q] HTC Sensation reboots all the time after CWM restore to CM7 before using Hypers.

Hello boys and girls,
I would like to say hello first. Because I'm new I can't post into Hypersensation Thread, which is very baaad (I gotta say, I'm not a noob, I just don't post but read usually...)
What I did:
- Used current CM7 Alpha for Sensation (worked like a charm but used a bit too much battery imo)
- yesterday: flashed Hypersensation
- Market didn't work, so I flashed Market Patch
- Flashed new radio because old one was relatively old
- But Hypersensation was a mess (alarm clock not working, Vibration not working, ...)
-> Restored CWM Bak.
Since then, the phone restarts every few minutes.
Any idea, what to do now? I'm very frustrated, to say the least... why on earth does restoring not solve all problems?
.edit: Reflashed fresh cm but only wiped dalvik and cache - same error. It only restarts when not connected to pc via usb, though

[Q] Eos1.0.0 problems?

I rooted and upgraded my rom to Eos 1.0.0 several months ago. Ever since then ive been having issues with my bluetooth devices staying connected and working property. Also, lately my browser has been closing randomly and will get worse unless I reboot.
I absolutely love the team Eos build and hope they can help me find a solution. I am wondering if anybody else has had the same issues or know of anything that can help me?
Would upgrading to their new rom build help you think?
Upgrade to EOS 2.0.0
Can you go into recovery and wipe cache, and davlik? and check again.
And, if you decided to upgrade to EOS2.0, don't forget to wipe cache, dalvik and battery stats thru recovery.

Cant hear the caller CM 10 20121009-NIGHTLY

Hello. I have a big problem. I cant hear the caller. It doesnt matter if I call him or if he calls me. I just dont hear anything. When he picks up, I can see time starting but I cant hear a thing. I restarted the phone and installed "MODEM_CWM_I9300XXDLI7". It worked for 1 phone call but than it was the same. What could be the problem?
What I am using:
-Samsung Galaxy s3 i9300 (international)
-CM 10 20121009-NIGHTLY
-i9300XXDLI7 (modem cwm)
Everything worked fine on stock 4.0.4 ics.
This was the first time I rooted a phone and installed rom so maybe I did something wrong but I am 99,9% sure that I did everything right because no error was given during the process of root or installing the rom. Maybe there is a problem with a ROM becouse it is a today release? I did use 8. october release but I thought that updating to 9. october would solve the problem but it didnt.
Is there any other (more stable) version of CM10 out there for galaxy s3 ?
Thanks
wrong forum
Did you do a clean install, as in wipe data, wipe cache and wipe system?
Sent from my Galaxy S3 running Eclipse ROM V2.1
Oh snap, I didnt see "verizon" there. I thought it was general ><. Hope mod will move it.
Anyhow, I did wipe out everything just as tutorials said.
I used CF-Root v6.4 for root with odin, and ClockWork for installing ROM
edit: I Solved the problem !
I factory restarted, wiped out everything and installed ROM again. It seems like its working now.

[Q] Samsung Captivate (i897) very weird problem when going to any JB ROM. please help

Hey there XDA,
I have a weird problem when using a Samsung Captivate (ATT i897)
I was running CM9 and i wanted to flash Paranoid Android JB rom, so i followed the instructions to the letter(factory reset, and format cache, etc) and a weird problem occurred, everything works perfectly except:
1) i have no lock screen (even though it is check on (slide))
2) no notifications arrive, (i hear the ringtone and all, but it doesnt tell me anything)
3) i hold the home button and no recent menu comes)
i flashed back to cm9 and the problem came with me.
So i OdIn back to stock and followed this link (http://forum.xda-developers.com/show....php?t=1350266 ) to get root and CWR and went to CM9, it works.
Fast forward one month and i decided to flash Lanight V6.5DD Jelly bean Rom.
The Same exact problem happened, i went back to CM9 and it followed me.
So i want to format everything on my phone using CWR (including /BOOT) and then going in to download mode and using the same method as above as a fresh start ( i have GB boot-loader from Kf1, and two ATT flashes come up whenever i boot my phone up)
maybe if i flash the ginger bread boot-loader again and cleanly (clean format of /boot) then install it will fix it.
.
(QUICK Q: if i format the /boot in CWR can i go into download mode????????)
Hopefully that will fix the problem
i would like to see what is your opinion and expert help.
Sincerely,
Thatguy2007

[Completed] Having Some Issues

Hello all, I have some problems I hope you guys can help with.
My phone is a Samsung Galaxt S3 i-747, the att version, running CWM 6.0.4.7.
I am having an issue with every rom I have installed thus far. My battery level registers at anywhere between 14-51 percent and discharges rapidly from there. I have reinstalled each one at least 3 times. Before installing, I made sure to format /system, wipe cache partition and wipe dalvik cache. I ahve even tried such apps as Battery Calibration.
The roms I have used are as follows, and the problem persists with each one.
- Carbon Rom
-Gummy Rom
-LiquidSmooth
-SlimKat(would not go past the Sliktkat logo)
-Dirty Unicorn(would not go past the Unicorn Logo)
-Stock Rom with Root
-Have tried LeanKernel, Archie Kernel and the stock kernel.
Each one has these problems, and two won't even boot. I'm at my wits end and I'm about to repurpose this phone for target practice. Hopefully one of you can help me out.
n3onxhaze said:
Hello all, I have some problems I hope you guys can help with.
My phone is a Samsung Galaxt S3 i-747, the att version, running CWM 6.0.4.7.
I am having an issue with every rom I have installed thus far. My battery level registers at anywhere between 14-51 percent and discharges rapidly from there. I have reinstalled each one at least 3 times. Before installing, I made sure to format /system, wipe cache partition and wipe dalvik cache. I ahve even tried such apps as Battery Calibration.
The roms I have used are as follows, and the problem persists with each one.
- Carbon Rom
-Gummy Rom
-LiquidSmooth
-SlimKat(would not go past the Sliktkat logo)
-Dirty Unicorn(would not go past the Unicorn Logo)
-Stock Rom with Root
-Have tried LeanKernel, Archie Kernel and the stock kernel.
Each one has these problems, and two won't even boot. I'm at my wits end and I'm about to repurpose this phone for target practice. Hopefully one of you can help me out.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
I think this is a battery issue, so in my opinion you should first try with a different battery to see if the issue persists.
But for any other questions you can always ask here: Galaxy S III Q&A, Help & Troubleshooting
Good luck!

Categories

Resources