yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 5] caderyn19:
Hi everyone. Thank you for reading.

I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.

Any insight would be much appreciated. Thanks again!
[T-Mobile Samsung Galaxy S 5] gspears:
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.

When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
[T-Mobile Samsung Galaxy S 5] caderyn19:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.

As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
[T-Mobile Samsung Galaxy S 5] gspears:
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.

Good Luck with it.

If I've been helpful, please hit the thanks button.
[T-Mobile Samsung Galaxy S 5] caderyn19:
That's what I figured... Thanks for your help! (I hit the button :P)
[T-Mobile Samsung Galaxy S 5] elesbb:
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.

But yeah, stick to XDA from now on :) We are good people here :) Welcome to the family! :D
[T-Mobile Samsung Galaxy S 5] caderyn19:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
[T-Mobile Samsung Galaxy S 5] elesbb:
Well get your friend over here too! :P
[Xperia Z2 General] lee480:
FIX UNMOUNTABLE SYSTEM AFTER ROOTING

Let's keep this short and simple.

This allows you to mount system even if you root.

Flash this and thank me. :\

Jokes aside. Just hit the download button.

Technical details:

This disables RIC service and the script is by NUT. RIC prevents R/W when system is booted.
[Xperia Z2 General] Ningyou Higeki:
Thx for your work!
[Xperia Z2 General] Yapperzitata:
Sorry but when do you flash this?
[Xperia Z2 General] lee480:


If your ROM cannot mount system.
[Xperia Z2 General] Yapperzitata:
Still can't mount... no errors during flashing
[Xperia Z2 General] lee480:
Try this:

Flash this:

http://nut.xperia-files.com/files/remountrebootfix.zip

After flash my file.

EDIT:

I found the issue, and zip file didn't set the correct permissions for the script. I'll fix it asap.

If you want it now, go to recovery and press 'fix permissions '.
[Xperia Z2 General] FabianLaRose:
Thanks a lot. After 2 days searching i found this. Works like a charm:highfive:
[Xperia Z2 General] MrCatalyst:
Had an issue with /system, and this has fixed it. NC works, I can still use Xposed, AdBlock, and change my DPI. THANK YOU! :D
[Xperia Z2 General] Lagamorph:
Don't suppose there's any way to fix this without a custom recovery is there?

I've rooted but can't mount/write to my System folder after doing a 4.4.4 OTA update, but I don't have a custom recovery installed. I just rooted using the toolkit and left it at that.
[Xperia Z2 General] sjamajee:
Doesn't work :(

Lost root completely after flashing the zip files
[Xperia Z2 General] ffarber:
For me it didn't fix the system mounting issues (won't mount R/W in either Root Explorer or Xposed) but I still have root.

Fred
[Xperia Z2 General] defsix:
Same as that. had to go back to Doom's CWM Stock Kernal to get system RW
[Xperia Z2 General] ffarber:
Will that kernel work with the stock 4.4.4 software?

Fred
[Xperia Z2 General] kulvertti:
All of you who found that this ain't working, it is because you need to have correct busybox installed. After you have that it works as mentioned.
[Xperia Z2 General] defsix:
I have 1.20.2 version of Busybox installed. Which version are you suggesting?
[Xperia Z2 General] kulvertti:
This is part of @Nutˋs XZDualrecovery and designed to work with busybox that is installed with that. With other busybox it may work or may not.

--
[Galaxy Note 4 Themes and Apps] KiingEdmund:
Here are some wallpapers off my computer. Looks good on the Note 4. Enjoy.
[Galaxy Note 4 Themes and Apps] wEaKlY27:
I love it!
[Galaxy Note 4 Themes and Apps] ElAguila:
Do you have them in a zip or rar file we can download?
[Galaxy Note 4 Themes and Apps] KiingEdmund:
na sorry but i can give you the link to where i got all of them from. http://wall.alphacoders.com/by_resolution.php?w=3840&h=2160&page=49#
[G 2014 General] Hitesh2626:
.:)

EDIT : You can downgrade via Fastboot not mFastboot.
[G 2014 General] ghostcoder:
Bootloader warning

I followed the steps exactly , and the only error occurred was the one you mentioned ,

but the "bootloader unlocked warning " still remains after i flashed the logo

