yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] Ajay P:
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
[Moto G Q&A, Help & Troubleshooting] pfufle:
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
[Moto G Q&A, Help & Troubleshooting] pr.itdude:
I have a similar question.

I have unlocked bootloader & rooted moto g.

I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
[Moto G Q&A, Help & Troubleshooting] SoberDogs:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.

Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.

Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.

The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)

Another thread suggests that I should

fastboot erase cache
fastboot erase userdata

Is that a viable course of action? Has anybody been able to recover from this issue?
[Moto G Q&A, Help & Troubleshooting] skyguy126:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.

---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------

Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
[Moto G Q&A, Help & Troubleshooting] pr.itdude:
Ok. Few more Q pls:

1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?

2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?

3. Any other alternative to this?
[Moto G Q&A, Help & Troubleshooting] skyguy126:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.

2. Yes but you can easily uninstall xposed with the click of a button.

3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
[Moto G Q&A, Help & Troubleshooting] pr.itdude:
ok so Here what i am planning:

1. Uninstall all modules & xposed framework

2. Unroot using supersu

3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)

4. Install the update either manually via recovery or using auto install.

Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.

TIA. Cheers !!
[Moto G Q&A, Help & Troubleshooting] skyguy126:
Yep you should be good good luck!!!
[Galaxy S 4 Q&A, Help & Troubleshooting] Xanishftw:
Greetings,

I would like to ask, is it possible to install custom recovery and ROM on a Knox Bootloader without triggering Knox Flag 0x1. Please guide step by step or link me threads containing the instructions. Thanks!

GT-I9505

AP: I9505XXUEMKF

Baseband version/CP: I9505XXUAMDC

CSC: I9505OXXEMK3

Build Number: JSS15J.I9505XXUEMKF

SE for Android Status: Enforcing SEPF_GT-I9505_4.3_0024
[Galaxy S 4 Q&A, Help & Troubleshooting] DSA:
Look in general
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
http://xdaforums.com/galaxy-s4/general/guide-how-to-install-custom-roms-t2852310
[One (M8) Q&A, Help & Troubleshooting] Manguish:
Bit of history here :

I had rooted and flashed TWRP etc prior to 4.4.4

Once 4.4.4 came out OTA nagging annoyed me, so i went back to stock, stock recovery, unrooted but still S-OFF running Super CID.

4.4.4 then took via OTA no problem.

Nothing has changed on phone since. Yet lollipop OTA won;t take (Red Exclamation).

I'm on 3.28.401.9 (shown via settings)

Bootloader shows :

*** Software Status: Official ***

*** UNLOCKED ***

M8_UL PVT SHIP S-OFF

CID-HTC__001

HBOOT-3.19.0.000

RADIO-1.22.21331147A1.29G

As far as i'm aware, i'm on a fresh flash of an OTA upgraded KitKat, with stock recovery?

Any ideas why new OTA won't work?

Thanks in advance.
[One (M8) Q&A, Help & Troubleshooting] quattro_rs:
i have the exact same problem with exact same ROM HBOOT and cid !

only thing is my htc is rooted ..
[One (M8) Q&A, Help & Troubleshooting] Manguish:
I was unrooted and it didn't work. I then rooted it and tried again - still didn't work.

I've given up and am downloading the lollipop RUU to blast the whole thing back to standard.
[One (M8) Q&A, Help & Troubleshooting] quattro_rs:
looks like the only way for now :)
[One (M8) Q&A, Help & Troubleshooting] Daniel Son:
I had the same problem. Flashed a Nandroid for my device, went back to stock recovery for that backup and did not root. Worked a treat and I'm now on Lollipop. I'd suggest you try the same.
[One (M8) Q&A, Help & Troubleshooting] diwani4u:
Copy OTA zip to your laptop. Unzip it and find framwork.zip. use 7zip to browse firmware zip and extract recovery.img and flash this one, erase cache and try to install OTA. I had same problem by doing this OTA got installed.
[Xperia Z1 Q&A, Help & Troubleshooting] Flamejim:
I've tried several times (several different versions latest is the last version is 14.4.a.0.157) to remove the bootloader, I think its because I removed the bootloader earlier and than put it back (did that with the flashtool) on but the fastboot/phone still recognizes the earlier unlock because it hasn't been put back the correct way.

