I am on the canadian g4 stock firmware never updated , I have rooted it and installed xposed on it. I have also checked the box under developer options to allow bootloader unlocking even though it isn't unlockable yet.
I was reading through a bug report that my g4 automatically saved and it listed the bootloader as "unknown".
Also when I try "adb reboot bootloader" on pc, it just does a normal reboot same with "adb reboot fastboot"(This may be for unlocked bootloaders but I thought I would try it)
Is this because of either being rooted or having xposed installed? or did i corrupt my bootloader somehow?
EDIT: I can access stock recovery, as well as download mode and the imei thing with barcode.
Could be like the USA tmobile version that has no boot loader
Related
I've got an LG G4 H811 (tmo) that I'm trying to install CyanogenMod on. (They list it as a supported device.) I successfully rooted it (Thanks, Team Codefire!), but "adb reboot bootloader" is just restarting the phone normally, and holding power & vol+ isn't working for me either. I'm running H81110h and I checked "Enable OEM unlock" in dev options. Does tmo have the bootloader locked down completely, or am I missing something?
Did you install TWRP? Whenever I get a new G4 (I'm on my 3rd one due to bootloop issue - this one was made in September, so hopefully I don't have anymore problems) I flash rooted image, and use that to install TWRP via Flashify or similar app. Once I have TWRP, I install whatever ROM I want.
So basically, I have a Verizon note 4 with permanent root. I bought it second hand and it came with permanent root, but the problem is that I have no idea if it has an unlocked bootloader or not . It doesn't have any custom recovery on it aswell. But then it gets me to question how the heck did it get a Permanent ROOT without getting an unlocked bootloader. Oh and i also don't get shown a verizon logo when i reboot my device, only a samsung logo. And i live in South Asia btw, and can run a local
sim with 3g on it no problem as well....
Also worth mentioning is that on "About Device" in "Settings", it says SM-910F...but when i go to fastboot mode, it says SM-910V, and when i connect it to computer, it also says verizon model. Anyways, the real problem is finding out if my phone has bootloader or not. (READ BELOW ASWELL)
Any suggestions plez
PS: I tried to put a code in the dialer, something like *#*#7432XXXX*#*# (tried a lot of diff. codes in dialers aswell). PLUS, I also tried finding if i had an unlocked bootloader from adb and fast boot where u put this command in; "fastboot oem device-info" something like that, but I cant get "fastboot devices" to work (it doesn't give any result even with proper usb drivers and while in fastboot menu from phone) :crying: plez halp me....
MajorMcNugget said:
So basically, I have a Verizon note 4 with permanent root. I bought it second hand and it came with permanent root, but the problem is that I have no idea if it has an unlocked bootloader or not . It doesn't have any custom recovery on it aswell. But then it gets me to question how the heck did it get a Permanent ROOT without getting an unlocked bootloader. Oh and i also don't get shown a verizon logo when i reboot my device, only a samsung logo. And i live in South Asia btw, and can run a local
sim with 3g on it no problem as well....
Also worth mentioning is that on "About Device" in "Settings", it says SM-910F...but when i go to fastboot mode, it says SM-910V, and when i connect it to computer, it also says verizon model. Anyways, the real problem is finding out if my phone has bootloader or not. (READ BELOW ASWELL)
Any suggestions plez
PS: I tried to put a code in the dialer, something like *#*#7432XXXX*#*# (tried a lot of diff. codes in dialers aswell). PLUS, I also tried finding if i had an unlocked bootloader from adb and fast boot where u put this command in; "fastboot oem device-info" something like that, but I cant get "fastboot devices" to work (it doesn't give any result even with proper usb drivers and while in fastboot menu from phone) :crying: plez halp me....
Click to expand...
Click to collapse
Put it into download mode and see if it says, mode: Developer. If it does your bootloader is unlocked
dhplap said:
Put it into download mode and see if it says, mode: Developer. If it does your bootloader is unlocked
Click to expand...
Click to collapse
Well it doesn't say so ... sadly.
Anyways, I'm still wondering how the heck did someone install permanent root without unlocking this Verizon??? Like you have to do temporary root and then you unlock bootloader, and then you do perm root... how does one bypass that?
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
you might be able to fastboot boot path/to/recovey.img like when you were flashing twrp but im not sure if that works on locked devices try it with a factory image with the recovery extracted and if that works you can sideload the full ota in recovery.
and possibly lgs flashtool can rewrite the phone with it locked but idk if there are imgs out there or if it works with pixel 2 xl
for next time never lock your phone on a custom rom really never relock once unlocked there is no need to and it only takes away your recovery options
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
How the heck did your bootloader get locked if you didn't do it yourself?? Do you get your phone ID displayed when you type in "fastboot devices" in bootloader mode???
You probably ended up switching slots when you reflashed. You need to use Deuces flashing script. Say yes to unlocking.
Try downloading and installing skipsoft tools. It might not see your device but try. If it doesn't see it, manually select your device. Have it install USB drivers. Restart skipsoft and see if it sees your device then. I got into a situation once where in fastboot it showed something like a corrupt bootloader and my computer could not see my device. After messing with the phone with skipsoft running, skipsoft could see it when my computer couldn't.
Op3, stock recovery and official 9.0.2 rom.
Eveything elese is fine but bootloader is unlocked and when starting phone the dm-verity says that bootloader is unlocked.
I can go to fastboot and command fastboot oem lock and phone Will show that yes and no screen, but even If I select yes phone just boots and shows that bootloader is still unlocked.
I can not fine any info for this kind of problem or how to solve this. Anybody has any ideas how to get bootloader locked?
Have you tried selecting no, instead of yes?
When I tried the first CB, I had something similar where, with the new bootloader, the responses were inverse.
morphvale said:
Have you tried selecting no, instead of yes?
When I tried the first CB, I had something similar where, with the new bootloader, the responses were inverse.
Click to expand...
Click to collapse
Yes I did try that also but did not work.
But I know figured a way to do that. I used the MSM Download tool program. That flashed some very old software but did not lock the bootloader (like I think it should do?) But after that fastboot oem lock worked. Then I sideloaded newest 9.0.2 and now bootloader is locked and phone is completely stock and works fine. So no idea what was wrong, but luckily there is this MSM.
I also found out that newest windows10 has the qualcomm 9008 drivers so no need to install them separately like the instructions says.
You probably used MSM with 3.2.8 or similar. Newer ones also lock the bootloader.
Pie 9.0.2 cannot lock the bootloader. Potentially a bug.
Works fine on 5.0.8; simply downgrade, lock and install Pie again
I have a US RETAIL XT2071-3 model. I unlocked boot-loader and manual flash two Android 11 firmware.
SMITH_RETAIL_RPS31.Q1-40-17-12_subsidy-TELMXLA_regulatory-XT2071-3-MEXICO_CFC.xml.zip
SMITH_RETAIL_RPSS31.Q1-40-17-12-4_subsidy-DEFAULT_regulatory-XT2071-4-SOFTBANK_CFC.xml.zip
Both works. However I encounter a side issue which make me prefer to lock the bootloader. However, after "fastboot oem lock", phone won't boot. It says "invalid OS", it will boot up if I unlock it. Somehow the unlocked boot-loader think either firmware is not stock.
The issues I encounter. G-pay won't work. Netflix won't install from playstore. I can do a "adb install Netflix.apk" to get Netflix working, but it does not do HD. Folks who want to do this, please be aware.
You can relock it if you flash back to the original firmware line.