what is the soulution ?

thankyou,
[G 2014 General] archies20:
Good job hitesh :good:
[G 2014 General] Sebastian94:
If i relock the bootloader will miss the root?
[G 2014 General] Hitesh2626:
Yes.
[G 2014 General] Hitesh2626:
Thanks buddy , just i cleared all doubt's and errors .
[G 2014 General] Hitesh2626:
First just check the Bootloader status in bootloader menu , if it is locked then just flash the logo.bin that's it .
[G 2014 General] linasmit:
OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).

Later in your post:

Note : Don't try to lock the boot loader after flashing the firmware it will give you error like

sst lock failed.

This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).

This guide is misleading.
[G 2014 General] Hitesh2626:
You are not getting properly , i told that after flashing firmware and after booting it , then taking back into boot loader now in these state if you will give command then it wont work !!

That's the point i have explained in that Note .

And above what ever i have written it is 100% working not only tested by but also some other users .
[G 2014 General] Anonymous 360:
Cannot relock bootloader

I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.

The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.

While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.

Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.

Applied flash according to :

my mobile version info is attached
[G 2014 General] pradeepmaddy:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image :( plz help me to get out of here plz:(:(:(:crying:
[G 2014 General] Anonymous 360:
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....

please, inform me, if it works
[G 2014 General] StariX37:
The user u have quoted is trying to lock the bootloader for Global version retaildsds.en03

If it works then its well & good..
[G 2014 General] Anonymous 360:
Solved! Solved! Solved!

YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!

After lots of flashing, at last ::fingers-crossed::D

followed these steps:

after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))

reboot and copy your lollipop update file (same variant) to the internal storage

now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img

Now go to recovery and select your lollipop update... ta-da.... explanation:

After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.

Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.

apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish

You dont need to lock the bootloader at all :good: :good: :D

Hit thanks if it helps
[G 2014 General] savnex:
Do you still have your device rooted after lollipop update?
[G 2014 General] pradeepmaddy:
bro am in kitkat now... i dont want to go with us variants again but i want to lock boot loader in kitkat itself please give me the solution for tht
[G 2014 General] Anonymous 360:
I afraid I do not have a solution......

---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------

You still have SU app, but you will not have the binary, so you have to appy CF auto root : http://xdaforums.com/moto-g-2014/help/solved-cf-chainfire-autoroot-problem-t2942154
[G 2014 General] Iruhoru:
Help please

I've got an XT1068 bought in UK.......and stuck with the same problem after upgrading to lollipop (xt1063 way) and downgrade.

I cant' lock the bootloader and if I install a stock firmware trying to locking it i receive a lot of FAILED messaged (in partition,motoboot,boot, system system.img_sparsechunk1-2-3....) And can't lock with "SST lock failure ! failed to validate system image" error.

What I have to do? T_T Can someone help me please? I want to bring back everything as before...clean!

If I try to install a stock rom and i don't try to lock the bootloader i receive FAILED error only in the first 2 strings

mfastboot.exe flash partition gpt.bin

mfastboot.exe flash motoboot motoboot.img

and this never happen. What I have to do for locking the bootloader again? :\ I try with fastboot instead of mfastboot commands too..but...same results.

Thanks.... :crying:
[G 2014 General] smitharro:
After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.

So, if you have, for instrance, an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.

So in short: after a downgrade (as from Lollipop to Kitkat) it's impossible to lock the bootloader!

Please correct me if I'm wrong!
[G 2014 General] Tonal4Nagual:
According Motorola downgrading from lolipop to kitkat is not possible :)

Moto G (2nd Generation) - Android™ 5.0 Lollipop - Release Notes

INTRODUCTION

We are excited to announce a new software update for Moto G (2nd Generation) by Motorola. This update brings Android™ 5.0 Lollipop to your phone along with other improvements.

For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.

NOTE: You cannot downgrade to a previous software version after installing this update.
[G 2014 General] smitharro:
Just like I said: not officially, no!

Of course it's possible to downgrade (many people did that already) but the bootloader cannot be locked again after that! (we would need some bootloader hack for that, also for setting the status code of the bootloader back to 'status code 0' instread of 'status code 2' after a succesfull relock)
[G 2014 General] Tonal4Nagual:
Yes I know , but relocking bootloader is some kind of "want to be official way" :)
[G 2014 General] pradeepmaddy:
So I can lock bootloader after lollipop update that means if I get ota ... It s possible to flash the lollipop build manually again to relock bootloader?
[G 2014 General] smitharro:
I suppose yes... If you can get your hands on an official build! (And I suspect that, soon after the official release, to be here on XDA somewhere). But I'm afraid I'm can't give you any garantees.
[G 2014 General] pradeepmaddy:
What will happen if can't able to flash the lollipop firmware ?
[G 2014 General] smitharro:
People who want to be 'the official way', don't really need to come here... This is XDA!! But I know why many people want to relock their bootloader: they want the OTA of Lollipop! But they've 'messed up' their device already... Regrets always comes after the sin! I can tell, because I'm one of them! I was just lucky to find een newer build and was able to relock again!