[IMG="try"]https://dl.dropboxusercontent.com/u/2327750/try-code-removed.png[/IMG]

So I was wondering has anybody found a solution? because I can't find it? (also searched XDA ...)
[Xperia Z1 Q&A, Help & Troubleshooting] BlAckXpeRia:
I think you dont know what you are actually doing.You are trying to unlock the bootloader.If you somehow really "remove" it, your device wont be able to boot.So I will assume you mean unlocking.

First, make sure your bootloader can be unlocked.Dial: *#*#7378423#*#*; then go to “Service info -> Configuration -> Rooting Status” and check if the “Bootloader unlock allowed” says yes. If the “no” answer will be displayed then you will not be able to unlock the bootloader of your device.

When you finish all the operations on the Sony site, you will receive an email with the unlock code.replace the word KEY with your code.

fastboot.exe -i 0x0fce oem unlock 0xKEY

From the screenshot I think you are not typing the correct key in there.

Note:You have to be sure that you have proper ADB connection with your device.Be sure you have enabled ADB debugging and have fastboot and adb drivers on your PC.

Here is a link with detailed explanation:

http://www.android.gs/unlock-bootloader-sony-xperia-devices-universal-tutorial/
[Xperia Z1 Q&A, Help & Troubleshooting] Flamejim:
Fixed

I already did it I had to make a folder(Flashtool\custom\mydevices\(device id)) and a text file in it (ulcode.txt) with just the code in it in flashtool and it worked, and I do now what I'm doing I just used the wrong word. You don't want to know how many times I already did the above.
[Xperia Z1 Q&A, Help & Troubleshooting] Robert_1968_:
I have the exact same issue, driving me nuts. haha I am now back on stock installed via pc companion but i have no working nfc and can not get into stock recovery. If I root the device dual recovery is still installed.
[Verizon Motorola Droid Turbo General] kraj123:
Hi,

I have updated the android L before 2 day.s.:cowboy:Can you please provide me the steps of downgrading to kitkat 4.4.4

Some Points

1. Bettery performance is not great compared to kitkat 4.4.4, Battery Saver On is not a new feature of lollipip

2.UI is not great compare to kitkat 4.4.4

3. FRequent button on the home screen, wondering what is the use of that
[Verizon Motorola Droid Turbo General] Sam_11:
On wich phone?
[Verizon Motorola Droid Turbo General] the_rooter:
your in the wrong thread. Lollipop has not been released for the turbo/maxxx
[Verizon Motorola Droid Turbo General] Pika71:
Mistaken...:p
[Verizon Motorola Droid Turbo General] r3pwn:
Well, for starters, it is likely that there is no way to roll back. It is highly possible that even attempting to roll back would result in a permanent brick (I wouldn't risk it if I were you).

Now, on to your points:

1. Battery Saver is, indeed, a new feature of Lollipop. Your device manufacturer (whoever that may be, because, as others have stated, you appear to be in the wrong forum) may have implemented their own version before, but Lollipop is Google's (pretty good) first attempt at a Power Saving mode.

2. I can neither agree or disagree with you because I don't know what device you have. Most people comparing (an un-skinned) KitKat to (an un-skinned) Lollipop say that Lollipop looks light-years better. (Do you happen to be using an HTC One M8? That's the only device I can think of that got uglier with Lollipop.)

