Forgive me if this has been covered already; I did my due diligence and found nadda regarding this. Anyhow, heres the observation: If you take a vk410 and flash that test 4.4.2 kdz to it, you can unlock the bootloader via the fastboot oem unlock command. Then, you can flash back to 5.0.2 lollipop vzw rom and retain the unlocked bootloader. HOWEVER, with fastboot apparently missing or disabled in 5.0.2, it seems impossible to properly test this. So, for sh**s and giggles, I did this, then flashed BACK to the test rom again so I could see the lock status @ the fastboot menu, and presto its still locked. What usefulness can be had from any of this? Probably nothing just thought I would share with ya'll heh
lk410
I was wondering the same question
I have the same tablet on at&t, with the lg logo on the top (at&t variant) and I used the test kdz to go back to 4.4.2.
Also, partition #33 (userdata) was labeled "grow" and I was missing 8 gigs of space. The bootloader on mine was not locked by default tho
Hello!
I've recently got into a big problem while doing stuff I don't know much about (and probably in the wrong way, because of that...). So, let's get to the problem, shall we?!
Well, I wanted to root my Moto G4 Plus (XT1640) but I had never done anything like it, so my phone was basically the way it came out of the factory. Before all of this, my phone was using Nougat 7.0.1 (I do OTA updates). I installed TWRP and followed the steps (even some from this forum). However, at that point my phone was boot-looping in the screen "Your bootloader has been unlocked, your device can't be trusted. Your phone will boot in 5 seconds.". Despite the warning, my phone didn't boot. After a while, screen got black and the only way I could use the phone was while in the bootloader. Then, I've made wipes through the Recovery, hopeful that it'd help, but it didn't. Finally, I surrendered and went looking for an original stock ROM I could flash and maybe get things working again. Found SOME ROM that's probably the right one ("XT1640_ATHENE-RETBR_MPJ24.139-50_cid50_subsidy-DEFAULT_CFC.xml.zip") (I'm from Brazil, btw). Great, downloaded, followed steps in the forum to flash it, great, it boots again! Can login to Google, default settings stuff, etc... HOWEVER.
Then, with my phone working again, I wanted to get rid of the nasty boot screen that said my device can't be trusted, etc. So I looked it up and tried to reflash the same stock ROM as above, but now doing it so I could re-lock the bootloader. To do that, I repeated the flashing commands but added the command "mfastboot oem lock" at the end (also used "mfastboot oem lock begin" as the 1st command). Then the CMD said I had to retype the command to apply. Did that, but then the following message showed: "Waiting for signed boot.img, enter the command again" or something like that (didn't printscreen, sorry). Then I reentered the command a 3rd time and then it said "Please flash a signed ROM" or something. So, basically, it failed. After that, repeating the command just showed the last message again. Unhappy, but hopeful, I entered "mfastboot reboot" to reboot my phone. So, got back into the phone (still with the nasty "Your bootloader has been unlocked" warning) and then I basically gave up. I'm now trying to install an OTA update (for Nougat, since the ROM I installed is 6.0.1) but the WiFi download is REALLY slow (and the problem is not my internet, since I've tried downloading a couple of files in my PC to test it).
So my biggest fear is that I have a ROM that's not REALLY meant for my phone (despite looking EVERYWHERE for it) and that's causing problems with the WiFi. Maybe the OTA update is just slow in the server-side, but I'd like to know. Is there a way to get the ROM I got when I bought the phone (that EXACT SAME ONE)?! I wonder if there's a problem because of Motorola/Lenovo regional things. Otherwise, the phone works (gets 4G signal, making calls and downloading Play store updates is as far as I've tested for now). And I would also like to know if there's a way to relock the bootloader in my case(since when I tried those errors I've mentioned above happened)? What I seemed to have done is downgrade a version (since I was in Nougat and then installed a stock ROM that's 6.0.1) and I don't know where to go from here. Thanks a lot, guys! Sorry for the long post, I just wanted to describe the events in order.
There is no official source for you to get a rom. This is not a nexus. I wonder why people always want to relock bootloaders! (it seems in your case only for the 5 seconds warning). As far as i know only modem can differ but roms...
Do you still have TWRP?
if so: if you are on an N modem right now try to flash an N custom rom. If you are on an M modem flash an M custom rom.
KEEP YOU BOOTLOADER UNLOCKED and also:KEEP "OEM UNLOCKING" in developers options ENABLED AT ALL TIMES! (the last step will prevent you from a 72 hours lockout from your Google account.)
There are other ways to get rid of the bootloader warning. (flash a custom logo.bin)
Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
dlehmanusa said:
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
Click to expand...
Click to collapse
You need to download the latest stock firmware either from Samsung or Sammobile and use Odin to flash it. DO NOT DISABLE OEM!!!! That has nothing to do with locking the bootloader. Flashing the stock ROM will do that. The OEM enable only disables the FRP lock which makes you login with the same google account used BEFORE a factory reset. If you are sure you know that account login and password, the FRP lock isn't a problem.
edit: The problem with the FRP lock is that people will often create a new google account login and password when first setting up their tablet. And because you only have to do that once, they tend to forget one or the other. Then, if they do a factory reset without the OEM enabled, they are locked out of the tablet.
Thanks for the detailed information and clarification. Your help is much appreciated!
The T510 doesn't have a locked bootloader.
ashyx said:
The T510 doesn't have a locked bootloader.
Click to expand...
Click to collapse
No, but it does "lock" the tablet from getting OTA updates.
I have reflashed the stock firmware however I'm still receiving the following message during boot..."The bootloader is unlocked and the software on this device cannot be verified". Is there a way to remove this message? I am planning to return the device and I want to reset everything. Thanks!
Hello, I am trying to unbrand my LTE Tab A from Sprint SM-T517P by flashing another CSC, or flashing another PIT on a patched version of ODIN with no success.
Can anyone tell me how to do it properly? I have read about Chimera, and Samkey, but they are too expensive, and I worry about bricking my LTE tablet (do not want to root, and there is no root anyway).
Any help?
I made little progress. I think I got the latest correct firmware for it downloaded, but it didn't want to flash with a patched Odin, but it did flash successfully with a non patched version of Odin.
After that, I tried flashing a CSC from another firmware of an LTE that is unbranded (SM-T515), but I always get a SECURE CHECK FAIL PIT error.
Does that mean I need to unlock the bootloader? Is that even possible? I wonder how Chimera, or Samkey is able to change CSC thru just software, but they are too expensive for me
Any help?
I soft bricked the tablet by flashing the AP, CP, and CSC of the latest firmware of International unlocked model SM-T515... I was able to recover by flashing its latest firmware for SM-T517P.
I worry about hard bricking it, but after so many tries with different things, I feel so close
Flashing only the CSC of any other firmware hasn't worked so far, and flashing anything other than Android 10 Q doesn't work either, even after unlocking bootloader.
I have NOT flashed bootloader of another firmware yet, super worried I may hard brick it if I flash another BL even after unlocking its bootloader.
hmmm i dont think there are many modifying the sm-t517p. i also own one of those on t mobile . i wanted to add twrp and root ....i cant seem to find any version made for it...so onto the magisk played with thatfor a couple days and locked it up a few times ...i think for now ill be okay with no modding ..idk why im compelled to screw p a perfectly fine working tab-phone. i did however just see that kali linux can be run on it without messing the os up..maybe ill ry that next... why did you want to modify yours? so you could switch carriers im guessing? luckily for me t-mobile took over sprint........just curious
bootloader unlock...
Unlocking Bootloader​Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Crystaltransistor said:
hmmm i dont think there are many modifying the sm-t517p. i also own one of those on t mobile . i wanted to add twrp and root ....i cant seem to find any version made for it...so onto the magisk played with thatfor a couple days and locked it up a few times ...i think for now ill be okay with no modding ..idk why im compelled to screw p a perfectly fine working tab-phone. i did however just see that kali linux can be run on it without messing the os up..maybe ill ry that next... why did you want to modify yours? so you could switch carriers im guessing? luckily for me t-mobile took over sprint........just curious
Click to expand...
Click to collapse
Hi, I also have a sm-t517p and have searching to find twrp and root. So you had no luck at all? No root even with magisk?