yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
I like how this old thread's title is "knock off" (double tap homescreen to sleep) and everyone talks about double tap to wake. Lol.
[Nexus 5 Q&A, Help & Troubleshooting] wangdaning:
Tapping twice is easier than pressing the power button?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Yeah could be if its in a cradle of wireless charger. The device needs force applying to the power button and a counter force applying to the left side of the phone, which can be awkward.

That said , I removed double tap status bar to sleep from my slim room m because I kept accidentally triggering it.
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
Mobile keyboards :o
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
For the same reason I always trigger double tap to sleep, I live in the bumpy road laden, Yorkshire country side and spend 2.5 hours a day bouncing my fingers all over the screen on a bus :p
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
I can't ever trigger double tap statusbar to sleep lol, I always miss the spot. I have my launcher set to double tap wallpaper to sleep for when I'm lazy :p And I do hate it when it corrects "ROM" to "room" xD
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
My keyboard knows ROM. It will only put room if I hit "o" twice :)
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
Hello

I have big problem my phone stuck in cm 10.1 in cm logo boot loop, I think this is because of the hboot 1.55. I have big problem with no back up also, but I will try to get it from one of the friend.

Please can you help me step-by-step with issues to get my phone working. I can get to boot, and recovery boot... also transfering data to phone using adb, but I cant get into phone by OS.

Is there any possibility to get my phone back to working. it is M7_UL pvt s-on rh

hboot 1.55.0000

radio-4a.21.3263.04

OpenDSP-v32.120.274.0909

os-3.62.401.1

I will be very glad for helping me, I also pay a few bucks if you want, I just wanna get my new phone back
[One (M7) Q&A, Help & Troubleshooting] muayyadf1:
S-OFF that thing!
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
yes but how can i set it' revon doesnt help me :'(
[One (M7) Q&A, Help & Troubleshooting] lanewhit:
You need to use rumrunner.
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
i

also get error something with drivers or adb
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
I have reset my htc to stock room using this ROM, but again I can only get to the HTC LOGO - HTC quietly brilliant and wouldnt go on... on video it should this dissapier in na few second my stays for hours.

Any suggestion?
[One (M7) Q&A, Help & Troubleshooting] vaibhav satam:
If u hv unlocked bootloader, try to flash Newest recovery(TWRP) by fastboot flash recovery Name.img :) once u flashed recovery ..Boot into it ..if u r not able to boot into recovery ..then hold volume Down + power button ..Connect ur phone to computer ..type fastboot erase cache :) u will Nw be able to enter into recovery :)
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
do I have to instal again twrp, cuz now says no device found?
[One (M7) Q&A, Help & Troubleshooting] vaibhav satam:
Hold volumedown+ power button for some tym ..phone will boot in bootloader mode ..Connect ur phone to computer ..it will show fastboot usb on ur HTC one :) Nw flash latest twrp or simply write fastboot erase cache if u hv flashed it before ..nw try to boot into twrp

---------- Post added at 12:37 AM ---------- Previous post was at 12:32 AM ----------

http://xdaforums.com/showthread.php?t=2265618 this thread might help ..if u r getting no device found ..power off device completely and start it by holding vol down + power ..select FASTBOOT and connect to computer ..it will Show FASTBOOT USB then type fastboot erase cache ..OR Flash recovery again by fastboot flash recovery nameofrecv.img :) then boot into it
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
but will it go with s-on... I cant get s-off even with rumrunner... allways show error with adb connection or drivers :(
[One (M7) Q&A, Help & Troubleshooting] piimp:
Yes, you should be able to use fastboot/adb commands with both s-on and s-off. So do as the above user suggested

Now, if you are getting an error with rumrunner because of adb/drivers, i thinks its because to use rumrunner your phone has to be on the homescreen, because your phone must be able to boot/reboot upon rumrunner's adb commands (and since your problem is you cant even boot the phone, i guess at this point you cant use rumrunner)
[One (M7) Q&A, Help & Troubleshooting] vaibhav satam:
http://xdaforums.com/showthread.php?t=2191279

If ur device is not detected ..plz reinstall latest drivers ..u will find latest drivers in above thread :) and first try to get a bootable device ..then s_off using rumrunner :)

1.install latest drivers

2.power off ur phone

3.power on by holding vol down+ power (it will take u to d bootloader screen)

