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
Related
Hello.
I know that this topic was posted many times on the forum but I still didn't found the answer.
The thing is that I can't unlock my bootloader without losing my camera. I've tried all the bootloader unlock tools that I found and none of them worked. Every time I lose my camera and simple flashing stock dnx and ifwi files from lollipop 3.24.40.78 also doesn't re-lock my bootloader. I have to use this method http://forum.xda-developers.com/zenfone-5/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704 but instead of flashing vanilla files I use DNX and IFWI from 3.24.40.78.
Can someone answer me is it even possible for me to unlock bootloader without losing a camera or it's something with my device model and I won't be able to do it?
Reikz said:
Hello.
I know that this topic was posted many times on the forum but I still didn't found the answer.
The thing is that I can't unlock my bootloader without losing my camera. I've tried all the bootloader unlock tools that I found and none of them worked. Every time I lose my camera and simple flashing stock dnx and ifwi files from lollipop 3.24.40.78 also doesn't re-lock my bootloader. I have to use this method http://forum.xda-developers.com/zenfone-5/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704 but instead of flashing vanilla files I use DNX and IFWI from 3.24.40.78.
Can someone answer me is it even possible for me to unlock bootloader without losing a camera or it's something with my device model and I won't be able to do it?
Click to expand...
Click to collapse
Hi,
It's something with your device, especially your device, not your model. ASUS sometimes ships different hardware in same model, which causes this issue.
Thanks!
So it seems like custom ROM's are not for me then. But one thing bothers me. One time I've tried to unlock bootloader and everything was fine (camera was working) and then I've flashed TWRP 2.8.7.0. Problem is after I did it I couldn't turn into recovery mode (my device just rebooted into system). But after that something bugged again, I lost my camera and had to flash stock ROM once again to relock bootloader. I was trying couple of times to unlock bootloader without loosing camera but it didn't work out with any method.
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)
For some reason I can't post when I use the model number listed in the title and the Canada variant model name. Says the post is "flagged". So that's why I'm not using the model numbers.
Hi. So last week I got a new V20....and I bricked it...within 3 hours. I'm hoping someone can help me out. So, here's what happened. I'm sure this subject has been posted 1000 times, but nothing I've read is exactly like my situation.
I bought a AT&T Model. I didn't realize how complex it was to root it. Was very easy on my D855. First I made a backup of all partitions with LGUP. Which is useless, since it's, not a kdz. I tried to unlock the bootloader with Dirtysanta. I got the static. I reflashed it with the stock Canada variant kdz. It booted just fine, but had no service. Dirtysanta also resulted in static with Canada variant rom. Reflashed Canada variant again. This time using one of the LG tools I tried merging the AT&T Model modem into a kdz file, hoping it would get a cell signal again. This failed spectacularly, because LGUP said it wasn't a valid kdz. (I'm guessing kdzs are signed and LGUP verifies them? Don't know. This stuff is clearly new to me.) Anyway, at this point I tried the dirtysanta method one more time. Got stuck with a bootloop about "corrupt device" and the red triangle. Finally managed to get download mode to work again. Flashed it with stock US996 v10f. Now it's impossible to go back to Canada variant kdz, and there is still no AT&T Model kdz. So it looks like my once AT&T Model is now stuck as a US996. Which, I guess is ok with me. Mainly I just wanted to get rid of the AT&T crapware. But, of course the FM Radio doesn't work now. Also, dirtysanta also gives static with US996 rom. Most people said if you turn the screen off and back on, the static goes away. But for me, the buttons don't. Phone doesn't show up in ADB, Windows explorer or device manager. But it's fully booting, because through the static I can see the "Welcome" screen. Now, if I'm understanding this right, the FM Radio doesn't work in the US996 version because of the kernel. And boot partiton = kernel? So using LGUP with PARTITON DL, I flashed just the boot partiton from the Canada variant kdz. Got to the second "LG" screen and doesn't boot past that. So, I flashed the correct boot partition back and it once again booted. So, fianlly to what I'm asking. Is there anyway to get:
1. TWRP recovery
2. Rooted US996 rom
3. The static to go away...and go away permanently
4. FM Radio working (there was talk about custom kernel?, but haven't gotten that far since I can't get the static to stop)
5. Red triangle error to go away
Last issue isn't that big of a deal, but just wondering if anyone has a fix for this yet. Help would greatly be appreciated. Thanks.
popit12 said:
For some reason I can't post when I use the model number listed in the title and the Canada variant model name. Says the post is "flagged". So that's why I'm not using the model numbers.
Hi. So last week I got a new V20....and I bricked it...within 3 hours. I'm hoping someone can help me out. So, here's what happened. I'm sure this subject has been posted 1000 times, but nothing I've read is exactly like my situation.
I bought a AT&T Model. I didn't realize how complex it was to root it. Was very easy on my D855. First I made a backup of all partitions with LGUP. Which is useless, since it's, not a kdz. I tried to unlock the bootloader with Dirtysanta. I got the static. I reflashed it with the stock Canada variant kdz. It booted just fine, but had no service. Dirtysanta also resulted in static with Canada variant rom. Reflashed Canada variant again. This time using one of the LG tools I tried merging the AT&T Model modem into a kdz file, hoping it would get a cell signal again. This failed spectacularly, because LGUP said it wasn't a valid kdz. (I'm guessing kdzs are signed and LGUP verifies them? Don't know. This stuff is clearly new to me.) Anyway, at this point I tried the dirtysanta method one more time. Got stuck with a bootloop about "corrupt device" and the red triangle. Finally managed to get download mode to work again. Flashed it with stock US996 v10f. Now it's impossible to go back to Canada variant kdz, and there is still no AT&T Model kdz. So it looks like my once AT&T Model is now stuck as a US996. Which, I guess is ok with me. Mainly I just wanted to get rid of the AT&T crapware. But, of course the FM Radio doesn't work now. Also, dirtysanta also gives static with US996 rom. Most people said if you turn the screen off and back on, the static goes away. But for me, the buttons don't. Phone doesn't show up in ADB, Windows explorer or device manager. But it's fully booting, because through the static I can see the "Welcome" screen. Now, if I'm understanding this right, the FM Radio doesn't work in the US996 version because of the kernel. And boot partiton = kernel? So using LGUP with PARTITON DL, I flashed just the boot partiton from the Canada variant kdz. Got to the second "LG" screen and doesn't boot past that. So, I flashed the correct boot partition back and it once again booted. So, fianlly to what I'm asking. Is there anyway to get:
1. TWRP recovery
2. Rooted US996 rom
3. The static to go away...and go away permanently
4. FM Radio working (there was talk about custom kernel?, but haven't gotten that far since I can't get the static to stop)
5. Red triangle error to go away
Last issue isn't that big of a deal, but just wondering if anyone has a fix for this yet. Help would greatly be appreciated. Thanks.
Click to expand...
Click to collapse
Static after engineering boot is fine. It boots up after a minute of wait on static screen. Also that triangle mark screen is fine too, wait for a minute which u didn't.
You should have followed brian's guide to root an H910.....
[ROOT] HOWTO: AT&T H910 up to v10v (FULLY TESTED)
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Even I was able to root using this method on my Puerto Rican v20 H910PR
Thank you. I finally realized what I was doing wrong. I was skipping the step on installing H915 kdz FIRST. Guess it helps to actually follow all the instructions! Anyway, I got it working. I was even able to completely get rid of static boot with MegaRom & the mk2000 kernel. FM Radio works, too!
My friend has an odd phone. I believe it to be an XT1680 - the latin american model.
Prior to this issue it showed in the device info as a moto g4.
We suspect maybe it had a tech or service rom flashed to it at *some point*
The IMEI listed could not get him an unlock code. The IMEI on the sim tray however did.
He tried to unlock the bootloader and in the process wiped the phone. So now he's stuck with a locked bootloader and no OS on his phone.
How do we salvage this?
We've tried reflashing several different firmwares, but with no luck. The motorola rescue tool does not recognize his phone.
English is his second language (He speaks it fantastically well!) so I told him I'd post this to get him started.
Thanks guys, I want to see this phone function again!
XT-1680 is a G5 Plus so device info showing G4 is odd. Unlocking wipes data not the system partition. Also you don't need an unlocked bootloader to flash firmware files. Fastboot might show some error. Is it booting into fastboot? Try flashing the latest firmware. What firmware was it on before trying to unlock.
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?