yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] gigsaw:
OK it's a great news thank's everybody :)

So double tap to sleep doesn't work? And how to solve this problem? You know, the back button is not so comfortable to turn on and off the phone :)
[G2 Q&A, Help & Troubleshooting] magistrateee:
Is the KnockON/OFF a software or hardware feature?

If its a software issue which app uses it in the system?
[G2 Q&A, Help & Troubleshooting] drc13:
No knockoff doesn't work in AOSP until you setup a couple more things such as a double tap gesture in nova to activate a screen off app.
[G2 Q&A, Help & Troubleshooting] gigsaw:
It's software, a kernel related feature :D even before g2, many developers created this feature for many devices (see PGM for nexus, sweep2wake or slide2wake for almost all HTC phones..and even xperia z has it...
[G2 Q&A, Help & Troubleshooting] Xenovias:
I think G2 knock on (only on) is 50% hardware and 50% kernel

Because, when i try knock on while i cover sensor on top with my hand, knock on doesn't work.

No problem with knock off even covered sensor with my hand.
[G2 Q&A, Help & Troubleshooting] magistrateee:
Does that mean that the ROMs and kernels have to integrate this whether on this device or another and there is no simple port for those with just root? In other words is there an app that can control this?
[Galaxy S 4 Q&A, Help & Troubleshooting] PinoPano:
I'd really appreciate it if someone could help with the problems I'm having.

Here's the rundown. Rooted my phone and installed a google edition rom almost immediately after buying. Unfortunately, though, as time went by I'd get frequent reboots with any GE rom I tried so I decided to go back to a custom TW rom. But I'm now getting another problem which is really odd. Basically, on a fresh factory reset 100% charge the phone starts up fine and works impeccably for the whole day until the battery goes down to 20-30%. At this point it either shuts off or gets stuck on the black screen with the white Samsung logo. It will reboot but as soon as it finishes loading up it either reboots again by itself or gets stuck on the Samsung screen. I've even tried the stock 4.3 rom and it does the same thing.

Any ideas as to what it might be? Any solutions?

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] Obagleyfreer:
You have a faulty battery. Check serial number,if it starts with BD this is a recognised faulty batch.

If you plug your phone into charge it should boot up fine yes?

Buy a new battery and call should be good mate :)
[Galaxy S 4 Q&A, Help & Troubleshooting] PinoPano:
Thanks, but just checked the s/n and it starts with AA.

The behavior's the same even when the phone's charging
[Galaxy S 4 Q&A, Help & Troubleshooting] galaxysduane:
I believe its the battery as mine did the same thing until i replaced it with a new one.
[Galaxy S 4 Q&A, Help & Troubleshooting] PinoPano:
More odd behavior

...Taking out the battery and putting it back in stops the bootloops and allows it to start up normally again till the next charge. Any ideas because I'm not sure it's the battery? The battery lasted nearly 2 days on a full charge yesterday and went down normally this time to 0% before turning off
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] kamransar:
Hi there

I have battery issue on my tablet, i takes sometimes 1 day to be 100% of charge!!! just from upgrade to 4.1.2.

Please let me know if you have the same problem or you know how to solve it.

Android Version 4.1.2

Baseband version: N8000XXCLL1

Build Number: JZO54K.N8000XXCMC1

:angel:
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
Change cables clean USB port change charger .

Change battery requires a service centre .
[T-Mobile Samsung Galaxy Note 3] atinder:
Is there any way to restore IMEI number. I have efs backup when it worked but after restore IMEI still stays unknown. I tried Qualcomm NV tools from EFS Professional, it connects to phone and shows Error! SPC not found. when I write imei it gives me error parsing nvitem. Any help would be greatly appreciated.
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Hi,

I followed your instructions up to point 13 - which is where the first problems in your instructions start. The page you are referring to doesn't exist anymore. Unfortunately you also didn't mention what exactly needs to be downloaded, which means people don't know what they have to look for. All I found was "trickdroid". Is that the one you were referring to?

14 - my bootloader is still unlocked, however I followed these instrucktions

16 - I am unable to boot any other image. During the steps you posted - which I followed - at some stage my system went S-ON. Revone is unable to map memory (and noone actually is able to answer me what that means even though there are many people that seem to have that issue) and rumrunner also is not capable anymore of bypassing the S-ON.

I don't know why I can't boot a recovery image, I assume it is because of the S-ON? There is for a millisecond a bootscreen with a red error message text, however I can't read it, because it's too fast.

So I am basically two steps away from getting back to stock and I don't know what to do so I can boot into the recovery image.

HTC One / O2 / hboot 1.44