Honestly, I don't think that just an unlocked bootloader wil stand in the way of an OTA. As long as you have a stock recovery, are unrooted and did not mess up any system files.
[G 2014 General] pradeepmaddy:
hey dude i knw tht too ...y am asking s i tried to lock while downgrading to kitkat i failed to lock ..... and i wont lock again am just asked for clarification
[G 2014 General] androidcrazy1601:
Hi dudes,

Apologies if I am repeating the same question. Just needed the clarity. I am about to unlock BL and root my XT1068 Indian version. I have posted my system info.

I want to unlock the boot loader only to root my phone. I don't want to install any custom ROM. Interested only on lollipop update. From unlocking guide, I see that we need to replace original recovery with TWRP recovery to install Superuser.

in this case, ORIGINAL RECOVERY IS REPLACED.

I have a slightly higher version of firmware to flash back the stock in case if I get any problems. Changes are only in build number.

Current build: KXB21.85-23

Firmware to flash build: KXB21.85-27

If I want to get lollipop update, is it enough if I just unroot using full unroot with SuperSU app or I should lock the boot loader as well? Because stock recovery is replaced.

If I want to relock the boot loader for lollipop update, will I be able to do by flashing the different build which is higher than the current build :confused:
[G 2014 General] NWKENT:
Locked or Unlocked bootloader, has absolutely NOTHING to do with taking an OTA..the OTA looks for a STOCK recovery..if the STOCK recovery is not present, the OTA will fail..simply flash back to stock recovery..I have had to erase devices before, even revert to a clean system before an OTA will pass..make backups of precious content before doing anything..

Try reverting to stock recovery first, before attempting the OTA..if it fails..probably will need to flash stock firmware, if an erase system doesn't pass..anotherwords, if OTA fails the first time, do a full erase, except for internal storage, and try the OTA again..

An OTA could care less about locked or unlocked bootloader..besides, I'm pretty sure as of two weeks ago, the bootloader cannot be relocked anyway, unless someone has found a way to relock as of two weeks ago..I do not like, (at this point) Lollipop, a few more OTA's and Google will probably work it all out..I reverted and will stay there for at least a couple more OTA's..

FIRST and FOREMOST..I miss XPosed and Gravity Box..the status bar icons, look very cheap in Lollipop, as does alot of other features..the animations are nice thow..add the animations, and some other features from Lollipop to Kit Kat and Google would have an awesome OS..just me thow, what do I know..lol

BTW..as long as the fastboot version stays the same, reverting is possible..also a higher version of OS firmware can present problems sometimes..be sure and have the current version (on the device now)..on hand, before doing anything..for insurance..

ANOTHER note: if you have TWRP and SuperSU and are officially Rooted..then make a "known good" backup..and store to a hard drive, So if you brick, then you have TWRP backup to restore to the present setup..which is what I always do..more insurance..

But..this is my personal experience with the XT1064..not the model mentioned in your posts..

Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
[G 2014 General] gvala:
Search for a thread that explains how to boot in custom recovery without actually flashing it.this way you can preserve the official bootloader and whenever needed you can have custom recovery to flash whatever you like. I'm not at home so I can't find the thread right now.

Found it

http://xdaforums.com/showthread.php?p=57092904

It works on lollipop of you have the correct twrp image