4.select fastboot (use volume keys and press power for selecting fastboot)

5.connect ur phone to computer it will show FASTBOOT USB (if its not showing try another usb slot)

6.Goto d adb folder ..hold left shift key and right mouse click ..u will find "open command prompt" option

7.put latest recovery in adb folder of ur computer

8.Type In prompt fastboot flash recovery name.img

9.fastboot erase cache

10.boot into recovery :)

Hope it helps :)

Sent from my HTC One usin xda app-developers app
[One (M7) Q&A, Help & Troubleshooting] peca_slo:
tenx I will try is there any costum ROM which will run on hboot 1.55 if I install it just to come into phone then install the rumrunner and go back stock?
[One (M7) Q&A, Help & Troubleshooting] vaibhav satam:
Roms r not hboot specific ..to install custom roms u need custom recovery like twrp
[Galaxy Note 3 Q&A, Help & Troubleshooting] jmw2207:
Hi there. Just wondering if anyone has figured out how make the snote program to launch by default when you pull the spen out? Currently there is only 3 options.....action memo, air command and do nothing. Thanks.
[Upgrading, Modifying and Unlocking] jssjnkvch:
Hello all new to the forums and relatively inexperienced rooting device (only done once) I just update to the 4.3 firmware update a few days ago and now want to root. I have searched xda pretty thoroughly and found no instructions or how two's for rooting with 4.3. I found 1 site with instructions on true android blogspot

I have tried their method numerous times on different computers and it fails every time with a write error shortly after clicking start. If anyone has any ideas or Knows how I can successfully root My device it would be appreciated. Haven't been able to find and help anywhere.
[Upgrading, Modifying and Unlocking] zedhed:
Same here on trying the Other Blog List method Write fail after clicking start to.

Does anyone have another way to Root?
[Upgrading, Modifying and Unlocking] bledoux78:
I just got the 4.3 OTA update from Verizon on my note 2 and lost the root I had (used Framaroot that time). I too tried the true-android.blogspot.com method which failed, but Kingo worked a few minutes ago. There are some posts about on here, but you can go over to kingoapp.com. It is one of those 1-click-almost-too-good-to-be-true methods compared to what I did on my Motorola Bionic.
[Upgrading, Modifying and Unlocking] Bloodrushed:
I'm on kingoapp now and the sch-i605 model is not listed under their list of supported devices. Only the international version is there. Does it still work even though my model is not listed? Thanks.
[Defy Q&A, Help & Troubleshooting] wirespot:
TLDR: See this post for the solution; but do read through the thread, lots of good info!

I've got a MB525 for parts, seller got rid of it because it won't boot up anymore. I've tried it and it shows black screen but it can be seen over USB and I can flash .sbf files. Now, I'm curious whether it can be made to work after all.

First I've tried most of the smgver=4 stock .sbf files but no luck, still got black screen. From what I've read, black screen means the efuse has blown to a higher version. So I tried the JORDN_U3_97.21.51 (smgver=5). Still nothing.

The only thing left would be to flash a Defy+ .sbf, I've seen people recommend DFP-231 Taiwan retail or similar, hopefully a smgver=6 or 7 would work.

I've no idea what the seller did to the poor thing, nor what ROM it came with originally or from where.

Am I right that I should try a Defy+ .sbf? On the one hand, no risk really, I got it for pennies so no big loss. On the other, it just irks me that a potentially fully working Defy should just be abandoned for scrap. :)
[Defy Q&A, Help & Troubleshooting] cyrusct82:
You can try it. But if your defy is green lens the camera won't work on stock Rom only on custom Rom CM10.....CM11.
[Defy Q&A, Help & Troubleshooting] wirespot:
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
[Defy Q&A, Help & Troubleshooting] hotdog125:
Try DFP-231. If it works, you can go ahead with custom ROMs.
[Defy Q&A, Help & Troubleshooting] wirespot:
I've successfuly flashed DFP-231. By "successfuly" I mean it now shows the Moto logo and I can enter bootloader (version 10.00, FWIW) and the stock recovery.

But it won't go past the Moto logo, shows it for about 10 seconds and then it reboots, forever. I pulled the battery after ~10 reboots in a row.

Yes, I did a factory reset from recovery (ie. cache and data wipe).

