so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
"HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
Press key to choose Dload Mode/Reboot/Fasatboot.
1) Vol up : Dload mode.
2) Vol Down : Reboot.
3) Power : Fastboot
If you choose Dload Mode,
Please do the following action.
1) Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Dubug App
3) Send email to contact point or [email protected]
--------------------------------------------------"i was very careful to press the Vol Down button...hell, i even looked at the button cause i was a bit off put by this funky screen. well it seems to have received a Vol Up command and replied with:
"Vol Up is pressed : Jump to Dload Mode."
I tracked down and installed the QPST 2.7 but am unable to get it to detect my phone. So I guess i'm off to BestBuy in a few minutes. joy.
thought i'd share this in case it's of any use to anyone. i'm not a developer nor a programmer. but i've mucked about with Android for a while and have not seen such a screen in the past...nor have i come across something i couldn't eventually undo/back out of. but i can't pull the battery...i've pressed all buttons...i've pressed both Vol+/Vol- at the same time...can't get the phone to reboot. damn non-removable battery.
edit: holding down pwr button for more than a few seconds resolved it. yes, i freaked out a bit.
Did you hold the power button in for 20 seconds to force a shut down and then just turn it back on?
DraginMagik said:
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
"HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
Press key to choose Dload Mode/Reboot/Fasatboot.
1) Vol up : Dload mode.
2) Vol Down : Reboot.
3) Power : Fastboot
If you choose Dload Mode,
Please do the following action.
1) Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Dubug App
3) Send email to contact point or [email protected]
--------------------------------------------------"i was very careful to press the Vol Down button...hell, i even looked at the button cause i was a bit off put by this funky screen. well it seems to have received a Vol Up command and replied with:
"Vol Up is pressed : Jump to Dload Mode."
I tracked down and installed the QPST 2.7 but am unable to get it to detect my phone. So I guess i'm off to BestBuy in a few minutes. joy.
thought i'd share this in case it's of any use to anyone. i'm not a developer nor a programmer. but i've mucked about with Android for a while and have not seen such a screen in the past...nor have i come across something i couldn't eventually undo/back out of. but i can't pull the battery...i've pressed all buttons...i've pressed both Vol+/Vol- at the same time...can't get the phone to reboot. damn non-removable battery.
Click to expand...
Click to collapse
Like Whiteguypl just said... thats all you have to do. Just hold power off for 20 seconds and it will turn off. Then you reboot it. It will boot up fine.
It was just a HW crash.
My phone has had it happen quite a few different times and its still running.
Jhoopes517 said:
Like Whiteguypl just said... thats all you have to do. Just hold power off for 20 seconds and it will turn off. Then you reboot it. It will boot up fine.
It was just a HW crash.
My phone has had it happen quite a few different times and its still running.
Click to expand...
Click to collapse
The demigod screen I had said watchdog bark detected, it also registered vol dn as vol up. Wouldn't boot and went into dl mode when connected to charger, had to use lgnpst to fix it.
thank you guys. in my concern i guess i wasn't holding down the power button long enough. i was doing a 10count in my head...which was prolly more like 5 or 6 seconds given how my mind was like "awww crap".
Also, for future reference, most of the debug screens seem to swap volume up and volume down. And I got this screen once, but never have had it again.
Sent from my LG-E970 using xda app-developers app
SnowLeopardJB said:
Also, for future reference, most of the debug screens seem to swap volume up and volume down. And I got this screen once, but never have had it again.
Click to expand...
Click to collapse
well that is just ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Eh, vol up... Vol down... Same difference.
Sent from my LG-E970 using Tapatalk 2
I've been meaning to ask about this, but since I'm a noob, I didn't want to get flammed. I've been getting a similar crash screen on average of twice a day ever since I unlocked the OG. Everything is the same as your HW crash screen, except that it says "Kernel Crash" instead. After realizing the volume buttons were switched I've just been restarting with the power button.
Anyone else getting that crash? It's getting annoying especially since if it happens when it was supposed to be asleep in my pocket, the screen being on will suck down my battery. Fortunately, since it's a new toy, it doesn't stay in my pocket long, but at some point this could be trouble.
In case it matters, I unlocked using the FreeGee app (TWRP recovery) and am currently running The Base 0.7.3 and KernelSk8 2.2, but it did it back when I just had the stock ROM and kernel as well. Any insight would be appreciated. I may be a noob, but I've spent hours on this forum reading up on this phone, and that has helped me immensely, but this is the first issue I've come across that hasn't been addressed until this thread.
Sent from my Nexus 7 using Tapatalk HD
DraginMagik said:
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
"HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
Press key to choose Dload Mode/Reboot/Fasatboot.
1) Vol up : Dload mode.
2) Vol Down : Reboot.
3) Power : Fastboot
If you choose Dload Mode,
Please do the following action.
1) Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Dubug App
3) Send email to contact point or [email protected]
--------------------------------------------------"i was very careful to press the Vol Down button...hell, i even looked at the button cause i was a bit off put by this funky screen. well it seems to have received a Vol Up command and replied with:
"Vol Up is pressed : Jump to Dload Mode."
I tracked down and installed the QPST 2.7 but am unable to get it to detect my phone. So I guess i'm off to BestBuy in a few minutes. joy.
thought i'd share this in case it's of any use to anyone. i'm not a developer nor a programmer. but i've mucked about with Android for a while and have not seen such a screen in the past...nor have i come across something i couldn't eventually undo/back out of. but i can't pull the battery...i've pressed all buttons...i've pressed both Vol+/Vol- at the same time...can't get the phone to reboot. damn non-removable battery.
edit: holding down pwr button for more than a few seconds resolved it. yes, i freaked out a bit.
Click to expand...
Click to collapse
Off topic but how did you get your Ingres activation code? I've been trying for over a month with no success.....
Nastybutler said:
In case it matters, I unlocked using the FreeGee app (TWRP recovery) and am currently running The Base 0.7.3 and KernelSk8 2.2, but it did it back when I just had the stock ROM and kernel as well. Any insight would be appreciated. I may be a noob, but I've spent hours on this forum reading up on this phone, and that has helped me immensely, but this is the first issue I've come across that hasn't been addressed until this thread.
Click to expand...
Click to collapse
i'm rooted/unlocked running TWRP & TheBase .7.3. used the FreeGee app as well.
have you tried reflashing TheBase and not using Sk8's kernel?
if it happens with TheBase and Sk8's kernel...then i'd post the question and error in that thread.
if it happens with TheBase and either kernel...then i'd try posting in TheBase thread.
don't be afraid of getting flamed. we all ask dumb questions from time to time and we are all weak on some topics...just try not to come off sounding rude or belligerent and most folks will do as they can to help.
Yamahar6riding said:
Off topic but how did you get your Ingres activation code? I've been trying for over a month with no success.....
Click to expand...
Click to collapse
every day i'd enter my email addy on the ingress.com website. took me a while as well. sadly, i got no invites to pass on to folks.
DraginMagik said:
i'm rooted/unlocked running TWRP & TheBase .7.3. used the FreeGee app as well.
have you tried reflashing TheBase and not using Sk8's kernel?
if it happens with TheBase and Sk8's kernel...then i'd post the question and error in that thread.
if it happens with TheBase and either kernel...then i'd try posting in TheBase thread.
don't be afraid of getting flamed. we all ask dumb questions from time to time and we are all weak on some topics...just try not to come off sounding rude or belligerent and most folks will do as they can to help.
Click to expand...
Click to collapse
Thanks DM. My kernel crashes have occurred with the stock ROM and kernel, then also after I flashed TheBase but kept the stock kernel. So I thought I'd try Sk8's kernel to see if that would stop the crashes, but no such luck. The frequency didn't really vary after any particular step, and the only constant has been the FreeGee unlocking and TWRP. I guess I can try CWM, but then I won't be able to make backups (I believe that's still an issue with CWM, right?).
Sent from my Nexus 7 using Tapatalk HD
I had it happen when the volume got to high and the ear damage warning popped up, then a few seconds later BAM Demigod screen.
Nastybutler said:
Thanks DM. My kernel crashes have occurred with the stock ROM and kernel, then also after I flashed TheBase but kept the stock kernel. So I thought I'd try Sk8's kernel to see if that would stop the crashes, but no such luck. The frequency didn't really vary after any particular step, and the only constant has been the FreeGee unlocking and TWRP. I guess I can try CWM, but then I won't be able to make backups (I believe that's still an issue with CWM, right?).
Click to expand...
Click to collapse
not sure about CWM. i've been hesitant to use it since my early days with my EVO4G, there were a couple tasks it didn't do quite right. haven't read up on it much since.
i'd try to get someone like Sk8 or another low level developer to see and ponder your issue. if that's not the case, perhaps document how often it happens and contact LG or ATT for a device replacement. it's well beyond my limited knowledge. although, sometimes a well timed threat with a ball peen hammer can help.
I will upload my source compiled kernel after I have a few more cups of coffee. I have been on it since Dec. 6th without a single issue. I also should mention I updated my TWRP in Goo Manager and I have backed up and restored dozens of times on my external SD. My music is there, init.d works so I added a zipalign script. Rock solid...give me a little while. Team Nov is using it in their latest release until they start bringing some flamethrower kernels
Edit..kernel compiled by Shabbypenguin. Check his resumé if you haven't heard of him. He's legit
Sent from my LG-E970 using Xparent ICS Tapatalk 2
Hi folks, new here, been lurking a while, yadda yadda. Hardly the place for intros.
Anyhow, I am having this problem as well, usually multiple times a day. Stock firmware/rooted/unlocked. Phone is the earliest revision (have there been hardware revisions?); it was a pre-order. As stated, it's been happening since unlocking with Freegee; however, even before rooting my phone would randomly reboot and on a couple of occasions simply power off while in my pocket as has been mentioned in other threads.
Has anyone made any headway with this? I get that the reset procedure is simple, but it's hard to take phone calls when your phone's had a panic attack.
Spot-on text dump on the first post; I grabbed a picture of the screen my crashed phone for the record.
xcmartin said:
Hi folks, new here, been lurking a while, yadda yadda. Hardly the place for intros.
Anyhow, I am having this problem as well, usually multiple times a day. Stock firmware/rooted/unlocked. Phone is the earliest revision (have there been hardware revisions?); it was a pre-order. As stated, it's been happening since unlocking with Freegee; however, even before rooting my phone would randomly reboot and on a couple of occasions simply power off while in my pocket as has been mentioned in other threads.
Has anyone made any headway with this? I get that the reset procedure is simple, but it's hard to take phone calls when your phone's had a panic attack.
Spot-on text dump on the first post; I grabbed a picture of the screen my crashed phone for the record.
Click to expand...
Click to collapse
For whatever reason the frequency of my kernel crashes has dropped way down. Not sure what I did to make it so. Hasn't happened to me at all in about a week.
I just got on ingress and just got my first yellow sod...wonder if it's related.
DraginMagik said:
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
L
Click to expand...
Click to collapse
Sent from my Xoom using xda app-developers app
You are getting that screen because of the kernel from freegee. Normally your phone would just reboot.
Over here from the Sprint Optimus G forum. We're seeing all these freezing/kernel crash/HW reset issues on Stock locked unrooted and everything base off of it. We are also seeing this with custom kernels as well.
Thinking this is not an Ingress issue but an LG issue as jokersax and I have found a number of things broken from the kernel level on up.
EDIT: As a point of note. I've tried to duplicate any of these issues on a Hero, Evo Shift, HTC View, Original Galaxy Tab (wifi & Sprint), Atrix, Photon, Photon Q, Nexus One, GNex and Nexus7. Except for the obvious, like the Hero lagging really bad, none of these devices are anywhere near as unstable as the Optimus G.
Related
Is anyone else experiencing these. I've only had the phone a few days but started to notice it once I put infected rom eternity on it not sure if it is a rom issue or a hardware issue
Sent from my PG86100 using XDA App
I'm having random reboots and I haven't even rooted/modded in any way. I got a system update earlier today, but it was doing it before that. It might be one of my apps, but it only happens when the screen is off and I'm trying to turn it back on to use the phone. I've tried factory resets and battery pulls so I figure its an app, or having the social lock screen.
Sent from my PG86100 using Tapatalk
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
mteezey said:
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
It's definitely hardware. It's the proximity sensor, I believe. I picked up a phone call, and when I put the phone up to my face (I didn't touch my face to the phone, just my ear), the screen didn't shut off, and then rebooted. After it started back up, I called the person back, and when I brought the phone up to my face, the screen shut off as it should, and stayed in the call until I hit end, and it's still on. I received a second call and it had the same behavior. Reboot upon bringing it up to my face the first time, fine the second time. When I try to bring the phone out of standby I thought it was the live unlock screen I had (weather), but it seems to bee the light sensor or proximity sensor... boo..
[EDIT] Just did a factory reset. Market is installing my apps. We'll see how this time around goes.
So far so good. all my apps are re-installed. I have yet to check my games for my data, but I took a phone call and the screen turned off quickly when I brought it up to my face.
That's the same way it happened to me during a phone call but I was on hold for twwenty minutes with it on speaker and once they picked up I put it to my face and ....reboot. like you said boo
Well I got rid of eternity and with new rom(Olympus Trinity XE) and kernel mild anthrax I have not had a reboot yet. Its only been 12 hours but it was happening every few hours before.
Sent from my PG86100 using XDA App
heat
I usually have my E3D in it's Otterbox clipped on my belt, and no problems arise. Last week I went out to a bar and it was very warm in the bar, and the phone was in my pocket. It rebooted once out of the blue. I'll keep it on the belt clip.
Rooted, Stock rom.
I'm planning on getting am otterbox very soon.
As for rebooting, it's still doing it, once when a Words with Friends game wouldn't load and another time while trying to load Paradise Island. I'm now thinking it's the video driver.
I rooted my Intercept and changed the driver. I would rather not root this device if I can't unroot it...
Sent from my PG86100 using Tapatalk
Mines not rooted either and mine just rebooted like literally 3 times in a matter of 30 minutes
Sent from my PG86100 using XDA App
There is a rom to unroot. Its a stock rom once you flash turns your securities back on(s-on). Which is good in case you ever have to take it back to sprint.
Sent from my PG86100 using XDA App
I've only had one reboot with my new kernel. It seems now like its only when its on the charger I set a charging profile now to Max CPU speed of 648mhz with interactive governer gonna see if that helps. If not I'm gonna try a temperature profile.
Sent from my PG86100 using XDA App
From what I can do on an unmodified device, I found this in the "Tell HTC" log.
local_clk_disable_reg: clock 72 status stuck at 'on'
This happens a few times in the log. I've been taking screenshots of the log to post, but I haven't had the time to go through the whole log. The next time I get a chance, the phone has already rebooted 3 times. It's definitely not my app because it's no longer on my system.
Also, I don't know if this goes with it, but I sometimes have to do a PRL update to get out of roaming. I'm in my local, high-signal area... I'm eventually just going to call and get a replacement.
[EDIT]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here we go. Here's the error message, then it dumps the memory locations. In a minute I'm going to post a link to an album I have with the log, error to end.
Another oops 17 prempt smp.
Sent from my PG86100 using Tapatalk
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
mteezey said:
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
Click to expand...
Click to collapse
This is all untouched stock from Sprint.
But wait! It gets better! I wasn't using the phone last night, and it kept rebooting every 20 minutes +/-, then it gets stuck in a boot loop (which it's still stuck in). As mentioned before, I have to update the PRL every time I reboot the phone, so could it automatically be routing itself to a bad radio? Not that it matters, I have to factory reset anyway...
I went into recovery to do a factory reset (boo... going to try to adb pull my data, first) and I noticed that during the image check, two of the images are the "wrong" image (PG86DIAG and PG86IMG... something like that). Is this bad? I went from a Samsung Intercept to the Evo 3D so there's some major differences between stock recovery and CM01 heh.
Shooter XC Ship S-On RL
HBOOT version 1.50.0000 (used to be 1.4 and I only did the OTA update and install some apps/games)
eMMC-boot
Sorry for somewhat hijacking this thread, by the way. I just think it's strange to have all these problems on a stock device (though stock isn't great... ever). When I initially came on to search about it I noticed your post and jumped right in lol.
I'm glad I didn't root this thing right off the bat because of the watermark, and because of this stupid page fault.
I think wrong image thing is just your phone searchiibg for update IMG when you open the bootloader I would have to see exactly but its normal for it to check for pcwhateverimg. Whenever the bootkaoder opens. Since you have s on and don't have to worry about losing root access it night not be a had idea to update to the latest radios . Then if you still have the problem try to tIe it back. I haven't been having the problem anymore with a new kernel and new usb cord. Since it seemed to be when I plugged in. But as ling as I don't overclock above 1.6ghz I've has no problems Anymore
Shot from my Shoot3Rvo
I'm going with the acct holder (my bro-in-law) tomorrow to get a replacement. Seems we're not the only ones. There's another thread on here about this very topic...
As for rooting it, I need to read more, but doesn't it leave a mark saying it's been modded if it's 1.5 or greater, thus not returnable? I remember the Intercept doesn't have that so it was no problem switching back and forth, but it was a b***h to get a solid root...
Sent from my PG86100 using Tapatalk
I didn't read everything on hboot 1.5 but I know there is some different steps. I know there is a ROM to flash to get back to s on which is all you need for warranty to not be void I'm sure it says whether or not it works with that hboot.
Shot from my Shoot3Rvo
Awesome to hear there's a work around for the S-On. Looks like I got some reading to do when I get home from work!
Sent from my PG86100 using Tapatalk
Oh, this is so good it has to be fattening!
So I did a factory reboot and it lasted like 8 hours, whoopee...
I bring it in to Sprint and they have the tech look at it, estimating 45 minutes to an hour. Good, I had gift shopping to do. I come back and the girl gives me the (same) phone and asks me to log in. I do, and it updated my contacts, etc. She then said "He reset and updated the software so it should be okay now."
"... so why does it still say I'm roaming?"
"It does? Let me see."
She brings it to the tech, who performs the "magical" PRL update, which I TOLD them I HAD to do after every reset I did. Fine. It's working now, and I have no roaming charges, so not worried about the bill. I go home and enjoy the rest of my time before work. I get into my work parking lot, and the phone resets. Mother ****ers. I'm back in roaming, too!
Looks like I have somewhere to be first thing in the morning and to directly talk to the tech and ask, "Did you really think that a severe page fault that's embedded into the ROM would be cleared by a factory reset? The device needs to be flashed or replaced."
I told the girl straight up that I can fix it in 20 minutes, and that I rooted and modded my Intercept on Virgin Mobile (which they sign contracts at that location for heh) and it cleared up all my problems. Then, that I can't do that with this phone because I can't return it if it screws up again.
Ugh! Why do they release crap like this?! There are thousands of people that have this phone with this rebooting problem... Shouldn't there be a recall? Even on the Sprint customer forums there's posts about it, so Sprint KNOWS of this issue, especially if a manager replaced 8 devices in one day for the same problem.
So anyway, I'm on my way home from work, and I click the phone on to pull Pandora up, and it resets, but it doesn't go back to the home screen. It's stuck in a boot loop again! YES! I removed and replaced the battery and it did it again. I took the battery out and just set it on my desk, waiting for the tech to turn it on. Hooray that it got stuck, so I can rub this in his face. I should be working there, not him. (Sorry for my ranting, I'm just tired of Android problems because of carriers changing the software and locking it up. Google WANTS people to make the software their own!)
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
rigmort said:
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
Click to expand...
Click to collapse
I've seen that on another forum. Thank you for the SD card insight. Just as a precaution, I'm just going to pull all the crap off my card and format it with the SD Formatter. I don't remember what the "brand" is but I know it's the right one. Should I back it up and format through the phone, or use the adapter and format the computer way? I'm thinking phone...
I talked directly to the tech today and told her what the log said and that it needs to be reflashed. After the estimated time she gave it back saying that she ran it through every test their system can run and the software has no errors (which my logs say as well), but she reflashed anyway to make sure (I'm still not sure how she logged into my gmail if she reset it...) I have to call corporate for the roaming issue because I'm connecting to the wrong tower, which she doesn't have permission/clearance to change. If, after fixing the roaming, it still does reboot, it will be replaced. I'm still under warranty, so I'm curious as to why they're trying to keep me on, what I believe to be, a defective device... Because they can't detect anything wrong with it...
I have yet to install any apps (minus Tapatalk) and the phone has yet to reboot, and its been in my pocket all day so I would have felt it reboot. Shame because it's one of my paid apps (one out of 6), Paradise Island, Angry Birds (which wasn't opened at all during this, but it was installed), or Words with Friends. I also had ScummVM but the reboots started way before I installed it and the engines. Those are the only apps I installed the last couple times because I'm sick of reinatalling all my apps. Bigger shame because I can't install apps until I'm sure of what the problem is. Why have an amazing phone I can't use a paid app on? I'm just frustrated at this point... I have a lot of back traces to read through and no list of what is what because the phone has been cleared since then... Does the memory map stay the same no matter if it gets reset? I haven't done any Linux kernel programming so I'm learning as I Google which is what it's meant for.
I really want to Update the PRL to see if it will help with my battery life, which it should, but I don't want to change anything, in case it messes up again. It will be proof its defective. Ugh... What to do...
Merry Christmas, to those who celebrate the holiday! Happy holidays to everyone!
Sent from my PG86100 using Tapatalk
...I have a lot of problems typing with a touch screen so I edit a lot to correct things... That and my screen feels my fingertip before it touches the screen...
[EDIT] My SD card has been unmounted for who knows how long! I just remounted it as is to see if it starts rebooting.
Samsung Galaxy Tab 10.1 GT-P7510 (wifi only)
I had recently switched from Task 14 to stock ICS which I rooted and I was running A1 kernel. Everything was going great.
I decided to switch to Pershoot's latest. I was following the instructions and updated to the latest recovery as he stated should be done. That went fine.
Then I went to flash the kernel. While flashing the kernel the tab lost power. I'm not sure how, but I was charging/plugged into the PC when it happened.
I tried quick pressing the power button thinking the screen just went to sleep but nothing. I waited quite a while figuring it was just rebooting but after an hour or so I decided to long press power on. Still nothing.
I only get a black screen, no back light, no logo, nothing. Every button press combination I've tried gives no response. Using the wall charger makes no sound when plugging in.
The ONLY response from the tab is being able to get it to show up as an APX device showing up in the device manager.
While searching for a remedy I came across an old rooting thread here http://forum.xda-developers.com/showthread.php?t=1130574] that used Nvflash and thought I'd give it a try since I thought maybe that would get me back where I could odin back to stock, but I only get error messages or a flashing prompt no matter what I try. I know little about Nvflash but have repeated the instructions several times with always the same results.
Such as:
"nvflash --sync or nvflash --bl bootloader.bin --go (results in)
Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
and I have to set the tab back into APX mode because it disconnects.
Since this is the only way I can get any connection to my tab, does anyone have the knowledge to get me from here to stock or even download mode so I can use odin??
Any other suggestions?
Thanks in advance for your time and efforts.
Can you get into recovery mode?
1 Hold 'vol down' and 'power' buttons on tablet Don't be shy hold them for 30+ seconds
2 Release 'power' when samsung image is shown
3 Release 'vol down' when the two icons are shown
4 Use the 'vol down' to navigate between the icons
5 Highlight the left icon (box)
6 Press the 'vol up' to select it and boot into recovery mode
You may just not be doing step 1 for long enough? Worth a try!!
Good Luck
Pep
Same problem here, was restoring a nandroid backup and power went out, now only a black screen, no matter how long I hold down the power button.
Pep71 said:
Can you get into recovery mode?
1 Hold 'vol down' and 'power' buttons on tablet Don't be shy hold them for 30+ seconds
2 Release 'power' when samsung image is shown
3 Release 'vol down' when the two icons are shown
4 Use the 'vol down' to navigate between the icons
5 Highlight the left icon (box)
6 Press the 'vol up' to select it and boot into recovery mode
You may just not be doing step 1 for long enough? Worth a try!!
Good Luck
Pep
Click to expand...
Click to collapse
Thanks, but pretty experienced flashing and can't get into any mode but APX. I've held every combination I know of all for a few minutes. I even searched and found one I didn't know of but everything is still black screen only.
I am about to mess with it again to check battery drain from guide by Misledz and will try your suggestion just in case I missed holding the combo for recovery/download mode long enough. I will be amazed if it was that simple, and smack myself in the head.
I'll report back shortly.
UPDATE: Unfortunately no such luck for an easy fix. Held the button held the Power and Vol- down together several times for at least 2 minutes each time. Still get NOTHING and only APX mode which is how Misledz suggests checking to see if battery is completely drained. Hoped it would be drained when I got home today but computer still recognizes it in APX. When it doesn't pop up it in devices it will be drained completely and hopefully I can get his method to work from there.
Any other suggestions from ANYONE on something I may have missed or not be trying correctly would be greatly appreciated.
Someone posted in Pershoot's kernel thread almost exactly what happened to me...
Personally having so much RESPECT for Pershoot's knowledge I consider this this to be my only options also.
So my search ends unless someone has some magic up their sleeve. :silly:
This is the link to the battery drain guide by Misledz mentioned. Pershoot just says tape the power button but this link is an actual guide to the method of draining the battery and getting your tab back.
http://forum.xda-developers.com/showthread.php?t=1478361
Here is Pershoot's response to the other user with the same issue.
you've had some corruption while installing/odin, etc., what have you, it was forced down in that state (you hard powered off) and the device locked itself.
this just happened to a friend of mine recently (and to many others in the past).
if you cannot get to download mode, then you have only 2 options.
1st option:
tape the power button until it runs completly out of juice, then plug in power, and wait for some charge, then try to power up.
if that does not work (it did not for my friend),
send it back to samsung and they will reflash/replace what they need to, to get you back up and running.
Click to expand...
Click to collapse
That's an incredibly detailed guide. Thanks for linking, I just subscribed!
Let us know how this goes man. Seriously interested...I might add stories like this are why I will only flash stuff with a battery charged to more than 50 on a laptop that is not connected to the wall, and am super OCD on the condition of my cables lol! I hope this never happens of course but can't predict the future and am grateful so many great peeps are here to help each other out.
djmatt604 said:
That's an incredibly detailed guide. Thanks for linking, I just subscribed!
Let us know how this goes man. Seriously interested...I might add stories like this are why I will only flash stuff with a battery charged to more than 50 on a laptop that is not connected to the wall, and am super OCD on the condition of my cables lol! I hope this never happens of course but can't predict the future and am grateful so many great peeps are here to help each other out.
Click to expand...
Click to collapse
Yeah. Misledz has helped MANY people "un-brick" their tabs even when a drain was not needed.
It was a totally FREAK occurrence of this happening to me. Still not sure what exactly went wrong. I've flashed and flashed since I've owned the tab. I've had many soft-bricks which I quickly got out of, but this one was throwing me for a loop.
I was going to PM Pershoot to look at this question and BOOM there was my answer in his thread!
I'll keep this post updated. I just wish the drain didn't take so long. Hoping it's done by the beginning of next week or I'm sending it in since I'm still under warranty and can't seem to have a good day without my tab in hand. But if I send it in I can't confirm or deny if the drain method worked for me.
For a moment I lol'd when Pershoot had basically mentioned the same steps I had written down, Makes me wonder how many have read that without my knowledge
On another note, there's good news and bad news, the bad news, you get 0x4 and that means you have a locked bootloader which is why APX mode fails for you, It's written on the first line of the APX thread you linked " If you get the 0x4 error then you have a locked tablet."
The good news is your tablet is safe, I know most would find this difficult to agree with but Sammy products are potentially hard to brick. In most cases the power outage happened probably with a disconnection or kernel wasn't supported, it's like a fuse that trips to save the device from being further damaged I suppose is the best way to put it,
Anyways, yeah you may need to tape that bad boy down. If you haven't charged it recently, Then that's good it makes it easier to be drained. If you don't have the USB mod that charges the tab when connected to the PC then you're good. Otherwise you need to have it taped down and hope it drains that way.
There's still a way to fix it Thing is your locked loader just makes APX commands useless now. If it wasn't then you can push busybox or something and get adb up and running.
PS: I hope your tab was atleast 50% or less to have it drained faster. The drain process is really slow I admit. Not exactly sure how many mAh the battery of the tab is but having it connected all day would be a good start to get it down to atleast 10% battery
Misledz said:
For a moment I lol'd when Pershoot had basically mentioned the same steps I had written down, Makes me wonder how many have read that without my knowledge
On another note, there's good news and bad news, the bad news, you get 0x4 and that means you have a locked bootloader which is why APX mode fails for you, It's written on the first line of the APX thread you linked " If you get the 0x4 error then you have a locked tablet."
The good news is your tablet is safe, I know most would find this difficult to agree with but Sammy products are potentially hard to brick. In most cases the power outage happened probably with a disconnection or kernel wasn't supported, it's like a fuse that trips to save the device from being further damaged I suppose is the best way to put it,
Anyways, yeah you may need to tape that bad boy down. If you haven't charged it recently, Then that's good it makes it easier to be drained. If you don't have the USB mod that charges the tab when connected to the PC then you're good. Otherwise you need to have it taped down and hope it drains that way.
There's still a way to fix it Thing is your locked loader just makes APX commands useless now. If it wasn't then you can push busybox or something and get adb up and running.
PS: I hope your tab was atleast 50% or less to have it drained faster. The drain process is really slow I admit. Not exactly sure how many mAh the battery of the tab is but having it connected all day would be a good start to get it down to atleast 10% battery
Click to expand...
Click to collapse
Thanks for the reassurance of hope. I hate the thought of sending it in for repair. It was around 20-30% charged. So I hoping for only a few days of discharge.
I am confused on one specific part. Is just keeping the power button taped or in my case down with hair ties enough?
I know plug it in the PC to check to see if it pops up the APX in devices and so far it has always popped up, but of course back off and back up, etc.
I think my ultimate question is "Do I need to keep it plugged in to the computer for it to loop or will keeping it unplugged and the power button down drain it?".
Will it drain faster plugged in the PC or unplugged?
Again thanks for the help bro.
Did you know at one time you were FRONT PAGE NEWS on XDA? Very Cool!
Here's the link for proof.
http://www.xda-developers.com/android/tutorial-released-to-fix-galaxy-tab-10-1-brick-woes/
Just to add....our tab has a 7000mAh battery in it which equals some serious wait time if you're fully charged lol
djmatt604 said:
Just to add....our tab has a 7000mAh battery in it which equals some serious wait time if you're fully charged lol
Click to expand...
Click to collapse
If only we could use that for a smartphone, that's some serious uptime.
---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------
Benzoman said:
Thanks for the reassurance of hope. I hate the thought of sending it in for repair. It was around 20-30% charged. So I hoping for only a few days of discharge.
I am confused on one specific part. Is just keeping the power button taped or in my case down with hair ties enough?
I know plug it in the PC to check to see if it pops up the APX in devices and so far it has always popped up, but of course back off and back up, etc.
I think my ultimate question is "Do I need to keep it plugged in to the computer for it to loop or will keeping it unplugged and the power button down drain it?".
Will it drain faster plugged in the PC or unplugged?
Again thanks for the help bro.
Did you know at one time you were FRONT PAGE NEWS on XDA? Very Cool!
Here's the link for proof.
http://www.xda-developers.com/android/tutorial-released-to-fix-galaxy-tab-10-1-brick-woes/
Click to expand...
Click to collapse
HOLY SMOKES. I never actually realized that I had made it to the front page D: LOL, Well this comes a surprise. No wonder the thread has been vamped up every now and then. Made me wonder about that.
And well, You need to have it taped down, unplugged, It's a bit slow but it takes quite the power to boot it up and when it fails, it just boots up again which is crazy but would normally go on for a day, and yeah anything that keeps the power button completely pressed. Normally its the tape that seems to do a better job, the ties would just loose their elasticity over time I suppose?
And it doesn't matter plugged or not, as long as you don't have a USB module that charges it.
Still, can't believe I made it to the front page LOL.
Hey Benzoman find yourself a old USB 1.0 device and the Samsung USB adapter like I have!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Desire HD using xda premium
I am sorry to tell this but i think there is no other solution but sending it back to Samsung and probably they will replace the mainboard and lucky you still under warranty. I have done some researches about this problem since I have the 8.9 tab with the same problem and results are that there is no use of apx mode or nvflash for the bootlocked devices (rcm version 0x4) unless you have the SBK (secure boot key) which is yet unknown for Samsung devices (note that other devices like Acer ICONIA TAB A100 use a calculator to generate the sbk from CPUID number I also tried this method but didn’t work .and the asus tabs use different methods too) ,even the jtag method is not supported for 10.1 and 8.9 tabs (only supports 7.7” and 7” tabs) which seems to be the last hope for other devices in such cases of hard brick . And I think even Samsung can’t fix it and they are only going to replace the mainboard. Finally I tried the Misledz method but with unplugging the battery without draining it (I remember Misledz mentioned that taking the battery out is the same as draining it to zero %) but nothing happened and the device still dead. So my question before I send the device back to Samsung (I am not covered by warranty and the cost will be huge) is taking the battery out really as same as draining it to zero???
DSHV said:
I am sorry to tell this but i think there is no other solution but sending it back to Samsung and probably they will replace the mainboard and lucky you still under warranty. I have done some researches about this problem since I have the 8.9 tab with the same problem and results are that there is no use of apx mode or nvflash for the bootlocked devices (rcm version 0x4) unless you have the SBK (secure boot key) which is yet unknown for Samsung devices (note that other devices like Acer ICONIA TAB A100 use a calculator to generate the sbk from CPUID number I also tried this method but didn’t work .and the asus tabs use different methods too) ,even the jtag method is not supported for 10.1 and 8.9 tabs (only supports 7.7” and 7” tabs) which seems to be the last hope for other devices in such cases of hard brick . And I think even Samsung can’t fix it and they are only going to replace the mainboard. Finally I tried the Misledz method but with unplugging the battery without draining it (I remember Misledz mentioned that taking the battery out is the same as draining it to zero %) but nothing happened and the device still dead. So my question before I send the device back to Samsung (I am not covered by warranty and the cost will be huge) is taking the battery out really as same as draining it to zero???
Click to expand...
Click to collapse
I did just that this morning and it did the same thing as draining the battery.....tab is still dead!
bugs9477 said:
Hey Benzoman find yourself a old USB 1.0 device and the Samsung USB adapter like I have!
View attachment 1298189
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I wish I had the adapter so I could drain it faster. That was a great idea! I would love to prove Misledz method works or not for me.
I made the mistake of leaving mine plugged in the PC too long and my last kernel I flashed has USB charge enabled so any discharge I was getting was being over powered and the tab was actually charging instead of discharging. Now most likely being fully charged or nearly full at least. I read in another thread using this method that one person got about 10% per day drain but I'm old and may not live long enough for it to drain completely now.
I know this has helped many people, as I've seen and participated in many of the threads Misledz has helped people using his method. But it also seems it will not fix every tab. I know Misledz has personally fixed several for himself and many others have successfully used his method. Many have failed but I think the ones that have failed may have hardware issues and just appear to have the same issues as have been fixed using Misledz battery drain method. I wish I had some extra tabs to "break" in special ways to prove and disprove what exactly what Misledz method fixes. I may do so this winter since I'll have extra time and money to get 2 or 3. There are several other things I want to test on these also so it would be a fun (or possibly maddening) winter.
I don't have the patience to wait for the battery to drain, and being I'm still under warranty I will be sending this in tomorrow. I've already chatted with tech support, unfortunately already knowing and doing everything they wanted me to try. I went ahead and did everything they said except when they wanted me to charge it for 6 hours...lol I told them it had just came off a 12 hour charge right before this happened so he skipped to the next thing the script on his computer screen told him to have me try. After almost an hour, mostly waiting for him to "get required information" from somewhere on his computer or manual, wherever, I ended up with a service request page and a label to print to send it in for repair. This was really my only reason for chatting with them in the first place. I pretty much knew they were not going to really help, because their "script" only allows things be said that I was sure I already knew and/or already tried.
So, sometime tomorrow my Tab starts it's journey to Plano Texas to be repaired. Hopefully in less than 2-3 weeks I'll have it back like new. With my lack of patience it is going to seem like forever.
I was told it takes about 30-45 working days I wish there was a way to generate a key for the 0x4 locked tabs. Would be amazing to get that working. The bootloader tends to get killed really easily. Ironic since Samsung should have seen this coming that flashing and upgrading is an essential thing so to look into the matters addressed and hope that there is a solution aside from the draining method.
Sent from my Galaxy Nexus using Tapatalk 2
Got my tab back today. Took less than two weeks. Very cool.
When I had it last before the brick, I was running OTA ICS rooted using sockmonkeys sticky guide and the same files I rooted with before ICS. It rooted my tab perfectly fine with that method and files last time even though I was on stock ICS.
When I got it back today it was already ICS. About the first thing I did was try to root so I could restore some tibu stuff. Sadly immediately ran into to rolling recovery issue. I know enough that I was able to restore quickly without searching and reading forever.
Now for reading the many threads on the rolling issue...ugh.
Anyone want to save me some time and link to a recovery for me to Odin that wont roll?
Please? LOL
EDIT: After a LONG NIGHT of searching, reading, flashing. I'm up and running smooth.
Fixed rolling recovery with this thread http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
That fixed the rolling recovery, but then after flashing Toldo's ROM from here http://forum.xda-developers.com/showthread.php?t=1831040 I got a rolling screen on wake lock every time.
So I fixed it with this from Pershoot's boot loader 4.0.4_bootloader.tar.md5 from here http://droidbasement.com/galaxy/roms/cm9/p4wifi/ But that only fixed the rolling on wake and the rolling in recovery was back.
Then I came across this post http://forum.xda-developers.com/showpost.php?p=31153208&postcount=5 Finally no more rolling recovery or on wake lock.
Maybe the above grouped links will get someone out of rolling recovery and if needed after out of rolling on wake.
It took me almost all night to get the correct order and files from searching and reading.
For now no problems, but we'll see as I do some more playing around.
Benzoman said:
Got my tab back today. Took less than two weeks. Very cool.
When I had it last before the brick, I was running OTA ICS rooted using sockmonkeys sticky guide and the same files I rooted with before ICS. It rooted my tab perfectly fine with that method and files last time even though I was on stock ICS.
When I got it back today it was already ICS. About the first thing I did was try to root so I could restore some tibu stuff. Sadly immediately ran into to rolling recovery issue. I know enough that I was able to restore quickly without searching and reading forever.
Now for reading the many threads on the rolling issue...ugh.
Anyone want to save me some time and link to a recovery for me to Odin that wont roll?
Please? LOL
EDIT: After a LONG NIGHT of searching, reading, flashing. I'm up and running smooth.
Fixed rolling recovery with this thread http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
That fixed the rolling recovery, but then after flashing Toldo's ROM from here http://forum.xda-developers.com/showthread.php?t=1831040 I got a rolling screen on wake lock every time.
So I fixed it with this from Pershoot's boot loader 4.0.4_bootloader.tar.md5 from here http://droidbasement.com/galaxy/roms/cm9/p4wifi/ But that only fixed the rolling on wake and the rolling in recovery was back.
Then I came across this post http://forum.xda-developers.com/showpost.php?p=31153208&postcount=5 Finally no more rolling recovery or on wake lock.
Maybe the above grouped links will get someone out of rolling recovery and if needed after out of rolling on wake.
It took me almost all night to get the correct order and files from searching and reading.
For now no problems, but we'll see as I do some more playing around.
Click to expand...
Click to collapse
By Jove! You might have just found a way to help 25-30% of the people who have either scrolling recovery, or scrolling wake-up.
I wish to thank you for the effort and results of the issue. I will follow this method and see if it works just as well for me too.
Just_Another_N00b said:
By Jove! You might have just found a way to help 25-30% of the people who have either scrolling recovery, or scrolling wake-up.
I wish to thank you for the effort and results of the issue. I will follow this method and see if it works just as well for me too.
Click to expand...
Click to collapse
Hope it helps. Please post your results.
I was gonna take this experience and make a thread "How I fixed rolling recovery and rolling on wake lock." Then I realized I really don't have the time or patience to help everyone that might reply in the thread needing help. There are too many variables to make a guide that works for everyone. It took me a lot more threads and posts on how to fix it than the 3 I posted, but only the three I posted applied to my situation and had the files I needed to get both problems fixed. So the information and files are out there already but just takes forever to find relevant posts and working links, and such.
Benzoman said:
Hope it helps. Please post your results.
I was gonna take this experience and make a thread "How I fixed rolling recovery and rolling on wake lock." Then I realized I really don't have the time or patience to help everyone that might reply in the thread needing help. There are too many variables to make a guide that works for everyone. It took me a lot more threads and posts on how to fix it than the 3 I posted, but only the three I posted applied to my situation and had the files I needed to get both problems fixed. So the information and files are out there already but just takes forever to find relevant posts and working links, and such.
Click to expand...
Click to collapse
One thing is there are different versions for recovery, i remember this being mentioned by pershoot and you would need to flash the v6 and perhaps see if it happens again buddy
Sent from my Galaxy Nexus using Tapatalk 2
I was in class today and my phone vibrated a few times notifying me of text messages. I checked the phone when I got outside and was greeted by this screen
http://i.imgur.com/WFQ33Rf.jpg
Not my phone, but the same problem!
I've been running the same CM 10 rom for months now. I can't remember if it was a stable or RC but it was good enough that I didn't feel the need to mess with my phone for perhaps the last 5 or 6 months. It's been a while.
Details:
The phone still vibrates and receives messages. I know this because I'm confirming with google voice online that messages are coming in when its vibrating. I can turn the screen on and off, but I'm just greeted by this screen. I can force the phone to reboot by holding the power button, but even the starting animations won't show. It turns on immediately to this. During the start-up animation, it usually has a point where the screen brightens and then dims and even this occurs. The buttons and everything are all doing what they need to do. I can unlock the screen and everything as I can feel the feedback. The volume rocker works and reacts properly. Everything is working except the screen.
Any ideas?
I'd like to apologize if this is a common problem and the solution is posted somewhere as I have not frequented these boards recently and am currently at work so I can't spend much time searching.
Yeah, see my post about the confetti. It went confetti very soon after it went contrast. I run stock CPU speed with stock voltage.
Ironic that yours happens just as mine did. I'm using the phone now. I have the screen turned on to never go to sleep now so that I don't have to try and wake it up. Then I may get that screen and to prevent that? Turn it off, turn it on, turn off, turned on and eventually I'll get the lock screen.
I run meanbean rom with the 1.19 hboot, s-on. I'm going to return it to stock then take it back to sprint. Provided I can keep the phone functional long enough to do this.
This will be my second phone to do this. First 1 did it last September.
Sent from my EVO using xda app-developers app
It's a shame. I've had this since launch and haven't had a single problem with it. Unfortunately, no matter how many times I turn the screen on and off, I can't get it to the lock screen.
Edit: I have a feeling this isn't going to be an easy fix. I'm gonna switch to my brothers old Evo 3D as soon as I get home
http://forum.xda-developers.com/showthread.php?p=38160970 is my original post (first)
I would like to add the screen freezes when the battery gets to a full charge. Unplug it and it recovers almost instantly. Interesting I'd say.
Sent from my EVO using 2 kidneys and a rock.
Yeah, I went through your post. I can see that no one really had any idea for you either which was kinda disheartening. I'll have to play around with it when I get home tonight, but I'll be forced to switch to an older phone as I won't have enough time to fix this on my own right now
Sprint exchanged the first one because the grfx chip went bad according to them. My concern is that it was not that long ago and now I have the same issue. How old is your phone?
Sent from my EVO using xda app-developers app
My concern is that they won't exchange it unless I can get it back to stock, but I'm assuming there's no way for them to know considering they can't access anything on the screen?
I've had the phone since June. Never had a problem with it
I think the screen might show via the hdmi feature but I'm not going to force the issue. You should be able to answer incoming call via bluetooth adaptor. I can also listen to Pandora via bluetooth through my head unit in my truck. Also make phone calls through my head unit to but I'm not going go to the car in the phone calls unless I'm in it.
If your proficient with voice commands via bluetooth or Google Voice you maybe able to get some functionality of the phone for a little bit more time. I would like to see if other folks have this issue also.
Sent from my EVO using xda app-developers app
http://code.google.com/p/androidscreencast/
I found a link to this program which allows you to access your phones screen that I think may be helpful! I'm going to use this to get what I need off the phone, get it back to stock, and return it to the store tomorrow. I'll update this post later tonight when I get home
The only time this happened to me is when my voltages were too low. I would boot into recovery and reflash your ROM or the voltage increase script in thick lizards dev host folder.
If you can get to recovery which shouldn't be a problemyou can fix this easily.
Sent from my EVO 4G LTE using xda premium
So I'm back to stock using racun's soff procedure. I still has pixy dust issues. Will look into the thicklizzard angle tomorrow.
Zori said:
I was in class today and my phone vibrated a few times notifying me of text messages. I checked the phone when I got outside and was greeted by this screen
http://i.imgur.com/WFQ33Rf.jpg
Not my phone, but the same problem!
I've been running the same CM 10 rom for months now. I can't remember if it was a stable or RC but it was good enough that I didn't feel the need to mess with my phone for perhaps the last 5 or 6 months. It's been a while.
Details:
The phone still vibrates and receives messages. I know this because I'm confirming with google voice online that messages are coming in when its vibrating. I can turn the screen on and off, but I'm just greeted by this screen. I can force the phone to reboot by holding the power button, but even the starting animations won't show. It turns on immediately to this. During the start-up animation, it usually has a point where the screen brightens and then dims and even this occurs. The buttons and everything are all doing what they need to do. I can unlock the screen and everything as I can feel the feedback. The volume rocker works and reacts properly. Everything is working except the screen.
Any ideas?
I'd like to apologize if this is a common problem and the solution is posted somewhere as I have not frequented these boards recently and am currently at work so I can't spend much time searching.
Click to expand...
Click to collapse
Have you tried getting into the bootloader?
Sent from my EVO using xda premium
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
aFoodStampBaby said:
Have you tried getting into the bootloader?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Zori, is your evo S Off? Then you can flash individual kernels I think. If it is, then take a CLOSE look at unlimited.io/jewel.htm because most of that procedure is remote terminal. If you do it via ubantu, I'm thinking you can push the proper package onto the phone and update it that way.
The hardest part will be getting to recovery from the hboot screen and BAM!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader screen:
At the very least it can get you to the point of getting to stock I think. My phone seams to have recovered a bit at stock. I briefly see the confetti when I wake it. I can imagine that it would be an under volt condition while powering on. You can do it mate the force is strong.
---------- Post added at 06:23 AM ---------- Previous post was at 06:08 AM ----------
vipermod looks relevant to our issue. I will need to do some reading while the bosses are not looking.
Zori said:
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Click to expand...
Click to collapse
The online esn swap always prompts you to change plans for some reason now..have to call or chat.
Sent from my EVO using Tapatalk 2
Well my phone went all confetti, all the time. Got a new one today.
Zori said:
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Click to expand...
Click to collapse
How did you make out with this issue? The same thing happened to me today. Running 10.1. Cant even see revovery.
Answer to confetti screen issue
My phone did this exact thing on Saturday. I took it in to the Sprint store, and the tech there (the only one I've ever run in to who really knows his stuff, Phil in Westminster), explained that there is a cable between the battery and screen that is "kinked" and loses contact. If you squeeze the phone really hard just above the back button the screen will come back on for a bit. They did agree to send me a new phone (I am rooted, and running a custom ROM, they did not care). I've been able to get enough functionality out of it to get by for about two days, but as of last night the screen only stays on the "confetti", and won't come back at all.
Anyway, hope that helps a bit!
crapid said:
My phone did this exact thing on Saturday. I took it in to the Sprint store, and the tech there (the only one I've ever run in to who really knows his stuff, Phil in Westminster), explained that there is a cable between the battery and screen that is "kinked" and loses contact. If you squeeze the phone really hard just above the back button the screen will come back on for a bit. They did agree to send me a new phone (I am rooted, and running a custom ROM, they did not care). I've been able to get enough functionality out of it to get by for about two days, but as of last night the screen only stays on the "confetti", and won't come back at all.
Anyway, hope that helps a bit!
Click to expand...
Click to collapse
Yup.. mine started doing the same thing couple of days back..
I instinctively started pressing the screen and it came back on.. must be the same prob like ur sprint guy said..
I'm thinking of going to sprint store but I don't have their insurance or total equipment protection plan.. so, any clue on if they will replace? Do u guys have the TEP?
Edit: Let me add that I have noticed that the screen fuzziness happens whenever i put the phone in my pocket... have started carrying it around in my hand now!!
Sent from my EVO using xda premium
[email protected] said:
Yup.. mine started doing the same thing couple of days back..
I instinctively started pressing the screen and it came back on.. must be the same prob like ur sprint guy said..
I'm thinking of going to sprint store but I don't have their insurance or total equipment protection plan.. so, any clue on if they will replace? Do u guys have the TEP?
Edit: Let me add that I have noticed that the screen fuzziness happens whenever i put the phone in my pocket... have started carrying it around in my hand now!!
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I didn't think I had insurance, and they were going to charge me $50 for a replacement. After they looked at my account it turned out I did have insurance on this line, so no charge.
Unfortunately, I got the replacement last night, and sound doesn't work on this one! Getting yet another replacement on Friday.
[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.