Related
Well I have had my Xoom now for about a month. I use it pretty heavily and as soon as I got it I rooted it and installed Tiamats v1.4.4 kernel with OC'd GPU. I was running pretty flawless OC'd to 1.5Ghz until last night. I was in the middle of reading some posts on here on tapatalk and out of the blue the screen went black and rebooted. It was stuck on the spash screen for 20 minutes. I tried a hard boot and got bootloops.
I then downloaded the stock images and reflashed it back to stock and even relocked the bootloader. Still bootloops. I ended up flashing the stock images like 3 times in all with the same results. Sometimes I can get into the OS and go through setup and sometimes not. Most of the time if I can get into android apps start force closing and it reboots, or the touchscreen becomes unresponsive. I noticed most of the time when rebooting I get bright white flashes of light on the splash screen. Here is a video of the boot sequence:
http://www.youtube.com/watch?v=1ctODeIPANU&feature=player_profilepage
Around 1 minute into the video you can see the white flashes of light. Anyone know if there is any chance of recovering this? BTW, its a verizon 3g xoom. I'm pretty sure its a brick. I just wanted to see if anyone else had seen this same thing happen.
EDIT: I also noticed that sometimes the front camera is flashing red also when rebooting. Weird.
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
okantomi said:
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
Click to expand...
Click to collapse
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
sabbotage said:
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
Click to expand...
Click to collapse
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
okantomi said:
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
Click to expand...
Click to collapse
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
sabbotage said:
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
Click to expand...
Click to collapse
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
okantomi said:
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
Click to expand...
Click to collapse
Thanks I jumped on there and i'll see what everyone says. I've tried it all and nothing is working.
I have Samsung Galaxy 2
I have custom ROM (Dark Knight V2) installed so
After installation screen does weird
I see the keyboard background, logo splash screen, different colors
........
After this problem I am back to stock ROM was not helped
what is his problem and how do I turn back
Please help me
serkonl said:
I have Samsung Galaxy 2
I have custom ROM (Dark Knight V2) installed so
After installation screen does weird
I see the keyboard background, logo splash screen, different colors
........
After this problem I am back to stock ROM was not helped
what is his problem and how do I turn back
Please help me
Click to expand...
Click to collapse
Did you wipe data and dalvik cache or did you just flash?
Did you flash via CWM or Odin?
I've tried everything
serkonl said:
I've tried everything
Click to expand...
Click to collapse
Surrreeee you have...
IF WE ARE TO HELP YOU MAKE A LIST OF EVERYTHING U HAVE TRIED... (caps for truth)
serkonl said:
I have Samsung Galaxy 2
I have custom ROM (Dark Knight V2) installed so
After installation screen does weird
I see the keyboard background, logo splash screen, different colors
........
After this problem I am back to stock ROM was not helped
what is his problem and how do I turn back
Please help me
Click to expand...
Click to collapse
What do you mean? Could you capture and upload a photo of it?
My S2 is running the new check rom and it works well
Sent from my GT-I9100 using xda premium
You have given us very little information to work with. Based on the information you have given, it sounds like you flashed a custom ROM known as Dark Knight V2, but when it boots up it goes "weird"
Try the following:
1. Boot into Clockwork Recovery
2. Wipe EVERYTHING (Cache, Davlik, System, Data\Factory Restore)
3. Flash the ROM again
If that fails, try putting the phone into "Download Mode" and flashing a STOCK ROM.
If those steps don't work, you need to give us more information.
http://imageshack.us/photo/my-images/28/img09092011225210.jpg
http://imageshack.us/photo/my-images/225/img09092011225145.jpg
i am back to stock rom but evertingh same
i upload foto
serkonl said:
http://imageshack.us/photo/my-images/28/img09092011225210.jpg
http://imageshack.us/photo/my-images/225/img09092011225145.jpg
i am back to stock rom but evertingh same
i upload foto
Click to expand...
Click to collapse
Also stop creating new threads about the same issue.
Do a hard reset of the device not a factory reset
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
jnktechstuff said:
MOD : EDIT
try dleeting you who system, except your recovery , there should be a system whipe that should work, then reflash ur rom
Click to expand...
Click to collapse
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
yeatsie said:
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
Click to expand...
Click to collapse
check you camera connector. It may come lose from the motherboard. Try reseat the connector.
Sent from my A500 using Tapatalk
.
opened up the A500 last night - all looked good, all connectors in place, nothing obviously wrong?
Noticed the screen when i switch to the rear camera has artifacts from other screens in the background (ie Pulse app title heading etc) suggesting some kind of software glitch?
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
Known issue in the CM10 alpha test ROM. You should go to the one in general rather than making your own thread which WayDownSouth is unlikely to see.
http://forum.xda-developers.com/showthread.php?t=1789711
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Moscow Desire said:
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Click to expand...
Click to collapse
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
yeatsie said:
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
Click to expand...
Click to collapse
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Moscow Desire said:
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Click to expand...
Click to collapse
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
yeatsie said:
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
Click to expand...
Click to collapse
Boot loader is different from cwm recovery. When you boot, it should say in white text.
If in doubt, run Acer recovery installer from the market. It will tell you which version.
MD
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
I have always had this intermittent problem on my a500. I have always used the stock ROM since I purchased it, and it's been the same since each OTA upgrade, so I doubt that it's a problem inherent to one custom ROM or the other.
A Dalvik cache clean has never worked for me, sometimes a restart has helped, but more often than not it doesn't help.
If someone discovers a set of steps that fixes this problem every time it occurs, I would be glad to hear of it.
yeatsie said:
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi, What was your final solution to this problem? I'm trying to fix mine right now.
-Thanks-
No fix as yet, pretty much gave up trying to use the camera.
Sent from my Nexus 7 using Tapatalk 2
If anyone else's having this problem with ONE OF THE CAMERAS (Not both of them but frontal OR main) then this should be the solution:
Watch this video someone uploaded https://www.youtube.com/watch?v=Cjevl8I6rIA but HAVE THIS IN MIND:
That cord (FLEX) he's talking about is for the FRONTAL camera. Not related with the main or back camera. So that should fix the green trouble for the frontal one.
But, if the main camera shows green image or weird lines, that's likely because its connector is not correctly attached to the main board. That connector is NOT a flex, but it's a built in block in the board of the same camera unit. You need to remove or lift the main board, totally remove the main camera unit, clean the connector (both male and female) with alcohol and connect it again applying some pressure. If the trouble really was the connector not being correctly placed, that totally fixes it.
If it worked, let me know
That totally worked and fixed my green screen camera problem, thanks! (was a total pain to re-seat the camera but worth it)
Does anyone know of a fix for the resolution getting reduced after rooting?
Resolution shouldn't change after rooting
Only thing I can imagine has happened, is you have managed to change the LCD Density setting with an app that needed root, and now you have root, it managed to change it
Normal setting in build.prop is 160
*Detection* said:
Resolution shouldn't change after rooting
Only thing I can imagine has happened, is you have managed to change the LCD Density setting with an app that needed root, and now you have root, it managed to change it
Normal setting in build.prop is 160
Click to expand...
Click to collapse
Any idea how to revert? I tried unrooting and restoring factory settings so it wiped out all the aps that were there. Any other ideas?
Aerobane said:
Any idea how to revert? I tried unrooting and restoring factory settings so it wiped out all the aps that were there. Any other ideas?
Click to expand...
Click to collapse
Hard to know what you mean by low resolution without any screenshots or photos.
When you unrooted, how did you do it, flash the stock ROM again? If you did flash back to 100% stock, it should be back to "normal"
Aerobane said:
Any idea how to revert? I tried unrooting and restoring factory settings so it wiped out all the aps that were there. Any other ideas?
Click to expand...
Click to collapse
Can you take a screenshot to show what you mean ?
You can edit build.prop using a text editor if you are rooted, it is in /system/build.prop
Lower section of the file has lcd density setting, mine is set to 160
My apologies for the lack of information in the first post. What happened was I rooted the tablet, I used the one button root found here under the tf101 forums, didn't do anything additional than that so if that script loads the stock rom then I flashed stock rom if not then I didn't. I then found an app on the marketplace to edit the screen density because after about 20 minuted of looking through build.prop i could not find a file that even remotely looked like pixel or LCD density. The app i used to change the pixel density said the screen res was 1280x752 but when it was stock before the screen res was 1280x800. After changing pixel density i started getting chain errors of launcher crashing when i'd start the tablet (poor choice to change it, I know) currently in rogue recovery trying to flash the stock rom.
Id would suggest flashing TWRP recovery using Easyflasher, then flash a Custom ROM from there
Recommend KatKiss 4.2.2 #226 or KatKiss 4.3.1 #27
Loaded KatKiss 4.3.1 but its hanging on the load screen with the dog and the colors
Aerobane said:
Loaded KatKiss 4.3.1 but its hanging on the load screen with the dog and the colors
Click to expand...
Click to collapse
Did you wipe everything before flashing ?
SYSTEM, CACHE, DALVIK CACHE, probably need DATA too if you're coming from an ancient ROM
And did you flash TWRP recovery first ?
I came from stock rom and this is my first time rooting so I'm not 100% sure what you mean by flashing the TWRP. I just used the one click root program from this forum. Right after I did it I noticed the resolution change, tried to find the lcd density value in build.prop with no luck so i then used cm recovery to boot to KatKiss. Now i still have the resolution error of it being 1280x752. What is the TWRP stand for?
TWRP = Team Win Recovery Project
It's a custom recovery that is recommended for Jellybean ROMs
Others work too, but some have issues like not booting once you've flashed JB
Run Easyflasher, choose TWRP recovery
http://forum.xda-developers.com/showthread.php?t=1688012
EDIT - Download Updated Easyflasher (Use this one to flash TWRP, it contains a newer recovery version)
https://hostr.co/cMzNtGRqE1nJ
Then when you have TWRP working as your recovery, flash your KatKiss ROM again
*Detection* said:
TWRP = Team Win Recovery Project
It's a custom recovery that is recommended for Jellybean ROMs
Others work too, but some have issues like not booting once you've flashed JB
Run Easyflasher, choose TWRP recovery
http://forum.xda-developers.com/showthread.php?t=1688012
EDIT - Download Updated Easyflasher (Use this one to flash TWRP, it contains a newer recovery version)
https://hostr.co/cMzNtGRqE1nJ
Then when you have TWRP working as your recovery, flash your KatKiss ROM again
Click to expand...
Click to collapse
It says the table needs to be in APX mode to flash twrp but ive tried holding power up and hitting the power button to put it in apx with no luck at all. Now KatKiss simply hangs on the load screen.
Made it into KatKiss again, nothing changed, but I do not believe the Easyflasher ran correctly due to the APX mode issue I'm having. To clarify, i have the tablet connected to my pc, have easyflasher on the pc set to the correct SB mode and then set it to flash twwp i get a dialog asking if I am in APX mode but when i power off the tablet and try to power into APX by holding the up volume rocker and hitting the power key nothing happens. I know the screen should remain black but my computer is also not picking it up as being connected then. Any ideas?
Plug it into the PC > USB
Turn it off
Hold Power & Volume Up until you hear the USB connection sound, the PC should recognise the device in APX mode
Nothing will happen on the TF screen
Now run Easyflasher
*Detection* said:
Plug it into the PC > USB
Turn it off
Hold Power & Volume Up until you hear the USB connection sound, the PC should recognise the device in APX mode
Nothing will happen on the TF screen
Now run Easyflasher
Click to expand...
Click to collapse
Have tried that, it seems to be stuck in a loop now, if i power off the tablet it just reboots right away by itself
It's becoming clearer that I'm terrible at this. Got it into APX mode and ran the easyflash, it only ran for maybe a second then asked me to boot into recovery but it's still showing the team rogue xm revovery.
I finally got TWPP to load and successfully got everything installed. The down side is im still showing resolution at 1280x752 and the pixel density is set to 160. I have no clue where to go from here.
The screen resolution changing to 1280x752 is not actually changing the resolution. The other 48 pixels are the nav bar at the bottom. Most screen resolution apps will report the screen resolution not including the nav bar.
Using CPU-Z app, my screen resolution is only 1280x800 when I hide the nav bar at the bottom.
frederuco said:
The screen resolution changing to 1280x752 is not actually changing the resolution. The other 48 pixels are the nav bar at the bottom. Most screen resolution apps will report the screen resolution not including the nav bar.
Using CPU-Z app, my screen resolution is only 1280x800 when I hide the nav bar at the bottom.
Click to expand...
Click to collapse
Feel really dumb now, thanks for the help both of you and the initial resolution :/
Yea as Fred says, that Rez and LCD Density is correct now
*Detection* said:
Yea as Fred says, that Rez and LCD Density is correct now
Click to expand...
Click to collapse
I even hid the bar so it shows that the res is now 1280 x 800 and wallpapers that size still dont fit but oh well i at least have it stable with a ROM I like now.
Aerobane said:
I even hid the bar so it shows that the res is now 1280 x 800 and wallpapers that size still dont fit but oh well i at least have it stable with a ROM I like now.
Click to expand...
Click to collapse
The wallpaper issue is due to scrolling. You can try an app like Wallpaper Wizardrii to help set wallpaper that does not scroll.
I am too facing this problem
Please help me here is a screenshot
Installed a custom rom, was working great all day. All of a sudden I sat my phone on the bed to grab something, turned around and my selfie camera was popped up. Tried to switch from rear camera to front camera in hopes it'll go down but no go. Any suggestions on how to fix this?
reboot? flash stock rom over miflash
C2000K said:
reboot? flash stock rom over miflash
Click to expand...
Click to collapse
Try this! https://forum.xda-developers.com/mi-9t/how-to/guide-fix-popup-camera-calibration-t3987251