Related
Hello all -
My "bricked" situation appears to be unique as I've searched all over and have only found others with at least a phone that has a display.
Scenario:
Had SimplyHoney 4.0 installed (I believe Voodoo Lagfix was enabled). Decided it was time to go back to stock. ODIN'd back to stock (doesn't that wipe any VooDoo?). Re-rooted phone and connected to Kies for giggles to see if it would actually work this time for an "Official" update. (Last time I connected the phone it would not recognize the phone as the appropriate phone for an update) This time it saw it as a Vibrant and proceeded to do the Froyo update. Once it was completed, the Vibrant's screen never turned on.
It feels warm to the touch when you turn on the phone after a few minutes like it typically does, but I can't see anything on the screen.
Did this update do an extreme brick to my phone that it is now a lost cause?
I appreicate any advice you have.
BTW, tried the download button combos that are out here and none of those worked.
When I last had my phone open to fix the GPS contact, I see there is a small battery. Would popping that help reset anything?
It's the same scenario in this video on YouTube - "Video of hard bricked vibrant" by htcpro1212
Sorry can't post links yet.
I had a similar situation with a friends Vibrant this is what I did...pull out battery, plug phone to computer with usb, do the three button combo (volume up down &power) while holding replace battery and that should put phone in recovery mode... hope this helps good luck!
Sent from my Nexus One using XDA Premium App
no point rooting if you're going to update with kies, it wipes root
you could have just used whitehawkx stock 2.2 rom, kies has a history of hard bricks after you've been on a few custom roms
keep trying button combo's (vol + and power with the GB bootloades) but chances are its hard bricked, if it doesnt work phone samsung or t-mobile and say you tried updating with kies and it doesnt do anything now
Pm sent I can fix this for you...
You should always try ODIN back to stock. Its such an Relief.
I'm not sure if this will work in this case or not. When I thought I had bricked my Vibrant, I had a picture looking like a phone-triangle-computer on the screen, so it wasn't blacked out.
I got a "jig" (search the forums or google it.) They cost less than $10 and have saved me several times when I've messed up to get me to download mode so I can use odin.
First off I just have to say that I totally understand the 10 post minimum before posting in the development section but my god is that annoying. I just don't post a lot but have been doing this for over a year now. I very much dislike that I can't post into the CM7 Nightly section about this. ANYWAY with that out of the way....
I have a AT&T SGSII (i777) which at boot up the Samsung splash screen says i9100 which I find odd and I am running CM7.2.0 RC0 (KANG) and the alternat modem i777 UCKJ4. This Nightly saved my battery as it was intended to do so I am grateful for that. I have noticed something that I would like to tell Antinm about though.
When using the Google Music application if my screen rotates I lose the screen. It will rotate but then it will only show the background of the Music app and then if I hit the power button to turn the screen off it will not come back on. The music still plays and the buttons still work (volume) so I don't think it is a hardware lock up but rather something with the display. I have to powercycle the device to get back to normal operation.
Also, I have done everything I should as far as wiping dalvik and cache and reinstalling the ROM/Kenrel/Radio/Recovery etc. It's not a major issue but I just wanted to get it out there in case anyone else is having this peoblem so the devs can look into it is they find it necessary which they may not as I know everyone especially Antinm is working on ICS/CM9. Can I get a woot! for CM9/ICS?!?!
Thanks
Woot
With that out of the way, I can answer the first part. It boots the i9100 screen because the flash counter has been tripped from a non stock kernel being flashed. This most likely happened when you rooted it. Should've went entropy512's route of rooting. A usb jig will bring back stock splash screen and reset the flash counter.
As far as the google music app, so far no issues have been reported on like that. Doesn't mean that rules out it being a cm7 problem.
But to try and rule that out, reflash cm7. It's known for not 'sticking' the first flash. Then wipe everything you can in recovery, minus battery stats of course. Make sure to back up your apps somewhere else so they don't get erased.
Once that's done post if google music app is still giving you issues.
Sent from my páhhōniē
USB JIG
Yo hairy1, it totally worked. I got it from mobiletechvideos.com for $8. Thanks!
Thanks for the update. Glad it worked out.
Sent from my páhhōniē
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
[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.