I am having an issue with my atrix when booted into no bp mode via boot options the phone will crash and restart regardless of what I do with it. Can anyone share there experience with no bp mode or help me out somehow?
What's np mode?
Sent from my MB860 using XDA App
Right my spelling is rather off. My question is when booted into no bp mode my atrix will crash or rather restart no matter what im doing. When booted everything works fine then 5 minutes up and boom screen off and restart. I am wondering if this is a serious issue or if there is anything I can do. Can someone confirm no bp mode works fine with there atrix. I have tried a factory reset with no luck.
touchscreen unsensitive
after install of the stock kernel 4.5.91 each time i have my touchscreen freezed !
Do you guys have an idea???
Thanks
Related
I need help, please.
I upgraded to the Oficial Froyo 2.2 today and everything went fine, rebooted the phone with no problems.
After that I used SuperOneClick to root the phone.
The process was ok, at least I believed that, but a few hours later, after a reboot the phone kept rebooting time after time.
It shows the S Samsung logo then vibrates one time, after a few seconds it vibrates 3 times in a faster way... it does that a few times then reboots again.
I have no working 3 buttons, can't get into download or recovery mode.
Is there anything I can do?
Why did this happen??
I would very much appreciate your help.
Regards,
Ricardo
Can someone help me?
Please?
Well, I got no responses but I managed to recover my bricked phone by using the 301kohm trick. Got it to enter download mode then flashed a new rom.
Thanks.
Sent from my GT-I9000 using XDA App
Hello XDA Community/ Vibrant users!
So I recently tried a GPS fix that involved no flashing. I don't have the link but it was the method where you dial *#33214789650# (yeah I memorized it) from the dialer and go into LBS Test mode, and delete GPS data.
In addition, I have also flashed a GPS fix from this link http://forum.xda-developers.com/showpost.php?p=7565713&postcount=149
before I tried the method from the dialer.
Now, (after I tried the dialer method), when I reboot my phone, the small loading circle appears and it shuts back off. The only way I can start my phone is to go into the Android recovery and reboot system.
Anyone have any ideas as to what I should do to fix this problem?
P.S. I restored a nandroid backup from last week before I flashed the GPS fix or tried the dialer method and the problem persists.
HELP!?
Another weird thing I noticed, when I reboot into recovery mode, it wont allow me to "reinstall packages" because it says that there is no such directory for update.zip.
Also, before I shut off this phone and discovered the re-boot issue, I noticed that even after I disconnected my phone from my PC, the UBS Debugging and UBS connect sign kept blinking on and off. In fact, it is still doing that now.
Could this UBS be the issue of my phone and not the GPS?
If a working nandroid restore has failed, it could be your Kernel's problem, try flash a new Kernel that works with your ROM.
FYI: nandroid does not restore Kernel.
Hope this can help.
Sent from my SGH-T959 using XDA App
One more thing, if I hold the power down for a REALLY long time, like over 10 seconds, the loading indicator will flash a couple of times and then the phone will turn on
dumb question but which kernal should I flash?
ahhh anybody have any idea??
My phone ALWAYS says USB Connected and USB Debugging even when its not connected to the computer. Whats going on?
Hello Guys,
I opened dolphin browser last night then it hanged. I held the power button and down button to shutdown the device which it did. It tried to boot up to the Google screen(the one with the lock/unlock symbol) but it took a while so I powered it down again by holding the power button. And now, it doesn't boot anymore. I tried connecting it to my pc but it isn't being recognized, only the apx can be recognized.
Help help.
I'm on stock ROM, rooted and unlocked. I tried the button combos to no avail.
wow thats impossible... or a rare thing i guess...
Stock ROM stock Kernel,
just rooted and unlocked?
I think the device was dying from start...
try booting to recovery...
There is a decent amount of info on your problem of the N7 suddenly going into apx mode. Search Google for nexus 7 apx mode and maybe you'll find your way outta here. Wish I had a little better advice but I haven't experience it first hand... Good luck...
Sent from my Nexus 7 using xda app-developers app
i just got a new phone the phone worked good for three days all of a sudden the phone just froze so i reboot it and it wont pass the x logo. i tried doing factory reset it didnt help. after a while i discovered the phone works perfect when i plug it in the computer the minute i unplug it the phone gets stuck again but the live wallpaper keeps on moving!! . the phone is unrooted does anyone have any idea how i can fix this issue??!? my phone is not very mobile right now
Either RMA or boot recovery img
Sent from my Nexus 4 using xda premium
Restore the device using TWRP recovery . May be.
first of all thanks for the replies.
i tried restoring from twrp recovery didnt work, i tried rooting the phone and even changing kernel nothing seems to work the phone still works perfect when connected to the computer the minute i unplug it stops. in order to use the warranty i have to send the phone to united states and im from israel so it kinda sucks :/ do you have any more Suggestions how to solve this problem???
I've been searching everywhere for a solution, but nothing has come up. I own a AT&T galaxy S4 that was on NC1 and today, I noticed that it wasn't in sleep mode even though I had not turned it off. I held the power button down and it presented me with the Samsung Custom boot screen with the unlocked lock. After that, nothing. The phone just turned off again. I went to try and flash the NB1 stock ROM through odin. It booted up fine the first time. I was setting it up and while I was doing so, it shut off. I pressed the power button to power it on, this time I get the normal samsung boot logo, and once again, nothing afterwards. I tried reflashing through odin and trying to access recovery mode to wipe the cache and factory reset. I ran odin and when I tried to enter recovery mode (it showed entering recovery mode in the top left corner of the menu), it shut off again. Does anyone know what I can do to resolve this? I would really hate to have to get another phone as I am currently under contract for another 8 months. Thanks in advance for anyone that helps!
cxzzcx said:
I've been searching everywhere for a solution, but nothing has come up. I own a AT&T galaxy S4 that was on NC1 and today, I noticed that it wasn't in sleep mode even though I had not turned it off. I held the power button down and it presented me with the Samsung Custom boot screen with the unlocked lock. After that, nothing. The phone just turned off again. I went to try and flash the NB1 stock ROM through odin. It booted up fine the first time. I was setting it up and while I was doing so, it shut off. I pressed the power button to power it on, this time I get the normal samsung boot logo, and once again, nothing afterwards. I tried reflashing through odin and trying to access recovery mode to wipe the cache and factory reset. I ran odin and when I tried to enter recovery mode (it showed entering recovery mode in the top left corner of the menu), it shut off again. Does anyone know what I can do to resolve this? I would really hate to have to get another phone as I am currently under contract for another 8 months. Thanks in advance for anyone that helps!
Click to expand...
Click to collapse
I'm guessing it's a hardware failure.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Sorry
thebestiam said:
I'm guessing it's a hardware failure.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
I couldn't believe how simple the solution was. I figured out my battery had simply ran out and a charge got it right back up. Thanks for the response!
cxzzcx said:
I couldn't believe how simple the solution was. I figured out my battery had simply ran out and a charge got it right back up. Thanks for the response!
Click to expand...
Click to collapse
XD