yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD General] DarthBelan:
I don't think people are intending to be rude. The OP doesn't provide a link to said article. Lithium Ion batteries aren't affected by overcharging, or undercharging, just no charging. Nickle Cadium batteries are affected by over charging and charging before the battery completely drains. The Fire has, I believe, a litium Ion battery as most of todays tech does. The only thing I've ever read about Lith Ion is that you should allow the battery to completely drain every once in awhile.
[7" Kindle Fire HD General] Simba.7:
Looks at the post count

I wonder..
[7" Kindle Fire HD General] TheFantom:
Been on this site for a long time, but unfortunately lost access to the email I used to register and I forgot my pass.
[Samsung Galaxy Nexus] jeffreynothing43:
I get homescreen redraws - constantly. I have tried removing every widget possible, changing every setting, and all the ''keep activities etc'' unchecked, keep homescreen in memory. I need help on this. It's driving me crazy. I've tried live wallpapers, regular wallpapers. I can't think of anything else.
[Samsung Galaxy Nexus] neerajvd:
Redraws drive everyone crazy.

But in order to help you, we need some details like Android version, root, ROM, kernel, launcher, total apps installed, free RAM..

If you haven't rooted your phone, I'd suggest you to do it and get rid of the unwanted apps.

If you have root, try changing kernels to find out the one that suits ur ROM.

Also, you can install Greenify to restrict background apps.
[Samsung Galaxy Nexus] AndyYan:
My guess is that you have so many apps running in the background and eating RAM that the launcher has to be cleared out of memory. Check your available RAM.

Sent from Motorola Photon Q 4G LTE @ CM11
[Samsung Galaxy Nexus] jeffreynothing43:
I am running Beanstalk, 4.2.2 build. I was using the kernel that came with the rom, which I guess CM based. I was using stock launcher but switched over to the KK Launcher. Not sure about free RAM as I flashed Mopang's kernel after I read both of your responses. According to System Panel, I don't have that much running in the background. Is there a better app to use to help manage that?

Looking at "apps" it shows I have about 270mbs of RAM.
[Samsung Galaxy Nexus] neerajvd:
Are you still getting launcher redraws with 270mb free RAM?

And do you mean 4.2.2 or 4.4.2?

A few suggestions would be to switch to a 4.4.2 ROM now that they are almost stable.

Else try some other launcher like Nova, or Apex.
[Samsung Galaxy Nexus] jeffreynothing43:
I haven't had one yet since I have installed the other kernel... I am on 4.2.2. All the KK Roms I've tried have been really choppy and slow, or don't have all the features I like. I'm open to suggestions though. I am on the Sprint network. I will try another launcher if it keeps happening. I wish I had a more definitive idea of what is causing it. My girlfriend never has these problems and is using the same launcher has me. I set up most of her phone as well.
[Samsung Galaxy Nexus] bsmitty83:
try using lagfix app from the play store , should take care your problem on a 4.2 rom
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KinkyGolab:
Jag har pratat med en pekniker på Dangaard Telecom i dag han har fåt ett email från HTC eller vad utverklaren till 9100 och 9000 heter, HTC har sakt det kommer inte slepas nån blue Stereo profil, det är för bugigt, det va nåt med att hårdvaran i 9100/9000 inte är få bra till blue prfile så HTM kommr ej spela det
[Verizon Samsung Galaxy S III] asparky:
Sorry but doing the casual on my Verizon S3 4.1.2 @F1

I did step 1 and 2 and checked supersu as it said to update binary.. Not sure how to update. I've seen the same question many times without an answer. I haven't went any further and I'm still hooked up.. so I guess I am rooted now and unlocked, as I have supersu and titanium backup (root) but I haven't installed one of the 2 recoveries.

I'm not sure how to proceed. I just want to stay at 4.1.2 so I can keep my phone as a hotspot and keep apps on sd car, but I am afraid I might get forced into taking 4.3. It happened on an earlier update when My phone rebooted even though I had checked no updates.

For what I want, I don't know which recovery I should take or which custom ROM. I need good signal strength, stability, to be able to leave my options open, and Tethering ... I have a cabin where I have to use a cell phone amp. to just get a marginal signal. and no Wi-Fi there so want to be able to tether to my wi-fi only tablet.

suggestions appreciated!

Thanks
[Verizon Samsung Galaxy S III] asparky:
PLEASE
[Verizon Samsung Galaxy S III] shopman59:
I just did this to I installed EZ-unlock to unlock the bootloader and then GooManager to put TWRP on for the newest ver. stayed stock for a week now I on Hyperdrive RLS16 .

Google EZ-unlock to find the apk GooManager is in the play store hope that help
[Windows Phone 8 Q&A, Help & Troubleshooting] Room408Design:
It seems the Jail Break/Root is coming to Windows Phone 8 soon. It may free more features from wp8. Looking forward to it. :laugh:
[Windows Phone 8 Q&A, Help & Troubleshooting] DilanChd:
For the moment, not too hope...
[Windows Phone 8 Q&A, Help & Troubleshooting] GoodDayToDie:
Yeah, the closest we have right now is the capability-unlock for Samsung phones. That's not a full root (working on it!) and beyond that, we have almost nothing.
[Windows Phone 8 Q&A, Help & Troubleshooting] DavidinCT:
Anyone find any new news on this so called "920 Unlock" that has been claimed it will be released soon ? If this is true, this could open the doors to most WP devices...
[Windows Phone 8 Q&A, Help & Troubleshooting] GoodDayToDie:
The only thing I saw was Ultrashot saying it was a Riffbox "hack" (meaning you'd need to have some special hardware and probably physically open up your phone, to do it).
[Windows Phone 8 Q&A, Help & Troubleshooting] CodingBird:
It's still better than nothing ^^
[Windows Phone 8 Q&A, Help & Troubleshooting] ceesheim:
and that's also not that easy ( retail)

because the wp8 phones also have so called E-fuse in Soc

on retail they are blown ( even the Jtag E-fuses are blown)
[Windows Phone 8 Q&A, Help & Troubleshooting] dazza9075:
its also unbelievably dodgy if you don't know what your doing.

You effectively connect directly to the ROM chip, an I mean that in a physical sense and rewrite any data you want, you can "root" anything doing this as you'll bypass any security measures, its just a matter of getting the correct software to flash on to the thing that's tricky, oh and the small matter cracking open your device, locating the chip, working out the necessary configurations to power it up and flash it :D

I did some research on this for the focus S and yes its possible but its way beyond my abilities

And there you have it, its even harder on WP8!
[Windows Phone 8 Q&A, Help & Troubleshooting] DavidinCT:
It's dispointing for sure....All I want is 3 rows of tiles and custom colors on my 928.... is this too much to ask ? (Not at Devs at Microsoft)...
[Windows Phone 8 Q&A, Help & Troubleshooting] thals1992:
Then get the ATIV Odyssey, which I just unlocked InteropUnlocked Sunday, except three tiles might be overkill on a 480x800 screen. O_0

I haven't updated to GDR3 yet because I'm not sure how to avoid Diagnosis' changes once I update.
[Windows Phone 8 Q&A, Help & Troubleshooting] DavidinCT:
It's been updated with a XAP...

http://www.silenstd.com/silenall/silentech/highxap/

any idea if it's any good or if we need an account to download it ?
[Windows Phone 8 Q&A, Help & Troubleshooting] DilanChd:
Deploy with SDK, BUT: http://xdaforums.com/showthread.php?t=2435697&page=48
[Windows Phone 8 Q&A, Help & Troubleshooting] meccy:
lumia 625 root

Hi thanx for all the hard work.

Could anyone tell me if there is any way of rooting Lumia 625
[Windows Phone 8 Q&A, Help & Troubleshooting] ngame:
If you are 8.1 user use custom wpsystem and customPFD

also you can use resource hacker of djamol after that . Using resource hacker is not maybe very safe for this time so wait for it
[Windows Phone 8 Q&A, Help & Troubleshooting] GoodDayToDie:
Note that djamol's hacks don't make a complete root, though they are the closest thing that is public right now for a Lumia like yours. Nobody's going to say anything about a full root until it's ready, and ideally not even then not until after a major update (to give the most possible time before MS <REDACTED>s us over with an update that takes away control of our personal devices again).
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
I've always had trouble finding a definitive answer for this question.

In general, are bootloaders backwards compatible? For example, if I flash a JB 4.2 bootloader, will flashing a JB 4.1 or ICS ROM work as expected, or does the bootloader need to be downgraded too? I know that some newer phones (like the S4) have an efuse that prevents going backwards (at least for stock), but does that concept hold true for all phones?

I have an S2 that I just replaced with an S4, so I'm going to play around with it some now (currently on stock 2.3.4 KH7 with rooted kernel). It's been a while since I've flashed an entire ROM (usually I just work on getting root), but since this won't me my primary phone anymore, I can play around with it a bit.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I can't give you a definitive answer. We have established that even though the file size for the boot loaders remains consistent from Gingerbread through jelly bean, there are differences between the files when examined as hex code. So the engineers do perform modifications with each version. I have never seen any discussion of the boot loaders not being backward compatible. So, since we have lots of stock and custom firmware on the forum that does not contain boot loaders, I would assume that you could flash a Gingerbread or ICS over JB or KitKat boot loaders without problems. And even if there were issues, it would be no problem to flash a full stock distribution to get the correct boot loaders. But again, this is only my surmise, and not based on direct knowledge.

There have been some statements by at least one developer that you must upgrade the boot loaders for the latest versions of Jelly Bean or KitKat. I would think it advisable to have matching boot loaders on your daily driver.
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
(apologies ahead of time that my initial post was probably in the wrong forum).

Well, at least I'm not the only one who hasn't been able to find a definitive answer. :)

Speaking specifically about the S2 (since that seems to be one of your specialties), if I need to update the bootloader to ICS or JB (since I'm on gingerbread) and something goes wrong, will it hard brick the phone or can I still get into the ODIN download mode to recover/reflash? Is the download mode on this phone considered part of the bootloader? I get a little confused sometimes in regards to what is included in the "module".

For example, it seems like (at least for this phone), the recovery image is built into the kernel as opposed to a separate image like my ASUS Transformer TF300T. Is that correct? On my TF300T, I can flash the recovery image separately through fastboot without touching the kernel, bootloader, or anything else, but it seems like the recovery image for the S2 always comes with a kernel.

Basically, I want to do anything I can ahead of time to reduce the risk of a brick (and know what I should avoid to reduce bricking the phone). Based upon what you said, it sounds like the best way to upgrade my bootloader is to flash a stock ROM that includes the bootloader. If that is the case, since JB 4.1 was the last version release by AT&T, should I just go to that bootloader and hope it works if I install a JB 4.2/4.3 or KitKat based ROM? I assume if I reflashed the stock KH7 ROM, it would just replace everything (including bootloader) and get me back to where I am now?

I have a lot of experience in the Linux world, so I'm trying to map over the Android concepts to the Linux concepts, but I still get tripped up sometimes (recovery, bootloader, kernel, ROM, etc). Sometimes people don't seem to use the terms the same way.

From a technical standpoint, it doesn't surprise me too much that the bootloaders are the same size. It's probably similar to the MBR code for hard drives that just does a minimalistic job of getting the hardware in an accessible state so it can later boot the kernel (like GRUB).
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
Wow. A LOT of useful information in that response. Thanks! A few of the things finally made some light bulbs go on in my head and clear some things up.

So to get to an ICS or JB bootloader, does it mean I have to perform an update through Kies? I'm looking at the different custom ROMs running KitKat and at least some of them say to be on a JB bootloader. I've read that at least some some devices (such as my TF300T), the different bootloader versions can actually have different partition layouts

If I tried flashing your OCD package for UCLL6 4.0.4 on my current system (with gingerbread BL), would it boot (or worst case, just not boot but still allow me to enter ODIN download mode to flash back to stock UCKH7)? If I'm understanding things correctly, it seems like as long as I'm not touching the bootloader, the worst thing that could happen is that I get an unbootable phone that I can still recover using ODIN download mode.

I guess I'll have to start poking around the different partitions to see if I can find any signs that point to what is what (unless I can't do a simple dd of the partition to a file using adb shell).

Very useful stuff. I'll have to read around a bit more to understand the different functions associated with each image. And yes, it would make sense that the img files are simply a direct bit-for-bit copy of that partition (which I would assume could be obtained with a simple dd copy). That would also explain why the bootloaders are the same size (if you dd a block device/partition, the resulting raw file is the size of the block device/partition). My guess is that the flashing process essentially just takes each img and does the same thing as a dd of the file to the partition.

This makes me wonder... If the bootloader partition for a phone has a JB BL, I can't see why someone couldn't do a dd of that partition into an image file and then restore that to the bootloader partition of another phone (maybe there's built in security that prevents stuff like that).

Very nice. Thanks. I just got my S4 last month, so I don't plan on doing anything to it besides already acquiring root. I'm also on the MF3 release which doesn't have any known way of installing custom ROMs anyway.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I wouldn't use Kies. Flash the full distribution of the stock firmware that you want the boot loader. For JB boot loaders, flash UCMD8 full. You can find that in the Download Repository at the bottom of the page.

The OCD for UCKK6 does not have boot loaders. To get the Gingerbread boot loaders, flash UCKH7 full. To get the ICS boot loaders, flash UCLE5 or UCLL6 full. Again, you can get those in the Download Repository.

You can use dd to pull or restore the contents of a partition. You can use adb shell, or you can use terminal emulator right on the phone. In fact, it's a good idea to back up your efs partition using the dd command. I've posted how to do that several times in the forums. Advanced search for "back up efs" and "creepyncrawly" should find that for you.

I personally would never try to flash a bootloader using the dd command, although it is definitely possible. There is too much margin for error. Remember, the dd command is lovingly called the destroy disk command.
[AT&T Samsung Galaxy S II SGH-I777] bleggy:
wait. I've never flashed any bootloader. My phone came with GB but the last official firmware that my phone had was the ICS OTA. From there, I flashed up to JB and now I'm happily running KK.

I have flashed the latest modem, however.

Unless I am missing something, my phone works just fine with old bootloaders and new kernel/recovery/roms.
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
Once again, thanks for the useful info.

I would definitely only use dd to replace the contents of a partition as a last resort. Since I don't know enough about how android would handle a partition being changed underneath its feet, it would be risky.

I grabbed the file for UCMD8 (4.1.2) and I'll play around with that. I tried to grab UCLL6 (4.0.4) too, but the links point to the defunct hotfile site. Do you have updated links for that file (or is it exactly the same as what I can download at sammobile.com)? The full stock binaries (.tar.md5) go in the ODIN PDA slot, right?

Also, for those that may be interested, I made a copy of the bootloader from my stock UCKH7 (partition /dev/block/mmcblk0p2) and looked for strings related to the ODIN download mode, and I was able to find all of the strings that appear when in download (e.g. "ODIN MODE", "PRODUCT NAME", "ERASING DOWNLOAD INFORMATION", etc), so it's safe to say that ODIN download mode is part of the bootloader. All the more reason to just leave the bootloader alone if possible.

I also noticed that the two bootloader partitions (mmcblk0p2 and mmcblk0p3) are almost identical except for the text string SNBL in the mmcblk0p2 partition. I wonder why the two partitions...
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
Which JB version are you running? One possible reason I can think of where a newer bootloader would be needed is if the partition layout changes. I've heard of some devices where that occurred with JB 4.2. Maybe that's why TWRP recovery has two different versions for 4.1 and 4.2 on my TF300T.

At any rate, it's good to hear that someone hasn't broken their phone by running an older bootloader with a newer ROM.
[AT&T Samsung Galaxy S II SGH-I777] bleggy:
I'm on KitKat 4.2.2 now.

Previously, 4.3 & 4.2-something Jellybean. And a ICS rom before that.

I dont think flashing new bootloaders is necessary. I mean, I dont think its common.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I haven't finished uploading files to dev-host yet. But I'll be sure to upload that one today. I don't think you can get the file from sammobile either. They also used hotfile, and have not re-uploaded their complete library yet.

Yes, put the tar.md5 in the pda slot.

So you dd'd the contents of 0p2 and looked at that? What tool did you use to look for strings? And do you know if that is boot.bin or sbl.bin? I think it must be boot.bin.

Is it possible that there is built in redundancy? If one partition is bad, the second one can be used?
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I have uploaded UCLL6 Odin Flashable tar.md5 to dev-host and posted it in the Download Repository.

By the way, I forgot so didn't mention it earlier in the discussion, but both UCLE5 and UCLL6 contain boot bin, but do not contain either sbl.bin or param.lfs. Evidently, the secondary boot loader and param files were not updated in the upgrade from Gingerbread to ICS.
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
Thanks for the files. One more question about them. If I simply remove the boot.bin and sbl.bin from the tar file and flash, that's the same as the "no bootloader" flash images, right? Maybe param.lfs too? I'm just thinking of ways to make things safer while I'm doing my initial testing (and bleggy seems to be running newer ROMs off the original GB bootloader).

It was definitely the SBL, because it's a 1.25MB image instead of the 128K first stage bootloader. I found this thread about the Captivate (another extra phone I have) that says it works the same way (and does a good job explaining the boot process). I haven't figured out where the first stage bootloader (boot.bin) is stored, since it's not in a partition. I'll have to do some research on that.

In Linux, there's actually a command called strings that you can run on a file and it will extract all of the text strings it can find. A grep of that can find specific text. You could of course do the same thing by opening the file in a hex editor.

That was my thought, but I'm not brave enough to experiment to see if that's true. :)
[AT&T Samsung Galaxy S II SGH-I777] bleggy:
whats the point, anyway? having consistent bootloader and rom doesnt seem to matter and plenty of i777 owners are running kitkat which there is no available bootloader to download and flash.

Is this an OCD thing? I get flashing the various modems for signal improvement, but I've never had a problem booting any rom with my old GB or ICS bootloader.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Yes, that would be true. As long as you are using Linux to tar the remaining files, they should flash fine. I guess you can add the md5 if you want also.

The UCLE5 and UCLL6 one-click downloaders that I posted have the boot.bin removed. The UCLE5 and UCLL6 stock plus root also have the boot.bin removed. No one has ever said anything about any problems resulting.

My assumption is that it's ok to keep gingerbread boot loaders, or to flash the ICS boot loader, or to flash the JB boot loaders, and you would never be able to tell the difference. On the other hand, there must be a reason that Samsung puts them into the kies download. I just have no knowledge and no speculation on how they differ, or whether it is important to have matching boot loaders.

Edit: Oh, and boot.bin probably goes into 0p0 partition, just a guess. But it gets flashed in the pda slot just like sbl and param, so it must go into a partition.

Edit: A forum friend found this thread for us.

Edit: I just found Adam Outler's online pit file analyzer and ran the pit file from the Download Repository through it. Partition information for the AT&T SGS2 attached.
[AT&T Samsung Galaxy S II SGH-I777] jpasher:
I have no reason to make the bootloader match the ROM. I'm just making sure I understand how everything works together to avoid doing something that may potentially brick my phone. I flashed the no bootloader version of stock UCMD8 today and everything seems to be working fine. As long as things work, I don't really care which bootloader I have.

There's not a "zero" partition. My only guess is that it's embedded somewhere else. Not sure at this point.

I found that post the other day with the S2 partition layout (that's what I was using for my tests). The PIT file analysis gives a little more info, although it says boot.bin partition is 0 bytes. That's what confuses me a bit. But in the end, not really a big deal. More of a curiosity than anything else.
[AT&T Samsung Galaxy S II SGH-I777] yosmokinman:
When this forum was active "Don't mess with bootloaders" was common knowledge. Unless you absolutely have to. You can hard brick this thing if there's a problem while flashing it.

Don't mess with any of the files you mentioned. As far as I know it's unnecessary. I'm running Renders CM11 build with no problems with the original GB bootloader. Never had a problem with ICS or JB roms either.