Today I was able to flash the stock moto E firmware on my friend's moto E without unlocking the bootloader.
Does this mean the stock recovery identifies official firmware?
Is it possible to do the same on moto g 2015?
littleromeo said:
Today I was able to flash the stock moto E firmware on my friend's moto E without unlocking the bootloader.
Does this mean the stock recovery identifies official firmware?
Is it possible to do the same on moto g 2015?
Click to expand...
Click to collapse
Yes. As long as it's factory stock firmware it will flash on a locked bootloader phone.
Sent from my Moto G XT1034 using Tapatalk
GoBobAKnob said:
alfick3 said:
Yes. As long as it's factory stock firmware it will flash on a locked bootloader phone.
@alfick3 I know this thread & post are really old but...
How does the phone recognize that it's stock firmware? Is there any way to fool it & flash different firmware?
Click to expand...
Click to collapse
Wow! You're right about it being old. It's been a while since I had the Moto G, but from what I remember, the stock recovery recognized the stock firmware because of it being signed, or something like that. I don't know if it can be fooled.
Click to expand...
Click to collapse
GoBobAKnob said:
alfick3 said:
Yes. As long as it's factory stock firmware it will flash on a locked bootloader phone.
@alfick3 I know this thread & post are really old but...
How does the phone recognize that it's stock firmware? Is there any way to fool it & flash different firmware?
Click to expand...
Click to collapse
On a Motorola device with a locked bootloader, fastboot will recognize and allow installation of an official stock firmware package which is the same or a newer build as the firmware last installed on the device. In other words, downgrading is not permitted with a locked bootloader. It's not the stock recovery that is "recognizing" the stock firmware package, but rather the /aboot bootloader partition. Stock recovery recognizes and permits installation of signed OTA update packages, but not entire firmware packages Official firmware packages are installed using fastboot mode or RSD-Lite. As far as "fooling" your device into flashing an otherwise unauthorized firmware package, yes it has been done but is an extremely tedious and risky process. The process involves intentionally hard bricking your Moto device in order to trigger QDLoader_9008 mode. From there, QPST/QFIL is used in conjunction with a firehose program protocol to push the firmware package to the device. This method has been used to root a number of Moto devices that are unsupported for bootloader unlocking. Again, it's rather tedious, complex, and requires a rudimentary understanding of Linux and Python. A locked down bootloader on a Moto device presents a considerable obstacle in the way of rooting, modding and customizing the device. As a good rule of thumb, if you want a Moto device you can easily customize, root, flash, etc., always get a device supported by Motorola's bootloader unlocking portal. Moto devices branded by Verizon, AT&T, Straight Talk & Cricket are notorious for locked down bootloaders. Sprint, Boost Mobile, Virgin Mobile & T-Mobile branded Moto devices are known generally to support bootloader unlocking. And, of course, factory unlocked and developer edition Motorola devices support oem unlocking, rooting and customizing.
Click to expand...
Click to collapse
On a Motorola device with a locked bootloader, fastboot will recognize and allow installation of an official stock firmware package which is the same or a newer build as the firmware last installed on the device. In other words, downgrading is not permitted with a locked bootloader.
Click to expand...
Click to collapse
@Viva La Android Hello friends ,does that rule apply to other android devices with Stock Firmware,Locked bootloader and Stock recovery as well ?
Does reflashing the same ROM i.e going from stock firmware of an android version and SKU to stock firmware of the same android version and SKU wipe user data ?
Thank you
In general, yes it does. Some manufacturers configure device bootloaders where downgrading is permitted while in a locked state. For example, many MediaTek-based devices can be downgraded via the SP Flash Tool, even with a locked bootloader. And virtually any devices with an Allwinner chipset can likewise be downgraded using proprietary flash tools. But as a general rule, on a bootloader locked device, users are permitted to flash stock factory images.
On Motorola devices, fastboot flashing firmware packages will not result in a loss of data as long as you skip over this command:
fastboot erase userdata
This holds true whether you are flashing the same build or updating the build by flashing a more recent firmware package.
Viva La Android said:
In general, yes it does. Some manufacturers configure device bootloaders where downgrading is permitted while in a locked state. For example, most MediaTek-based devices can be downgraded via the SP Flash Tool, even with a locked bootloader. But as a general rule, on a bootloader locked device, users are permitted to flash stock factory images.
On Motorola devices, fastboot flashing firmware packages will not result in a loss of data as long as you skip over this command:
fastboot erase userdata
This holds true whether you are flashing the same build or updating the build by flashing a more recent firmware package.
Click to expand...
Click to collapse
Can you send me a message please? Ineed to ask you about Stock ROM on moto g6 play
This is a link to the official Motorola firmware packages for all carrier and retail variants of the Moto G6 Play (codename: jeter). Be sure to select the correct model number/carrier variant from the list. If your bootloader is locked, choose the most recent build version for your device.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Related
hi, i recently got a droid razr hd,, its on ics system version 7.21.11.xt925.skt.en.kr build number vanquish_u
_skt-userdebug 4.0.4 ,,7.7 1q-126_VQS-11 14 test-keys,, how do i update,, which are the correct files to dowload, and where to download them.....,.,.,.
seriosly?? atleast abuse me for this annoying question!!! cum on man,, someone reply
Bump!! Why this forum is so queit?
Sent from my HTC Desire S using xda app-developers app
Not many people have these phones, so traffic is very slow on this forum.
You have an engineering device with a userdebug testkeys firmware on it.
The good news is that your device can run any firmware because it has an unlocked bootloader, so all you need to do is download the full XML.zip for the current release for your region and flash it using RSD Lite.
The bad news is that a stock OTA update cannot be loaded successfully on that firmware because it's a testkeys build with different signatures and other debugging components, so you will have to manually upgrade it to a stock build.
You have a very unusual device and must have purchased it from someone who was a tester originally.
Enjoy it!
Edit: Here is the best link to find the right firmware files.
http://sbf.droid-developers.org/vanquish_u/list.php
cellzealot said:
Not many people have these phones, so traffic is very slow on this forum.
You have an engineering device with a userdebug testkeys firmware on it.
The good news is that your device can run any firmware because it has an unlocked bootloader, so all you need to do is download the full XML.zip for the current release for your region and flash it using RSD Lite.
The bad news is that a stock OTA update cannot be loaded successfully on that firmware because it's a testkeys build with different signatures and other debugging components, so you will have to manually upgrade it to a stock build.
You have a very unusual device and must have purchased it from someone who was a tester originally.
Enjoy it!
Edit: Here is the best link to find the right firmware files.
http://sbf.droid-developers.org/vanquish_u/list.php
Click to expand...
Click to collapse
U mean , I can download any firmware file and flash it via RSD? ,, hey. , wait a minute, my country/region is not in the list , what now? Which will be the correct firmware to use?
P.s I'm now looking forward to root and flash a custom JB rom, my bootloader is already unlocked, so if I manage to root my device,, can I just flash cwm recovery and start flashing wiping and flashing Roms? Btw , what do you recomend , upgrade or root?
Sent from my HTC Desire S using xda app-developers app
Yes, you should be able to just fastboot the latest CWM or TWRP recovery image for the xt925 and then flash anything you want because a status 1 device is a true engineering model that is NS(Non Secured) and performs no signature checks at all on the bootchain.
Rooting these devices is simply a matter of flashing a zip from the custom recovery and no exploits are required.
You also already have root in adb shell, that is what userdebug means.
You will have to find the best firmware for your region and carrier and it may take some experimenting and/or reading to find which is best for you.
Definitely make a full backup of your current build so you can restore it as needed.
You have more possibilities due to the completely unlocked status of the device but it also means you are on your own and must manage it yourself and be responsible for understanding how to do that.
Fair deal!
cellzealot said:
Yes, you should be able to just fastboot the latest CWM or TWRP recovery image for the xt925 and then flash anything you want because a status 1 device is a true engineering model that is NS(Non Secured) and performs no signature checks at all on the bootchain.
Rooting these devices is simply a matter of flashing a zip from the custom recovery and no exploits are required.
You also already have root in adb shell, that is what userdebug means.
You will have to find the best firmware for your region and carrier and it may take some experimenting and/or reading to find which is best for you.
Definitely make a full backup of your current build so you can restore it as needed.
You have more possibilities due to the completely unlocked status of the device but it also means you are on your own and must manage it yourself and be responsible for understanding how to do that.
Fair deal!
Click to expand...
Click to collapse
thanks for your response!! im pretty sure mine is a test model, there is also a label on the side of the screen "Not for sale" !! so, im just gonna boot in fastboot mode and flash twrp, do a nandroid,, flash cyanogenmod 10.1!! and thats it! i will not flash a firmware, i have heard the 4.1.2 update has reboot issues,, so im gonna go with a custom rom, :highfive: , a qusetion, since im a total noob in motorola! so , i wanna know , in motorola , unlocked bootloader means im free to do everything!?! i mean, in HTC , if i unlock my bootloader, i always have flash the boot.img seperatley from fastboot,, so i wanna know , if there are any issues in motorola like that? sorry for silly Q!!
In a stupid attempt to try to root my Moto G, I followed the instructions here up to step 6, rebooted, and was greeted in fastboot with a "failed to validate boot image" message. I have tried flashing a new boot image but I get a remote failure saying "Preflash validation failed", presumably because the phone's bootloader is locked.
The phone is from Cricket/AIO/ATT or whatever and does NOT qualify for bootloader unlocking.
Is there any way to fix this, or have I bricked my phone?
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine: http://theroot.ninja/)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video: http://youtu.be/laU6NQ0LxR0
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
skyguy126 said:
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
Click to expand...
Click to collapse
Thanks for the reply. Will definitely look into warranty if all else fails, I've only had the device for about a month.
The stock recovery factory reset doesn't fix the boot image. It successfully wipes everything but it still reboots right back to fastboot.
I cannot unlock the bootloader as it has been locked by the carrier and does not qualify for bootloader unlocking according to Motorola, and it looks like sunshine is a paid service, which even if I paid for I would have to be able to get into the phone to install the apk anyway.
It fails flashing any boot images or custom recoveries with a "(bootloader) Preflash validation failed" error.
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
skyguy126 said:
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
Click to expand...
Click to collapse
Yes, that's all fine and dandy, but like I said I'm stuck in fastboot so I wouldn't be able to use it anyway. At this point I don't even care about rooting, I'd just like to get my device working.
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
lost101 said:
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
Click to expand...
Click to collapse
It's an XT1032 and was running on 4.4.2. Maybe I tried with the wrong stock firmware, I used "AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml", which I found in this thread. The version matched the info I found using "getvar all" in fastboot so I figured it was the correct one. The http://sbf.droid-developers.org site seems to be down at the moment so I guess I can try a few more when it comes back up.
That would appear to be the correct firmware. However it would also appear your bootloader is preventing you from flashing it. As I said, the best solution would be to flash the 4.4.4 firmware image for your carrier, however there isn't one at this time.
You can always try flashing the XT1032 EU Retail 4.4.4 firmware image. It doesn't matter where you are in the world, it will should work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
I have some quentions:
Hey guys, i was wondering if it's possible to flash a custom rom without unlocking the bootloader and without installing other recovery.
Or if it's possible to edit the stock rom , and add new features , mostly customize , and flash it with locked bootloader and original recovery.
I heard somewhere that in some cases it can be done with locked bootloader .
What happen if i try to flash a custom rom with locked bootloader and original recovery?
Could this brick my Moto G ?
Could the bootloader be locked forever?
I wan't to keep it fully original ( Bootloader and recovery) and install Android 6.0
If this not possible i want to edit the stock Lollipop 5.1.1 rom , add some features and tweaks , and flash it , would be possible?
Luis
Moto G XT1032
Android Lollipop 5.1.1
16Gb
lprb99 said:
I have some quentions:
Hey guys, i was wondering if it's possible to flash a custom rom without unlocking the bootloader and without installing other recovery.
Or if it's possible to edit the stock rom , and add new features , mostly customize , and flash it with locked bootloader and original recovery.
I heard somewhere that in some cases it can be done with locked bootloader .
What happen if i try to flash a custom rom with locked bootloader and original recovery?
Could this brick my Moto G ?
Could the bootloader be locked forever?
I wan't to keep it fully original ( Bootloader and recovery) and install Android 6.0
If this not possible i want to edit the stock Lollipop 5.1.1 rom , add some features and tweaks , and flash it , would be possible?
Luis
Moto G XT1032
Android Lollipop 5.1.1
16Gb
Click to expand...
Click to collapse
Short answer: no!
Long answer: No - the only notable exceptions to this are the Bump-compatible LG phones like the LG G3, in which the ROM images/recovery images have a signature key appended to the images so that the bootloader will approve of said images and therefore said images can be installed onto an LG phone.
As a result of the way Motorola/Lenovo, HTC, Huawei, Sony et al works with custom image approval, the only way for you to install a custom image is to FIRST UNLOCK THE BOOTLOADER, and THEN INSTALL A CUSTOM IMAGE!
aha360 said:
Short answer: no!
Long answer: No - the only notable exceptions to this are the Bump-compatible LG phones like the LG G3, in which the ROM images/recovery images have a signature key appended to the images so that the bootloader will approve of said images and therefore said images can be installed onto an LG phone.
As a result of the way Motorola/Lenovo, HTC, Huawei, Sony et al works with custom image approval, the only way for you to install a custom image is to FIRST UNLOCK THE BOOTLOADER, and THEN INSTALL A CUSTOM IMAGE!
Click to expand...
Click to collapse
Hi aha360 thanks for you reply.
:good:
I have one more question :
Is it possible to root my moto g without unlocking the bootloader?
Root would bring me useful features , but i don't want to end with a bricked moto g.
As you noticed i want my moto g as original as possible, but with some tweaks.
I didn't understand if i can edit stock lollipop rom and flash it.
I just wanted to have Android 6.0 in my moto g , but that is not possible with Moto by Lenovo
lprb99 said:
Hi aha360 thanks for you reply.
:good:
I have one more question :
Is it possible to root my moto g without unlocking the bootloader?
Root would bring me useful features , but i don't want to end with a bricked moto g.
As you noticed i want my moto g as original as possible, but with some tweaks.
I didn't understand if i can edit stock lollipop rom and flash it.
I just wanted to have Android 6.0 in my moto g , but that is not possible with Moto by Lenovo
Click to expand...
Click to collapse
Sadly, no - I have done my research on this and unless the OS/ROM itself has an exploit that allows root access, you'd also have to unlock the bootloader just to have root access on a stock ROM.
It sucks, as I also ideally wanted to just get root access on a stock ROM on my newly-acquired Moto G LTE (Peregrine) so like I said, for all things XDA-friendly mod-related, Motorola/Lenovo et al says 'unlock bootloader and lose your warranty or STFU'.
aha360 said:
Sadly, no - I have done my research on this and unless the OS/ROM itself has an exploit that allows root access, you'd also have to unlock the bootloader just to have root access on a stock ROM.
It sucks, as I also ideally wanted to just get root access on a stock ROM on my newly-acquired Moto G LTE (Peregrine) so like I said, for all things XDA-friendly mod-related, Motorola/Lenovo et al says 'unlock bootloader and lose your warranty or STFU'.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2774016
Would this work for xt1032 ?
or Would this acutally work?
lprb99 said:
http://forum.xda-developers.com/showthread.php?t=2774016
Would this work for xt1032 ?
or Would this acutally work?
Click to expand...
Click to collapse
The exploit looks like it is based on Jelly Bean and KitKat, so provided that you haven't upgraded, you could try it out, otherwise you are out of luck.
aha360 said:
The exploit looks like it is based on Jelly Bean and KitKat, so provided that you haven't upgraded, you could try it out, otherwise you are out of luck.
Click to expand...
Click to collapse
I have lollipop 5.1.1 ...
lprb99 said:
I have lollipop 5.1.1 ...
Click to expand...
Click to collapse
Then you're **** outta luck - you'll have to unlock your bootloader then.
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
New debloated version with insecure kernel and init.d support, rooted with Chainfire's Beta 2.71 SuperSU credit to SuperR for the help with the updater perms.
FIXED DOWNLOAD ALL APOLOGIES
Skinny Stylo Alpha version
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Saved
Requirements- Unlocked bootloader
Click to expand...
Click to collapse
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
runningnak3d said:
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
Click to expand...
Click to collapse
@runningnak3d
I would prefer to be bootloader unlocked through fastboot oem unlock before doing any mods in 6.0. Every single time I did not I got secure boot error. If you make any system change on 6.0 with locked boot it will not boot.
Thank you for taking the time to do this.
:good::good:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
The main reason I made this was because I can never boot recovery or fastboot manually ( ex. w/hardware buttons) when you have the insecure kernel adb works when at the splash screen so it's easier to recover if you have any problems.
Sent from my LG-H631 using XDA-Developers mobile app
Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
wrenchman76 said:
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
Click to expand...
Click to collapse
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
runningnak3d said:
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
Click to expand...
Click to collapse
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
wrenchman76 said:
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
Click to expand...
Click to collapse
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Waiting on the debloated version.
Sent from my LGMS631 using Tapatalk
runningnak3d said:
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Click to expand...
Click to collapse
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You didn't need to ship it back to LG. Firmware download mode is always available (hold vol up while plugging in USB cable -- just vol up, not vol up + power). Continue holding vol up until FW DL mode displays). Then just use the LG flash tool to flash a KDZ. It is a PITA when you have to go back that far, but you can't brick these phones, not with software at least -- they would need to be physically altered
-- Brian
Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You sent your device in for a soft brick? You should set up the flash tool for our phone with a 10j.kdz before doing anything. Hope you get it back soon.
Debloated version
Fixing some force close problems on a debloated version now, should be up later today or tonight.
@runningnak3d
Flashing the KDZ seems easy enough. But how could I fix it without unrestricted access to a computer? And my stock charger is broken without a USB cable. I had no choice but to send it in for repairs. Guess I'll be stuck on Lollipop for a while longer, at least.
Edubyah said:
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Click to expand...
Click to collapse
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
Can the bootloader be unlocked on the CDMA versions (ex. Boost, Sprint, Verizon)? If you can I will make a variant for it. But if you can't NO.
I just found out that the unlocked bootloader in 6.0 survives even the .kdz flashtool. So once you unlock your boot in 6.0 with fastboot oem unlock you never have to do it again even survived kdz downgrade to lollipop and update to 6.0 stayed unlocked.
JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
works great on metro ms631 just need wifi to stop turning its self off can you guys fix it! h631/ms631 mm kernel works find no errors help needed fixing wifi connection thanks
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.