Any idea what might be causing this or what else I can try?
[Defy Q&A, Help & Troubleshooting] sterver1:
Try to reflash sbf.

And say "bye" to your battery charging via phone.
[Defy Q&A, Help & Troubleshooting] wirespot:
I've been trying all kinds of DFP-231 .sbf images. So far no luck, still got a few to go. Some of them have a longer delay, such as the first Moto logo staying on for more than 10 seconds – some for 20-30 seconds... but eventually they all bootloop.

I have another Defy+ so I can charge the battery through that one, but why do you say I can't charge through this one anymore?

PS: I've just realized that the stock recovery can flash stuff from the SD card. Would it be ok if I take a nandroid backup and slap it in there? Does it matter from what kind of system the backup is from eg. stock, a CM version etc? Or will anything work?
[Defy Q&A, Help & Troubleshooting] sterver1:
For battery you can check lasts posts of my problem here http://xdaforums.com/showthread.php?t=2568049... I have never solve it :(.
[Defy Q&A, Help & Troubleshooting] thekguy:
Try ti omap blank flash option in rsdlite

Stock recovery cannot help unless you can brute force or steal Motorola's private key

You could try making a custom sbf, which would include custom recovery, from where it could work out.

[MENTION=4819966]sterver1[/MENTION] the battery issue is an exception, it does not occur for most
[Defy Q&A, Help & Troubleshooting] sterver1:
Oh, so ok. I'm only unlucky...

Good luck...
[Defy Q&A, Help & Troubleshooting] wirespot:
Still no go unfortunately.

I tried DFP-231, including with TI OMAP blank flash option. If TI blank flash didn't work, am I looking at a hardware problem?

To recap: it's a MB525 (unknown whether red or green) stuck in bootloop: will show Motorola logo for ~10 seconds then restart and repeat forever. I can enter bootloader and flash SBFs but so far none of them helped. I can enter stock recovery and wipe /data and /cache, still no help from there. It was already at BL7 when I got it (tried lower versions first and got blank screen, only BL7 will allow it to boot).

Cannot flash ZIPs from stock recovery because it will only accept ZIPs signed with Motorola's private key which I obviously don't have. :)

I've read that the wrong region SBF might be the bootloop cause so I will still try out the rest of the official BL7 SBFs, just in case.

The only thing left I can think of is to somehow put custom recovery in there so I can try flashing a custom ROM.

But how do I build a custom SBF with 2ndinit and CWM or TWRP? I have the unpacker and I know how to unpack and repack a SBF. I also know that CG39 is an ext3 image of the /system partition, but that's about it. Which CG files do I have to modify and how?

I'm also not clear on what a "fixed SBF" is. I've noticed that it usually contains only certain CG files, but not sure how it works together with other types of flash and what good are they.
[Defy Q&A, Help & Troubleshooting] thekguy:
You can flash one of the cm 10 sbfs in the dev forum. Basically you need the sbf to contain the boot menu and recovery to try flashing from custom recovery. A fixed sbf is used to prevent bl version from incrementing by removing the higher version files
[Defy Q&A, Help & Troubleshooting] wirespot:
I did it! The SBFs that did the trick are the ones in the OP in the thread Motorola defy bl7 sbf all in one. First the Asian Retail BL7, then wipe from stock recovery, then the MIUI SBF (which also contains CWM custom recovery). Then it booted right up.

I'll be back with more info about this Defy just returned to the land of the living :) after I poke around a bit (the MIUI ROM is in Chinese, gotta figure out how/if I can switch to English...)

So! Once again it's been proven that it's nearly impossible to softbrick a Defy. Given enough obstinacy ^_^ you can find a SBF that will put it right again.

PS: I should probably also add to the wiki page various stuff I've learned while doing this. I've had a hard time looking up some info, maybe it will help others.
[Defy Q&A, Help & Troubleshooting] wirespot:
Aaaand I spoke too soon. :) It booted MIUI successfuly exactly once (1 time). Now after the Moto logo dissapears I get a blank screen (but lit, not off) and nothing happens. I also tried a CyanogenMod ROM (Quarkx), both 10.0 and 10.2 – the CM spinning logo appears, it goes on for a while, sometimes it attempts to boot (got to the Dalvik generation, for example) but then it reboots, other times it will keep spinning and nothing happens.

