So I bought the GTab today,the stock UI wasn't very responsive and was quite slow, so I went about installing a custom firmware on it.
I started out with zPad, it booted up fine, but I needed to reboot. After I rebooted, it went into a boot loop. I tired reflashing back to stock with nvflash, but the boot loop wasn't resolved. Thanks to the help of some guys in the chat room, I repartioned the internal storage, flash with nvflash again, and it eventually booted.
However, after it booted, the touch screen no longer works. The menu buttons work, the volume works, the device will rotate, but it does not register any screen presses.
I reflashed with zPad, TNT, Cyanogen, and stock. None of them work with the touch screen.
What's going on? Was it just a random fluke?
At this point, I'm thinking I have no recourse but to return it. But I'd like to keep it as there aren't any more GTab's in stock locally.
I gave up and returned it.
They didn't have any others in stock, so it looks like I'll have to wait a week and a half before I get another.
mine had the same problem but with the stock rom.. took it back.. staples was out so I got a refund and got a new one from sears.. works better now
Related
Howdy,
I noticed on my phone that my screen locker looked wierd so i soft reset the phone then played a game of madden and looked down at my phone and it was at the orange windows boot screen hung up at it. I soft rest again then it would flake out at the verizon splash screen i soft reset a bunch of times and still the same results. I yanked the battery and let it sit for an hour and still nothing i replaced the battery and nothing.
So i proceeded to go into bootloader and hooked it to pc and reflashed with the stock MR2 verizon rom and now its hung up on the white htc screen with the red writing at the bottom.
Only thing done to the phone was HArd-SPL a week or 2 ago with no rom flashes after was on the stock rom.
Ive searched the topic also and am thinking i might have to do a task 29?
ATM im going to try and flash the first stock VZW rom and see where that goes but likely same outcome.
so do i have a brick or is there a fancy way to get it working?
got it working with the MR1 update so im good
Hi all,
I've had my HTC sensation for about 9 months. I've flashed the phone twice with HD revolution roms. The last flash was conducted about a month ago and is currently running version 3.6.1. Around 2 days ago the phones screen, short cut keys below the screen, power button and volume stopped responding. Upon rebooting the phone the screen and all buttons will respond perfectly normal however. It is only when you turn the screen off or it goes into sleep state automatically after the reboot the screen, shortcut keys, power and volume buttons stop responding again when powered back on. After this the phone needs to have the battery taken out and rebooted before anything can be used again. In this state the phone is completely useless, only being able to be used once the phone has been rebooted and the screen must be prevented from going into a sleep state.
The last form of any sort of software update I can remember before the problem began occuring was updating facebook
I have not tried super wiping and reflashing a new rom yet.
If anyone could suggest something it's highly appreciated.
Regards,
Samuel
I've had the phone quoted by a repairer saying the touch screen needs to be replaced but I don't see how this can be so.
It works perfectly fine on initial boot. It also doesn't explain why all the other buttons cease to work.
Hi Samuel,
by the sound of it I'd say your touchscreen is working fine, I think its more likely that your Android OS has got screwed up a bit at some point. If it was mine I'd do a nandroid backup of your currunt OS, and then superwipe and reflash a fresh installation of ARHD on it. If that doesnt work you can always go back to the nandroid backup you make.
Probably be worth waiting to see what some other XDA members think though.
Good luck with it.
You might check your SD-card for errors.
So, we keep coming back to our TF's and seeing that it has rebooted- has anyone seen a reboot, while the tf was on in their hands, doing something? Or is it safe to assume this is a sleep-related issue?
...just had my 1st random reboot. I was reading your scathing remarks in another thread and decided to look and see what my battery status was. It rebooted on the settings screen as I was setting it back down. On the bright side, it came right back up and is running fine.
I'm currently running [ROM/WIP][Unofficial] CyanogenMod 9 for TF101 and have only had the known issues in the OP. The script fix Tahl came up with for the MicroSD not mounting took care of the only one I really cared about.
Weird these RRs though, any thoughts?
Mine went through a random reboot while in my hands. This has happened once this whole time since ICS was released up to now. It has also randomly rebooted while sleeping at least twice.
Yes, it does seem to come back up, mine hangs on boot when it does, but I think that has something to do with being on the dock...yet I've tried manually rebooting while docked and closing the lid, and that doesn't make the device hang as it previously did on it's own RR at the boot animation.
But, speaking of which, I modified the old CMOS-style boot animation to reflect the ICS update..for both 16GB and 32 GB models
http://forum.xda-developers.com/showpost.php?p=23093227&postcount=9
I did have one reboot while in my hand with the stock rooted ICS ROM. With the Team Eos ROM i have had two instance of coming back to a tablet sick at the Eee screen. Reboot solved problems both time. will see how it goes tomorrow with a full night sleep.
FWIW. I also just installed Apex launcher work this ROM.
i did not have a reboot while holding my tf in hands so far, but i already had the case, that i found the tf hanging on bootscreen after obviously rebooting out of sleep mode...
...and as i have no dock, this does not seem to cause it.
luna_c666 said:
Yes, it does seem to come back up, mine hangs on boot when it does, but I think that has something to do with being on the dock...yet I've tried manually rebooting while docked and closing the lid, and that doesn't make the device hang as it previously did on it's own RR at the boot animation.
But, speaking of which, I modified the old CMOS-style boot animation to reflect the ICS update..for both 16GB and 32 GB models
http://forum.xda-developers.com/showpost.php?p=23093227&postcount=9
Click to expand...
Click to collapse
Now that you mention it, I had just installed my own custom boot animation (based on the TV show `Fringe`) - coincidence? Mine hasn't hung there though, it has always booted up completely...
Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.
Hello,
I recently changed the LCD of a S6 edge. I installed it and turned it on and it booted up fine. I went to make sure everything was working. While I was playing music it would restart. I thought it was odd, so i was waited til it came back on and started using other apps. Same thing..restart. So, i booted to safe mode. Same thing...restart.
So, I tried factory resetting. After that, it would just get stuck in a endless restart loop cycle.
I have also tried reinstalling the OS using Odin. I ran Odin and it said everything passed. The phone restarts and goes to installing updates.
It gets to 32% every time then it says "erasing". After a few seconds of displaying "erasing" it just starts its endless reboot cycle again.
**EDIT: I should add that it never restarts when it's in the download manger.** So, that makes me think its a OS issue.
*EDIT#2: This is a good video. I did all of this. Got to the 9 minute mark and where his comes on, mine restarts again.
Any help?
Thank you!
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
3mel said:
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
Click to expand...
Click to collapse
Hi,
thank you for your reply. I learned about all of this last night lol. so, i'm not exactly sure what you mean. I bought the LCD+frame from Ebay. It stated it was pulled from a working unit.
Could a bad battery cause all these issues? I notice when i power down (only way I can power down is if I Hold POWER+VOL DOWN and select power down) that the LED light stays on.
Hello, could someone delete this thread. I have posted a more detailed thread on this issue.
if it says it's an LCD screen it's not an original part. my point was that some people have had issues booting up roms because of screens.
that was something that was fixed in custom roms though so if you can't another solution a custom rom that works with 3rd party LCD displays might be an option to consider.