Could anyone help me with this? I really don't know what to do and I have no experience whatsoever. And I don't wanna break my phone more than it is already ;)
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
Don't know why the links don't post correctly - 13: http://xdaforums.com/showthread.php?t=2200628
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
I also had the failed map memory error. Only way I could fix it was by repeating the command until it worked. Only happened once bit I'm aware of this being an issue

As for booting into the recovery image - is the image in your fastboot folder? And are you typing fastboot boot CWMTG.img (or whatever name.img)

Wt is the status of the bootloader?
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
Also the red error message is because you are booting into a custom recovery and this is normal. It would also say entering recovery at the top of the screen. Are you using the CWMTG.img from hasoon's toolkit in your fastboot/adb folder?
[One (M7) Q&A, Help & Troubleshooting] dispereo:
I've been repeating it over and over again (rough guess, about 15x) and it doesn't work. Still the map memory error.

I put the recovery-clockwork-6.0.4.3-m7ul.img (and I tried 2 others on their website) in the c:\android (where my adb/fastboot exe are in)

My bootloader says "unlocked" (however I manually unlocked again, just in case) - no change.

I entered fastboot boot recovery-clockwork-6.0.4.3-m7ul.img and then it just reboots (assuming it crashes and has the failsafe reboot)

---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------

No I downloaded it manually. Because you say "fastboot boot" it won't flash it. But Hasoon's tool says "flash recovery" which sounds to me like overwriting (flashing) the current original, that would be thing i don't want. So i am a bit confused there.
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
What I did was pull the recovery image from hasoon's toolkit, not download the recovery image from the website. If you download the toolkit and go to the directory where you downloaded it there is a folder called recoveries where I copied the image to my adb folder. I did NOT use the toolkit as this involved flashing it so please try it that way instead of downloading it from the website

As for manually unlocking again - how to you do this without revone working? And put of curiosity are you using the toolkit to push/flash revone? If so I would reboot the phone between every step and try it again

Try that and see
[One (M7) Q&A, Help & Troubleshooting] dispereo:
I got to 17 now (had to adjust minor things to get that work, thanks for your help!) and the problem is, my phone obviously doesn't support revone anymore as it doesn't have the permissions. Can I lock manually (with the HTC Dev command?) and I haven't had a ****TAMPERED**** since I installed the RUU.zip, do I still need to do 17. remove the tampered flag ? If so, how to do that with revone not having the permissions?

Almost there... almost there... *nervous*
[One (M7) Q&A, Help & Troubleshooting] dispereo:
So, I updated, I couldn't wait for a reply. ;)

Now I've got "relocked" in the hboot, which is the way HTC Dev intended it (as far as I understand). Is there a way to get rid of that afterwards?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you should set it to LOCKED (not relocked), using either revone or http://xdaforums.com/showthread.php?t=2475914 (or any of the other method available)
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Thanks! Will have a look into that. So my phone updated without an issue now, and I am on Android 4.3 actually which made me wonder... if I ever do have to do a factory reset, what's the phone being reset to? Do you know that by chance?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Factory reset will just wipe everything (rephrase DATA) off your phone, it will not change ROM, firmware or anything like that, so it will remain on 4.3
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Awesome, thanks for that. Phew. So now I am just stuck on a "re-locked" bootloader because rumrunner can't seem to find a way to get S-OFF again, as hboot 1.55 was installed. So i prolly got to wait until someone found a way to do that.

Thanks A LOT (!!!) for your help!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No problem

As for rumrunner it should work on 4.3 (ie base 3.62.xxx.x), if it's currently not, the guys are updating it quite frequently, but

if

I recall correctly, it's best to have unlocked bootloader and ROOT.

Cheers
[One (M7) Q&A, Help & Troubleshooting] dispereo:
I found a major issue here... when you boot it up and are in the setup screen, it says in red:

This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.

Where did that come from? That sucks...
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That usually comes if you have S-Off, I though you said you went back S-On :confused:
[One (M7) Q&A, Help & Troubleshooting] dispereo:
I did! Weird... I am repeating the procedure again.

---------- Post added at 07:32 PM ---------- Previous post was at 07:09 PM ----------

The bootloader is definitely unlocked as I just did it manually again with the HTC Dev unlock_token.bin.

The locking procedure from the website you posted:

C:\Android>adb shell

shell@m7:/ $ su

su

/system/bin/sh: su: not found

127|shell@m7:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1

seek=33796

dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 <

/dev/block/mmcblk0p3: cannot open for write: Permission denied

1|shell@m7:/ $

Rumrunner:

!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!

Please wait....

..........

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (6/120)

Waiting

Test 2: Booting device

Waiting for ADB (28/120)

