yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S8 Questions & Answers] miguearamburo:
My s8 sprint unlocked, unlocked remotely on a page I found, the phone is unlocked but from the unlocking the battery does not charge 100%, it stays with 80% I saw in a topic that is because of the temperature in fast charge , I did some tests, I loaded it with a load of slow load not charge more than 80%, with that discard that it is temperature the phone was not hot, ok I thought it may be some bug of the unblocking, but continued doing tests, load it On a cold surprise basis I got to 81% but nothing, well I made the last attempt I put to charge the phone in the refrigerator, surprise the battery according to the app 3c battery monitor when it reached 80% had a temperature 17.6 degrees centigrade and even so Remained at 80%.

With these tests discard the email I saw in the other issue of samgung that said that it is a protection of overload or anti-inflation of the battery that the phone will reload when the temperature goes down, you who think unlock bug or software bug ?
[Sprint Samsung Galaxy S8 Questions & Answers] Ph3n0x:
Sounds like you have eng firmware flash back to stock with odin
[Sprint Samsung Galaxy S8 Questions & Answers] allaidback:
I have the same problem...I flashed eng root firmware and now can't flash back to stock in odin...can someone provide a stock flashable file or can I just replace the boot.img file inside the eng root file?

*EDIT: Used ODIN 3.15.5 and G955UOYN1AQEF_SPR worked great.
[Moto Z Play Questions & Answers] eldoggor:
Hi, need to ask for your help. The camera of a friend Z play loose focus while recording video and doesn't focus again. This problem is not present while taking pics.

He already restored the phone with no luck and he is still in 6.0.1,maybe if he upgrades to Nougat the problem will be solved? Or maybe he needs to go to technical service? The phone still has warranty.

I attached a test video.

Thanks for any help.
[Moto Z Play Questions & Answers] Zeljko1234:
I'm using Cinema FV-5 for years to record videos. It has several options, including for focus and do not have focus problem.
[Samsung Galaxy S8 Questions and Answers] JustusIV:
I have the verizon model of the s8 so i am unable to use samsung cloud(Thanks Verizon you jerks). I was wondering if someone would be willing to make a video showing samsung cloud restoring and app with appdata.

I found this feature still is available in my secure folder however it does not store appdata and am yet to see proof that it actually works with appdata.

Does samsung cloud really able to replace the need for titanium backup? How the F is this not built into android already. sigh....
[Samsung Galaxy S8 Questions and Answers] thahim:
Samsung cloud?
[Samsung Galaxy S8 Questions and Answers] JustusIV:
Yes.

Everyone accept Verizon get an app called samsung cloud that backs up pretty much everything.

https://www.youtube.com/watch?v=n0kwrA4Pa3U

for an overview.

I want to see it specifically do appdata.
[Samsung Galaxy S8+ Questions & Answers] SevnSins:
I'm patiently waiting for root for my s8+, and I'm already getting updates pushed to my phone. Should I hold of updating until I can root my device or is it safe to proceed with the update? I don't want to update if it might disable my ability to root later.
[Samsung Galaxy S8+ Questions & Answers] A|ex:
you answered your own question
[Samsung Galaxy S8+ Questions & Answers] Aridon:
If root is important, then skip the updates. Taking them creates risk of not being able to go back. That said, I wouldn't count on the US version getting rooted. If that is important get an international version or stick with the pixel.

Thing is, root is getting less and less necessary. Used to be 110% for me, now I'm sitting with this device and no root. The only thing I'd like to do is change the Bixbie button.

Android has come a long way.
[Samsung Galaxy S8+ Questions & Answers] SevnSins:
I'll hold off for a bit and just purchase the package disabler app. Thank you for feedback.
[Samsung Galaxy S8+ Questions & Answers] RockyAJ:
there are apps in the playstore for the bixby button remap already
[Samsung Galaxy S8+ Questions & Answers] hinds90:
Same here. Even the last Samsung phone I had didn't really need root which was a note 3. The phone just works.
[Samsung Galaxy S8+ Questions & Answers] SevnSins:
The s8+ is a great phone so far, I just like the ability to install custom roms and customize my phone how I want.
[Samsung Galaxy S8+ Questions & Answers] JazonX:
Don't Update, If you have a Note 7.

If you dont have a Note 7, Update.. By all means.

So, Rather than wasting a post,

