Hey guys i have the samsung galaxy tablet 10.1 model gt-p7510ma and the screen wont turn on. One day i accidentally hit the power and the volume buttons and now this device's screen wont turn on! I am at a complete loss as to what could be wrong. i was told that i may have to flash it back to factory to get it to work but i cannot find any stock rom download links. i have never dropped this thing so i dont know why the screen would just go out.
Does anyone have any suggestions tips or things that i may try to get this thing back operational? Right now it is just a 500$ brick. Has anyone ever heard of this happening?
EDIT: when you hook tab up to computer it shows up as APX in device manager under unknown devices. I dont know if this helps but that a little more info.
Steve
have you tried charging it?
Apart from that I believe this is non-dev related, should go to Q&A section.
It might be that your device has hung. Press Power button and keep it pressed for 10seconds or something like that. And then try to turn it on again.
Sometimes it hangs like that. Especially if you are on some unstable custom rom.
/Edzz
it is actually running the stock rom I never rooted it or anything like that. To the guy above, of course I tried charging it that didn't work. It doesn't even show that it is charging on the scree. I have pressed and held the power button trying to get it into bootloader mode, but that did nothing. Wonder why the computer is picking it up as APX. Wonder what that is? Thank for the suggestions so far!
If you are on stock and not even rooted, then just take it back to shop or service for warranty. You will get if fixed immediately or working back in a week. Better play safe.
In your case I would do so.
/Edzz
black screen and apx on the computer usually means you're in the mode needed for nvflash.
i forget how to get out of that mode, but google nvflash and apx you should be able to get an answer.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Hold the power button while holding one finger on the screen works everytime my locks up
dcj64 said:
Hold the power button while holding one finger on the screen works everytime my locks up
Click to expand...
Click to collapse
Ha!!!! worked thanx. Was sitting here trying to figure this out and Viola ur method worked right away.
I know this may be a day late and a dollar shoprt but i just wanted to let everyone know that i was able to fix the problem using the let the battery drain out and than power it on trick. I dont know how this guy put this device into APX mode but that is the only way i have found to get it out! Thanks for everyones help!
Hey guys,
I've been having this same problem the last 24 hrs or so now. I'm running custom rom Cynagoen mod ICS 4.03. This is apparently one of the more stable roms out there. Prior to this I ran an alpha stage jelly bean rom which ran just fine until last night. After leaving the screen off for an hour or so, the screen won't turn on after pressing the power button. I reboot every time and that seems to work. Is there something I need to do here? Should I look for another rom, maybe a 3.x? Thanks guys
AlphaJ1 said:
Hey guys,
I've been having this same problem the last 24 hrs or so now. I'm running custom rom Cynagoen mod ICS 4.03. This is apparently one of the more stable roms out there. Prior to this I ran an alpha stage jelly bean rom which ran just fine until last night. After leaving the screen off for an hour or so, the screen won't turn on after pressing the power button. I reboot every time and that seems to work. Is there something I need to do here? Should I look for another rom, maybe a 3.x? Thanks guys
Click to expand...
Click to collapse
Maybe try upgrading your CM9 install. 4.0.4 is the latest flavor of ICS.
AlphaJ1 said:
Hey guys,
I've been having this same problem the last 24 hrs or so now. I'm running custom rom Cynagoen mod ICS 4.03. This is apparently one of the more stable roms out there. Prior to this I ran an alpha stage jelly bean rom which ran just fine until last night. After leaving the screen off for an hour or so, the screen won't turn on after pressing the power button. I reboot every time and that seems to work. Is there something I need to do here? Should I look for another rom, maybe a 3.x? Thanks guys
Click to expand...
Click to collapse
You could try reading the entire thread. Hold the power button down while touching the screen. That fixes the SOD (Sleep of death).
Related
Okay so I was running CM9 3/22/2012 just fine. I noticed a nightly went up listed as 3/23/2012. So I downloaded and clicked on the downloaded file, for some reason Rom Manager took over and asked if I wanted to go into CWM. So I agreed and it took me to the AT&T screen with the exclamation mark. I then rebooted and got stuck on the same At&T screen. So I decided to use Odin to go to stock and start from scratch. For some reason Odin 1.81 was supposed to go back to stock with Root. For some reason it got stuck I turned off my phone and now it is unresponsive to most of the tricks listed on this forum.
So will a jig get me out of this jam, a quick search pulled up nothing reliable or I would have to wait 3 weeks to receive, I need it this week like tomorrow if possible.
Searched the forums before going to work real quick couldn't get anything concrete So I'm posting this and I will search some more when I get to work.
Thanks for any help.
logicrulez said:
Okay so I was running CM9 3/22/2012 just fine. I noticed a nightly went up listed as 3/23/2012. So I downloaded and clicked on the downloaded file, for some reason Rom Manager took over and asked if I wanted to go into CWM. So I agreed and it took me to the AT&T screen with the exclamation mark. I then rebooted and got stuck on the same At&T screen. So I decided to use Odin to go to stock and start from scratch. For some reason Odin 1.81 was supposed to go back to stock with Root. For some reason it got stuck I turned off my phone and now it is unresponsive to most of the tricks listed on this forum.
So will a jig get me out of this jam, a quick search pulled up nothing reliable or I would have to wait 3 weeks to receive, I need it this week like tomorrow if possible.
Searched the forums before going to work real quick couldn't get anything concrete So I'm posting this and I will search some more when I get to work.
Thanks for any help.
Click to expand...
Click to collapse
not sure why you would even be using Rom Manger other then maybe renaming backups. This is i known issue with our phones and Rom Manager and has been stated way too many times. Try holding the power button down for a while to see if it resets. A jig is going to put you in download mode so that you can use Odin again.
Thanks for the reply. Yes I have heard of issues with Rom Manager and i stopped using it. But for some reason or another I kept it on my phone and idiotically agreed to having it put me into CWM. Also I kept the battery in the phone till I got to work, pulled it out of my bag to try the suggestion that was given above and noticed my phone is warm. Not sure what's up with that, I immediately pulled the battery and will let it cool for a while and then I will try with the above suggestion.
Can you recommend a jig for our phones or does any jig work on any phone.
Thanks for all your help and wisdom.
logicrulez said:
Thanks for the reply. Yes I have heard of issues with Rom Manager and i stopped using it. But for some reason or another I kept it on my phone and idiotically agreed to having put me into CWM.
Can you recommend a jig for our phones or does any jig work on any phone.
Thanks for all your help and wisdom.
Click to expand...
Click to collapse
you can get a jig from just about anywhere. you probably dont need one though. have you even tried manually putting your device into download mode by powering down the phone, plug usb into comp, then holding down both volume buttons, then plugging in the device?
http://www.ebay.com/sch/i.html?_fro..._nkw=galaxy+s+2+jig&_sacat=See-All-Categories
Yes I have held the power and up/down volume buttons(that's what works on my phone) and plugged usb into phone while it was plugged in to my computer to get into download mode but nothing happened. Too late I already ordered a jig as I am despearate and hopefully it will be of further use in the future. I also tried holding the power button down for a while and still nothing. Hopefully the jig comes in a couple of days and works.
Thanks for all your help and wisdom.
Okay, so I got my jig today and put it into my phone and nothing happened. I put my phone on the charger and left it til I got home so it should be charged up.
So am I bricked or is there any other options I can try.
Thanks for your help.
Did you try holding both Vol and power keys (all 3) together for 30 seconds? It's saved my bacon a few times, despite how nonintuitive it seems. Also try the USB thing with battery removed, or try putting USB in and inserting battery while holding all 3 keys.
Still a no go I'll call warranty to see if I can get it replaced. If not I'll just wait for sgsiii to come out since its supposed to come in April now.
Thanks for all your help!
If your phone locked up while flashing bootloaders..
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
Hi People of the world! As you can see im new to here so yeah i just might be in the wrong section...
So, I just got my shiny android a week ago, and know it sits on my desk, lifeless, like a brick. Like literally its dead! I don't know if I can fix it or the BIOS (if theres one in Samsung Galaxies) is fried, or maybe the motherboard is fried, or the battery overcharged, etc. But I just cant do anything! I'm totally out of ideas!
Heres the problem, I first rooted my android successfully, and played around with my android a while. But as you expect I just coudn't wait for the jelly bean update! So, I desided I would give a try to take the Russian firmware instead. That was already a bad idea, but I read on some threads that it would work fine, so I downloaded one from Sammobile.com. The real mistake? I downloaded the wrong phone. I own a Samsung Galaxy S Advance NFC Version;GT-I9070P The one I downloaded was UnNFC version; GT-I9070. Well, I didn't realize that, and proceeded with entering download mode and eventually flashing the PDA file from Sammobile with ODIN. So I pressed start. It started the process, and after 5 min it said in blue: RESET. I saw the phone rebooting. Now, another big mistake: I started touching the power button, which I shouldn't have done. Then, instead of waiting, as soon as seeing the thing wasnt booting, I took out the battery and unplugged the USB cable. Then after a while the PASS appeared in green. So it went successfully? NONONO Now it wont boot! More specifically, it wont TURN ON! like it wont whow any sign of life. As if it had no battery or USB.
Today I discovered, If I hold Vol UP+Power+Home when its connected to my PC, it makes the beep, shows that it failed to install the driver for "U8500 USB ROM" What the (*^&(&%*(&^&* is that??? Also, in 5 seconds, the device disappears, meaning that I must hold the button combo for another 20 seconds.
So, I've got no connectivity to ODIN, nor Kies, and I cant go into download mode, nor recovery mode.
Any Help?
Pleeaase if you can help youre a super god of androids!
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
MikeSome1 said:
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
Click to expand...
Click to collapse
Exactly. Nothing at all.
The only evidence that its not fried is that the computer detects it as U8500 USB ROM for 5 seconds whenever i hold the power button or any combination. Nothing on the phone though.
Hey
Hey man got the same problem... I have put mine to a service center i will see what the'll do
pafiking said:
Hey man got the same problem... I have put mine to a service center i will see what the'll do
Click to expand...
Click to collapse
Yeah i think I should take it to service too, but I want to try at least first:cyclops:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Lynnfield4000 said:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Click to expand...
Click to collapse
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
Please help! I also bricked my Samsung S Advance I9070P after downgrading from JB to GB, since JB was updated for India I9070...but the phone bricked after downgrade. Everything was successful and it had auto-rebooted after the downgrade and stuck with Start up screen. When I removed battery and tried again..it bricked! No recovery mode, No download mode, no power on.
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
So you find any solution? I have a similar problem right now.
My problem continues
i read all, 3 days reading and testing, and nothing new about my problem.
I have a problem with rebooting loop. (i cant touch correctly the power button, didnt work, also all the time is rebooting, or staying without screen light, i cant explain correctly!!)
I did all, back to stock, tried install many roms and kernels, but nothing works.
the best thing that i did to use it for few moments was.. use the swipe 2 wake, with AJK - using Siyah v.4.3.3 ICS over the SHOstock3.
The swipe 2 wake not works all the time, most of time the screen only wake up when i receive a income call.
But continues rebooting, most of times when i shake the phone.
Any idea for me?
Thank you
brubrazil said:
My problem continues
i read all, 3 days reading and testing, and nothing new about my problem.
I have a problem with rebooting loop. (i cant touch correctly the power button, didnt work, also all the time is rebooting, or staying without screen light, i cant explain correctly!!)
I did all, back to stock, tried install many roms and kernels, but nothing works.
the best thing that i did to use it for few moments was.. use the swipe 2 wake, with AJK - using Siyah v.4.3.3 ICS over the SHOstock3.
The swipe 2 wake not works all the time, most of time the screen only wake up when i receive a income call.
But continues rebooting, most of times when i shake the phone.
Any idea for me?
Thank you
Click to expand...
Click to collapse
I got a great idea.....
STOP MAKING NEW THREADS FOR THE SAME PROBLEM!!
Sent from my SGH-I777 running AOKP
Here is an idea. Get a new phone, or your phone repaired. YOU HAVE A FAULTY POWER BUTTON. With all the reading and testing you have done would have thought you had that figured out. Quit making new threads about the same issue please. I am guessing we won't be seeing too much more of you around here if you keep it up.
Good luck getting you power button fixed.
Butchr said:
Here is an idea. Get a new phone, or your phone repaired. YOU HAVE A FAULTY POWER BUTTON. With all the reading and testing you have done would have thought you had that figured out. Quit making new threads about the same issue please. I am guessing we won't be seeing too much more of you around here if you keep it up.
Good luck getting you power button fixed.
Click to expand...
Click to collapse
It cant be the power button! its restarting without pressing the button!
brubrazil said:
It cant be the power button! its restarting without pressing the button!
Click to expand...
Click to collapse
Dude. Exactly because your power button is defective! Was it really that hard to figure out? Just stop posting from now on before you make a fool of yourself.... Woops already did
Sent from my SGH-I777 running AOKP
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.