Device detected.....................

[------------------------------------------------------------]

Rebooting into bootloader (again)

Waiting for fastboot (6/120)

Waiting for ADB (27/120)

ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!

!

Press ENTER to exit

---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------

And someone had the same question here:

http://xdaforums.com/showthread.php?t=2470957

Apparently with 1.55 it's not possible to get S-OFF (even though I didn't go S-ON at any stage, at least not myself...)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I'm 100% sure that before rumrunner was changed to a universal toolkit, there were quite a few packages for base 3.xx (hboot 1.55) including 3.62.401.x and they worked.

But like your output said:

you would need to flash a ROM with ROOT (maybe a Guru Reset) compatible with your firmware for it to work. (obviously you need to be unlocked to flash ROM)

Also, going from S-Off to S-On on hboot 1.55 will result in "tamper detected - rebooting" and showing TAMPERED again, so you'll need to do that before hboot 1.55 (at least I'm well over 50% sure of that by now).

If the universal rumrunner tool really does not work for you at this time, I'm sure they're fixing it and it will be along soon.

EDIT: fastboot oem writesecureflag 3 is what makes you go S-On, and you have to do it, no way it's done by itself
[One (M7) Q&A, Help & Troubleshooting] dispereo:
I might have done that, even though I thought I left that out. However, my bootloader says ***** relocked ***** , that's all. It doesn't say ***** tampered ***** (that definitely disappeared after putting the ruu.zip on, I didn't have to do anything. i was wondering about that because you specifially mention it in your walkthrough but for me it disappeared automatically right at the start of the procedure.)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No way to go S-On without doing it yourself, no big deal, as long as you can unlock again.

In theory, as long as you have stock ROM and stock recovery, the tampered should not show up, even if unlocked (S-On or S-Off), however for some, it did stay, even under those conditions. no real idea why. repeating myself: tampered should go away as soon as you have stock recovery.

Not my guide, it's [MENTION=4638827]stovie_steve[/MENTION] guide. I'm just visiting :cyclops:

So if you want to start over again, you need to get unlocked, flash a ROM compatible with your current firmware, which has root, and use rumrunner to get s-off.

I'm off for tonight see you guys around....
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
Thanks for taking over [MENTION=2605798]nkk71[/MENTION], your help is always appreciated!

As nkk71 said you must have did the command for writesecureflag 3 at some stage to s on

As for rumrunner - I have successfully s offed using the 3.62.xxx.x package as long as you are unlocked bootloader. If this doesn't work you need to install a guru reset and 're do the s off again

When you tried the adb shell command to unlock the bootloader you need to have su installed

If you plan to start all over again I would advise NOT to use the unlock token once you are on hboot 1.44 and instead use revone only for locking/relocking the bootloader. I followed my guide from start to finish and had no issues - i corrected the bad links as well

Retry rumrunner and ensure you have usb debugging on and your firewall / antivirus switched off!

If you are s-off with rumrunner, then use the adb commands to get rid of the tampered and lock the bootloader. Then start again from step one of the guide and you should have no issues. Once back on 4.1.2 then do the command fastboot oem writesecureflag 3 to s on before flashing revone and ensure your CID is back to 02___001

If you run into problems with revone again using hasoo's toolkit then try manually doing it following a revone guide
[One (M7) Q&A, Help & Troubleshooting] dispereo:
LOL, sorry, am so used to Steve replying that I didn't pay attention. :D

Technically, as soon as someone found a way to bypass 1.55, I should be able to lock without a big fuss again, so without having to do everything from scratch, right?
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
Post deleted
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Not good. :(

!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!

Please wait....

..........

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (6/120)

Waiting

[PN0710000-1.55.0000]

Test 2 (ALT): Booting device

Rebooting from fastboot

Waiting for ADB (36/120)

Device detected.....................

[------------------------------------------------------------]

Test 3: Rebooting into bootloader (again)

Waiting for fastboot (6/120)

FATAL: F U C K it

............................................................

....................................................

Had to manually reboot and now the HTC boot-screen shows a red warning message. Which it didn't before. This Build is for dev purposes only (bla bla) however my phone is now locked, which doesn't help much... so it says locked but this red error message literally tells people someone tampered with it. :-/
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
You said you had this warning message before tho after trying it the first time?

Can you post a fastboot getvar all for me please?

EDIT:

You said you had this message before - This is a test device. Tell HTC is automatically enabled so that HTC can collect critical information about the device during testing. It is not possible to turn this feature off on this phone.

Is this the same message?
[One (M7) Q&A, Help & Troubleshooting] dispereo:
No. The error message i know have is in the splash screen. So when you boot up your phone it says HTC quietly brilliant and in red "this is a development device something bla bla.

The error message I had since I followed your guide is when you set it up the first time and it asks if you would like to provide HTC with the statistics of the use of this device. Usually you can tick the box or not (which i usually untick, I don't like people spying on me how I use the phone, NSA and GCHQ do that already...) however since I followed your steps it says in red under this "as this is a test device ALL information will be sent to HTC, this cannot be deactivated" (or something like that).

C:\Android>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.62.206.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: O2___001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4272mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-bb768ae1

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.077s

C:\Android>
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
That text is always there if you are s-off, which I see you already are! I don't know why you are trying to run Rumrunner when you are NOT S-On

For now I would start from the beginning again i.e. downgrade the hboot to 1.44 and start from the very beginning and follow the guide step by step

I will help you along the way as much as I can until you are 100% happy. If you try and reset the bootloader to read as ***LOCKED*** rather than ***RELOCKED*** in hboot 1.55 and then S-ON you WILL get a TAMPER DETECTED - REBOOTING message when you boot up your ROM

So as I said, lets start again from hboot 1.44 downgrade as before, change your CID to HTC__032, flash the RUU etc then once that is done, in fasboot please carry out the command fastboot oem writesecureflag 3

When you have that done, come back to me with a fastboot getvar all again and we will take it from there, ok?
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Hold on, I just had my bootloader LOCKED with that fancy command... and if I do S-ON the text in the BOOT SCREEN (this is for dev purposes only do not redistribute) will then disappear?

That's alright.

What about the "tell HTC" one? Screenshot attached. If I go S-ON, will this disappear too?
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
Yes, once you go s-on that text disappears - it's ONLY there when you have S-OFF

I'm warning you now tho - I was completely stock and went S-ON on hboot 1.55 and like other users the TAMPERED reappeared again. That is the reason I made the guide in the 1st place

So I'm telling you, you are safer doing this from the very beginning again! Otherwise you will be S-ON, ***LOCKED*** and ***TAMPERED***

From experience, once I did S-ON in hboot 1.54 I had no issues
[One (M7) Q&A, Help & Troubleshooting] dispereo:
OK, done it and now my phone is not booting anymore. It's stuck in the bootloader. Damn ****.

I really should have never touched that phone. -.- *frustrated*
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
What have you done?

EDIT:

I assume you went on ahead DESPITE ME WARNING YOU NOT TO and performed the command fastboot oem writesecureflag 3 to get S-On. I don't know how many warnings you needed NOT to do this!!

Thankfully, all is not lost. You can unlock the bootloader again using the unlock token from HTC Dev which will allow you to boot up the phone. You can then use the rumrunner that I sent you a few posts back

It is frustrating for me to sit and wait here while you carry on with instructions that I tell you not to do! So I tell you again - follow the guide in the original post and do NOT deviate away from whatever you think is the right thing to do. Follow each step and READ!
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Gimme some credit, I followed all your steps, even though some stuff was definitely different whilst I was doing it even though I followed your instructions. Just thought that this was my lucky day. -.- You didn't say ALL users had that issue, so I thought I might have a chance.

Unlocked it now, can't get it S-OFF.
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
I still advised you to start at the beginning again as there was a risk this would happen. But you went on ahead despite the warnings. I told you I had the same issue and nkk77 mentioned a similar comment earlier today

The links for some reason posted incorrectly the first time. I merely reposted them exactly and they worked, I still don't know why they wouldn't work in the first place

You also say some things were different - I believe that's because you were unknowingly s off when you thought you were s on. Probably a reason why revone would not work

Are you trying to s off again with the rumrunner package I uploaded or the universal package?

If you are running the one I sent - make sure you are unlocked and have usb debugging enabled. If you are not sure of you are, let me know

I haven't used the latest download of rumrunner but I believe it works even with a locked bootloader?
[One (M7) Q&A, Help & Troubleshooting] dispereo:
Well I followed your steps, but as I said earlier, some things were different when I did it even though I followed your steps. That's the thing that confused me. I never had an Android and I am no dev or anything. So once I got to the point where my phone did something else than your instructions said, I had to go along with it. And I asked people in another forum and they didn't reply anymore. -.-

However I am unlocked, otherwise my phone wouldn't boot up anymore. Bootloader says ***** unlocked *****

I tried both rumrunners, both of them won't work, each of them having a different error message.

C:\Android>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.62.206.1

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: O2___001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4321mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-bb768ae1

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.045s
[One (M7) Q&A, Help & Troubleshooting] stovie_steve:
FYI - Remove you IMEI and Serial No. from the previous post for security reasons

Can you post me the error messages please?