3. I'm not quite sure what you're saying. By "frequent button", do you mean a link to the recent apps menu? You can change the Launcher (home screen) of your device to another one (Try this one: https://play.google.com/store/apps/details?id=com.google.android.launcher) and it will likely get rid of your issue. As you were not very specific or descriptive, there is a chance I may have misunderstood you.
[Verizon Motorola Droid Turbo General] Linexus579:
OK I know for a fact Lollipop hs not been release on the droid turbo haha.. secondly even if you had upgraded motorola often flashes the security partition that reads the build and rom information so that it would be impossible to downgrade even if you wanted to.. they started this way back in the droid 2 days
[Verizon Motorola Droid Turbo General] wadamean:
True true there is no way to go back and it has to be the droid max cuz turbo hasn't received 5.0. Maybe just maybe a FDR may get you back to KitKat but if your completely stock with no root and recovery.
[Verizon Motorola Droid Turbo General] r3pwn:
Nope. FDR just clears everything out of the "userdata" partition.

Quick Android Knowledge Session:

- Factory resets do nothing other than wipe the userdata partition (pictures, apps, accounts, etc.).

- When a software upgrade is downloaded, the device boots into recovery, and checks the upgrade to ensure that:

1) It IS an upgrade

2) It is signed by Motorola (so nobody can give a "fake" update to hack your phone)

- If those checks pass, the upgrade is "flashed", meaning it overwrites anything and everything in /system (this is why/how upgrades remove root, root is installed to the system partition)

- So therefore, Factory Resetting the device will do absolutely nothing to help him.
[Verizon Motorola Droid Turbo General] ChazzMatt:
Obviously posted from the future. The man has a time machine!

But if he has a time machine, why doesn't he just go back and tell himself not to upgrade to 5.02?

He is right that 4.4.4 is better for now -- at least on Moto Maxx, as we have root, TWRP, and Xposed modules to give us custom ROM features. Not so on 5.02.
[Verizon Motorola Droid Turbo General] prking07:
Wtf is this? http://www.lollipop-update.org/mp3-0/motorola-moto-maxx-6779.html

This obviously cant be true right?
[Verizon Motorola Droid Turbo General] the_rooter:
Obviously its false if u check out the picture. the maxx has physical buttons
[Verizon Motorola Droid Turbo General] ChazzMatt:
Obviously some kind of attempt to get you to install malware. The "about us" , "privacy policy", "contact us" and other buttons on that page all point back to the install page. Not a legit website.
[Verizon Motorola Droid Turbo General] phatwcinfrcr:
Ok, let's so...hypothetically speaking of course, that one may have accidentally flashed RSD 5.1 image to the phone but has not rebooted the bootloader. Would a flash back to kitkat work or brick it?
[Verizon Motorola Droid Turbo General] ntxct:
What phone model are you on? I believe this whole thread is for an international version. However if you're on the Verizon Droid Turbo (XT1254) and took an update that brought you to 5.1.. (outside of the recent discovery of yesterday) I'm sorry, you may have to wait a very long time if ever for someone to find a hole in the 5.1 bootloader...

If you followed the fastboot flashing to flash all but the 5.1 bootloader that was released yesterday, there is a way to go back, First post here

Without more knowledge about what you have and what you've done, thats all I've got.
[Verizon Motorola Droid Turbo General] JulesJam:
Once it is flashed, it is flashed. There is no way to unflash it and rebooting or not rebooting the bootloader doesn't affect anything.

Once you have flashed the partition table and the /motoboot partition with the 5.1 files, you have overwritten the 4.4.4 bootloader and partition table. There is no going back. Best case scenario if you try to flash back the 4.4.4 BL and PT you get a failure. Worse case scenario you get a brick.
[Verizon Motorola Droid Turbo General] phatwcinfrcr:
I'm on the XT1254. I did accidently flashed the new bootloader but did not reset (currently says BL: moto-apq8084-70.47 2014-10-30).

I tried flashing back, here is what I got:

D:\Home\Mike\Android\DROID TURBO XT1254\IMG\VRZ_XT1254_KDF21.128-15_15_CFC_SVC>f
astboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.101s]
finished. total time: 0.104s

D:\Home\Mike\Android\DROID TURBO XT1254\IMG\VRZ_XT1254_KDF21.128-15_15_CFC_SVC>f
astboot flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2159 KB)...
OKAY [ 0.071s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.356s]
finished. total time: 0.432s

