yashsingh1/xdaforums huggingface dataset:
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
right i got it now thank you

well i have lollipop 5.0.2 build 23.1.A.1.28

and i read some where it drain battery when the mobile data is on because the application on lollipop keep the connection on all the time so that person had to downgrade to kitkat

is that true?

if it's true then what would be the best Rom which wont drain battery when mobile data is on
[Xperia Z2 Q&A, Help & Troubleshooting] Skanin:
Well, I have not heard that story, and neither have I experienced it. I can use my phone with mobile data activated for 2 days without charging (stamina mode activated). However, I am now using the eXistenz ROM (lollipop ROM: http://xdaforums.com/xperia-z2/development/rom-existenz-y-1-0-0-preparing-thread-t3113649 KitKat ROM: http://xdaforums.com/xperia-z2/development/rom-existenz-ultimate-1-0-5-light-dark-t2835196), witch automaticly deactivates mobile data when my phone connects to a wifi network, and then activates it again when I disconnect from the wifi network. The battery holds for a very long time with this ROM aswell.

You have to experiment, and experience for yourself what is best for your daily use of you phone :)
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
so if i want to install this Rom i do these steps

From Stock Sony Lollipop:

Backup your datas.

Reboot in recovery.

Flash the rom.

If something went wrong, do a fresh install.

but how to reboot in recover dos stock Rom have recovery

also what about Fresh installation:

LOCKED & UNLOCKED Bootloaders

Flash latest rootable Sony's rom with flashtool (http://xdaforums.com/show....php?t=2162907)

Root

Install NUT dual recovery (http://xdaforums.com/show....php?t=2261606) or the recovery of your choice.

Reboot in recovery, Wipe Data, Cache and Dalvik/ART Cache.

Flash the rom.

1- what is rootable Sony's rom

2-what dos he mean with Root

3-what is NUT dual recovery

4- will this steps make my phone boot-loader unlocked?
[Xperia Z2 Q&A, Help & Troubleshooting] Skanin:
First, let me say sory for the slow reply, I was working :p

1. The latest rootable rom(or rootable firmware) is the last firmware you can root. At this time, root for Lollipop can only be done by downgrading to KitKat, root, install recovery and then flash either a Custom ROM, or a Lollipop zip file. So the latest rootable ROM for sony xperia z2 is now KitKat, buildnumber 17.1.2.A.0.314.

2. Root itself is just a user with elevated permissions, who can do anything to any file or folder in the system.

3. NUTS dual recovery is a set of two recoveries, TWRP and ClockworkMod. These are just two different recoveries, and can do pretty much the same, however someone likes TWRP over ClockworkmMod, and opposite. Stock ROM(Or Stock firmware) does NOT have recovery installed. To get recovery on Lollipop, you have to downgrade to KitKat, root, and install recovery.

4. No, this steps will NOT unlock your bootloader. To unlock your bootloader, you have to go to Sony's website, type in your device' IMEI, your email and get a code. Flashing a Custom ROM will NOT unlock your bootloader. :) (If you want to unlock your bootloader, here is the link to Sony's webisite: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/).

A fresh insallation is when you wipe all data, and your whole phone. (Pretty much a factory reset) and then flash the rom. The ClockworkMod recovery even has an option who says "Clean to install a New ROM." witch is a fresh installation

Stock firmwares for Lollipop and KitKat can be forund here: http://xdaforums.com/showthread.php?t=2759934

Don't be afraid to ask if there are anything else you are curious about! :)
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
so now to installthe eXistenz ROM i'll do this steps

1-Backup My datas.

2-downgrading to KitKat.

3- Root

4- install recovery

5- and then flash the eXistenz ROM

or i wont need this steps and can flash the eXistenz ROM right away
[Xperia Z2 Q&A, Help & Troubleshooting] Skanin:
If you have recovery now, you can flash it right away, but if you do not have recovery, that is your steps! :)
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
how can i tell if i have recovery or not
[Xperia Z2 Q&A, Help & Troubleshooting] Skanin:
Turn of your phone, and then boot it again, If it vibrates and the led lights up, you have recovery.
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
it did not
[Xperia Z2 Q&A, Help & Troubleshooting] Skanin:
Then you do not have recovery
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
well i can't writ to my SD card

i can't save office files to it

i can't you use file commander to move files from internal memory to sd card

my camera make unknown error when i try to record video and select SD card as storage

how can i be able to writ to my sd card and save files to it
[Xperia Z2 Q&A, Help & Troubleshooting] Alex Charles:
Use a PC or something similar (card reader, spare phone etc). Be careful though, make sure you don't wipe he system if you can't read the memory card, it's ok to factory reset, but if you wipe the system partition and you can't access the ROM files on your memory card from recovery, you won't be able to use your phone until you can get one that reads (or phone repaired). a factory reset option is all you need from recovery for most things though, so only "wipe to install a new rom" if your card definitely works! Worst comes to worst and something did happen, flashtool should have your back anyway :)
[Xperia Z2 Q&A, Help & Troubleshooting] @pharaon:
how can i let office get Editing access to files on SD Card
[Xperia Z2 Q&A, Help & Troubleshooting] mr.loverlover:
You have to be rooted. Then you download sdfix for kitkat (works on lollipop too) from play store, run it and you're done.

