It Appears that a few people are receiving "Encryption Unsuccessful" error messages when installing the PRIMO-S 4.0 ROM. If you experience this issue simply "REBOOT" your handset using the process provided below by "djisgod", From here you will be presented with the HBOOT screen, Use the "Vol down" key again to navigate through the menu until you highlight "Clear Data/Factory Reset". Press the power button to select, Your handset will now "clear saved data and reset" as the option would suggest, Once this complete you may need to enter or recovery and select reboot system or the handset may reboot itself. Either way the issue should be resolved.
Hope this helps
DO NOT PULL THE BATTERY.this is the fastest way to break your phone with an emmc error.not good advice at all.hold both volume keys then hold power to force a reset.dont pull the battery,unless you like a fried phone.
Thanks "DJISGOD" for correcting me with the removal of the battery. Wouldn't want to be held responsible for bricking peoples devices
This way you will be stuck still (the 3 button combo normally reboots your device, not to bootloader), use adb or pull the battery in the small gap between shutdown and startup, maybe reboot a few times before you pull it to get the right timing.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Tectas said:
This way you will be stuck still (the 3 button combo normally reboots your device, not to bootloader), use adb or pull the battery in the small gap between shutdown and startup, maybe reboot a few times before you pull it to get the right timing.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
My initial advice was to pull the battery in order to gain access to the bootloader but was told not to pull the battery as it could result in damaging eMMC chip
dannyhoughton74 said:
My initial advice was to pull the battery in order to gain access to the bootloader but was told not to pull the battery as it could result in damaging eMMC chip
Click to expand...
Click to collapse
Have a proper search on the forum. My understanding is that pulling the battery isn't what actually seems to kill the phone. I have frequently had to do it, just do as posted above between the shutdown and restart. Make sure you leave the phone powered down for a while before reconnecting the battery though - the problem is when you reconnect the battery before things have fully discharged.
Simon.TS.HTC said:
Have a proper search on the forum. My understanding is that pulling the battery isn't what actually seems to kill the phone. I have frequently had to do it, just do as posted above between the shutdown and restart. Make sure you leave the phone powered down for a while before reconnecting the battery though - the problem is when you reconnect the battery before things have fully discharged.
Click to expand...
Click to collapse
My thoughts exactly, I've never had a problem removing the battery and have myself removed the battery on a number of occasions. I no longer have the problem as was able to resolve myself. I started the thread in order to advise others how to resolve should they have the same issue. Thanks though... It's good to have input from another person
Is there still any way how to successfully encrypt Desire S? Not working in any rom I tried...
Related
Hi guys,
I have a little problem where my phone's power button will not function in any way, long presses, short, almost embedding my thumb in it, all to no avail. This is doubly dissapointing as I have just installed the latest dexter plus patch to fix the problem. I still had the problem on the previous version and I thought a clean start may fix it. The only way I can get the screen on is to press the media play button! Which of course isn't doing anything on dexter.
Hunches:
I have been playing with a light sensor program and using a 3 second press to turn the phone off, I am only thinking this is related as when I re-installed then turned off the phone using a battery pull, that now the media gallery button will now not work at all, so that is a change.
Second, the power button is buggered. Seems unlikely as everthing feels normal, no big drops have occurred from heights, and the button is travelling in and out as usual.
I have also noticed that as soon as I re-insert a battery that the phone starts immediately, the M pops up as if it is already posting. So maybe it is stuck down?? Again, I don't think so, as the mechanism is working per usual.
If anyone can help it would be fantastic, you guys haven't let me down yet, and this thing is purring, but unfortunately I cannot use it lol. Just my luck.
Thanks in advance
another thing, still not solved
Another thing is happening, the phone screen turns on "after" pressing the power button, it may be once or a few times, and then pressing the gallery button.?!?!
Also, at random times it plays a podcast on my phone, the exact same podcast, and from the start, though the duration may be a few seconds then repeat, or it may go for ages, its quite a rude podcast too which has caused me to throw my phone under the car seat to shut it up when people have been trying to talk to me, as you can imagine its quite embarassing.
There are no services or apps running that I can find related to music, it may happen after pressing the camera button, or opening a website.
It is still going really fast though. And I have also reinstalled the light sensor program so I can turn it on and off without causing damage to the power button.
Thanks again everyone.
pisceanblue said:
Another thing is happening, the phone screen turns on "after" pressing the power button, it may be once or a few times, and then pressing the gallery button.?!?!
Click to expand...
Click to collapse
please clarify
sure, so the only way I can get the screen to turn back on, after turning off as per display power saving preferences, is by pressing the power button, maybe a couple of times, then following that up by pressing the gallery button next to the shutter button, pressing the gallery button doesn't seem to be working to turn the screen on now, but this combo is.
I hope that helped.
Cheers.
EDIT:::
The gallery button alone is working again. sorry guys.
You might just want to reflash it to stock to see if this resolves the problem.
Yeah I think I may have to.
Before I do., I was reading a post on a different forum where another person was having a similar issue. They seemed to solve the problem by using rom manager to boot to a manual restore menu where there was a button tester section, after using it the power button worked for them. I tried but after resetting it displayed a triangle graphic then rebooted.
Is there any way to do this with our open recovery program or any other utility to test the functionality or maybe reset the button or apply a patch etc.
Thanks again :-D
Sent from my XT720 using XDA App
Getting Frustrating
Alright so I followed your advice on your videos on how to reflash to stock, so of course my bootloader does not show up the same as yours on the video. I can get to the bootloader fine, using the button combo or by using quick boot > bootloader, both have the exact same result, the boot loader screens as follows:
Bootloader Fastboot mode
80.89
and that is it....
Also, my computer using rsdlite does not acknowledge the phone, not omap drivers loading etc. Followed your instructions exactly.
This is frustrating me to no end lol.
I am guessing that because I can get to the bootloader with combo no problem, that the buttons physical connections are working.. At least thats a positive.
Can I flash to stock with openrecovery? Or maybe to an earlier version of Dexters froyo? Other ideas?
Any help would be much appreciated guys, trying to use this phone at work with light sensors to turn off screen is not as easy as they say. OMG....
Thanks so much
pisceanblue said:
Bootloader Fastboot mode
80.89
Click to expand...
Click to collapse
The fastboot bootloader isn't the right one. So... if you hold volume up + camera shutter while powering on you end up in fastboot? That's really weird.
Maybe your keys have been remapped somehow? Does anyone know a chord to boot fastboot? Perhaps check to see if your USB port is clean?
Lmao
Just my luck to have a weird problem. I thought it may have been remapped so I have been trying the program buttonremap. It doesn't seem to let me do anything except stop the buttons I re assign doing anything :'(
Does anyone have a proper key mapping file that I can replace with my faulty one to hopefully fix it?
Or any other ideas?
Cheers everyone
Sent from my XT720 using XDA App
Just checked my system / user / keylayout folder. How many files are supposed to be inside, there are a few. I checked the contents of some and they seemed to be the same. Just an idea.... thanks again.
Sent from my XT720 using XDA App
Ok installed anyunlock it allows you to use any physical button to unlock the screen. It doesn't respond when the Power button is pressed, it responded fine to volume rockers, gallery and shutter though.
Anyone know if this would mean for sure its a physical problem before I crack it open and try and fix it.
Thanks guys.
Sent from my XT720 using XDA App
No one has any solutions for me? Come on guys.
Sent from my XT720 using XDA App
Breakthrough!
I am pretty sure I have fixed the problem, I tapped the phone fairly hard on its sides and back, and lo and behold after a battery pull and replacement it didn't turn itself on, I waited, nothing, so then I held the power button and it started up!!!!
But....I have another problem that happened before that, I am stuck in the boot animation that open recovery uses before going into its program (i.e. where you can load nandroid, wipe dalvik cache etc).
I was about to load a new rom, and was in open recovery, had installed it and about to do the reset and the phone turned itself off, and thats when I got the problem with the sticking boot animation.
So just to be clear, I am stuck in a boot loop, but not with the M logo, the restore logo.
I hope the power button solution can help someone else, as random as it is.
If anyone could help me get out of this boot loop without flashing stock that would be great. ( i can get to the real bootloader now btw)
Thanks again everyone.
Solved it all
Just took the sd card out and rebooted. And the power is getting better after banging it.
Thanks to all.
Sent from my XT720 using XDA App
pisceanblue said:
Solved it all
Just took the sd card out and rebooted. And the power is getting better after banging it.
Thanks to all.
Click to expand...
Click to collapse
So, is your conclusion is that the button was stuck and the banging freed it? It doesn't restick?
The Button is not perfect still. Sometimes over sensitive Occasionally it will not even work but it works most of the time. I am just wondering what cleaning solution I could use to free it some more.
It has certainly been a trying problem. Cheers for the help.
Now I need to figure out why I have this strange ghosting on the top of my screen.....
Sent from my XT720 using XDA App
Samsung Galaxy S2 Power Button Not Working
Hi Guys,
Any solution for the power button problem? Current latest Android 2.3.3 Samsung Galaxy S2 also having the same power button problem. Most of the time I can't use my power button to turn on/off the screen (wake/sleep) and there's no menu for long tap as well. Luckily it does wake when i press the only physical Samsung center button.
What i have already tried: Factory Reset, disable Power Saving Mode, Spare Part+ (apps), Screen Off and Lock (apps), and all won't help.
Is there any current updates or patches to allow the power button to work as usual?
Thank you.
take it to the samsung technical centre
Thats if you still have warranty
archer88 said:
take it to the samsung technical centre
Click to expand...
Click to collapse
won't help because this is the 3rd phone replacement from the shop with the same problem. 100% Android software problem.
Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!
PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.
Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?
Hey guys,
So my brothers Nexus 5 came to an end but i'm determine to recover it (Already Partially Recover)
Backstory:
So initially the power button wasn't working like it couldn't be pressed, and as the device was already off i decided to plug a charger in and it would enter the boot stage but enter a boot loop which further research showed me it was a issue with the powerbutton, So i came to the conclusion to remove + replace the power button so i opened it up, took a look and soldered the broken power button off, with alot of time and effort i managed to remove it and clean it up with the intentions of installing a new powerbutton i bought a fine tip solder tip however it wasn't burning properly as i noticed eventually, in which i was unable to solder a new power button on even with flux, aswell as this i managed to solder it on in which i was convinced it was a decent soldering job as all the points were clearly connected i placed the board into the device (wHICH WAS A MISTAKE) as i should've waited a solid hour, to ensure it was strong, as of this the power button had come off as i was placing the board back in which meant the button was practically scrapped and i was extremely fustrated, so i decided to screw it a put the device back together without the back casings over the board, and i wanted to see if i could bridge the connection whilst the charger was plugged in in which i did and the device booted up.
Main Question:
Now my main question is, i need a workaround for the powerbutton currently i've installed Gravity Screen for him, however it's got a high battery consumption and it's not too reliable so i'm trying to get a solid method.
I've come across a headphone jack that has a button which i can configure to be a power button (Pressy or iKey)
Now that the issue with Locking + Unlocking is solved
How can i power the device back on when it shuts down due to lack of battery as i've sealed the phone back up, He currently runs Android 6.0 MRA58N, My main idea was to Root his Device + get TWRP installed however i was wondering if i could do this without rebooting his device / setting up a method to power his device via ADB however i haven't installed any ADBs etc so far.
My second idea was if i booted the device into fastboot by plugging in in the power cord and holding volume button, with the battery unplugged via the ribbon would it power on the device?
Last question is, i powered the device with the Camera Unplugged via ribbon cables however it's not working as the app just opens and closes without a FC so i was wondering if a reboot would just fix this?
ADDITIONALLY Another method could be rebooting via terminal However i'm unsure on how to use the Terminal / if i need root or not etc.
Thanks!
Contact a kernel dev. He will probably be able to remap the power button, to get it to boot from the charging screen. Or try to disable offline charging alltogether.
playitlouder said:
Contact a kernel dev. He will probably be able to remap the power button, to get it to boot from the charging screen. Or try to disable offline charging alltogether.
Click to expand...
Click to collapse
I'm quite new to the Nexus 5 Area, and infact i don't know any Kernal developers - Is there any chance you could probably help me out and give me some contacts etc.?
Hussain_Salam said:
I'm quite new to the Nexus 5 Area, and infact i don't know any Kernal developers - Is there any chance you could probably help me out and give me some contacts etc.?
Click to expand...
Click to collapse
I dont do much in terms of custom kernels, but post in some kernel threads in the nexus 5 development forums, or contact the creator of the thread via pm. Just look for threads with KERNEL in the name
UPDATE!
playitlouder said:
I dont do much in terms of custom kernels, but post in some kernel threads in the nexus 5 development forums, or contact the creator of the thread via pm. Just look for threads with KERNEL in the name
Click to expand...
Click to collapse
Okay Thank you,
UPDATE:
*I've Overcome the Powerbutton issue as i've ordered Pressy/iKey which should be arriving tomorrow which will lock and unlock my screen
*I'm now trying to figure out another method to power on my device if it shuts down:
One idea was to some how get the device to power on when i plug in a charger maybe by installing TWRP
Or another method was to power it on via an ADB shell on pc Or Something like that
*I'm also trying to reboot the Device however im unsure on how to do so without a power button.
Hi,
I also posted this in the Moto G forum, possible by mistake. If the Mods. could decide which location is better, and delete the unnecessary post, it would be great....
Wondering if anyone can help.
I have a Moto G3 8Gb model. Everything is stock. Not rooted, unlocked. The phone is 4 Months old.
The problem I am having is the battery symbol always displays the "Lightening Flash" for charging, even when the phone is not plugged into the charger. I have tried clearing the cache, but that didn't work. I am not sure if this "bug" is only an indication issue, or if the phone will actually think it is in charging mode and that will have knock-on effects to the phone itself. I am tempted to do a Factory Reset to see if that cures the problem, but maybe someone has a fix......
Thanks for your help.
Does it also show 'charging' in the settings>battery page? Or only statusbar?
Edit:- Sorry no idea.
Broadcasted from Zeta Reticuli
No, on Settings>Battery it shows XX% - approx. YY hrs left.
First, do a hard reboot... With the phone operating, press and hold power for 10+ seconds until it reboots. Test
Second, boot in safe mode and see if it persists. Hold the power button a different when prompted to Shutdown, long press the button and select Reboot to Safe Mode. If the trouble is gone after reboot, it's an app you have installed that causing the issue
Third, clear cache... https://motorola-global-portal.cust...ail/a_id/105527/p/30,6720,9390/kw/clear cache
Lastly, do a full factory reset to wipe all information (delete Google account first).
If it still persists it's a hardware issue and there is nothing you can do but send it in for repair.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
First, do a hard reboot... With the phone operating, press and hold power for 10+ seconds until it reboots. Test
Second, boot in safe mode and see if it persists. Hold the power button a different when prompted to Shutdown, long press the button and select Reboot to Safe Mode. If the trouble is gone after reboot, it's an app you have installed that causing the issue
Third, clear cache... https://motorola-global-portal.cust...ail/a_id/105527/p/30,6720,9390/kw/clear cache
Lastly, do a full factory reset to wipe all information (delete Google account first).
If it still persists it's a hardware issue and there is nothing you can do but send it in for repair.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Did hard reboot, and factory restore. Problem still there. Contacted my mobile operator. They are sending phone for repair (phone still under warranty). Hopefully that's the end of the saga. Mind you, it seems very easy to replace the charging port. There is an access panel at the bottom of the phone - 3 screws, and out pops the charging port. Anyone any experience replacing the port?
So my Note 10+ screen broke so that I can only see the top 15% and only touch the bottom 60%. I booted into TWRP to backup everything, and now I'm in a situation where I can't turn the thing off. I am unable to press the shutdown button, only the download mode and recovery mode buttons. I am also unable to press the ADB side load button to send a shutdown command. It will be quite some time before I am able to fix the screen, so I don't want the phone battery to be sitting dead and degrading for a month or more. I already tried draining the battery and then plugging it in to charge, but the phone automatically booted into TWRP.... hardware key combos only reboot, they won't shut down...
Does anybody have an idea how to power off my device? Or to reboot into system or gain ADB access without being able to use the touchscreen? Thanks for the help
Humm, after reading the "how do we make XDA a better place thread", and the "this place is just not as good as it use to be" thread, I thought I would try to help. But I suppose that if you were on the forum since 2010 you have probably already thought of this. Also, I don't have a "Note 10+", so this is just guessing based on general Android behavior.
My screen is also unresponsive and I was able to reboot/power off by just by holding down the power button for half-a-minute. Sometimes I would have to "pull the battery", as soon as the phone started to reboot. I've done it a few times and haven't bricked the phone yet. So it is not something you do not want to do all the time. But then again this response will probably not be helpful because your phone does not have a removable battery. (whether or not a battery is pull-able is not something generally listed in the phone specks unless you do lots of digging).
TheLexx said:
Humm, after reading the "how do we make XDA a better place thread", and the "this place is just not as good as it use to be" thread, I thought I would try to help. But I suppose that if you were on the forum since 2010 you have probably already thought of this. Also, I don't have a "Note 10+", so this is just guessing based on general Android behavior.
My screen is also unresponsive and I was able to reboot/power off by just by holding down the power button for half-a-minute. Sometimes I would have to "pull the battery", as soon as the phone started to reboot. I've done it a few times and haven't bricked the phone yet. So it is not something you do not want to do all the time. But then again this response will probably not be helpful because your phone does not have a removable battery. (whether or not a battery is pull-able is not something generally listed in the phone specks unless you do lots of digging).
Click to expand...
Click to collapse
Yeah unfortunately battery is sealed inside and holding the power button yields no result
@TheLexx
Take phone to authorized service center and let them fix it.