I then flashed the 5.1 Boot, logo,radio, and recovery files like you are supposed to. Restarted bootloader and it says moto-aqp8084-70.3a 2014-09-24 software status: modified does not boot to the OS.

I then flashed the stock system img, with mofo, followed by the rooted and modified image with mofo. On reboot the moto logo flashes and goes right back to bootloader. Phone states unable to validate system image.

God I wish motorola/vzw would just unlock the forsaken bootloaders and quit being dicks to the customers.
[Verizon Motorola Droid Turbo General] JulesJam:
IME with the newer Motorola phones, you can downgrade everything but the bootloader and partition table provided the partitions have not changed in size w/o hard bricking. You may get a bootloop, but you will be able to recover from that by getting into bootloader mode and flashing back to the higher version files.

Where I have seen people get in trouble though is when they take an OTA and attempt to downgrade before the full images (fxz) of the newer firmware are available for their device. If they get into a bootloop and can get into fastboot, if they don't have a way to flash back the higher version files because no one has leaked a copy yet they are bricked until the fxz is released for their device.

But you can't downgrade the BL or PT. I have seen some people here say it is just the PT you can't downgrade and that certainly has not been the experience on the Moto X 2013 or 2014. On the MX, a BL-PT version mismatch causes problems as does attempting to downgrade both the BL and PT together. You either get a failure or you get a brick.

There are rare exceptions where you could downgrade the BL - I believe jcase used one of those rare exceptions to root the MX running 4.4.2. And according to some on the MX14 forum, you could downgrade the 5.1 soak test BL 60.14 to the 5.0 BL 60.11. But you needed to downgrade the PT too. Idk if that is true, just what they were reporting.

No one has reported being able to successfully downgrade the final 5.1 BL (60.16) to the 5.0 BL (60.11).
[Verizon Motorola Droid Turbo General] ntxct:
I have some good news for you, at this point the person with much more experience is here [MENTION=5983610]JulesJam[/MENTION]

