So before anything this is what I have.
SPL: Danger SPL
MOD:Cyanogen 4.0.4
RADIO: latest
THEME: CyanogenMod-4.0.4-CustomV7 by: Z҉A҉L҉G҉O
So what happened was after I installed this theme everything was running smoothly. My phone was low on battery so I pluged in my Charger. After being on the phone while charging for 30 - 60 minutes my touch stopped working, so I turned it off and on thinking it'll fix the problem and it didn't.
I leave it alone hoping the touch will comeback the the next morning and it didn't. So I wiped and reinstalled CyanogenMOD 4.0.4 hoping that'll do the trick and it juat made things worse.
Now I'm stuck a the "Tap the Android Screen To Begin" and I can't tap it because my touch isn't working.
Is there any way to fix this or just skip that screen?
I need to ge4t back to my gf or all hell is going to break loose.
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
i agree if a reflash didnt work your g1 needs to go under the knife
JJbdoggg said:
i agree if a reflash didnt work your g1 needs to go under the knife
Click to expand...
Click to collapse
He never said it was a "G1"...
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
No I don't, it would always say error when I tried that.
and how do I kill the process?
Thanks in Adavance if you teach me how.
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
marlopainter said:
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
Click to expand...
Click to collapse
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
AustinAce said:
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
Click to expand...
Click to collapse
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
fenixnr said:
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
Click to expand...
Click to collapse
Exactly, why would you think it's a good idea to put your phone in the fridge?!
THIS ENTIRE THING HAPPENED BEFORE I PUT MY PHONE IN THE FRIDGE.
Can someone just help me skip the initial process, or just teach me how change the Cyanogen image at the beginning to the original android image.
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
jmon777 said:
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
Click to expand...
Click to collapse
I kinda don't know what that is.
from the beginning:
I had the hard SPL and wanted the custom V7 them cyan 4.0.4 so I installed Danger.
Then installed the theme, and once I plugged my charger in my touch stopped working so I tried turning it off and on to fix it and it still wasn't working.
So i tried to wipe and reinstall 4.0.4 and got stuck into "tap android screen"
Now I'm back to the hard SPL but I still get stuck at the beginning.
I'm going to send it in, because I think it's a hardware issue not a software issue.
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
So I should jusr send it in?
AustinAce said:
So I should jusr send it in?
Click to expand...
Click to collapse
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
AdrianK said:
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
Click to expand...
Click to collapse
you can also edit cpu speeds as well has some other things. but your right mainly used for swap settings.
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the rc29
And when I tried flasjing cupcake it said something about no signatures error
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
AustinAce said:
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
Click to expand...
Click to collapse
Are you useing the one that came from tmobile? If its hard to find there a guy that has I like in his sig ill try and find it for u if u can't.
Related
Ok so, i just added the Fresh Toast v1.1, it was working AMAZINGLY. But then i accidentally hit the camera button while tryin to remove it from the home screen, it poped up the camera, Said "Updating PRL", force closed like 4 programs, then rebotted it self. Since then, no service. Contacted sprint (Did'nt tell them it was rooted) but they did a few master resets, troubleshooting here and there. still nothing
note: did wipe/factory reset twice and reinstalled toast, didnt work
note: also wiped, then restored my nanoid back up. also didnt work
anyone know how to help me out? would prefer not to have to go to the sprint store then they find out its rooted >.>
would greatly appreciate the help
Downtime24 said:
Ok so, i just added the Fresh Toast v1.1, it was working AMAZINGLY. But then i accidentally hit the camera button while tryin to remove it from the home screen, it poped up the camera, Said "Updating PRL", force closed like 4 programs, then rebotted it self. Since then, no service. Contacted sprint (Did'nt tell them it was rooted) but they did a few master resets, troubleshooting here and there. still nothing
note: did wipe/factory reset twice and reinstalled toast, didnt work
note: also wiped, then restored my nanoid back up. also didnt work
anyone know how to help me out? would prefer not to have to go to the sprint store then they find out its rooted >.>
would greatly appreciate the help
Click to expand...
Click to collapse
wow... idk man, i actually have no clue really. ive been hitting the camera button for days trying to debug camera and havent ran into some crazy stuff like that. all it does is sit with a black screen on mine.
oh man! and your 1 of the developers lol
my phone is done?
Downtime24 said:
oh man! and your 1 of the developers lol
my phone is done?
Click to expand...
Click to collapse
Nah. Just RUU back to 1.5, that oughta fix it.
smw6180 said:
Nah. Just RUU back to 1.5, that oughta fix it.
Click to expand...
Click to collapse
+1, RUU back will usually fix any crazy abnormalities. This will unroot your phone too, so if you do need to bring it to sprint, it will be back to complete unrooted factory
Yeah man go ahead and ruu. Or flash fresh 2.0d first and see if that fixes it. His Rom includes a pri fix
sounds like a plan lol.
mind providing the link to RUU? I've never done it before
Fresh 2.0d has a PRI fix?!? I've loaded that before and my PRI still says Flipz_01...
SupahDave said:
Fresh 2.0d has a PRI fix?!? I've loaded that before and my PRI still says Flipz_01...
Click to expand...
Click to collapse
That is the PRI fix.... If your PRI is Flipz_01, you're good..
Also, the RUU is here:
http://forum.xda-developers.com/showthread.php?t=608434
did the RUU, but at the end it gives me an error, now my hero aint responding at all O
errors the file open error, re-downloaded about 6 times, still hasnt worked T_T
i would reccomebd unrooting sans sd card.
theres a fix floating around for the ruu error, assuming your getting the same one
good luck!
mountaindont said:
i would reccomebd unrooting sans sd card.
theres a fix floating around for the ruu error, assuming your getting the same one
good luck!
Click to expand...
Click to collapse
Search ruu error 110 fix. This should help fix the problem
I rooted my phone and was doing about to flash fresh when my phone started rebooting. I`m able to use the phone, but the Sdcard and USB do not work....what can i do. i`d like to get back to stock unrooted....whatever is easiest for me to start over with. Thanks!
skovy said:
I rooted my phone and was doing about to flash fresh when my phone started rebooting. I`m able to use the phone, but the Sdcard and USB do not work....what can i do. i`d like to get back to stock unrooted....whatever is easiest for me to start over with. Thanks!
Click to expand...
Click to collapse
Try this. http://forum.xda-developers.com/showthread.php?t=695243
bccbryan said:
Try this. http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
for whatever reason I cant get that method to work....been trying to work it since 10am this morning. Now my HTC sync is messed up...I have uninstalled reinstalled still same error, "missing tlib_log.dll" file from computer? I`m not sure what to do....I``m still within thirty days to return to to BB...not sure if they`ll even take it?
long story short, i had root and oclf, i uninstalled it and installed voodoo, let system sit for 30 mins, i guess i got impatient, so i pulled and restored, i created the disable_lagfix file and it ran through the paces, so i decided to put one of the other roms back on that had d1 update.. anyways, it loaded but i had NO cell radio, none, also i seem to get a invalid argument when booting up to recovery but i can still boot into CWM, i have tried to restore just the modem file part to see if that works but i think it freezes about 2/3 of the way and i get a scirpt ABORTED MESSAGE (STATUS 7).
I really need someones help.
any suggestions
Odin! Or you can just odin clockwork kernal and find the nanadroid back up on here. Then restore.
magicriggs said:
Odin! Or you can just odin clockwork kernal and find the nanadroid back up on here. Then restore.
Click to expand...
Click to collapse
tried that, several times, no luck.. i took it back to the store cuz i was under 30 days, it was just easier that way. Ill run a proper CWM back up this time
Andwhy81
Not saying u did this but not having a cell radio is often a symptom of flashing something in the "phone" part of Odin instead of in the "PDA" again not saying u did this but I've seen several instances of people having this problem in irc all being caused by that. Be a little more careful with the new one. I do t think a backup will even save u if u flash something to the phone part. Goodluck sir
Sent from my SCH-I500 using XDA App
ksizzle9 said:
Andwhy81
Not saying u did this but not having a cell radio is often a symptom of flashing something in the "phone" part of Odin instead of in the "PDA" again not saying u did this but I've seen several instances of people having this problem in irc all being caused by that. Be a little more careful with the new one. I do t think a backup will even save u if u flash something to the phone part. Goodluck sir
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
That is a possabilty, i was up late and tired, thanks for not flaming.
i now have voodoo and loving it,
andwhy81 said:
That is a possabilty, i was up late and tired, thanks for not flaming.
i now have voodoo and loving it,
Click to expand...
Click to collapse
You could easily determine this by looking in setting - about phone - baseband version. If it says uknown, you've killed your cell radio by flashing to "phone" instead of "pda." If you have a version number, you're fine.
I flashed CWM into "phone" instead of "pda". Is there really no fixing it? I've tried nandroid recovery, Odin, everything and still no cell radio and also force closes everywhere...
Also will VZ take the phone back? The phone's less than a week old...I'll make sure to be more careful next time
Try and say you tried to run the ota update and it loaded that
Sent from my SCH-I500 using XDA App
Ahodson1985 said:
I flashed CWM into "phone" instead of "pda". Is there really no fixing it? I've tried nandroid recovery, Odin, everything and still no cell radio and also force closes everywhere...
Also will VZ take the phone back? The phone's less than a week old...I'll make sure to be more careful next time
Click to expand...
Click to collapse
Yes, there's really no fixing it. To fix the FC issues you need to get to the OS to do a privacy wipe, or wipe /dbdata from the shell. I would start with restoring everything from the Odin post to get everything back to stock. At least when you go to return it, it will look like a fully functioning phone, with just a radio that happened to crap-out.
namebrandon said:
Yes, there's really no fixing it. To fix the FC issues you need to get to the OS to do a privacy wipe, or wipe /dbdata from the shell. I would start with restoring everything from the Odin post to get everything back to stock. At least when you go to return it, it will look like a fully functioning phone, with just a radio that happened to crap-out.
Click to expand...
Click to collapse
yep i flashed something to the phone part of my phone too. no signal and no baseband version. took it to verizon and they said since i didnt get it from them, they cant relplace it. samsung said that i hafta mail it in to be repaired. freakin gay. if they dont fix it, its not much a problem for me cause my contract expires next month so ill make a new one and get the same phone. until then im on my sch-u740 lol
hopefully some baseband files get leaked so those of us who did this can fix it.
This has scared me from using odin behond installing CWM, i hope froyo wont crap anything with voodoo.
em.Tea said:
yep i flashed something to the phone part of my phone too. no signal and no baseband version. took it to verizon and they said since i didnt get it from them, they cant relplace it. samsung said that i hafta mail it in to be repaired. freakin gay. if they dont fix it, its not much a problem for me cause my contract expires next month so ill make a new one and get the same phone. until then im on my sch-u740 lol
hopefully some baseband files get leaked so those of us who did this can fix it.
Click to expand...
Click to collapse
so there is no way to fix this at the moment?
lucious584 said:
so there is no way to fix this at the moment?
Click to expand...
Click to collapse
nope. unless someone somewhere releases the complete baseband file, and we flash that. the only thing we have close to that is the modem update which is just an update to an existing modem.
btw random question that might save us,
if someone skilled pulls SCH-I500_OpenSource.zip from opensource.samsung.com, maybe theres a baseband file there somewhere that just needs to be built? idk just a desperate thought
em.Tea said:
nope. unless someone somewhere releases the complete baseband file, and we flash that. the only thing we have close to that is the modem update which is just an update to an existing modem.
btw random question that might save us,
if someone skilled pulls SCH-I500_OpenSource.zip from opensource.samsung.com, maybe theres a baseband file there somewhere that just needs to be built? idk just a desperate thought
Click to expand...
Click to collapse
yeah i fixed my problem i just did a nand restore. Fixed it right up
lucious584 said:
yeah i fixed my problem i just did a nand restore. Fixed it right up
Click to expand...
Click to collapse
really? that didnt work for me
em.Tea said:
really? that didnt work for me
Click to expand...
Click to collapse
He was talking about some other problem.. There's no way to fix the modem.bin file issue at this point. It's been a problem since the device was released, the only fix I can see in our future is an official firmware release from Samsung.
namebrandon said:
He was talking about some other problem.. There's no way to fix the modem.bin file issue at this point. It's been a problem since the device was released, the only fix I can see in our future is an official firmware release from Samsung.
Click to expand...
Click to collapse
Yeah different problem. I found out i did have cell service but it took forever for the phone to find it. It took about 30-40 minutes.
namebrandon said:
He was talking about some other problem.. There's no way to fix the modem.bin file issue at this point. It's been a problem since the device was released, the only fix I can see in our future is an official firmware release from Samsung.
Click to expand...
Click to collapse
Yeah lets not start breath holding
For that
Sent from my 1.2Ghz voodoo fascinate
I don't have a baseband file but i may have a fix for this. I just need to know if you are able to boot into CWM.
Hey people.
I'm just looking to findout how many of us have the issue of bootlooping (splash screen) overclock kernel is installed...?
I have seen at least 10 ppl on here - please post so it gets known how many we are.
I have tried formatting SD-card w both HP-formatter and Panasonic SD Formatter - neither helped -
I have Cleared Dalvik, Wiped Cache, Wiped to Factory Settings - and redone it over and over.
Nothing helps. Bootloop. As soon as i reflash Froyo kernel official (0050 on WildPuzzle Rom) everything works perfectly.
I have ruled out that the problem would be in SD-card. I have tried three diff cards of various brands and sizes - and also tried without SD-Card. All resulting in Bootloop when OC is flashed.
ADB won't let me get a logcat - as it don't find a device connected - or - as in the latest v5 OC kernel, says Device is offline.
How many - and who - has this issue - There has gotta be something we can do? POST to show the devs you exist please.
I have the same problem too. I've just installed new roms and also kernels. Nothing happened. My wildfire won't boot-up
I understand your frustration guys, really.
Unfortunately though, it is hard for me to be able to fix it without any logs, and I don't have time to play around with potential causes at the moment.
Hope you guys understand
We so do.
But is there noway to get a log w-o booting past splash?
HCDR.Jacob said:
I understand your frustration guys, really.
Unfortunately though, it is hard for me to be able to fix it without any logs, and I don't have time to play around with potential causes at the moment.
Hope you guys understand
Click to expand...
Click to collapse
Here's a question to everyone who cant boot OC - what color is your phone?
the 2 i gave physically encountered that have the problem are both red...?
I solved my bootloop by simply removing my SD-card and then booting. :O Format didnt work forme neither.
try it out
I have - made no difference. As i said before - there is no way that the issue is with the sd-card... I have tried everything regarding that. Results are the very same with - or without sd-card...
But thanks for trying to help...
danne_jo - adeadrat? any of you two live anywhere near stockholm..? if yes i could meet either of you and you can see the issue 1st hand..? maybe you can dig out a log somehow?
worst case scenario (i am desperate yes) maybe i can mail my phone to you jacob and you send it back in two weeks or so? (can't believe i'm saying this)
Phinxy said:
I solved my bootloop by simply removing my SD-card and then booting. :O Format didnt work forme neither.
try it out
Click to expand...
Click to collapse
fireplayer said:
We so do.
But is there noway to get a log w-o booting past splash?
Click to expand...
Click to collapse
Perhaps you can get the logcat via adb when in recovery?
naserbaser said:
Perhaps you can get the logcat via adb when in recovery?
Click to expand...
Click to collapse
There's a kernel debug message system too, although I'm not sure if it'd work if adb doesn't
fireplayer said:
I have - made no difference. As i said before - there is no way that the issue is with the sd-card... I have tried everything regarding that. Results are the very same with - or without sd-card...
But thanks for trying to help...
danne_jo - adeadrat? any of you two live anywhere near stockholm..? if yes i could meet either of you and you can see the issue 1st hand..? maybe you can dig out a log somehow?
worst case scenario (i am desperate yes) maybe i can mail my phone to you jacob and you send it back in two weeks or so? (can't believe i'm saying this)
Click to expand...
Click to collapse
I don't want you to mail me your phone. I'll help out where I can, but if you send your phone to me and it gets lost in the post or I accidentally kill it, I'll feel really bad so I'd rather you didn't :/
hehe, no im not living close to stockholm, and sorry I can help out either
I had the bootlooping too, but that was untill i used the Remove HTC apps puzzle piece, maybe it's sense / rosie thats causing the issue, i'll try my best to look into it.
Been stupidly busy as of late, haven't had time to even work on my own rom lol, peace yall
So how would I get to that..? Everything is worth a try..
HCDR.Jacob said:
There's a kernel debug message system too, although I'm not sure if it'd work if adb doesn't
Click to expand...
Click to collapse
Sent from my HTC Wildfire using XDA App
understandable lol. just trying to make something happen ;p it's frustrating...
HCDR.Jacob said:
I don't want you to mail me your phone. I'll help out where I can, but if you send your phone to me and it gets lost in the post or I accidentally kill it, I'll feel really bad so I'd rather you didn't :/
Click to expand...
Click to collapse
tried that - didn't help, tried openfire rom too - same result.
Elbie said:
I had the bootlooping too, but that was untill i used the Remove HTC apps puzzle piece, maybe it's sense / rosie thats causing the issue, i'll try my best to look into it.
Been stupidly busy as of late, haven't had time to even work on my own rom lol, peace yall
Click to expand...
Click to collapse
fireplayer said:
tried that - didn't help, tried openfire rom too - same result.
Click to expand...
Click to collapse
Curious but which version of the touch screen do you have?
You can find out by pressing the Vol Down button and Power button at the sam time when turning on the wildfire.
A Load of txt will come up, Will tell you if you have the Atmel or not.
Could be that as I know the PSFreedom guys are having issues with the other type of touch panel.
Elbie said:
Curious but which version of the touch screen do you have?
You can find out by pressing the Vol Down button and Power button at the sam time when turning on the wildfire.
A Load of txt will come up, Will tell you if you have the Atmel or not.
Could be that as I know the PSFreedom guys are having issues with the other type of touch panel.
Click to expand...
Click to collapse
I have the same problem.
My touch panel is ATMELC03_16ac.
I too have the atmel, and I have no issues, although I have gone back to the non OC kernel as it seams more stable. I had a few force closes on a few apps...allllll the time, double twist mainly lol.
Ummm confusing one this..
Hi all the guru,
Please..Need help.. My wildfire have problem that is always bootlooping also..
I just updated from puzzlerom 8.07 to 8.10.. successfull then I do partition sdcard ext.. the WF rebooting it seft... until now..
Just flash rom again, but this theme is about OC problems...
Hi, I got my Nexus 7 yesterday. Everytime I leave it in sleep mode for more than 10 minutes it shuts down and i need to hard reboot. I've read somewhere that its possibly Sleep of Death. I tried shutting wifi of during sleep, installed an auto airplane mode app, reset to factory settings about 5 times but nothing seems to help. I run stock rom, not rooted. Do you think i should return it or is there a possible sollution? Greatings
I'd return it
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Build number is JRO03D
Goldcell said:
Build number is JRO03D
Click to expand...
Click to collapse
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
kris4o2 said:
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
Click to expand...
Click to collapse
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm stock. I've never used a custom ROM or rooted my devices.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Goldcell said:
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
Click to expand...
Click to collapse
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
irishrally said:
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Click to expand...
Click to collapse
Is reflashing the stock rom the same as resetting it to factory settings?
Silentbtdeadly said:
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
Click to expand...
Click to collapse
I don't have my box anymore. Is there another way to see what your hardware number is?
kris4o2 said:
I don't have my box anymore. Is there another way to see what your hardware number is?
Click to expand...
Click to collapse
I'm not exactly sure, I know the sticker on the back of the tablet itself, toward the bottom has it.. I'm still somewhat new to this tablet yet.
Goldcell said:
Is reflashing the stock rom the same as resetting it to factory settings?
Click to expand...
Click to collapse
I said in my last post, restoring to factory just deletes the /data partition, and leaves the /system files exactly the same. Reflashing actually overwrites the system files.
I get it occasionally but I'm running a CM nightly and Clemsyns elite kernel so I chalk it up to that.
I've flashed stock rom and several other roms, but it did not help so I've returned it for a new device, i have to wait 3 weeks for a new one . Thanks for the replies!