Anyone else notice that the version leaked last night (1.12.605.9) is actually higher than that which comes pre-loaded on the phone (1.12.605.6)?
A second question for those who've got the thing since I cant post in the development forums yet. Has anyone figured out what the key combination is to boot the phone into recovery mode yet?
Volume down while turning on will get you into hboot
could have sworn i tried that, lol... thanks... just took way longer than the other phones i've used.
Related
Hey all,
My phone was workin great until about yesterday, i did a factory reset to see if a flash app was preinstalled or not and then i charged the battery until full and let it run out over night (which it drained all the way). Last night until this morning i let the battery drain again, although this time i got the error:
"Modem did not power up (0)
Starting RSD protocol support
Not enough power to flash" (somethin like that).
So i charged it to about 30% and it was finally able to boot, however, i'm now getting random reboots where it's gettin stuck on the screen:
"Modem did not power up (0)
Starting RSD protocol support" (slightly different then previous error)
What are my options here?
Thanks
*EDIT* This phone was never rooted.
Not to be rude...but why isn't Motorola or AT&T the first place you went to for this problem? If the phone isn't even rooted or modified at all...and it's having problems with rebooting and hardware issues (the modem problem)...you wouldn't think of getting a replacement before posting on an internet forum? It's almost obviously a hardware issue...
hotleadsingerguy said:
Not to be rude...but why isn't Motorola or AT&T the first place you went to for this problem? If the phone isn't even rooted or modified at all...and it's having problems with rebooting and hardware issues (the modem problem)...you wouldn't think of getting a replacement before posting on an internet forum? It's almost obviously a hardware issue...
Click to expand...
Click to collapse
Wasn't rude at all, we just approach a problem in two different ways. Part of me knew it was a hardware issue, part of thought it could have been a software issue. So i figured i'd post here to see if this has happened to anyone else, maybe it was an app running in the background that didn't like this new dual core and was crashing the phone? I certainly didn't know, so i posted here. It's far easier to post on an internet forum designed for the phone, than it is to drive to the store and have a back and forth with the employee.
*EDIT* and for clarification i just brought it back to radio shack and had them exchange it
Its great when people come here and ask questions that way if its a larger issue then when people search for a fixx they can see other people are having the problem too.
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).
Well I went to flash a test mod I made last night trying out the new vrtheme engine and pretty much bricked my phone. Not sure what happened worst I expected was a boot loop :silly:
I have a new one on the way but figured I'd give one last try incase I missed something. When flashing the mod I got an error, then rebooted the device to see if the mod took or not and my phone went dead and won't turn back on. I tried different batteries- fully charged (I have 3), using amonra so I know its not the CWM bug. I get nothing, no recovery or hboot, no adb or fastboot, No charge indicators, no physical mutations no nothing.
The only thing I get is 2 quick beeps when I plug it into my laptop. My work computer doesn't have the drivers so I get a device not recognized but nothing else.
Ideas anyone????
would like to know what happened so I don't do it again but I can't even check .
i did something similar.
i was attempting to build a rom and the phone booted then the screen went black and now pretty much the same thing, but i don't even get the 2 beeps.
it kills me, lol. I've flashed hundreds if not thousands of tests builds and "experiments" to my phones, done mods and themes for multiple phones never had an issue then something that is essentially a meta-morph breaks my phone, I'm more in awe than upset.
edit: please don't think that I'm blaming vr theme engine. I've flashed other vrthemes and was fine, this is something I did with a mod I was working on, just not sure what went wrong.
Run an RUU?
Tried, just waits for device for the exe version and cant get to hboot for the other. My phone was due to be returned at some point I had major heat issues saw the 150*f 's a few times and other quirks. Still think it was the mod though.
Well replacement just got here. It was nice of Verizon to ship out a replacement Incredible that is years old but now I have to wait 2 more days for my replacement Rezound....sigh @ Verizon....
Just got this same issue as well on my phone.
Only difference being that mine wasn't installing a theme.
I had just flashed the newest Ineffebilis Deus (1.1), had an issue where I only saw the menubar, rebooted, wiped and flashed again. Told it to restart, now it won't do anything. No charge light, etc. Using AmunRa, btw.
I have no other batteries to test with, unfortunately.
adb shows no devices and even the wall charger doesn't do anything.
Just my luck that it does this two days before I get on a plane, haha.
So I was looking to leave my Sprint contract (long story) and decided to sell my Evo 4g LTE to help pay off the massive contract-breaking bill. I'd had my phone rooted and running CM10 nightlies for quite a while without any sort of trouble.
So right before I put the phone on the market, I took out the SD card, and wiped everything using TWRP recovery. This included Cache/Dalvik/System/Factory reset and the only thing I did different, which was to wipe Internal and External storage.
After that, I flashed the latest CM10 nightly at the time (which was cm-10-20121008 at the time) and called it a day as I didn't want to put any of my info on the phone before I sold it.
Flash forward a couple of days, I sell the phone and almost immediately get a call back saying it has no sound at all.
The guy I sold it to tells me he even tried unrooting and flashing the stock ROM to no avail. I bought the phone back from him, and am trying to figure out what exactly is wrong with it.
Since then, I've discovered that not only is there no sound, although occasionally I will hear the buttons click, so I know the speaker hardware itself is fine, There is also no video playback at all, which makes me think this is some sort of software or firmware problem, though I can't tell where the problem lies.
I've tried installing different ROM's and the best I could get out of video was the Youtube app showing still images every couple of seconds, without any sound at all. I tried loading videos to the SD cards only to get a message saying "This video cannot be played" without any further reason.
I'm currently downloading the latest OTA stock ROM to see if I can restore it to Factory settings, but I'm lost as to what could possibly cause this strange behaviour.
Anybody ever encounter something similar? Any ideas what I could try next?
Alternatively, does anyone want a (mostly) working phone at a steep discount?
Have you ran an RUU yet?
How much do you want for it as is?
jayjam99 said:
Have you ran an RUU yet?
How much do you want for it as is?
Click to expand...
Click to collapse
I tried running the RUU, still won't work.
If you want it, an even $100 will do.
i have the exact same problem ive ran ruu and relocked and locked bootloader i have unrooted ive done everything and the problem still is there please someone help me
4.3 update causes strange glitch
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?