I have some bad news for you.. from my perspective, this doesnt sound good :(
[Verizon Motorola Droid Turbo General] JulesJam:
Motorola is not the problem - Verizon is the problem. Motorola will allow any phone's bootloader to be unlocked provided that the carriers don't object. Verizon objects so the Verizon devices don't qualify for the bootloader unlock program with the exception of the dev eds. But as you know there is no dev ed for the DT.

---------- Post added at 05:57 AM ---------- Previous post was at 05:47 AM ----------

So your BL verision is 70.47 when you are in fastboot? That is the 4.4.4 bootloader?
[Verizon Motorola Droid Turbo General] phatwcinfrcr:
Yeah, sadly VZW is the only option where i am at... I have wrote their corperate HQ about it but no response. here is the addy for fun.

ATTN: Correspondence Team

PO Box 5029

Wallingford, CT 06492
[Verizon Motorola Droid Turbo General] JulesJam:
I am not familiar with the version numbers for the DT. But are you saying you have a bootloader-partition table version mismatch in that you are still on the 4.4.4 bootloader but have upgraded to the 5.1 partition table?
[Verizon Motorola Droid Turbo General] phatwcinfrcr:
That appears to be the original 4.4.4 bootloader version. However I can not confirm without a third party phone that was not flashed.
[Verizon Motorola Droid Turbo General] JulesJam:
Did you flash the 5.1 gpt.bin (partition table)?
[Verizon Motorola Droid Turbo General] phatwcinfrcr:
Yup

Additionally: I just flashed VRZ_XT1254_KDF21.196-8_8_1FF.xml and I booted to a clean 4.4.4 image. Trying to upgrade to rooted 5.1 now. :good: I will update
[Verizon Motorola Droid Turbo General] JulesJam:
I am not familiar with the DT version numbers other than 4.4.4 and 5.1 so I don't know what you are flashing. But in general, a BL-PT mismatch causes problems unless the partition table from the earlier/later version is similar to the newer/older PT.

If you are finding that you are stable with a BL-PT mismatch, then you may be able to get away with the version mismatch.

The good news is that whatever you did, you didn't upgrade your bootloader. The 4.4.4 BL can be exploited by mofo.exe. The 5.1 BL cannot be.

Also IME, you can flash the older PT just so long as it corresponds to the BL version you are running.
[Verizon Motorola Droid Turbo General] phatwcinfrcr:
Synopsis on what I believe occurred.

I accidentally flashed 5.1 but did not reboot the bootloader. I then flashed a old version of the BL which caused the system partition to not boot. After reflashing the correct OTA version of the bootloader the phone booted and I was able to update to rooted 5.1 with mofo. Maybe this will save someone one day. If you accidentally flash. DO NOT RELOAD THE BOOTLOADER AND TREAD CAREFULLY. 4 hours down the drain...who says stupidity is not it's own reward? Thanks for the assist!

I'll be balls deep in titanium backup if anyone needs me.
[Verizon Motorola Droid Turbo General] kitcostantino:
can anyone explain this?

Okay. First off, allow no false hope here. if you are on Lollipop, there likely is no help via what I am asking about. However, I have figured out that bootloader versions pictured on Kit Kat Droid Turbo are interchangeable. 70.47 and 70.3a both work on the 21.44.12 I am running.
[Verizon Motorola Droid Turbo General] kitcostantino:
Update: I have figured out this BL is the same *size* as the x1250. (2159kb) I may have put it in the folder with everything else at a point where I was gonna flash it. Again, this doesn't help lp peeps, but it may help kk peeps.

---------- Post added at 06:17 PM ---------- Previous post was at 05:21 PM ----------

Also, I have figured out we cannot manually or otherwise flash the xt1250 firmware. I tried. Lol. Mfastboot fails preflash validation on several things. System being one.

Update 2: fxz'd back to 21.44.12 with zero issues.
[Verizon Motorola Droid Turbo General] danger2u:
so?

can we downgrade from 5.1 to 4.4 with locked bootloader?
[Verizon Motorola Droid Turbo General] kitcostantino:
nope. not w/o bricking...and nothing says said brick would even be recoverable.
[Verizon Motorola Droid Turbo General] rriffle08:
What's sad is I have a spare turbo, and he wanted me to send it to him, said if it works he would give me mention me in the past for the phone, but he could never say I'll give you the phone back. It was like, will I'm pretty sure York get it back... F that. Thank god I'm a little smarter than that....

---------- Post added at 05:54 AM ---------- Previous post was at 05:52 AM ----------

Wow, and my spelling sucks, but hopefully you get what I'm saying.

What really sucks is that I realized this is in the wrong topic. Should have been at shiftydog root. Sorry
[Verizon Motorola Droid Turbo General] Cobra04:
Don't give that guy anything
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Askemaack:
Hello ppl's have looked everywhere online for someone whit the same problem as me but whit out luck so now I am crying out for help!

I have a problem i don't know how to solve, I have a Samsung Galaxy Note Pro 12.2 and I want to disable to button's (the return and the task bar button) I have found a couple of guides that all lead to the same conclusion

Which is: I need to write/edit in a script called "Generic.kl" located /system/usr/keylayout/Generic.kl

The problem is that when I rewrite/edit the script it comes whit an error "/system/usr/keylayout/Generic.kl: open failed: EROFS (Read-only file system)"

I have a custom ROM called hyperdrive installed

My device is rooted whit superSU and ES File Explorer have # (super user permission)

I have enabled ROOT Explorer, pressed it and mounted R/W set all to R/W after that in propperties change the file so that it say r/w under every domain

It diddent work whit ES Explorer so I tried Super Manager

My device is rooted whit superSU and Super Manager have # (super user permission)

I have enabled ROOT function and in propperties change the file so that it say r/w

I have spent a lot of time looking for a solution and I'm a sek away from giving up..

So there it is hope that there is someone able and willing to help me whit my problem
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Razvan:
Sir,

Please wait until mods will move this thread to the device specific forum for more relevant answers.

Stand by

Good luck