I have rooted mine, and I manually flash my updates over ODIN using the Home_CSC, so my data stays intact.

As soon as you flash over odin, you need to boot to TWRP, and then flash the Kernel, or else, you will enable the encryption again.

Root - Was worth it. The only things I lost was SamsungPay and Secure Folder. However, on the other hand - I've got built-in Call recording, Built-in Caller ID, Bixby button remapped to open the Camera, Ads Blocked from Hosts file, iOS Clean Emjoi's installed to system, TouchWiz removed and Nova installed in system... I can go on.
[Samsung Galaxy S8+ Questions & Answers] SevnSins:
Which phone so you have? Root for the US s8+ isn't available yet last time I checked.
[Samsung Galaxy S8+ Questions & Answers] TRoN_1:
The last time you checked AND the next time too. He obviously has a rootable phone(probably F).
[Samsung Galaxy S8+ Questions & Answers] RockyAJ:
Why shouting?a simple google search will show snapdragon will not have root
[Samsung Galaxy S8+ Questions & Answers] SevnSins:
Actually a quick Google search finds a root method supposedly provided by chainfire, but it's not hosted on XDA, soi I didn't trust it.

http://www.teamandroid.com/2017/05/03/root-galaxy-s8-plus-android-firmware/
[Samsung Galaxy S8+ Questions & Answers] JazonX:
Mine's Exynos. G955FD
[Nexus 7 Q&A, Help & Troubleshooting] Ghoast:
After an update to my 2012 Nexus 7 a ways back, it became unbearably slow and I gave up on it. I'm assuming it was the 5-dot-something update because after doing a bit of digging just for kicks, it seems the same thing has happened to everyone else. So, I wasn't paying close enough attention and I flashed the 4.2.2 2013 nexus 7 version (from here https://developers.google.com/android/images) onto my 2012 Nexus 7. Feel free to point and laugh now.

My tablet is now stuck with showing the Google logo, and won't go past that. Plugged into my pc, it now longer shows up under devices in adb. However, if I go into recovery mode and then into sideload mode (and I've tried all the other options, clearing cache and factory reset I think), it will show up under adb, and will let me sideload. I've tried just about every file on this page https://xdaforums.com/showthread.php?t=1745781 and still no luck. I've gone into the update script and removed the assert line as many suggest. Always ends up at "Aborted Installation" with no errors.

Are there any other options at this point, or do I have a new paperweight?

Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Ghoast...

I think you need to reflash it.

It's been quite a while since I flashed my Nexus 7 2012, but if I remember correctly...

Long press and hold the power button and volume-down button together; this will reboot the Nexus 7 2012 into the bootloader.

Using fastboot, flash a Nakasi/Nakasig (depending on your device) Google factory image available from the first link in your post.

Sorry I don't have the time to provide more details, but I have to go out soon.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ghoast:
I wish I could! In flashboot mode my device doesn't show up under the device list in adb. I can enter the commands but it just says <waiting on device>. Adb only seems to acknowledge it when I go into... I think it's called Recovery Mode. From there I can sideload updates, but as far as I can tell that is all I am able to do. Thanks though!
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Ghoast...

You're using ADB when you should be using Fastboot!

ADB doesn't work whilst the tablet is in fastboot mode.

ADB only works in fully booted Android and Recovery.

Only fastboot.exe will flash a device whilst it's in fastboot mode.

So, with the Nexus 7 booted into fastboot mode, type...

fastboot devices

If you have a successful fastboot connection (ie., assuming no driver problems), this should return your Nexus 7's serial number.

Your should then be able to flash the device using fastboot flash commands...

e.g.

fastboot flash bootloader [I]<<name-of-bootloader.img>>[/I] file
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc,
etc.

Or alternatively by running the flash-all.bat batch script file which accompanies factory stock images, although if I remember correctly there may be some problems with this method with the Nexus 7.

