Related
resolved. Close thread
Shaquiel Harris said:
Thanks to tnpapadakos for the info. to fix the charging phone with phone off auto boot to recovery issue all we have to do is use the 2.5.1.4 recovery. then you could always flash back to the latest clockwork recovery when you dont need this one anymore but can go back to the other one when you wanna charge with the phone off.
You could either flash it or put it in your sdcard in clockworkMOD/download/mirror.kanged.net/recoveries for easier access to flash from Rom manager. Make sure its named recovery-clockwork-2.5.1.4-vision once its there when you go to ROM managerr and go to all clockwork recoveries, you can flash that recovery without getting an Error! or rename it to recovery-clockwork-2.5.1.3-vision and flash it through that option.
Now does anyone still have that recovery? We can't get it from the ROM manager because you will get an ERROR. if anyone has it, post it here and ill add it here for everyone to get.
Click to expand...
Click to collapse
GO READ http://forum.xda-developers.com/showthread.php?t=834731
I have already posted a fix for both old and new recoveries.
damien667 said:
GO READ http://forum.xda-developers.com/showthread.php?t=834731
I have already posted a fix for both old and new recoveries.
Click to expand...
Click to collapse
I looked in the first page.. there is no such fix about fixing the phone booting into clockwork recovery when you turn off the phone. I'd lovea link to the page in that thread were you posted the fix.
edit: OP here is the recovery you were looking for 2.5.1.3 correct?
http://www.megaupload.com/?d=UE04MRCR
CaliBoyPhillip said:
I looked in the first page.. there is no such fix about fixing the phone booting into clockwork recovery when you turn off the phone. I'd lovea link to the page in that thread were you posted the fix.
Click to expand...
Click to collapse
Im gonna try to be nice...
Open your eyes and click the button that says "Search this thread" when you are looking through a particular thread.
And yes, this thread is an absolute waste of space as this fix has been around for quite some time now....
damien667 said:
GO READ http://forum.xda-developers.com/showthread.php?t=834731
I have already posted a fix for both old and new recoveries.
Click to expand...
Click to collapse
You led to me links on the first page of an ancient thread that have no use because they dont work. and the first link only leads you to download the latest recovery. But here's the best part, your link you had in that thread doesn't work anymore. How cool are you?
G1ForFun said:
Im gonna try to be nice...
Open your eyes and click the button that says "Search this thread" when you are looking through a particular thread.
And yes, this thread is an absolute waste of space as this fix has been around for quite some time now....
Click to expand...
Click to collapse
That's Great its been around for a long time. Some people still don't know about the fix so while you came all the way to this thread, to give absolutely NO help besides make yourself look like an Ass, is beyond me. Don't worry though, your as cool as your buddy.
CaliBoyPhillip said:
I looked in the first page.. there is no such fix about fixing the phone booting into clockwork recovery when you turn off the phone. I'd lovea link to the page in that thread were you posted the fix.
edit: OP here is the recovery you were looking for 2.5.1.3 correct?
http://www.megaupload.com/?d=UE04MRCR
Click to expand...
Click to collapse
No bro, i was looking for the 2.5.1.4 recovery.
Shaquiel Harris said:
You led to me links on the first page of an ancient thread that have no use because they dont work. and the first link only leads you to download the latest recovery. But here's the best part, your link you had in that thread doesn't work anymore. How cool are you?
That's Great its been around for a long time. Some people still don't know about the fix so while you came all the way to this thread, to give absolutely NO help besides make yourself look like an Ass, is beyond me. Don't worry though, your as cool as your buddy.
Click to expand...
Click to collapse
While you would rather be right. We would rather be happy.
Also... what good does it do you to give you what you want? It's more helpful if we show you how to get there instead... teach a man to fish, right? So how about you stop expecting (and demanding), and instead learn a little... it won't kill you to read through a thread (I'm still here, aren't I?)... instant gratification just shows how arrogant you are.
As for the broken link? There are numerous posts about a mirror being made by someone... how about you click "search" one more time?
Sent from my HTC Vision using XDA App
for some people who replay this thread,it's that hard to give the right answer?
it is just kill you for help a little more?
Sorry, search is temporarily unavailable. Please try again in 20-30 minutes.
for some one do not use english a lot ,and do not know the answer,it's just very hard to get that answer,but you guys just rather wast of you time to say bad to each other,not give the right answer,it seems to me,just like the mucsle Bully!
Shaquiel Harris said:
You led to me links on the first page of an ancient thread that have no use because they dont work. and the first link only leads you to download the latest recovery. But here's the best part, your link you had in that thread doesn't work anymore. How cool are you?
That's Great its been around for a long time. Some people still don't know about the fix so while you came all the way to this thread, to give absolutely NO help besides make yourself look like an Ass, is beyond me. Don't worry though, your as cool as your buddy.
Click to expand...
Click to collapse
avxjl said:
for some people who replay this thread,it's that hard to give the right answer?
it is just kill you for help a little more?
Sorry, search is temporarily unavailable. Please try again in 20-30 minutes.
for some one do not use english a lot ,and do not know the answer,it's just very hard to get that answer,but you guys just rather wast of you time to say bad to each other,not give the right answer,it seems to me,just like the mucsle Bully!
Click to expand...
Click to collapse
Here guys... wasn't too difficult for me to find, even with the search being down...
damien667 said:
Its not a kernel patch, its a init.rc service than runs before recovery that reads the kernel command line for the offmode_charging variable... if it sees it it stops recovery from starting (even though you are in fact already booted into the recovery system) and starts a keypressing service (to reboot phone into regular boot mode when power button is pressed) and also the battery charging service that is supposed to display the battery icon charging animation (which doesn't work in cwm)... those services (binaries) were grabbed from the OTA recovery... if you read my previous posts, you would know.
POST 326
and
POST 354
Click to expand...
Click to collapse
and here is a working mirror for the "patched" file: http://androidcustomroms.com/recovery-clockwork-3.0.0.5-poweroff_charging.img
thread can be closed now...
benjamminzIS said:
Here guys... wasn't too difficult for me to find, even with the search being down...
and here is a working mirror for the "patched" file: http://androidcustomroms.com/recovery-clockwork-3.0.0.5-poweroff_charging.img
thread can be closed now...
Click to expand...
Click to collapse
Fantastic. Thank you
I accidentally formatted everything from my phone. I was in CWM and I formatted everything, and now I basically do not have anything on my phone at all. After the LG boot up logo, the phone goes blank. I'm able to go into download mode. I tried following this method http://forum.xda-developers.com/showthread.php?t=2420219, I keep getting failed previousload() a few seconds after clicking the top left yellow icon in LG flash tool. Anyone have any idea whats going on or how to fix this? LG E988.
aisforadam said:
I accidentally formatted everything from my phone. I was in CWM and I formatted everything, and now I basically do not have anything on my phone at all. After the LG boot up logo, the phone goes blank. I'm able to go into download mode. I tried following this method http://forum.xda-developers.com/showthread.php?t=2420219, I keep getting failed previousload() a few seconds after clicking the top left yellow icon in LG flash tool. Anyone have any idea whats going on or how to fix this? LG E988.
Click to expand...
Click to collapse
Copy a compatible ROM to your memory card and start CWM to flash the ROM you have just copied.
Hope this helps.
Addicted2xda said:
Copy a compatible ROM to your memory card and start CWM to flash the ROM you have just copied.
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply, however i finally managed to solve the issue. I sideloaded a custom rom using adb. Phew!
aisforadam said:
Thanks for your reply, however i finally managed to solve the issue. I sideloaded a custom rom using adb. Phew!
Click to expand...
Click to collapse
What section did you find your fix in? My friend did the same thing to hers and I can't find the command line.
Sent from my VS980 4G using Tapatalk
cj2566 said:
What section did you find your fix in? My friend did the same thing to hers and I can't find the command line.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Hi I didn't find it in one particular section, I had to search everywhere, i spent a good 8 hours straight searching as I really needed my phone to work. I will try my best to start you off though.
I started here.
http://forum.xda-developers.com/showthread.php?t=2559200
Watched this.
http://www.youtube.com/watch?v=dWXHD7PlaQc
That's basically all you have to do. I did, however, run into plenty of issues along the way which is what took up all if not most of the 8 hours. What I did was google each and every issues that occured and I always found answers to it (with some added trial and error).
Here are some of the issues I faced while sideloading that you or your friend may come across.
''device not found''
''cannot read file''
Both of which can easily be solved by googling. I hope I guided you in the right path, feel free to pm me if you need anymore help.
aisforadam said:
Hi I didn't find it in one particular section, I had to search everywhere, i spent a good 8 hours straight searching as I really needed my phone to work. I will try my best to start you off though.
I started here.
http://forum.xda-developers.com/showthread.php?t=2559200
Watched this.
http://www.youtube.com/watch?v=dWXHD7PlaQc
That's basically all you have to do. I did, however, run into plenty of issues along the way which is what took up all if not most of the 8 hours. What I did was google each and every issues that occured and I always found answers to it (with some added trial and error).
Here are some of the issues I faced while sideloading that you or your friend may come across.
''device not found''
''cannot read file''
Both of which can easily be solved by googling. I hope I guided you in the right path, feel free to pm me if you need anymore help.
Click to expand...
Click to collapse
THANK YOU! This helps more than you know.
Sent from my VS980 4G using Tapatalk
I have been having this issue for weeks now. Any time I try to turn on my bluetooth, it flashes on for just a split second, then turns right back off. I was able to pull some info from logcat, I don't know if it would be of any help but hopefully you all can help me figure this out. Thanks in advance!
Logcat seen here (quite long)
JustAk said:
I have been having this issue for weeks now. Any time I try to turn on my bluetooth, it flashes on for just a split second, then turns right back off. I was able to pull some info from logcat, I don't know if it would be of any help but hopefully you all can help me figure this out. Thanks in advance!
Logcat seen here (quite long)
Click to expand...
Click to collapse
What ROM and what kernel did you flashed?
FcoEnrique said:
What ROM and what kernel did you flashed?
Click to expand...
Click to collapse
That's the weird part, I'm only running stock right now. I was going to flash cyanogen later but this bluetooth thing started up and I'm not sire what caused it
JustAk said:
That's the weird part, I'm only running stock right now. I was going to flash cyanogen later but this bluetooth thing started up and I'm not sire what caused it
Click to expand...
Click to collapse
Rooted and unlocked bootloader? What method?
Freegee likes to mess with the bluetooth. There should be a bluetooth fix flashable zip in the freegee thread for the ls970. I don't know if you can flash it on stock so make sure you read thoroughly.
Rooted yes, unlocked bootloader no. I rooted with fiddy619's batch file.
I'll take a look at their fix. As far as bluetooth suddenly breaking, is there anything that typically causes this or that I can look into? I've checked over all my settings, and none of my apps seem to be interfering (as far as I can tell), and I can't make sense of the logcat, so Idk what else to look at.
JustAk said:
Rooted yes, unlocked bootloader no. I rooted with fiddy619's batch file.
I'll take a look at their fix. As far as bluetooth suddenly breaking, is there anything that typically causes this or that I can look into? I've checked over all my settings, and none of my apps seem to be interfering (as far as I can tell), and I can't make sense of the logcat, so Idk what else to look at.
Click to expand...
Click to collapse
Freegee is to unlock the bootloader, if you're not unlocked and did not use freegee then you have no need for the fix. Do you have a recovery installed? What one?
you should definitely read this thread and maybe complete the process. There are tons of roms out there an as long as you follow the steps in this thread, you shouldn't mess anything up.
http://forum.xda-developers.com/showthread.php?t=2050582
dopy25 said:
Freegee is to unlock the bootloader, if you're not unlocked and did not use freegee then you have no need for the fix. Do you have a recovery installed? What one?
you should definitely read this thread and maybe complete the process. There are tons of roms out there an as long as you follow the steps in this thread, you shouldn't mess anything up.
http://forum.xda-developers.com/showthread.php?t=2050582
Click to expand...
Click to collapse
Regarding Freegee, I saw that after responding and then felt quote stupid. But I'll probably be doing that soon now so I can get a properly working phone.
Thanks for the suggestion, I'll probably be doing this tomorrow and will update the thread when I do.
For those still subscribed to this, I solved the problem. I am using SmartApp Locker, and in the Settings menu under System Lock I had Bluetooth checked. This should only have been locked when the app locking service was turned on, but it was interfering with all usage of bluetooth with the app lock service on or off.
Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.
Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justin
Cry_Cry said:
Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justinhttps://www.youtube.com/watch?v=
Click to expand...
Click to collapse
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
yldlj said:
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
Click to expand...
Click to collapse
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Cry_Cry said:
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Click to expand...
Click to collapse
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
yldlj said:
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
Click to expand...
Click to collapse
So basically there is no fix for my problem?
Cry_Cry said:
So basically there is no fix for my problem?
Click to expand...
Click to collapse
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Are you SOFF? What's your CID?
yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Cry_Cry said:
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Click to expand...
Click to collapse
Nope flash RUU and that's it.
I get a lot of random crashes and power offs since I've upgraded to Oreo. It's really been driving me nuts.
Can't wait for the OP6 or U12+ to come out - I really need a new phone.