Στάλθηκε από το XT1068 μου χρησιμοποιώντας Tapatalk
[G 2014 General] androidcrazy1601:
[MENTION=328028]gvala[/MENTION], thanks a lot dude. I will try this. :thumbup:
[G 2014 General] tbiwalkar:
Help Appreciated!

I relocked the bootloader but when i did , I got an error saying 'too many strings' or something

However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)

However i gave a 'oem lock' command again.

I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.

I could Still flash the warning remover 'logo.bin' file

Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
[G 2014 General] smitharro:
I'd did a relock of the bootloader too a while ago. The warning also stayed. I was still able to flash the logo bin file and the warning was removed. A couple of days days ago I unlocked the bootloader again. Warning is back too. I think everything is OK. Just flash the logo bin and enjoy being locked...

Send from my XT1068 using Tapatalk.
[Galaxy Note 4 Q&A, Help & Troubleshooting] polish_pat:
Hey guys,

I've been having some issues with an international rom on my W8 and i decided to go back to stock with odin. As i was flashing i realized that everytime i would reboot, even after a factory reset, or data/system/cache wipe, all my file and folders were not erased. So i booted into TWRP and wiped internal SD and all the other stuff, then flashed back stock rom with odin and now i keep getting this error:

Basically i start flash process and about 30 seconds in i hear the phone disconnect and i get the fail. I know it's not a bad firmware download as i've lready flahsed it 5 times today, i know it's not cable, or USB port because until i wiped internal SD i did not have any issues. Now, i can still access download mode, but i cannot access recovery because it tells me "firmware upgrade encountered an issue. Please select recovery mode in kies and try again." When i connect it to kies, it simply says phone not supported and doesnt show up under emergency recovery.

Anybody know how to get me out of this mess??
[Galaxy Note 4 Q&A, Help & Troubleshooting] polish_pat:
weird, my note 4 cable was causing the issue. I took my old S2 cable and it worked. Thanks anyways
[G 2014 Q&A, Help & Troubleshooting] zoomingrocket:
Hi,

I can see there are 2 US retail firmwares on http://sbf.droid-developers.org/phone.php?device=36

Which one should i use to restore a Consumer Cellular version to standard US Retail, also if you point me the steps guide using adb that would be great.

Also, would i need to unlock bootloader before flashing the retail version?

Thanks.
[G 2014 Q&A, Help & Troubleshooting] Trekker56:
Any way to flash lollipop update to consumer cellular branded Moto g 2014?
[G 2014 Q&A, Help & Troubleshooting] zoomingrocket:
Please check this link, i finally managed to downgrade to US Retail from Consumer Cellular version and flash lollipop via adb recovery!
[8125, K-JAM, P4300, MDA Vario General] forme:
I have 4meg when i use the WM5storage read it only see 3meg. Why i lost 1meg. Is the phone can only limit to hadle certain memory only???Thx.
[G2 General] kryptonite:
Force Phone into QDLOader 9008 mode (Only if needed)

YOU DO NOT NEED THESE STEPS IF YOUR PHONE IS ALREADY IN QDLoader 9008 mode.

If you have to force your phone into QDLoader 9008 mode please follow below, thanks to [MENTION=3037999]mss1988[/MENTION]

Here is some extra Information I got while digging around.

This app operates only in Qdload mode. Upon initial USB cable connection, do the following to send it to Qdload mode if no port or USB serial port is held.

Upon initial USB cable connection, don’t do the following if it’s already in Qdload mode.

Use either way below(#1 recommended) to connect the USB cable while the pin is grounded.

Check out the Device Manager for ports(COM or LPT). If Qualcomm HS-USB Qdloader 9008 port is activated, Qdload mode is successfully

ready to work!!

As for the USB cable, the SW download cable v2.1 (910K) for service is recommended!!

1. How to ground Boot Config switch

It may depend on models. Basically, the pin of the switch connected to Boot_config_0 or Boot_config_6 is grounded.

The circuit diagram above shows Q6000 switch’s #3 pin need be grounded.

2. How to ground EMMC SDC1_CLK resistance

It may depend on models. Basically, eMMC’s SDC1_CLK resistance is grounded.

The circuit diagram above shows R24010 need be grounded.
[G2 General] Use2:
Hmm,my phone is shown in the device manager as LGE Android Phone,CDC Serial and CDC ECM

what should i do?