Be very careful when flashing the bootloader. Flashing the bootloader is the riskiest part of flashing a Nexus 7 and can potentially hardback the device if you flash the wrong one, or if, whilst flashing it, the USB is disconnected mid-flash. This would then require a motherboard replacement :( .

If your Nexus 7 is already running bootloader v4.23 (visible in the bottom left hand corner of the bootloader screen), there's no need to reflash it, as this is the latest version of the bootloader.

-----------------------------------------

I haven't reflashed or bothered with my Nexus 7 for about three years now, so my recollection of the precise details on reflashing it are somewhat hazy.

You can find some useful and important info on returning a Nexus 7 back to factory stock, here...

https://xdaforums.com/showthread.php?t=1907796

-----------------------------------------

There are several different approaches that can be taken when flashing a Nexus device, including a Nexus 7 2012.

My own preferred method is to fully unzip the Google stock factory image to be flashed and then to fastboot flash the device partition by partition.

Apologies for the vagueness of my response - my memory isn't what it used to be,

but one thing I am absolutely certain of...

ADB.exe won't flash your device.

fastboot.exe is required for flashing.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ghoast:
Ged,

You were right! I was looking at the wrong thing, so thank you for that. I was able to flash the correct bootloader as the one I had on there was not the right version - I tried to update before updating the bootloader and it said it required 4.23. After updating and restarting the bootloader, I tried the flash-all bat file and got these results:

C:\nakasi-kot49h>flash-all.bat

...

FAILED (command write failed (No error))

finished. total time: 0.002s

erasing 'boot'...

FAILED (command write failed (No error))

finished. total time: 0.004s

erasing 'cache'...

FAILED (command write failed (No error))

finished. total time: 0.006s

erasing 'recovery'...

FAILED (command write failed (No error))

finished. total time: 0.007s

erasing 'system'...

FAILED (command write failed (No error))

finished. total time: 0.006s

erasing 'userdata'...

FAILED (command write failed (No error))

finished. total time: 0.004s

target didn't report max-download-size

sending 'bootloader' (3911 KB)...

FAILED (command write failed (No error))

finished. total time: 0.004s

rebooting into bootloader...

FAILED (command write failed (No error))

finished. total time: 0.004s

target didn't report max-download-size

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

archive does not contain 'vendor.img'

wiping userdata...

Erase successful, but not automatically formatting.

Can't determine partition type.

FAILED (command write failed (No error))

--------------------------------------------

getvar:version-bootloader FAILED (command write failed (No error))

finished. total time: 0.005s

Press any key to exit...

Lots of failing with no errors so... I dunno!

Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Just to confirm, is the bootloader unlocked? If not, you can unlock it with...

fastboot oem unlock

You can't flash anything with a locked bootloader. If the bootloader is unlocked, you should see a white unlocked padlock symbol underneath the white Google logo when booting the Nexus 7. It should also say 'unlocked' in the bootloader screen in tiny letters in the bottom left hand corner.

It's also possible your fastboot executable may need updating. You can get the most up-to-date version of fastboot (and ADB) from here...

https://developer.android.com/studio/releases/platform-tools.html

Other points worth considering... Ensure you have a good USB connection between your PC and the Nexus 7. Sometimes it's also worth trying different USB cables and/or different USB ports on your PC when encountering problems when flashing a device.

Hope this helps and good luck.

Rgrds,

Ged.
[Tilt, TyTN II, MDA Vario III General] tls246:
Apologies if this is covered elsewhere, but I'm on my second Tilt, after the first one suffered from unrecoverable lockup -- the dreaded Red LED of Death that several others over at the AT&T forum have talked about. Is this issue limited to AT&T branded phones? I'm wondering if there's something peculiar about the AT&T ROM or bloatware, and whether if I get rid of it I can head off this problem at the pass. I don't want to have to deal with it again.

If this has already been covered elsewhere, can someone point me to the answer?
[Tilt, TyTN II, MDA Vario III General] tyeo098:
Yes it was the charger that caused the power supply chip to fry.

If you have the fatter, vertical charger, request and exchange for a slimmer, horizontal charger, the newer one.
[Tilt, TyTN II, MDA Vario III General] Malik05:
do we have proof of this? or just speculation? because i remember it was talked about, but even those with different kinds of chargers experienced this.
[Tilt, TyTN II, MDA Vario III General] tls246:
Just found the relevant thread, but thanks for your answer! I guess I'll be charging from my computer's USB port... I don't know if I can talk to AT&T store into replacing my charger without proof.
[Tilt, TyTN II, MDA Vario III General] XtreMe_G:
i'm gonna say its bs, cause i have that exact fat vertical charger for my 8525, been using that for a year, no probs.
[Tilt, TyTN II, MDA Vario III General] Malik05:
yeah it is BS, there is no evidence as to why this is occurring...
[Tilt, TyTN II, MDA Vario III General] ekw:
i got my first red light with a htc branded kaiser, when i ran pocket mechanic file cleanup. Apparently it drained alot of power in 5 minutes then red light came. I was able to start the kaiser but it turns off after a few seconds. I somehow managed to save it thru playing with the charger(lucky me!)
[Tilt, TyTN II, MDA Vario III General] sWuRv:
I don't think the rlod means anything is "fried", I too resurrected my phone by playing around with it. It does seem to be a problem with the power management circuit, but there is no proof of a certain charger causing the problem. People have gotten the rlod using both htc chargers. If you turn the phone on without a battery, you get a rlod. I think the problem lies within the phone not realizing that there is a battery installed. I was playing with the battery contacts when i resurrected mine. I'm fairly confident that a fix for this problem is on the way. It would be more productive if people would do some tinkering once they get the rlod, instead of deeming it a brick and returning it without even trying to fix it. These assumptions that a rlod phone is a brick are counter-productive, and they arise from somebody lazily jumping to conclusions without doing any research.
[Tilt, TyTN II, MDA Vario III General] tls246:
Besides plugging and unplugging the various doohickies that come with the Tilt, and trying soft and hard resets, what does "playing around" entail? 'Cuz I thought I had covered all the permutations, before I decided I'd let the AT&T store deal with it.

It'd be cool to know what worked for you guys, before it happens again.
[Tilt, TyTN II, MDA Vario III General] cushcalc:
Red LED of Death - don't know why, but . . .

RLOD happened to me one week ago on my Tilt - got replacement 3 days ago. Certainly the RLOD didn't have anything to do with the bloatware because I Hard-SPL'ed and flashed a custom ROM on day 1 of ownership.

I do think that what chargers are used

might

be an issue - because I didn't always use the one that came with the unit - I used my old Wizard charger, aftermarket car charger, aftermarket wall plug charger, etc - with mA rating varying from 550 to 1000
[Tilt, TyTN II, MDA Vario III General] phi11yphan:
Regarding the Tilt Red Light of Death (RLOD), read this for a fix that's worked for me and many others:

http://xdaforums.com/showthread.php?p=2023559#post2023559

Mine was AT&T.

Regarding the power management circuit, absolutely seems to be a bug.

Good luck!
[Google Pixel XL Questions & Answers] droid_1989:
Can anyone help me, I'm on DP3 but I still don't have the new icon on my Pixel XL. Considering I've just had this device brand new because my last one was was RMA'd any ideas why it's not appearing?
[Google Pixel XL Questions & Answers] uicnren:
ummm that is the new icon...
[Google Pixel XL Questions & Answers] droid_1989:
Oh so it's Google Launcher putting a circle around it, how ****. It looks better on my 6P.
[Google Pixel XL Questions & Answers] jhs39:
Your post has me confused. The round icons are the standard ones on Pixels. You wouldn't have the round icons on a 6P unless you were using a custom Rom that included them as a feature.
[Google Pixel Questions & Answers] jdkzombie:
Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.

It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.

I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.

ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.

Any body have any ideas?
[Google Pixel Questions & Answers] Sh0X31:
boot-to-root is for Android O, you have to follow this guide
[Google Pixel Questions & Answers] bdr9:
I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.
[Google Pixel Questions & Answers] jdkzombie:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.

Doesn't matter. Google is sending me a new one.

:/
[Google Pixel Questions & Answers] X04D:
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:

fastboot flash --slot _a boot boot.img

fastboot flash --slot _b boot boot.img

Then reboot normally.
[Google Pixel Questions & Answers] milan187:
falsh factory image inside the bootloader, don't need to go to recovery.
[Google Pixel Questions & Answers] ravcodesign:
Step by Step

Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.

So for the less patient I will break down the steps to do stop the bootlooping.

DON'T PANIC

Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.

Hold Power + Volume Down until it boots into the Fastboot mode.

[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]

Connect your Phone to your computer using a USB 3.0 port.

[My PC wouldn't recognize my phone at all when connected to USB 2.0]

Download from Full Factory Image from Google. { https://developers.google.com/android/images }

[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]

Navigate to where your SDK/Fastboot folder is on your PC

[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]

Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).

Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.

["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]

Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.

Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.

At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.

Good Luck.