On the bright side, I now have access to the advanced bootloader and custom recovery with all the goodies (ADB shell etc.) which opens up possibilities. If anybody has any ideas what I could try to diagnose this, please speak up – like I said, I can now have access to the actual Linux system on the phone.

The only idea that pops to mind right now is the CPU settings. Maybe it got overclocked by the original owner and something got fried? Resetting them to defaults didn't seem to do anything.
[Defy Q&A, Help & Troubleshooting] wirespot:
Still no luck. The MIUI I linked above is the only one that boots up, but won't recognize the SIM card and claims there's no GSM connectivity.

I'm speculating that perhaps something is messed up with the radio hardware, and that MIUI is the only ROM that somehow works around that and boots up, but the other ROMs don't expect it and reboot halfway through the bootup sequence.

I'll see if there's any logs made during bootup.
[Defy Q&A, Help & Troubleshooting] thekguy:
The reboots are characteristic of bad eMMC(data not getting wiped properly). Does miui work fine apart from radio? Also 2ndboot builds require a specific stock kernel(from eu dfp 231) so try that as well. Try full wipes from cwm, and make sure the data partition is formatted correctly from boot menu(ext3 for ics and below, ext4 for jb+).

The miui sbf masked the data problem(atleast temporarily) allowing the phone to boot up. Unfortunately if you do have other /data issues(which are seemingly unrelated), they all point at bad eMMC, necessitating replacement of the motherboard as the only viable option.
[Defy Q&A, Help & Troubleshooting] wirespot:
[MENTION=2150021]thekguy[/MENTION]: Yes, apart from the GSM MIUI seems to be working fine, including WiFi. But only one time, if I reboot it doesn't start up again. Sometimes I get a hanged boot logo, sometimes I get endless bootloops. Other ROMs never work, it's straight to hanged or bootloop.

Are you saying that the internal memory has gone bad, like an HDD getting bad blocks? If that's the case, I can probably use a recovery update script to repartition the memory and work around the bad zone(s). As long as I can figure out which exactly are the bad zones (other than trial and error).

Or are you saying it's simply not getting scrubbed properly and it's a problem with the filesystem? In which case I can reformat at least some of them (/system, /data/ and /cache).

But doesn't the flash tool overwrite the partitions by raw-dumping images on them? So how can a bad filesystem survive SBF flashing?

And what about update zips? Do they reformat/raw-dump partitions – or do they just take the filesystem for granted and copy to it?
[Defy Q&A, Help & Troubleshooting] thekguy:
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.

I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.

A log obtained via adb should be able to verify the same
[Defy Q&A, Help & Troubleshooting] PhilipCetero:
If the bad eMMC blocks are entirely within the ext3/4 partitions, we should be able to run badblocks on them (taking care not to overwrite the signature at the end of /dev/block/mmcblk1p21 but past the actual file system) and avoid them. As the badblock list is stored in the file system rather than the partition table, I believe that would work.

I've also been experimenting with using an SD card partition for /system and keeping only a few minimal files on the eMMC (I think we could get away with busybox and a modified logwrapper script)—no unexpected problems. It's quite likely those two files won't interfere with the bad blocks, and after they've booted the kernel we wouldn't be touching the eMMC at all (assuming /data and /cache are also SD partitions, but that should be doable). I have been using Quarx's CM11, and I don't think my trick works with stock ROMs (at least I've never had success booting a stock kernel with 2nd-boot), so it might not be a helpful suggestion.
[Defy Q&A, Help & Troubleshooting] thekguy:
2nd system/ multiboot is a good idea to get past the bad blocks (probably some performance hit though) but better than a non functional phone. 2nd system should work even with a stock ROM as secondary system, not sure why it isn't working for you. I have no idea about the badblock remapping logic
[Defy Q&A, Help & Troubleshooting] PhilipCetero:
Thanks for that hint, I'll try 2nd-booting a stock system again if it's meant to work!

I think performance would suffer a little if the SD card is slower than eMMC, but not beyond that, once the system is up and running.
[Defy Q&A, Help & Troubleshooting] thekguy:
Could you please elaborate on the badblocks thing? It could help many with similar problems
[Defy Q&A, Help & Troubleshooting] PhilipCetero:
I'll try!