Sent from Xperia Z2

Luckily not from an iPhone = Yesterdays technology at tomorrows prices
[Android General] sytechcomputers:
I bought a samsung gt-i9500 yesterday with the original software on it and decided to to upgrade with kies to the latest version 4.4.2. I then proceeded to try and obtain root via kingo which takes and keeps failing after a while. Tried towel root -device not supported possibly because of a updated kernel release with the latest upgrade. Anyway i thought after playing around go see if i tripped the knox flag.....indeed i did. Status also changed to custom. Tried downloading super su chainfire for the time that the root actually works before failing......made kingo user crash. Restarted my device and my statust changed back to OFFICIAL and knox flag 0x0........thought i share this with you guys.
[Galaxy S6 Q&A, Help & Troubleshooting] dtlaon:
hi guys

i have galaxy s6 from Canada my brother bought it for me

the problem is that i'm from Israel and my device says that is network locked is there a way to unlock it?

i paid for a unlock cod to open it from the Canadian "unlock.canadagsm" website but it didn't do anything

can anyone help me please???
[Galaxy S6 Q&A, Help & Troubleshooting] thatsupnow:
I unlocked my Bell phone without a new sim card. I had my unlock code and in dialer #7465625*638*# and I input my code there and it was successfully unlocked
[XDA Assist] Qwerty0105:
How to root Galaxy A3(sm-a300f) Lollipop 5.0.2 ???
[XDA Assist] Razvan:
Hi there,

Take a look at this discussion:

[SOLVED]+[GUIDE] Root for Samsung Galaxy A3 SM-A300F (Lollipop 5.0.2)

Ask in that thread or in this general: [HELP THREAD] Ask ANY Question. Noob Friendly.

Good luck
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
I would urge you to reconsider locking your bootloader. There's no reason to unless you are returning it for repair.

With that said, if you really want to relock, follow this guide > http://xdaforums.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Thank you, I've been reading that thread already. But as I said, whenever I try to lock the bootloader I get "start with fastboot oem lock begin" followed by the error message written in the thread title. Also when trying to flash the factory image with the flash-all.bat file, I end up with the error message "Error: Update Package Missing System.img".
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
Flash all doesn't work. You'll need to flash each .img file separately. And make sure your Android SDK is up to date. Google updated fastboot back in November to enable flashing the very large Lollipop system.img.
[Nexus 6 Q&A, Help & Troubleshooting] GuestK0087:
Flash all doesn't work. You have to flash the images individually. Follow method 2 in the sticky thread in general forum. :)
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Thank you. That was my guide when I flashed the image manually. But I'll give it another go soon. :)

Update July 7th 2015

Nope. No matter what I do, there's always the same error message. Has anyone ever managed to relock this thin anyway? I actually need it as I want to return it.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Seriously, has anyone an idea why I can't relock my bootloader? I tried it as described in these methods posted above but no luck. I must be overlooking something. I'm not doing it for fun either; I have burn ins on its AMOLED panel and the earpiece doesn't work so I have to return it for RMA.

Also my post from another thread with further information:

[MENTION=5020010]Mr_S[/MENTION] have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message

...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s

Turns out I have to type

fastboot oem lock begin

first, then flash a factory image and end the process with

fastboot oem lock

However that doesn't work as upon finishing flashing BL and radio .imgs, the updater script tells me that system.img is missing, press any key to exit. The process aborts. Ending this process with

fastboot oem lock

gives out the same error message as above. Flashing the factory image manually and it's the same all over again. Now I'm desperate for a solution.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
My guess is not flashing something right. Start from scratch. Flash all the images. Reboot. Make sure unlock is checked in developer options. Then fastboot oem lock. Never seen the fastboot oem lock begin message. Here are all the correct fastboot commands. No need to really run the erase and format commands but don't hurt except will have nothing to boot which is good enough for RMA. lol

Drag and Drop or Copy/Paste Images to {}

STEP #1

fastboot flash bootloader {bootloader.img}

fastboot reboot-bootloader

fastboot flash radio {radio.img}

Step #2

fastboot erase recovery

fastboot erase system

fastboot erase boot

