ok. i have a BLU life X8. ive bee'n able to root it, but not unlock the bootloader. the problem, is that under developer options in settings, theres a non working "oem unlocking" switch. i press it, a dialog box says "are you sure" i tap "enable" and the box disappears, and then the little switch moves from the on position back to the off position immediately. does anyone know of a fix for this? ive restored firmware, and still nothing. i am able to run root commands, if that will help. is there a way to flip this bit with an adb command or HEX editing? maybe some nvram mod? im well versed, please point me in the right direction
edit for more info:
mt6592 DUAL SIM(i think this is the problem honestly)
android 5.1
Related
Hi.
Before my question I'll write about my experience because I am sure it will help many many people.
As many of you, I always ROOT my smartphones.
Nowadays, the new phones, they come with this new technology to avoid root and other things called " OEM Lock " under the Developer's Options.
Following every step provided in the root guide for you phone, the new step to enable OEM Unlock under Developer Options
is a must!
The only thing that they don't say is that you MUST leave OEM Unlock ALWAYS ENABLED during and AFTER the root, and not only during the root
process.
Not knowing that, what did I do? Right After rooting my Samsung Note 5 I disabled the OEM Unlock. When I restarted the smartphone, it got into something called FAP Protection Black Screen where you are not able to leave not even if you try to root the phone again with the img file!
If you get in the FAP Protection Screen, like I did, despair will take over, I promise! And Google will not help you!
Is there a solution?
I found one, but not in any Google Page.
You need to download the firware img file for your phone, exactly same model,
in my case it was SM-N920G (Samsung Note 5), and for your specific country. Luckily for my phone it was not so hard to find, just hard to download (1,7GB with average 15 kB/s speed!). You will find different versions, some related to a Phone Company Operator that your country has, other related to no operator at all (sure I chose that).
After you get the firware file, just use Odin with that file to flash the phone, just like how you did to root the phone, but now, instead of using the root img file with Odin Software, you'll use the firmware file. That will not only solve the problem and give you access to your phone again, but in my case the Operator Flag disappeared and the data and apps installed miraculously were intact! I was pretty sure I was supposed to lose everything, but that didn't happen!
I'm sure what I wrote above will help many desperate people out there!
Now, my main question here:
You can never disable OEM Unlock in your life, with a rooted phone, period! So, it's really dangerous to leave the developer options enabled, allowing anyone that uses the phone to change it, even if by accident. In my case, as another example, besides rooting my phone, I rooted my father's phone too (because it was previously mine). I'd like to avoid by any means that by any chance me, or my father, disable to the OEM Unlock.
So, my question:
If I disable the Developer Option in order to "hide" it, will the changes that I did inside it remain working perfectly? I'm afraid that if I disable the developer options, somehow, it might take every option inside it back to the "default", just like it was before I enabled the developer Options, meaning in this case, OEM Unlock would get DISABLED again!
Is it safe to disable the Developer Options when OEM Unlock is Enable and MUST Remain like that?
Thank you.
Lost a night of sleep for the same problem with a Samsung S8.
This should be added to *every* mod guide.
In my case was worse too...if you root the phone and wipe data, when you open first time developer option you'll find "OEM Unlock" disabled (but I assume it's enabled at bootloader level). So when I check / uncheck it I doom my phone to lock on next restart...
how to get to boot menu on htc u12 plus, smallest width setting got adjusted wrong in developer options and power got cycled, all I can see on lock screen are 1,2 and 3 cant unlock, any ideas?
Hi, hello everyone. i'm new here.
This is the first time i post something and it's because i don't find any solution to my problem.
I have a BQ U lite with android 7.1.1, security patch august 2017, stock recovery, locked bootloader, and can't acces to development options to enable usb debugging or oem unlock.
The thing is that a friend bought this mobile phone and when he turned on it was blocked by the FRP google lock. He doesn't have any document of the buying procces or anything like that. I've been trying to do everymethod i know to unlock this. The first method i used of the one that uses quick shortcut maker right after i got into google chrome navigator. That method goes like this:
-Install Google Account Manager acording to your android version (mine is 7.1.1)
-Install and open QuickShortcutMaker
-Search Google Account Manager section
-press the option where should be the "enter email and password" text
I can't because there is only written "Error"
After that i tryed the test dpc method which ended in a message saying that it was blocked and that i couldnt change the user or something like that.
I thought about using ADB methods like the one envolving commands like "fastboot oem unlock" but i can't because my device is TOTALLY locked and idk what to do with it.
I tryed to downgrade android or the google account manager to earlier versions but i just can't do anything.
I would like to know if i should throw this mobile phone by the window or if there is any hope for me. Thanks for the help and i hope this post is not eliminated.
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Kenvarus said:
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Click to expand...
Click to collapse
how did you unlock bootloader and did you ever figure out how to root it? going through same thing now.
Kind of an old thread and old device now, but I own one myself (branded Packard Bell) and just figured this all out, so here goes:
Root
This one is really easy now thanks to a MediaTek flaw. Just go to https://github.com/JunioJsv/mtk-easy-su, download the latest release, install the APK on the device, and run it by opening the app and pressing the button in the lower-right corner (still works on this since the latest security patch level AFAIK is from 2017). Note that this gives root temporarily, so you will need to run it again after reboot if you want root again.
Bootloader Unlock
When Kenvarus said "easiest bootloader on the planet", I took a guess at the method and it worked:
Back up any important data on your tablet, as this will factory reset it.
Install ADB and Fastboot on your computer if they are not installed, including drivers. For Fastboot (as that can be tricky sometimes), it "just worked" for me and I think Windows used an Amazon driver I had installed for my KF2. YMMV.
If you haven't already, enable Development Settings by going to Settings->About tablet and tapping the build number 7 times.
Go to Settings->Developer options (switch them on if they're off) and enable the "OEM unlocking" toggle.
In the same menu, enable "USB debugging" if it is not enabled already.
Connect the tablet to your computer, confirming the authorization prompt that pops up if it wasn't connected before. Check whether the connection is good with the "adb devices" command if needed.
Run the command "adb reboot bootloader", this gave me a blank screen.
Use the "fastboot devices" command to make sure the Fastboot connection works.
Run the command "fastboot oem unlock".
Press Volume Up when the text-mode confirmation screen pops up on the tablet.
Once the unlock procedure is complete, reset the tablet. You should see text on your bootscreen saying "Orange State" and a factory reset on the first reboot if it worked.
WARNING: I highly recommend charging your battery to be at least 10-20% filled before doing this. I stupidly did this at 1% battery thinking "it's plugged in anyway" and had quite the time rebooting after unlocking the bootloader (I thought it was bricked for a good hour or so, only after walking away for 20 minutes to eat dinner did I see that the battery was now at 20% and I could boot the tablet).
After unlocking the bootloader and temp-rooting it with the above app, I was able to use Magisk to patch the boot image (using dd to shuttle the files to and from /dev/block/mmcblk0p10, use "strings saved_boot_partition_name|head -n1" and check for "ANDROID!" to make sure it's the right partition) and I now have persistent root after all these years (note that Direct Install in Magisk doesn't work here). I'd definitely be interested in a custom recovery and/or ROMs for this device, but I'm not holding my breath (I'd take a crack at it if I knew better how to do it, but I have near-zero experience with ROM development and so far have only recompiled existing ROMs for a few phones).
Hello,
Let me tell you my story and perhaps someone will come up with a miracle solution for my problem.
I was trying to flash my device so: I opened developer options and enabled enabled USB debugging.
I though this was enough, but in the middle of the process I got some errors like "Preflash validation failture". So I went back and discovered that I had the fastboot locked and that in order to unlock it I should get a code from Motorola. I got the code, but when I was going to unlock it, I got another error saying that I can't unlock my flash boot since I didn't enable the check "Enable OEM Unlock" and at that moment was when I discovered I was screwed.
Someone said, that I was just a matter of downloading a Stock room, and repeat the process but I have downloaded tons of them and no luck.
At this point, I would try anything just to be able to open my phone in recovery mode because I can't do anything with it is dead,
I have read tons and tons of posts and all off them lead me to the same point, flash through fastboot repeat all the commands, but I have been there almost 100times. I'm about to get crazy.
If someone knows something, I will really appreciate it.
Hi all!
Today my Oppo Reno 5G 10x Zoom arrived. As my previous phones I would like to root my new phone too to use e.g. Titanium Backup.
I have currently installed Color OS V7.1, Android 10, Model CPH1921, Build CPH1921EX_11_C.35.
I did the following:
Enable the Developer Options on your device. To do this, go to Settings>>About Phone>>tap on the Build Number 7 times till you see a toast message “You are now a developer”.
Under the Developer Options, you need to enable the OEM Unlock option as well. To do that again head to the Settings>>Developer Options>>enable OEM Unlock.
Download and set-up the ADB and Fastboot tools on our PC.
Now, head to the Platform-tools folder and open the CMD or command prompt.
Now, in the command prompt, enter the below command and press the Enter button on your keyboard;
adb devices
You will get a pop-up on your smartphone with a message “Always allow from this computer”. You need to press OK
Type the below command to enter the bootloader mode, and press Enter;
adb reboot bootloader
After rebooting the fastboot window (this window) appears for about 1s an the phone immediatelly reboots.
So I am unable to finnish the steps from this guide.
What am I doing wrong or what is the problem causing this?
Thanks for any help in advance!
Try to see if your device supports bootloader unlock.
You'll need an app (deep testing) to apply for permission before you can unlock it.
I'm also looking for a way to unlock my bootloader... Same model cph1921. Mine unfortunately says it's a carrier phone so I can't go ahead with the unlock. I'll tinker around to change region and unlock if that be possible.
Let me know how you get along @htcdesire-hd
Hnk1 said:
Try to see if your device supports bootloader unlock.
You'll need an app (deep testing) to apply for permission before you can unlock it.
I'm also looking for a way to unlock my bootloader... Same model cph1921. Mine unfortunately says it's a carrier phone so I can't go ahead with the unlock. I'll tinker around to change region and unlock if that be possible.
Let me know how you get along @htcdesire-hd
Click to expand...
Click to collapse
Hi,
thanks for the suggestion with this app, that might be useful for me in the future!
That the Oppo Reno was not unlockable (or at least I did not find a way) was a dealbreaker for me! So I sent it back to the retailer a few days after writing the post above.
That means I am not able to test the app you suggested with the Oppo Reno 5G anymore.
Now I have a Xiaomi Poco F2 Pro 256GB and I am very happy with my device. Unlocking and rooting was even supported by the manufacturer (after 1 week mandatory waiting time) and the Hardware is also very good. So I am glad I sent back the Oppo Reno...
htcdesire-hd said:
Hi,
thanks for the suggestion with this app, that might be useful for me in the future!
That the Oppo Reno was not unlockable (or at least I did not find a way) was a dealbreaker for me! So I sent it back to the retailer a few days after writing the post above.
That means I am not able to test the app you suggested with the Oppo Reno 5G anymore.
Now I have a Xiaomi Poco F2 Pro 256GB and I am very happy with my device. Unlocking and rooting was even supported by the manufacturer (after 1 week mandatory waiting time) and the Hardware is also very good. So I am glad I sent back the Oppo Reno...
Click to expand...
Click to collapse
I hadn't have an oppo before so was unaware they are so strict with the bootloader. I ordered a OnePlus as well but still have the oppo. I'll try sometime and let you know.
For me, not having ad free experience and unable to change dpi is a deal breaker
Hnk1 said:
I hadn't have an oppo before so was unaware they are so strict with the bootloader. I ordered a OnePlus as well but still have the oppo. I'll try sometime and let you know.
For me, not having ad free experience and unable to change dpi is a deal breaker
Click to expand...
Click to collapse
Yes same for me, I also thought that Oppo is not that restricted! Ok, thanks, I will look forward to that.
Everyone has their own preferences. For me the adds in the system apps are barely annoying and I don't have any reason to change my DPI (battery performance is enough at my point of view). At most not having a 10x zoom is a little bit annoying but there are versions of my phone which have a 10x zoom instead of a macro camera.
I wonder if it would be possible to install the "update" with the modified Magisk boot.img to gain root access. Unpacking boot.img is hassle-free, but despite the "codecs" for 7zip, I can't repack the archive with the modified file. There is also the issue of bricking the oppo .. Has anyone tried something? Any other ideas?
Did anyone come to a solution for this , its such a great phone