Badblocks is a file system feature of ext2 and its newer derivatives. It is most easily accessed by specifying the -c option to e2fsck, either once or twice. If specified once, e2fsck will try reading every block on the file system, and record unreadable blocks as damaged. If it's specified twice, e2fsck will try reading and writing every block. While the manpage calls this latter test "non-destructive", that isn't true: e2fsck will try to restore each block after the test, but a reboot in the middle of things can leave the system unbootable, and you'd have to flash an SBF to recover.

We could do this from TWRP. Unfortunately, badblocks does not appear to be included in the TWRP ramdisk, so you'd have to build your own.

Another option is to combine checking for badblocks with mke2fs, with the same -c or -cc option, though we must be careful not to write a file system to the very end of /dev/block/mmcblk1p21. Again, a high risk of having to restart from SBF if the phone reboots during the operation.

In summary, here are untested instructions, assuming a Linux shell.

acquire a badblocks binary (I'm currently trying to generate one)

reboot into TWRP

adb push badblocks /system/bin/

adb shell e2fsck -c /dev/block/mmcblk1p21

adb shell e2fsck -c /dev/block/mmcblk1p24

adb shell e2fsck -c /dev/block/mmcblk1p25
[Defy Q&A, Help & Troubleshooting] thekguy:
While your theory seems fine, it will depend on the fact whether e2fsck would be able to access the part of the system partition where the recovery itself is stored(not sure if it is loaded entirely into memory).

If it could, then writing to them would crash the shell. Otherwise, those blocks could be marked as 'bad', and that will be another problem in itself. Just off the top of my head..
[Defy Q&A, Help & Troubleshooting] PhilipCetero:
Yes, TWRP is loaded entirely into memory. You're right that if we can't get to recovery, we can't use badblocks from it, but it's far more likely that the 6 MB TWRP uses are uncorrupted than that the entirety of /system is.

We can also combine my two ideas, and put a minimal boot script into /system/logwrapper, then load TWRP itself from the SD card. That would require only /system/bin/logwrapper and /system/bin/busybox to be writable (once) and readable (on every boot). If we can't even do that, I see no way of saving the phone.
[Defy Q&A, Help & Troubleshooting] thekguy:
Also, is the bad blocks list preserved after a format? Otherwise it would necessitate checking after every data wipe.

The second idea will most probably work
[G2 Q&A, Help & Troubleshooting] OldOldDev:
I got the little tinkle sound earlier that signifies that the battery is fully charged, but noticed that the battery icon in the top right seemed to indicate that it was still charging. Please see the 2 screenshots taken at 10.15pm.

So i decided to leave it a while and later noticed that the battery icon changed to full.

Does that mean that the lithium battery trickle charges for about half hour or so?
[G2 Q&A, Help & Troubleshooting] khaytsus:
LiIon/LiPoly do not trickle charge. Your guess is as good as mine as to why it indicated it was full prior to it really being full. Perhaps it indicates full charge at 95% or something? Did you look to see what exact percentage it was when it "tinkled"? ;)
[G2 Q&A, Help & Troubleshooting] Steamer86:
They do trickle charge(low mA) at top end... and bottom... and depending on temperature.... very apparent if checking mA readings. Charging logic. Your findings are correct. I still say there is ****ty top and bottom end calibration on this phone, though makes 0 difference in how long the battery lasts if you leave it sit. How we get that magic 1% top end and **** 5% bottom, that sometimes powers off at 2%.
[G2 Q&A, Help & Troubleshooting] OldOldDev:
Thanks guys. The prevailing logic is that lithiums don't trickle charge because when they are "fully" charged then they *should* automatically switch off the power, but there definitely does seem to be evidence of a trickle change effect.

My guess is that my particular phone has poor battery calibration, but i don't know yet.

It showed 100% (it also shows this in GSam battery monitor in the 2nd screenshot). Every singlge time the 'tinkle alarm' goes off it shows 100%
[G2 Q&A, Help & Troubleshooting] Steamer86:
It's all LG G2s. I wouldn't say it's trickle per say, the logic just slows the mA draw at top end. Doesn't shut on and off, Just starts again at a certain % threshold. Calibration at 100% and bottom is indeed mis-calibrated. The standby mA draw in BMW and LG diagnostics reports +27,28 mA. A bit odd of you ask me.... Should be negative... all the more to assume bad calibration.