My OnePlus 3T just came today, and I wanted to encrypt it as early as I could (right after I installed SultanXDA's CM13). Since I hadn't had it long enough to charge yet, it didn't want to let me encrypt. Here's how you can bypass it:
Go to Settings -> About phone, and tap Build number until it says "You are now a developer!"
Go to Settings->Developer options, and enable USB debugging.
Plug your phone into your computer, and run "adb shell".
Accept the ADB message on your phone.
Type "dumpsys batterymanager set level 100" and hit Enter. This will make your phone believe its battery is full.
Go to the encryption screen, and it will let you encrypt instead of making you charge your battery.
Once the phone reboots after encrypting, its battery level will be right again. (If you're curious, "dumpsys batterymanager reset" puts it back to normal without needing to reboot.) Note, though, that there's a reason for the battery check, since if your phone powers off during encryption, you'll lose all of your data. I only recommend doing what I did if you just wiped your phone anyway.
Why would you want to do this?
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
Why would you want to do this?
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I wanted to encrypt my phone as soon as I got it, but it didn't ship charged and I didn't want to wait for it to charge.
josephcsible said:
I wanted to encrypt my phone as soon as I got it, but it didn't ship charged and I didn't want to wait for it to charge.
Click to expand...
Click to collapse
It comes encrypted.
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
It comes encrypted.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I installed CM, though, which doesn't. (And I erased userdata, so the stock encryption didn't stick.)
In that case, why risk running short of power and ending up with non-functional partition, that will then require you to charge, wipe whole partition and re-do the encryption process?
Someguyfromhell said:
In that case, why risk running short of power and ending up with non-functional partition, that will then require you to charge, wipe whole partition and re-do the encryption process?
Click to expand...
Click to collapse
It was plugged in at the time, so I (correctly) guessed that I wouldn't have to worry about that.
josephcsible said:
It was plugged in at the time, so I (correctly) guessed that I wouldn't have to worry about that.
Click to expand...
Click to collapse
Impatient a bit? It literally takes 30 minutes to get to like 75%
J4DedPrez said:
Impatient a bit?
Click to expand...
Click to collapse
Yes
josephcsible said:
Yes
Click to expand...
Click to collapse
Lol don't blame you ?
Related
i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?
hard reset may work
Sent from my Incredible using XDA App
i tried hard resetting it. this did not solve the problem.
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.
Are you root?
When and how did this start happening?
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.
JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App
JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App
Try the RUU that was posted.
jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen
theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App
Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.
I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure
So, I've just upgraded to the epic (coming from the hero) and I love it...I'm not a huge fan of the root method/recovery but I guess I'll have to deal with that. I am confused by why each rom says I need to wipe 3x before flashing...
That is something I never encountered in all of my Hero days.
can anyone shed some light on that?
Its more to make sure you do it. I personally always wipe 2x. A habit I suppose.
Sent from my SPH-D700 using Tapatalk
I "think" its cause clockworkmod can't do it right the first time >.> lol
As the saying goes..3rd time's a charm
funny after hearing people say it doesn't do it right i watched in adb while I did a factory reset/data wipe and my data partition was clean when it was done.
gTen said:
I "think" its cause clockworkmod can't do it right the first time >.> lol
As the saying goes..3rd time's a charm
Click to expand...
Click to collapse
That wouldn't surprise me. I don't really trust Rom Manager/Clockwork. After doing everything manually for a year, I prefer to do it myself...
It just seems strange to me that devs have to remind people THREE TIMES to wipe their data. Are we gonna see "backup x3" next? lol
I believe it comes from the old wiping hard drives mentality of its not wiped until 3 passes and not really wiped till 7 on flash memory I've never seen much of a point.
I only wipe once. I have not run into problems. Deleting data is deleting data the software doesn't miss things to delete. I think it is a way to sidestep a problem. Like did you reboot your computer? Yeah! Three times? No...... try that dummy!
Sent from my SPH-D700 using XDA App
onilink67 said:
I believe it comes from the old wiping hard drives mentality of its not wiped until 3 passes and not really wiped till 7 on flash memory I've never seen much of a point.
Click to expand...
Click to collapse
Data is never wiped no matter how many passes you do, it jsut makes it harder/more expensive to retrieve..that said when doing 3 passes you are not just formating using 1 method..usually you format with different ones on each pass.
I only wipe once. I have not run into problems. Deleting data is deleting data the software doesn't miss things to delete. I think it is a way to sidestep a problem. Like did you reboot your computer? Yeah! Three times? No...... try that dummy!
Click to expand...
Click to collapse
There was an issue with clockwork not wiping correctly before(and before I mean before the Epic)...it may have been fixed...can never be sure :/
I wipe as many times as it takes to reduce skidmarks.
Sent from my SPH-D700 using Tapatalk
The same type of voodoo IT is going on regarding GPS.
Sent from my SPH-D700 using Tapatalk
So my sprint S4 arrived today and when i first booted it up it was in Factory mode... I called Tech support and they guided me to hard resetting it by going into settings and doing a factory reset, but that didnt work, also by holding volume up, home button, and power button at the same time during boot up, but that also did nothing. My only options apparently are to wait for a sprint store to get spare ones to replace mine with or pay up front for another one, and get one shipped to me and ship this one back... I'd much rather attempt to fix it myself, If i can.
Anyone know if I can root it or do a recovery with a stock rom or anything else? Ive only ever rooted one android phone and that was years ago, so im pretty rusty but I think i can handle it, im a comp science major and took an intro to unix class so i got this! haha just looking to get guided the right way, in the meantime i will continue reading rooting threads. PS: IDK if this means anything but while messing around with the buttons during boot up I entered Odin mode or something asking if i was sure i wanted to download a custom OS then it hung on Downloading... Also I navigated through the settings menu and there was no sign of a developement or USB debugging option :[ Below are screens of what it looks like.
xxdekuxx said:
So my sprint S4 arrived today and when i first booted it up it was in Factory mode... I called Tech support and they guided me to hard resetting it by going into settings and doing a factory reset, but that didnt work, also by holding volume up, home button, and power button at the same time during boot up, but that also did nothing. My only options apparently are to wait for a sprint store to get spare ones to replace mine with or pay up front for another one, and get one shipped to me and ship this one back... I'd much rather attempt to fix it myself, If i can.
Anyone know if I can root it or do a recovery with a stock rom or anything else? Ive only ever rooted one android phone and that was years ago, so im pretty rusty but I think i can handle it, im a comp science major and took an intro to unix class so i got this! haha just looking to get guided the right way, in the meantime i will continue reading rooting threads. PS: IDK if this means anything but while messing around with the buttons during boot up I entered Odin mode or something asking if i was sure i wanted to download a custom OS then it hung on Downloading... Also I navigated through the settings menu and there was no sign of a developement or USB debugging option :[ Below are screens of what it looks like.
Click to expand...
Click to collapse
AOSP???
Dude ship it back man. More edits to it will break it i think
Also it is in factory mode right ? @Chainfire lets pull Exynos Factory Sources
mithun46 said:
AOSP???
Dude ship it back man. More edits to it will break it i think
Also it is in factory mode right ? @Chainfire lets pull Exynos Factory Sources
Click to expand...
Click to collapse
Yeah its in factory mode. I guess im going to have to... :[ damnit. Gonna take forever. Oh well.. If anyone else has ideas let me know... ill be waiting a while for return packaging to arrive.
Tap on build number 10 times to get development options. Then pull me the system using adb
Sent from my GT-I9500 using Tapatalk 2
papi92 said:
Tap on build number 10 times to get development options. Then pull me the system using adb
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
Well that worked to get me developer access and enable usb debugging but can you be a bit more specific on how to pull up the adb? all i remember is having to use command line prompts to pull it up
xxdekuxx said:
Well that worked to get me developer access and enable usb debugging but can you be a bit more specific on how to pull up the adb? all i remember is having to use command line prompts to pull it up
Click to expand...
Click to collapse
adb pull /system
Why does it have AOSP theme?
mithun46 said:
adb pull /system
Click to expand...
Click to collapse
Thanks, I pulled the system folder onto my hard drive... is it safe to give this out? Its a lot of files obviously and about 250 MB :/
xxdekuxx said:
Thanks, I pulled the system folder onto my hard drive... is it safe to give this out? Its a lot of files obviously and about 250 MB :/
Click to expand...
Click to collapse
its safe. dont give the /data out
it should be more than 250 mb man
mithun46 said:
its safe. dont give the /data out
it should be more than 250 mb man
Click to expand...
Click to collapse
There's hardly anything on the Factory ROM, it isn't very surprising.
Sent from my HTC One using Tapatalk 2
humzaahmed155 said:
There's hardly anything on the Factory ROM, it isn't very surprising.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think its AOSP
Well i uploaded my system folder onto dropbox but apparently i cant post outside links until i have 10 or more posts :/
Anyone else have any ideas on what I can do?
Post a few times?
This phone of yours is what the devs need, so they can reverse engineer it and put AOSP, CM, AOKP, etc on it.
This thread should go to some where people/devs would visit more often, so it gets more exposure and have more productive work done faster.
Here's an idea: those, who bought the qualcomm version and hoping to run CM on it, should chip in to buy this phone, so this guy can buy another phone, then send this phone to some dev.
ste1164 said:
Post a few times?
Click to expand...
Click to collapse
I guess.. easier said than done.. i dont have much to say around here except for this problem hahaha:/
jk0l said:
This phone of yours is what the devs need, so they can reverse engineer it and put AOSP, CM, AOKP, etc on it.
This thread should go to some where people/devs would visit more often, so it gets more exposure and have more productive work done faster.
Here's an idea: those, who bought the qualcomm version and hoping to run CM on it, should chip in to buy this phone, so this guy can buy another phone, then send this phone to some dev.
Click to expand...
Click to collapse
Id potentially be willing to let go of it... if people are interested in it... I have to wait til tomorrow for preorders to stop anyways and to start the order process for a replacement.. Shouldve went with the htc one :/
xxdekuxx said:
Id potentially be willing to let go of it... if people are interested in it... I have to wait til tomorrow for preorders to stop anyways and to start the order process for a replacement.. Shouldve went with the htc one :/
Click to expand...
Click to collapse
Enjoying the HTC One so far I agree with the others they can all chip in and pay for the device so it can be shipped to a dev who can pull the AOSP source off it and build a CM ROM / Standard AOSP ROM.
Sent from my HTC One using Tapatalk 2
It's a 9500 or a 9505?
Thanks.
Chuck Bartowski said:
It's a 9500 or a 9505?
Thanks.
Click to expand...
Click to collapse
He said its from sprint so I'm going to say its a 9505
Sent from my A500 using Tapatalk HD
Chuck Bartowski said:
It's a 9500 or a 9505?
Thanks.
Click to expand...
Click to collapse
Tell me how to check which one it is, and I shall
After what appears to be a successful flash of the CM 7.2 build from 02282013 all my phone will do is go to the at&t logo and sit there. Never completes the boot. I wiped data, factory reset and cache to no avail. I was on Froyo before flashing. I used CWM to flash. Never completes the bootup. I have to pull the battery to get it to shut down. I tried flashing twice with no luck.
I then tried to restore my CWM backup but it boots back into the recovery screen with the following errors:
Can't open /cache/recovery/log
Can't open /cache/recovery/log/last_log
Any ideas anybody?
pastorbob62 said:
After what appears to be a successful flash of the CM 7.2 build from 02282013 all my phone will do is go to the at&t logo and sit there. Never completes the boot. I wiped data, factory reset and cache to no avail. I was on Froyo before flashing. I used CWM to flash. Never completes the bootup. I have to pull the battery to get it to shut down. I tried flashing twice with no luck.
I then tried to restore my CWM backup but it boots back into the recovery screen with the following errors:
Can't open /cache/recovery/log
Can't open /cache/recovery/log/last_log
Any ideas anybody?
Click to expand...
Click to collapse
Are you on 2.2?
Sent from my SGH-T769 using Tapatalk 4 Beta
Somcom3X said:
Are you on 2.2?
Sent from my SGH-T769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I was on 2.2. I'm on nothing now. My last attempt totally bricked my phone and it won't even turn on.
pastorbob62 said:
Yes, I was on 2.2. I'm on nothing now. My last attempt totally bricked my phone and it won't even turn on.
Click to expand...
Click to collapse
1. Remove battery, plug in usb power cable. (means no battery in the phone)
2. Press power button, volume up, and volume down button. All three at the same time, and hold.
Did it turn on?
badiyee said:
1. Remove battery, plug in usb power cable. (means no battery in the phone)
2. Press power button, volume up, and volume down button. All three at the same time, and hold.
Did it turn on?
Click to expand...
Click to collapse
No. It does the same as when the battery is in. It vibrates as if it is going to turn on but the screen stays black and nothing else happens.
pastorbob62 said:
No. It does the same as when the battery is in. It vibrates as if it is going to turn on but the screen stays black and nothing else happens.
Click to expand...
Click to collapse
if what i read from other forums is correct, it sounds like you need a motherboard replacement.
badiyee said:
if what i read from other forums is correct, it sounds like you need a motherboard replacement.
Click to expand...
Click to collapse
That is what I figured to be the case as well. Unfortunately I am not able to locate one. Not sure if I would do that anyhow since it only cost me $140.00.
pastorbob62 said:
That is what I figured to be the case as well. Unfortunately I am not able to locate one. Not sure if I would do that anyhow since it only cost me $140.00.
Click to expand...
Click to collapse
Look on ebay. Buy one with a broken screen and replace it yourself.
Sent from my SAMSUNG-SGH-T769 using Tapatalk 4 Beta
Good suggestion
Somcom3X said:
Look on ebay. Buy one with a broken screen and replace it yourself.
Sent from my SAMSUNG-SGH-T769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've already tried that. Several times. Lots of new screens but no used phones that I can pick up for parts. I am leaning toward buying a new phone from my provider. Different model, Samsung Galaxy Exhilarate, better phone all around for only $150.00.
I'm done tweaking and modding my phones. It's okay for PC's and tablets but I think I'll stick to stock phones from now on. Lesson learned the hard way.
pastorbob62 said:
I've already tried that. Several times. Lots of new screens but no used phones that I can pick up for parts. I am leaning toward buying a new phone from my provider. Different model, Samsung Galaxy Exhilarate, better phone all around for only $150.00.
I'm done tweaking and modding my phones. It's okay for PC's and tablets but I think I'll stick to stock phones from now on. Lesson learned the hard way.
Click to expand...
Click to collapse
The exhilarate is a beautiful phone with good dev support. My blaze is compatible with the exhilarate.
Sent from my SGH-T769 using Tapatalk 4 Beta
Just bought a used Nexus 6p and started through the setup and the phone died at 42%. It came right back on as soon as I plugged it up but this has me worried that this going to be an on going problem. Is anyone else having this problem and is it a sign of something worse?? Thanks in advance
Same problem here,I fixed it by using PureNexus ROM
Sent from my Nexus 6P using Tapatalk
Minh Dao said:
Same problem here,I fixed it by using PureNexus ROM
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks i will root mine and give it a try this weekend
jmcandrews83 said:
Thanks i will root mine and give it a try this weekend
Click to expand...
Click to collapse
Just need to unlock bootloader then install TWRP
To be honest, I bet this is why they sold it, was it mentioned that the device has an early shut down issue? If flashing a custom rom doesn't fix it, you may need to replace the battery.
Triscuit said:
To be honest, I bet this is why they sold it, was it mentioned that the device has an early shut down issue? If flashing a custom rom doesn't fix it, you may need to replace the battery.
Click to expand...
Click to collapse
Yeah i bet it is also. And no he didn't say anything about it when selling. Im hoping root will fix it i gave it a full charge and got it down to about 20 percent today before it shut off
jmcandrews83 said:
Just bought a used Nexus 6p and started through the setup and the phone died at 42%. It came right back on as soon as I plugged it up but this has me worried that this going to be an on going problem. Is anyone else having this problem and is it a sign of something worse?? Thanks in advance
Click to expand...
Click to collapse
Perhaps try deleting the batter stats (settings -> battery -> trash can icon) first and diagnose it with a battery app such as Ampere first? This can be accomplished without root.
AncientDeveloper said:
Perhaps try deleting the batter stats (settings -> battery -> trash can icon) first and diagnose it with a battery app such as Ampere first? This can be accomplished without root.
Click to expand...
Click to collapse
Thanks ill give it a try during my break
Triscuit said:
To be honest, I bet this is why they sold it, was it mentioned that the device has an early shut down issue? If flashing a custom rom doesn't fix it, you may need to replace the battery.
Click to expand...
Click to collapse
I have faced this problem with stock rom and I flashed PureNexus ROM then no more problem
Sent from my Nexus 6P using Tapatalk