(As a foreword, I've been searching and trying to find these answers myself but I haven't had much luck. If there are resources out there covering my questions, please direct me there. Thanks!)
Could someone please inform me of the specific difference(s) between the VRALEC and VRALE6 bootloaders? Also any background info would be interesting to know as well (order in which they were leaked, timeframes, circumstances etc).
Next question: I was able to successfully ODIN the VRALEC bootloader (only) to my stock phone on VRBMF1. When I tried to do the same with VRALE6 it failed with a signing-related error. However I was able to flash the VRALE6 directly using the CASUAL utility and that worked fine. I don't understand why/how the phone will allow itself to boot from that file, but wouldn't allow it to be ODIN'd. Could somebody enlighten me? Also, if I were to have tried ODIN'ing the entire VRALE6 bootchain, would that have succeeded?
Also, is there any rationale for using any other bootloader(s)? There appear to be at least 10 different bootloader and/or bootchain version varients out on the web in different places. From what I can gather though, only the two listed above are significant since they are 'unlocked'.
Lastly, which bootloader does the Developer Edition phone use? Does it come unlocked, or is it unlock-able via some web site or something? If it has its own 'special' unlocked bootloader, why could we not simply get a copy and use that on retail phones rather than the old/leaked version widely used now?
B
pluto01 said:
(As a foreword, I've been searching and trying to find these answers myself but I haven't had much luck. If there are resources out there covering my questions, please direct me there. Thanks!)
Could someone please inform me of the specific difference(s) between the VRALEC and VRALE6 bootloaders? Also any background info would be interesting to know as well (order in which they were leaked, timeframes, circumstances etc).
Click to expand...
Click to collapse
Well, for the longest time the VRALEC was titled the "boot chain" and I'm seeing now in Invisiblek's awesome thread over on Rootz, that's not the case anymore. So, I'll preface this by saying referring to both VRALEC and VRALE6 terms as "bootloaders" sounds weird now because VRALEC was originally titled "VRALEC.bootchain.tar".
VRALEC file should be a "tar" and the VRLE6 file should be a "zip." Cool? Here's how to differentiate, the VRALEC.bootloader.tar needs to be flashed in Odin to allow you to install a custom recovery. It is essentially just the first step of several to unlock the bootloader, it is not unlocked at this point. Someone of a more technical background can explain this better but its like this file is hijacking the boot sequence and telling the phone everything is still recognized as official firmware. There's no trigger that prompts the phone to give you the yellow triangle warning. Once a custom recovery is installed, you need to flash in recovery the VRLE6.zip to unlock the bootloader. Both of these files come from a pre-release VZW GSIII that were so graciously provided to AdamOutler by an African-Canadian Sock Monkey. Seriously, check post #317. This also serves to answer your question about times, leaked, etc. Moving on!
Next question: I was able to successfully ODIN the VRALEC bootloader (only) to my stock phone on VRBMF1. When I tried to do the same with VRALE6 it failed with a signing-related error. However I was able to flash the VRALE6 directly using the CASUAL utility and that worked fine. I don't understand why/how the phone will allow itself to boot from that file, but wouldn't allow it to be ODIN'd. Could somebody enlighten me? Also, if I were to have tried ODIN'ing the entire VRALE6 bootchain, would that have succeeded?
Click to expand...
Click to collapse
As I said above, VRALE6 should be a zip file and needs to be flashed in custom recovery NOT Odin. That's the key difference.
Also, is there any rationale for using any other bootloader(s)? There appear to be at least 10 different bootloader and/or bootchain version varients out on the web in different places. From what I can gather though, only the two listed above are significant since they are 'unlocked'.
Click to expand...
Click to collapse
Nope. Idk what you mean by "at least 10 different bootloader and/or bootchain version varients." Maybe there is a "bootloader" per each OTA that we have received? But honestly, every OTA thus far has been rooted/unlocked via almost the exact methods so this is a moot topic. There are only two unlock files of significance for any root/unlock method for the VZW GSIII: VRALE6.zip and VRALEC.tar
Lastly, which bootloader does the Developer Edition phone use? Does it come unlocked, or is it unlock-able via some web site or something? If it has its own 'special' unlocked bootloader, why could we not simply get a copy and use that on retail phones rather than the old/leaked version widely used now?
B
Click to expand...
Click to collapse
Well, AdamOutler actually received some help and got this phone unlocked well before the dev edition was released last year so there was never a need to look towards that device for bootloader unlock help. I have no clue about how to unlock that device and there's been no reason to think about having (at the time) a $650 dev edition GSIII when the retail one was officially unlocked. No clue on compatibility with bootloaders between either device.
Hey guys! I haven't seen any other guides about this so here you go. How to use Engineering mode in the G965U and G965U1. Engineering mode doesn't let you do much, but if you're interested in testing some root methods it is definitely worth your interest. The two things that are most interesting to me is that SELinux is in Permissive and the OEM unlocking option appears, but it seems enabling OEM unlock does nothing. Still, all the files for the regular S9+ software is there, it just seems to boot a different mode. If someone can figure out how to make the normal UI and settings show up and inject root this could be our method. DON'T DO THIS IF YOU DON'T MIND RISKING MESSING UP YOUR DEVICE. USE A GOOD USB CABLE AND ONLY FLASH THE RIGHT FILES FOR YOUR MODEL. YOU HAVE BEEN WARNED.
Screenshots:
https://i.imgur.com/Uynre9O.jpg
https://i.imgur.com/h1MGsNJ.jpg
https://i.imgur.com/zYyno9m.jpg
So first. Go ahead and download the ENG boot and CSC for your device HERE and HERE. These files are courtesy of @wolfgart . Please give him thanks on his post, all credit goes to him for his work.
Second, extract both zips and you will have two .tar.md5 files. You need the latest odin to install this. I was unable to restore to stock with regular odin but patched odin let me return to stock. Download it HERE.
Go ahead and download the latest stock firmware as well. There a plenty online but I suggest using one from HERE as it worked for me.
Extract the firmware zip and reboot your phone into download mode by holding Bixby + Vol Down + Power. Plug in and open up odin and select the CP, BL, and USERDATA from the stock firmware and use the ENG boot file for AP and Combination file you downloaded earlier for CSC. Hold on to that stock firmware because you'll want to be able to return easily. Go ahead and start the flash process in ODIN. This will take a few minutes. If you have an MD5 error simply remove the .MD5 from the end of the filename for AP and/or CSC.
That's it! If all goes well you will have ENG boot. It isn't much right now but I'm sure with all your brilliant minds it could be the pathway to something much bigger.
"Allow the bootloader to be unlocked"? It can't be that easy on Snapdragon, can it??
EDIT: My bad, missed the part where you said it doesn't seem to do anything. I'd just delete this if XDA allowed me to.
LinneaDenVarg said:
"Allow the bootloader to be unlocked"? It can't be that easy on Snapdragon, can it??
EDIT: My bad, missed the part where you said it doesn't seem to do anything. I'd just delete this if XDA allowed me to.
Click to expand...
Click to collapse
LOL no problem! I'm sure most of the devs probably already have this set up I just threw this guide together since there isn't one yet. It gives us some extra opportunities to tinker around and as far as I know it's pretty safe to use it doesn't even trip knox.
That's it! If all goes well you will have ENG boot
hjfgdsg said:
That's it! If all goes well you will have ENG boot
Click to expand...
Click to collapse
Yup..... Now root.. and the wait continues. This isn't anything experienced people didn't already have. This is a nightmare waiting to happen for a n00b. Don't mess with this unless you know what you're doing.
hey need some help with ENG BOOT for N976U
found a site that claims to have it just wanted so help in pm
thatruth132 said:
hey need some help with ENG BOOT for N976U
found a site that claims to have it just wanted so help in pm
Click to expand...
Click to collapse
Should probably ask in the note 10 threads this is for s9 and +
I would like to know if it is working on Android 10 I have a sm-g965u Verizon been attached and if it is necessary to unlock the bootloader?
osvaldo3091 said:
I would like to know if it is working on Android 10 I have a sm-g965u Verizon been attached and if it is necessary to unlock the bootloader?
Click to expand...
Click to collapse
No it is not And you cannot unlock this devices bootloader All the U W And U1 are permantly locked with no hope of unlock
TheMadScientist said:
No it is not And you cannot unlock this devices bootloader All the U W And U1 are permantly locked with no hope of unlock
Click to expand...
Click to collapse
I understand, what I would like to know is something I have this device is a sm-g965u with csc xaa is from Verizon I am in RD the security patches take a long time to arrive and the updates too.Do you think if i change the firmware to sm-g965u1 i would receive updates Faster? Thanks greetings
osvaldo3091 said:
I understand, what I would like to know is something I have this device is a sm-g965u with csc xaa is from Verizon I am in RD the security patches take a long time to arrive and the updates too.Do you think if i change the firmware to sm-g965u1 i would receive updates Faster? Thanks greetings
Click to expand...
Click to collapse
Not necessarily It just depends who gets their updates out the fastest Sometimes U1 is faster others carrier is faster then U1 unlocked
TheMadScientist said:
Not necessarily It just depends who gets their updates out the fastest Sometimes U1 is faster others carrier is faster then U1 unlocked
Click to expand...
Click to collapse
Ok I understand thanks for the explanation I think I would not benefit from changing firmware. I explain something to you: I have this mobile and when they gave it to me the active csc was the vzw and I looked for a tutorial and managed to change it to xaa which is the one used in my country for unlocked device, the device doesn't have a Verizon app not anything like that but when I was in vzw it had already been updated to the April security patch but as I changed the csc I only received the March one and to be able to update the patch I had to install a firmware with the updated patch greeting again
I have a SM-G930VL and have seen many threads from 2016-now that have been able to flash the 930U firmware but anytime I try flashing it can not get it to boot. I'm either in a bootloop or a recovery loop where it will never boot into recovery. Any help would be appreciated! I can answer almost any questions but I don't want to list them in case anything important gets lost in the list.
damion675 said:
I have a SM-G930VL and have seen many threads from 2016-now that have been able to flash the 930U firmware but anytime I try flashing it can not get it to boot. I'm either in a bootloop or a recovery loop where it will never boot into recovery. Any help would be appreciated! I can answer almost any questions but I don't want to list them in case anything important gets lost in the list.
Click to expand...
Click to collapse
Yes but you still need the correct G930U firmware for your region/country.
Your phone needs OEM and usb debugging enabled, not essential when flashing firmware but often helps.
cooltt said:
Yes but you still need the correct G930U firmware for your region/country.
Your phone needs OEM and usb debugging enabled, not essential when flashing firmware but often helps.
Click to expand...
Click to collapse
I am flashing the version for track-fone off of sam mobile and enabled OEM and Usb debugging
You'll need a patched Odin to flash G930U on a different model, otherwise you get mismatch errors. You can get it from here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
The OEM unlock step only applies to Exynos since that unlocks their bootloader, the toggle does nothing on USA/Snapdragon devices.
Beanvee7 said:
You'll need a patched Odin to flash G930U on a different model, otherwise you get mismatch errors. You can get it from here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
The OEM unlock step only applies to Exynos since that unlocks their bootloader, the toggle does nothing on USA/Snapdragon devices.
Click to expand...
Click to collapse
I feel like such a dunce...........I used this one to flash the 930U onto my 930A model so I even already had it. I just thought I had already tried it. After ~8 hours of working on this, it is done. Thank you so much!! I guess if you thought you tried something always try it again to be sure haha.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
I have a A125U that I can't unlock the bootloader of. There's no OEM unlock option in the Developer Options, there's no way to unistall system updates to try the date/time thing to get OEM unlock, nothing else I've tried has worked at all. I even tried flashing A125F firmware to no avail, of course. I was thinking, the BL file is the bootloader, is there a way to flash a bootloader that's already unlocked? Or is that not how this works?
If not, does anyone know how to get OEM unlock to show on the A125U? It's been driving me insane.
Not possible unfortunately
no
LOOOOOOOL
This is the biggest lie I've ever seen in my life!!! of course it,s possible ddd. Everything is possible especially this. Trick to your issue, is just that you have to corssflash to the Canadian firmware on your A125U which is the US model. But that doesn't matter, that's nothing because those 2 phones run on the same hardware so the firmware operates with both. Even the SW_REV value doesn't do anything in that situation. You can take the U models and flash it to W(Canada) but that's useless because then you're locked out of natively unlocking the PBL. Just grab the Canadian firmware and crossflash it via heimdall or patched Odin which is the same thing. Erase old NAND.
Also don't think that stuff like this isn't possible, of course it is. You just have to try harder and harder until you get the result you're stasifed with. There is community with a bunch of us enthusiasts (discord server link is on my profile). Don't be scarred to ask here on xda and there in the server. Also you can dm me for help, I'll help you, don't worry.
Hope I helped, be sure to ask if misunderstood or need more help. Also check out some stuff i wrote on this forum. It's very helpful and interesting.
Stay safe,
Krypton