fastboot format vendor {don't need for phone}

fastboot format cache

fastboot format userdata {optional}

Step#3

fastboot flash recovery {recovery.img}

fastboot flash system {system.img}

fastboot flash boot {boot.img}

fastboot flash vendor {vendor.img}

fastboot flash cache {cache.img}

fastboot flash userdata {userdata.img}

fastboot reboot

adb reboot bootloader

fastboot oem lock
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
Heres how. flash this bootloader: http://xdaforums.com/attachment.php?attachmentid=3399990&d=1436618712

Using

fastboot flash bootloader Teamkang-Shamu-Bootloader-Flashable.img

And then do

fastboot oem lock

and you should be locked.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
That is an unknown process and shouldn't be used. Should never blind download. Learn to do it correctly or don't do it at all. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
True but it works. you can just put the orginal bootloader back if you want if it wont work.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
This could also brick the device since no one knows where it comes from. Also for RMA it would have a bootlegged bootloader that may not pass RMA inspection. His problem has nothing to do with bootloader. There is nothing wrong with the stock bootloaders. I lock and unlock all the time. XDA is here to develop and teach. Although it does encompass hacks we prefer that they learn why it works and understand the repercussions. Blind downloading files is not a good idea unless don't mind bricks and spyware. :cool:

---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ----------

Did you unzip second folder in image to get get all the images. The flash all bat doesn't work. Never used mfastboot. No need for it. Looks like you trying full image. Need to unzip it all and use the single images. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
No, I actually unzipped the folder. As you can see in the CMD log, I flashed the content of said zip file (system.img/recovery.img/boot.img/userdata.img/cache.img) manually using both mfastboot and the commands you posted above. Rersult is the same. Also, this is shown in BL in "Bootloader Logs" (see attachment below).

cmd: oem lock
hab check failed for boot
failed to validate boot image
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Looks like all flashes took. Did you boot the phone before trying to lock it. :cool:

---------- Post added at 12:49 PM ---------- Previous post was at 12:44 PM ----------

Also could have corrupted image with corrupt boot.img from download. Have seen that before. I had corrupt system.img before. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Redownload the image or find a stock boot.img. That looks like the problem. Boot.img is corrupt in that download.

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
Like prdog said try another 5.1.1 shamu boot.img i have this boot.img from eariler today that i can confirm works. as i flashed it 2 hours ago
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
That's the weird part. It's not compressed but a naked boot.img missing almost 5mb. Not sure, but it looks kinda shady... As soon as the download is finished I'll post the update.

-------------------------UPDATE---------------------------

Download finished. Flashed the whole package manually with the commands you posted. Still getting the same error message :'(
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Good call. Your thinking now. :p:cool:

On a side note I locked mine for grins and softbricked it. :rolleyes::laugh::cool:
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
How did it get soft bricked?
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Don't know. Went into the boot/recovery bootloop. Was still able to unlock. Flashed boot.img and stopped the loop. Must have killed system.img also. Playing one image at time now to learn. :rolleyes:;):cool:

---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------

Back up. Looks like lock broke IMO's lean kernel. Flashed stock boot image and took two reboots to get back up. :good::cool:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Could someone post a screen from an unlocked SHAMU bootloader?
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Will say unlocked at the bottom. Not much else to see. Says locked or unlocked and status 1-3. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Thank you. What does the top line of BL say with the BL unlocked? Is it supposed to say "AP Fastboot Flash Mode (Secure)" in unlocked state?
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
It will say unlocked and status:2 at the bottom , status 3 when the BL is unlocked.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Can't see mine right now. It restoring. :p:laugh::cool:
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
Yes, but also will say that in locked state afaik.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
So, right now, I tried all the things suggested in this thread as best as I could. Still getting this:

...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s

Also, what I find interesting is what the Bootloader Logs say whenever I type

fastboot oem lock begin

then flash factory image, then

fastboot oem lock

After these commands, the "Bootloader Logs" menue item lists following text:

cmd: oem lock begin
cmd: oem lock
hab check failed for boot
failed to validate boot image

I got my hands on a Mac and even though it shouldn't be a PC problem, I'm gonna try it on Mac OS. Wish me luck, as otherwise I'm f'ed... :crying:
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
[MENTION=2743227]gee2012[/MENTION]. Looks like those that had the recovery/boot bootloop had an easy way out as long as didn't lock before first boot and enable unlock in settings. It just broke my boot image. Unlocked and flashed boot.img. Took 2 reboots to crank. First boot was black screen. Went back to bootloader and fastboot reboot cranked it. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Yes, I am pretty sure since I downloaded LMY47d/i/z and all of them have boot.imgs at least 7,5MB in size.

----------------Update---------------

Something more interesting; I noticed that upon flashing boot.img via "fastboot flash boot boot.img", the Bootloader Logs lists "Mismatched partition size (boot)".

-------------Update------------------

I found something new. The command "fastboot oem lock begin" has to be entered AFTER the first two(2) reboots after bl and radio flash, BEFORE starting with the other imgs. However, if I do that, fastboot returns the following message

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z-factory-33951732\shamu-lmy47z\image-shamu-lm
y47z>[COLOR="Red"]fastboot oem lock begin[/COLOR]
...
[COLOR="red"](bootloader) Ready to flash signed images[/COLOR]

OKAY [ 0.121s]
finished. total time: 0.123s

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z-factory-33951732\shamu-lmy47z\image-shamu-lm
y47z>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (7731 KB)...
OKAY [ 0.252s]
writing 'boot'...
[COLOR="red"](bootloader) Preflash validation failed
FAILED (remote failure)[/COLOR]
finished. total time: 0.271s

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z-factory-33951732\shamu-lmy47z\image-shamu-lm
y47z>

Important commands highlighted
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Thank you. As I hope you'll understand, I'm hesitating to flash a boot image on my 600€ device that deviates remarkably in size from all the official boot.img I came across so far. If everything else fails....
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Still looks to me you have a bad factory image. Never seen any of these faults. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
400€. it fell in price on the gpe store ;) but a boot.img can't even brick a phone. worst case you can just flash the stock boot.img again. or factory image. but i can promise nothings wrong with it though. maybe somethings wrong with your downloads?
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Try this one. https://dl.dropboxusercontent.com/u/30190874/5.1.1 Boot.image.zip Extract and fastboot.
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
Sorry dude XDA somehow broke my upload :( happy you didn't flash that! heres the real 8mb one.
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Hahah. Alright. I downloaded the boot.img you attached but it gave me the same error =(. See

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z-factory-33951732\shamu-lmy47z\image-shamu-lm
y47z>fastboot flash boot bootteamkang.img
target reported max download size of 536870912 bytes
sending 'boot' (3806 KB)...
OKAY [ 0.125s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.143s

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z-factory-33951732\shamu-lmy47z\image-shamu-lm
y47z>

Downloads seem to be fine as the boot.img you sent also resulted in the same error message.

What the hell is going on :crying:

-----------Update----------

[MENTION=6819117]Teamkang[/MENTION] Just saw your post after I already replied. Will give the boot.img another go but I don't think it'll change anything =(

--------Update-------------

See this thread talking about the exact error message I'm getting in OP http://xdaforums.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827

According to this, the errors I get only occur on an attempt to downgrade. But I'm not downgrading, I'm flashing imgs of the same build that were already on my device.
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
Try the boot.img i attached (The 7.8MB one) somehow xda wouldn't upload the other boot.img correct.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Why you got all this in command line.M:\SHAMU\FACTORY IMAGE\shamu-lmy47z-factory-33951732\shamu-lmy47z\image-shamu-lm

y47z>fastboot flash boot. Mine is:

C:\Users\PrDawg>fastboot boot boot.img
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
That's just my folder structure. I'm too busy solving this. But you're right, I should reorganize it. What's also weird is that whenever I flash a factory image on my N6 64GB, the device will show only 23GB of total storage. To get back my original space I have to reboot into stock recovery and make a factory reset.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Formatting userdata will fix that also. fastboot format userdata. The 23 GB ususally shows up with flashing Verizon E or the M builds. Format userdata will fix it without losing data. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Again....the same error message =(

How likely is a hardware or bootloader malfunction that won't let me relock my bootloader? The phone was sent for repair once after the battery inflated whereafter the battery was replaced. The RMA documentation says that a system update had been performed on it.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
If flash new everything should be good. Not sure what that long shamu string is doing to it. Must not have environmental variables set on PC as could open command prompt anywhere and just tell it to fastboot. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
Very small i would say. bootloader maybe. but something else no. and try this

fastboot erase boot

if that even exists? and try flashing boot.img again with this method it may work:

fastboot erase boot
fastboot flash boot boot.img
fastboot reboot-bootloader

Try it it may work.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Possible an erase could fix. Images may be overlapping in partition. :cool:
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
I set up adb and fastboot to work from anywhere via Windows variables settings. But that shouldn't be an issue.

Did. Still the same error.

Is it possible to flash a factory image via RSD Lite? I mean motorola provides Nexus Factory Images and I'm downloading one from their servers right now. Wish me luck.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Good luck. LMAO:cool:

---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------

If have the variables set should just open command prompt and should look like mine. No need for all that Shamu stuff in command line. Just fastboot whatever.

:cool:
[Nexus 6 Q&A, Help & Troubleshooting] Teamkang:
Good luck
[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
Nope... Still the same error messages, except that the factory image provided by motorola looks different (see attachment). Anyway. I opened up a thread over on motofirmware to see if there's someone who can help me. For now I can only thank you guys for your time and efforts. I'd hug you right now if I could. Thank you :)

Feel free to post updates or new ideas.
[Nexus 6 Q&A, Help & Troubleshooting] prdog1:
Yea. Only difference is Moto breaks system into chunks that have to be flashed separate. Fastboot does same thing automatically. :cool: