So, I got this phone today, its a major upgrade... I got it to replace my oh so crappy a10e. Got really lucky, only 250 bucks and its like new.
Now, the only reason I haven't rooted it is I've realized there's 2 different fastboot's... Fastbootd and the bootloader
I looked into it, fastbootd can't unlock bootloader and all that. When I boot into bootloader where I should be able to flash it... No driver I've found for this device has let my computer see the phone in bootloader/fastboot mode.
Anyone know where the heck we can get the drivers for this? I've tried the "Add Legacy Drivers" and that didn't work either
Update on this: I got the pc to recognize it in Fastboot/bootloader, Fastbootd, recovery sideload and ADB. Some fastboot oem commands work, but none of the standard oem unlock methods work
Android 10 feature
Flash boot, recovery, dtbo, vbmeta, and super in fastbootd
All other operation on bootloader
if you ever get this device rooted please let us know. I'm waiting for a root on this device before I will purchase. You may have to unlock the bootloader or get a engineer bootloader before you can root this device. I'm not sure because I do not own one yet.
---------- Post added at 06:43 PM ---------- Previous post was at 06:29 PM ----------
Have you tried King root yet?
Related
Phone wont boot to enable oem unlocking, soooo cant flash anything
gives error "(remote: oem unlocking is not allowed)"
Now is there anyway to get around my MASSIVE F%@UP
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 follow the steps and you should be ok.
cant do any of that till bootlaoder is unlocked, i cant flash anything till bootloader is unlocked..
Flashing the stock firmware using the stock recovery + adb sideload should work so far.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.6/
You can do it, I had the same problem and worked. It's not with fastboot but the panic mode tha Qualcomm developed for this kind of problems (and worse)
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
You aren't using the bootloader to write something on the soc but you are writing it directly in the Chip.
If you solve the problem please let the community know how. Thanks.
Hi guys.... Nokia 6.1 is an awesome phone... i was previously using LG v20 which i sold to my friend and got this baby being a die hard Nokia Fan from past (since Nokia 6630 till N-Series era).... Can we hope for any root for Nokia 6.1 (2018)... i need it particularly just to install Viper4Android... Thanks
You can try this:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930
And then use Magisk...
There is no TWRP for our devices, so you probably will need to extract the boot image (somehow) from your device, patch it in Magisk Manager and then flash it (maybe with fastboot command). But I'm not sure if it will work, if it is possible. I don't want to try it, I will wait if there will be someday any easier way, as it was on Nexus devices, just unlock BL with a simple fastboot command and flash everything via TWRP...
Ja_som said:
You can try this:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930
And then use Magisk...
There is no TWRP for our devices, so you probably will need to extract the boot image (somehow) from your device, patch it in Magisk Manager and then flash it (maybe with fastboot command). But I'm not sure if it will work, if it is possible. I don't want to try it, I will wait if there will be someday any easier way, as it was on Nexus devices, just unlock BL with a simple fastboot command and flash everything via TWRP...
Click to expand...
Click to collapse
BL unlock is not available for our TA-1043 Nokia 6 (2018).... maybe soon there will be a viable and easy way to unlock and root our device.... fingers crossed :fingers-crossed:
qazishehryar said:
BL unlock is not available for our TA-1043 Nokia 6 (2018).... maybe soon there will be a viable and easy way to unlock and root our device.... fingers crossed :fingers-crossed:
Click to expand...
Click to collapse
In the TA-1089 model we have an option to unlock bootloader under developer options...
veeruvims said:
In the TA-1089 model we have an option to unlock bootloader under developer options...
Click to expand...
Click to collapse
We have this option in TA-1043 as well but it is for allowing the bootloader to be unlocked by a bootloader unlock file which we can not get that easily
users of nokia 6 the make a custom twrp recovery i dont know if is same with us.. i am afraid to test it.
https://forum.xda-developers.com/nokia-6/development/recovery-twrp-3-2-1-0-nokia-6-t3762890
i am on oreo rom that mean only magisk work. i try to flash the Magisk with factory recovery but no luck
that twrp not work on my nokia 6.1.
about unlock bootloader:
if you are in android 7.1 and not updated ,there's a way ,through 9008 mode to unlock it.
if you already updated through ota, there's only paid way to unlock it till now.
I pay and I unlock it...
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
Next step is the twrp recovery but is out of my knowledge
im trying to fix my device wondering has any one ever flased a update package via sdcard and dload mode mines fail at 5 percent everytime
same here...
this might be closest we have for 7x at this point
This is only for nougat . And after reading the guide few more times, I see it is incomplete.
https://androidcure.com/unbrick-honor-7x-variants-stock-firmware/
untill we can get a "service rom" for 7x "service rom" is apparently what is needed for dload to work.
pLaTiNiO said:
same here...
Click to expand...
Click to collapse
aye bro i just fixed my honor 7x finally i paid the dc pheonix and took the risk it didnt work but what it do was write to the devic e whille frp was locked so me being a semi genuis lol i set up my fastboot to flash twrp the dc pheonix program does sometype of backdoor fastboot trick i hurried up and flashed before the program started and unplugged my device and walla it succeded i got the program for 72 hours and im not no stingy nigga pm so you can fix yours too
dcraffam said:
aye bro i just fixed my honor 7x finally i paid the dc pheonix and took the risk it didnt work but what it do was write to the devic e whille frp was locked so me being a semi genuis lol i set up my fastboot to flash twrp the dc pheonix program does sometype of backdoor fastboot trick i hurried up and flashed before the program started and unplugged my device and walla it succeded i got the program for 72 hours and im not no stingy nigga pm so you can fix yours too
Click to expand...
Click to collapse
Oh man, there should have been this kind of post a while ago. I wanted to go completely stock on emui 8 stable as I was stuck on emui 8 beta and I trusted the dload method so I locked everything up stock recovery, BL relock etc... Now, the dload fails at 5% and my phone is as good as bricked.
Can you tell me about this DC tool? How much did it cost? Even if I'm able to get rid of that frp lock, I can unlock bootloader again and flash any rom I want.
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
mrmazak said:
this might be closest we have for 7x at this point
This is only for nougat . And after reading the guide few more times, I see it is incomplete.
https://androidcure.com/unbrick-honor-7x-variants-stock-firmware/
untill we can get a "service rom" for 7x "service rom" is apparently what is needed for dload to work.
Click to expand...
Click to collapse
Hi, the guide never says "unlocked bootloader" so how does that Huawei tool installs twrp without Unlocked BL? Does it?
See, in my situation to unbrick my phone, all I need is to get that frp unlock. I can only do it by going into settings but my phone is all wiped out when I relocked the bootloader.
So, I saw your post in other thread about some command "fastboot frp-erase " "fastboot frp-unlcok unlock code" I know I don't remember the commands but my point is can we erase the frp with that command? or can we get frp unlock code from some service and unlock it? so I can simply Unlock BL by "fastboot oem unlock unlock code"?? I can get myself out of trouble by flashing any rom or twrp backup that I have. Now, my phone is as good as dead. Please reply!!
Thetpcguy said:
Oh man, there should have been this kind of post a while ago. I wanted to go completely stock on emui 8 stable as I was stuck on emui 8 beta and I trusted the dload method so I locked everything up stock recovery, BL relock etc... Now, the dload fails at 5% and my phone is as good as bricked.
Can you tell me about this DC tool? How much did it cost? Even if I'm able to get rid of that frp lock, I can unlock bootloader again and flash any rom I want.
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
Hi, the guide never says "unlocked bootloader" so how does that Huawei tool installs twrp without Unlocked BL? Does it?
See, in my situation to unbrick my phone, all I need is to get that frp unlock. I can only do it by going into settings but my phone is all wiped out when I relocked the bootloader.
So, I saw your post in other thread about some command "fastboot frp-erase " "fastboot frp-unlcok unlock code" I know I don't remember the commands but my point is can we erase the frp with that command? or can we get frp unlock code from some service and unlock it? so I can simply Unlock BL by "fastboot oem unlock unlock code"?? I can get myself out of trouble by flashing any rom or twrp backup that I have. Now, my phone is as good as dead. Please reply!!
Click to expand...
Click to collapse
The DC tool is 15euros to use for 72 hours I still have it and you can use it if you want my bootloader was unlocked and frp locked but niether of those matter because the program does some back door fastboot trick to flash......... To restore your phone or at least get a working version of TWRP I recommend you install the DC tool configure the update app in the application for your device once all the files are extracted in the application it will try to flash and it will fail then it will say backdoor open and you have to have your CMD prompt ready to flash your TWRP so all you have to do is hit enter it will flash real quick then pull the cable from your phone and boot into TWRP and fix from there
Hey everyone,
I have just purchased an oppo a52 and looking to find out if there is any root methods currently available. I have searched but unable to find any information about it.
Any help would be greatly appreciated.
Cheers
The first thing to look for is unlocking the bootloader which is not currently doable
Regarding unlocking the bootloader in the developer options menu it has an option for OEM unlock. Forgive me as I am very very basic at this type of stuff but would that have anything to do with unlocking the bootloader?
Nope that is not enough.
There should be access to bootloader first (usually through "adb reboot bootloader"), then the command for unlocking bootloader (usually "fastboot oem unlock" or "fastboot flashing unlock") should work. But none of this is available yet
Even the full ROM is not available on Oppo website yet. So nothing to develop here!
cdroge said:
Regarding unlocking the bootloader in the developer options menu it has an option for OEM unlock. Forgive me as I am very very basic at this type of stuff but would that have anything to do with unlocking the bootloader?
Click to expand...
Click to collapse
whoknowshimself said:
Even the full ROM is not available on Oppo website yet. So nothing to develop here!
Click to expand...
Click to collapse
I just spotted it on India's site: https://oppo-in.custhelp.com/app/software_update_detail/p_name/A52
I know nothing about rom development myself, but hopefully it gets some sort of custom rom support in the future
whoknowshimself said:
Nope that is not enough.
There should be access to bootloader first (usually through "adb reboot bootloader"), then the command for unlocking bootloader (usually "fastboot oem unlock" or "fastboot flashing unlock") should work. But none of this is available yet
Even the full ROM is not available on Oppo website yet. So nothing to develop here!
Click to expand...
Click to collapse
hey,
as said by Mango is it possible to root this phone now that we have the ROM?
https://support.oppo.com/in/softwar.../?productname=A52&series=A&modelMultilingual=
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
kuahnas said:
hey,
as said by Mango is it possible to root this phone now that we have the ROM?
Click to expand...
Click to collapse
We could try to unlock Bootloader via Fastboot..Then Patch the Boot.img from the Stock Rom With magisk and flash again via adb/Fastboot.
My concern...i have this Phone the First das xD
Skolotaie said:
https://support.oppo.com/in/softwar.../?productname=A52&series=A&modelMultilingual=
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
We could try to unlock Bootloader via Fastboot..Then Patch the Boot.img from the Stock Rom With magisk and flash again via adb/Fastboot.
My concern...i have this Phone the First das xD
Click to expand...
Click to collapse
I thought everyone said it's not able to be unlocked.
Although the setting is able to be changed in developer options. Has that only just been enabled due to an update?
So can we just enable the setting and run fastboot flashing unlock from fastboot. Backup before trying if someone does it.
it is not possible to unlock the bootloader.
The device is already over 6 months old, nothing else will happen.
With ColorOS11 many adjustments by Oppo disappear, it will be more like AOSP.
A first alpha of ColorOS11 went to the first 100 users last week.
Aren't these methods true?
Oppo A52 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Oppo with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
How to Root Oppo A52 Without PC & Via Magisk
Are you waiting to Root Oppo A52 CPH2061, CPH2069, PADM00, PDAM10? Follow our detailed tutorial with to guide process to gain Superuser privileges without TWRP Recovery.
www.thenextdroid.com
How to Unlock Bootloader on OPPO A52 Phone
Detailed instructions how to unlock bootloader on OPPO A52 phone with a full description
firmwarespro.com
Oppo CAN'T be UNLOCKED!
Unable to relock bootloader without receiving message that says "Your device is corru
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
I was able to relock my 7T using fastboot. If you can boot to fastboot? In linux the command was 'fastboot flashing lock'. Not sure in windows if it's the same. Worked for me. Now 'OEM unlocking' option is visible again under system / developer tools. Prior to re-locking it was grayed out, unavailable.
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
v.konvict said:
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
Click to expand...
Click to collapse
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
TBHSilentAce07 said:
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
Click to expand...
Click to collapse
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
Click to expand...
Click to collapse
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
---------- Post added at 11:17 PM ---------- Previous post was at 11:13 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
Click to expand...
Click to collapse
Being that this is Debian 9, maybe my fastboot is an old version as well. ADB and fastboot both seem to work pretty good though. No stinkin' USB driver issues like with Windows 10.
SenyorMauricio said:
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
Click to expand...
Click to collapse
xe0r said:
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
Click to expand...
Click to collapse
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
Thanks. Confirmed this works. Needed to install an older version (went with 10.0.8 global), then skipped through most of the setup minus wifi, did a system update to 10.0.12, reboot to bootloader, fastboot oem lock, and no more corruption errors.
SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
So to be clear, can a T-Mobile converted to Global be bootloader re-locked the same way without getting the corrupt phone boot refusal screen? The wife's phone refuses to lock, but haven't tried the update from OnePlus method above?
YES.