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
Related
Hi, I have already rooted and unlocked my bootloader then proceeded to flash a custom ROM. I want to try out a different ROM so do I have to re-do the whole root and unlock bootloader process ? I know its just flash one simple zip file in recovery but the reason I ask is my phone got soft bricked last time around.
dannyboy951 said:
Hi, I have already rooted and unlocked my bootloader then proceeded to flash a custom ROM. I want to try out a different ROM so do I have to re-do the whole root and unlock bootloader process ? I know its just flash one simple zip file in recovery but the reason I ask is my phone got soft bricked last time around.
Click to expand...
Click to collapse
Once it's unlocked you don't need to do it again unless you intentionally re-lock it or get a new phone.
Also be careful if you somehow get vzw OTA pushed to your phone (sometimes happens without you knowing it) it will lock your bootloader again and when you go to flash it will say something about taking your phone to verizon. Don't panic as most people do all you have to do is unlock again and everything will be fine
So i held out taking the otas for a while to avoid losing root and am still on 4.2.2 post camera update. I know, it's sad, but I have root so i haven't been dying to update.
However, i just saw that sunshine will unlock my bootloader, which I'm going to do. What I'm confused about though is once i unlock my bootloader, how do I get to 4.4.4? Can I just revert everything to stock and take all of the otas (and then flash twrp to get root)? I heard that something in one of the otas changed something with the bootloader, so i don't know if taking that would cause problems with an unlocked bootloader or make me lose my unlocked status. Either way, could i just flash a 4.4.4 image directly from 4.2.2? If so where do i get a stock image to flash? Thanks for any help!
Once you have successfully unlocked, make sure you are status 3 unlocked in fastboot.
Once confirmed, you can use the rsd lite, and use the stock firmware from:
http://sbf.droid-developers.org/
Next, flash twrp for the ghost from their website.
Lastly if you want root flash supersu.
So can I flash a different OS version from the site that you linked? Or is that just to return to stock in anticipation of flashing TWRP and using that to flash a later android version?
rule of thumb is you cannot downgrade, only upgrade or revert to the same version you are already on
This seemed like the easiest route to a rooted 4.4.4... Unlock bootloader via Sunshine, and proceed as instructed here: http://forum.xda-developers.com/droid-ultra/general/unlocked-boot-xt-1080-restore-4-4-4-pre-t2883131
Data remains intact, unlocked bootloader warning on boot logo fixed, and TWRP (or Philz) flashed as recovery. Super easy. Good times.
Deleted. Redundant post.
Sent from my DROID Maxx
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
rcji said:
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
Click to expand...
Click to collapse
Yep true. Can't take OTAs with out stock recovery. But it is easy to flash Stock Recovery then back to TWRP after the OTA. Of course safest option is to flash stock fxz without wiping data before taking OTAs.
Personally have my own recovery and logo.bin script I keep for just this reason. Run RSDlite with the stock software take OTA (if no fxz yet for the OTA) then full bit and setup and finally flash the recovery and logo.bin I use.
Many ways of doing it just find its easier for me this way probably cause this is how I learned from trial and error is all. Probably an easier way though.
Hi all,
The original credits for the root go to SuperPichu for the following post: http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
I simply "modified" his process, to make it even more "hassle free"
The process will wipe your data, so remember to backup it.
Besides, I'm not responsible if warranty voids or whatever. Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it. The fastboot unlock procedure has been taken directly by the NVidia Developer's site, so they actually expect the users to do that - but what you will do next, it's all your responsability
So, the overall procedure looks like:
Download&Install the "Mini" ADB/Fastboot from here: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 (remember to say yes to create the link on the desktop - it will be useful later)
Download&Install NVIDIA ADB Drivers from the official Nvidia site: http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip
Enable "Developer Mode" on the Nvidia Tablet (Settings -> About tablet -> Tap many times (5+) the "Build number" until the Developer Mode is activated
Developer Mode -> Enable USB Debugging
Copy the CWM image and SuperSU (rename it to supersu.zip) where you installed the Mini ADB/Fastboot (default: C:\Program Files\Minimal ADB and Fastboot)
Click the link created by the Mini ADB/Fastboot installation. It should open a DOS console already at the install folder.
(In the Windows console) Type "adb reboot bootloader"
From the rebooted tab, select "Load fastboot protocol" with Volume Keys and push the power switch to confirm
(In the Windows console) Type "fastboot oem unlock"
[ATTENTION: This step will wipe your device] Press the "Volume Down" button to select, with the "Power" button, the "Unlock bootloader" option on device
(In the Windows console) Type "fastboot flash recovery recovery.img"
On the tablet, select "recovery reboot"
You should be now on CWM. Simply select "install zip from file" -> install from sideload
In the console, type "adb sideload supersu.zip"
On CWM select "reboot system", CWM will ask to keep root => say yes
Enjoy your rooted tablet
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
Well first off I havent had any issues with ota updates on CWM (took kitkat otas). Second, if you really don't want a custom recovery why not just obtain root then flash back the stock recovery??
wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
To be honest with you, I haven't updated yet - but the OTA seems to work (i.e. it's currently saying that my Firmware is up-to-date, no errors). Just wait a couple of weeks (NVIDIA released a firmware update every month until now :good: ) and I'll let you know if it works
Btw, even if I loose the the root/CWM, it's not a great deal to install it again
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Good to know. ?But we should be able to flash the ota zips via recovery and flash super su and possibly recovery (locked bootloaders, ota can overwrite recovery) just like we did to update to lolli. I usually see zips before I see the ota anyways.
sandrodjay said:
Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it.
Click to expand...
Click to collapse
I have contacted NVIDIA today, asking steps to move back to Kitkat. I was given instructions to unlock the bootloader, and was assured it will not void the warranty. The assistant was being meticulous regarding this, since she asked around for her colleagues' advice before giving me the information.
So if I ever need to send in for warranty, all I have to do is reflash the factory image to get rid of the root and I'll be all set. If they make a fuss about me having an unlocked bootloader, I'll have a chat transcript to back me up. You guys may want to do the same too.
Thank you worked great!
An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Just took 5.0.1 (wasn't rooted or anything). So I was thinking if I flash the CWM, then do a stock backup, then proceeed to root I should be able to restore the backup when a new OTA comes out since it will be unrooted and stock. Then I can update, install recovery if needed, make another unrooted stock backup, for the next time then reroot, right?
Should work, but after restoring your stock backup you will need the stock Recovery too to update ota.
Hi
There is no need to flash the custom recovery if you don't want to. Just do a fastboot boot recovery <recovery.img>. I did that because i didn't want to change to another recovery.
After the reboot you will revert to stock recovery.
\Sorenjul
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Help
Anyone else not able to download supersu.zip the page wont load
Granger77 said:
Anyone else not able to download supersu.zip the page wont load
Click to expand...
Click to collapse
NM sorry just went it opened instantly, maybe to much traffic
eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
root method LTE compatible
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Driver issues
I cant for the life of me get my win 7 64bit pc to install the drivers I've tried uninstall and going through manually with the naked driver method and it still says the device doesnt need it his tutorial is for win 8 am I missing something, I'm losing my mind over here I want this thing rooted so bad I'm losing sleep, and google has been useless
cyraxx84 said:
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
Click to expand...
Click to collapse
Ty for info and reply.
Bogdacutu said:
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Click to expand...
Click to collapse
Got it. Thanks!
oleg77 said:
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Click to expand...
Click to collapse
Same here. I got mine on sale with the controlller. I suspect its the same on both wifi only and LTE version.
Can i follow this guide to unlock and root 5.0.1?
Was on NCG with root, unlocked the Developer mode http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
ProSeriesRacing said:
Was on NCG with root, unlocked the Developer bootloader http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
Click to expand...
Click to collapse
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
smokerbond said:
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
Click to expand...
Click to collapse
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
smokerbond, Thank you . Back up & running again
ProSeriesRacing said:
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
Click to expand...
Click to collapse
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
al50 said:
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
Click to expand...
Click to collapse
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
ProSeriesRacing said:
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
Click to expand...
Click to collapse
Ok. Glad to hear that you've gotten your device up and running.
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.